[Piuparts-devel] Piuparts cruft patch

Andreas Beckmann anbe at debian.org
Sat Mar 16 13:02:31 GMT 2019


On 2019-03-16 13:45, David Steele wrote:
>> The patch was inspired by an issue with a package (I don't remember
>> which one) that was blocked from migrating to testing because an old
>> binary was left in unstable, which has a piuparts error. The newer
>> version of that source package didn't have the binary. The patch was
>> meant to filter out the result for these outdated binaries. The fact
>> that this affects other packages was clearly not intended.

I think it's even more limited: the binary packages must still be built
on other architectures s.t. it shows up for the source package.
IIRC gcc-X (or more likely gcc-cross-X) was once responsible for this by
stopping to build a package on amd64 that was not intended for amd64,
but unfortunately got manually decrufted a few hours before I wanted to
finally look into this issue, so I didn't have something to test against.

> FYI - I intend to revert the patch.

ACK.

If some similar condition shows up in the future, please let me know
s.t. I can look into it.


Andreas



More information about the Piuparts-devel mailing list