What is the point of B-D-I in a package that has no arch:any component?

To: "debian-med@lists.debian.org" <debian-med@lists.debian.org>
Subject: What is the point of B-D-I in a package that has no arch:any component?
From: Nilesh Patra <nilesh@mailbox.org>
Date: Sun, 16 Jul 2023 12:23:44 +0530 (IST)
Message-id: <[🔎] 1858418335.117064.1689490424873@office.mailbox.org>

Hi,

There has been a recent pre-MBF mail sent[1] to -devel and I saw that is has jaligner mentioned there.
I see in d/control that it vendors only one arch:all binary package (jaligner), and it has both Build-Depends and Build-Depends-Indep, and I'm confused why that is so?

What exactly is the point of having two separate fields in an arch:all package?
(Combining these into one would likely fix the bug as well)

[1]: https://lists.debian.org/debian-devel/2023/07/msg00188.html 

Best,
Nilesh

Reply to:

Follow-Ups:
- Re: What is the point of B-D-I in a package that has no arch:any component?
  - From: Andreas Tille <andreas@an3as.eu>

Prev by Date: Re: Fwd: civetweb_1.15+dfsg-5_source.changes REJECTED
Next by Date: Re: Fwd: civetweb_1.15+dfsg-5_source.changes REJECTED
Previous by thread: Re: Fwd: civetweb_1.15+dfsg-5_source.changes REJECTED
Next by thread: Re: What is the point of B-D-I in a package that has no arch:any component?
Index(es):
- Date
- Thread