Bug#947794: python-apt: autopkgtest fails on deprecation *warnings* to stderr
Version: 1.9.1
On Mon, Dec 30, 2019 at 09:18:50PM +0100, Paul Gevers wrote:
> Source: python-apt
> Version: 1.8.4
> Severity: serious
> Tags: sid bullseye
> User: debian-ci@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:python3-defaults
>
> Dear maintainers,
>
> With a recent upload of python3-defaults the autopkgtest of python-apt
> fails in testing when that autopkgtest is run with the binary packages
> of python3-defaults from unstable. It passes when run with only packages
> from testing. In tabular form:
> pass fail
> python3-defaults from testing 3.7.5-3
> python-apt from testing 1.8.4
> all others from testing from testing
>
> I copied some of the output at the bottom of this report. I seems your
> test fails only on deprecation *warnings* to stderr. Please, either
> disable deprecation warnings in your autopkgtest or allow output to
> stderr (the allow-stderr restriction). Autopkgtest is not the place to
> catch deprecation warnings.
>
> Currently this regression is blocking the migration of python3-defaults
> to testing [1], although we will ignore this failure for this migration.
This was fixed agos ago in 1.9.1 in experimental. Unfortunately, we're
a bit behind on schedule. I hope to get it into unstable in a month or
two, there are more pressing concerns for this package atm. I might just
allow-stderr in the meantime.
The unfortunate situation is that unstable shares the branch with
stable, and things get really messy now, because I do not really want
to maintain two branches of 1.8.y. Ugh.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: