libosmium is marked for autoremoval from testing

Sebastiaan Couwenberg sebastic at xs4all.nl
Sat Oct 1 10:31:29 UTC 2016


On 09/30/2016 06:16 PM, Sebastiaan Couwenberg wrote:
> On 09/30/2016 05:28 PM, Jochen Topf wrote:
>> On Do, Sep 29, 2016 at 04:39:09 +0000, Debian testing autoremoval watch wrote:
>>> libosmium 2.9.0-2 is marked for autoremoval from testing on 2016-11-04
>>>
>>> It is affected by these RC bugs:
>>> 838463: libosmium: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory)
>>
>> Hm. Shouldn't this be fixed in 2.9.0-2?
> 
> It is, but the testing autoremoval tooling is a bit buggy at the moment.
> 
> There was an issue with the version tracking in the BTS not being fed
> with new versions from testing which recently got fixed, but there seems
> to be another issue keeping fixed packages marked for autoremoval which
> triggered these notifications.

The bugs data in UDD still lists the bug as affecting testing, even
though the fixed version has already migrated to testing.

It looks like the bugs_gatherer script doesn't update the affected
distribution columns correctly. It relies on the BTS too using the
Debbugs Perl modules which may have been broken by recent changes in
perl (. removed from @INC or transition to 5.24). Unfortunately the UDD
development environment does not include dependencies for the bugs_gatherer.

> If the packages actually get removed from testing I'll shake the Release
> Team tree to get it fixed. But I assume they're already on it since
> several people have contacted the Release Team about this issue already.

It seems the Release Team is not responsible, but the UDD maintainers.

I've reported this issue in: https://bugs.debian.org/839385

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



More information about the Pkg-grass-devel mailing list