Re: Potential MBF: packages failing to build twice in a row
- To: debian-devel@lists.debian.org
- Subject: Re: Potential MBF: packages failing to build twice in a row
- From: Simon McVittie <smcv@debian.org>
- Date: Sun, 6 Aug 2023 11:27:04 +0100
- Message-id: <ZM91eKj/uo0Ex5Rs@tautology.pseudorandom.co.uk>
- In-reply-to: <ZM6jBHuhflfAIk/1@durkon.wrar.name>
- References: <ZM5lc/khidcCF7wr@grub.nussbaum.fr> <[🔎] ZM52w3kTI0EVANzJ@localhost> <ZM6jBHuhflfAIk/1@durkon.wrar.name>
On Sat, 05 Aug 2023 at 21:29:08 +0200, Andrey Rakhmatullin wrote:
> I expect all Python packages that ship
> $name.egg-info and don't remove it in clean and don't exclude it via
> extend-diff-ignore (all of which is unneeded busywork even if recommended)
> to behave the same.
Python packages that *don't* ship $name.egg-info in their upstream source,
don't remove it in clean and don't exclude it via extend-diff-ignore will
also fail Lucas' test if they are 3.0 (quilt) format (or presumably will
have unintended diff instead if they are format 1.0). That's the only
reason bmap-tools_3.6-2 was on Lucas' list, for example.
smcv
Reply to: