Guillem Jover writes ("Bug#1123583: dgit: Fails autopkgtests with dpkg >=
1.23.0"):
> With the new dpkg >= 1.23.0 release series, which contains several
> API changes to internal/private modules and backwards compatible API
> changes to public ones, several deprecations that emit warnings, and
> makes code more strict when parsing data, the autopkgtests for this
> package are failing, making it also affect dpkg's own migration.
Hi. Thanks for the report and sorry for the inconvenience.
I have investigated. There were a number of issues. I've filed three
bugs blocking this one; two against src:dpkg and one against src:dgit
(although this last one hasn't been processed by the BTS yet).
I have a fix for the src:dgit part which I expect to upload today.
dgit normally migrates quickly so that should be fixed by Monday at
the latest.
Mostly for Sean and my reference: I have triaged the remaining test
failures in sid, from a local run, as follows:
#1123652 (1.0-with-diff debian/rules permission)
defdistro-rpush
mirror-debnewgit
push-buildproductsdir
push-nextdgit
rpush-source
rpush
t2u-origs
#1123630 (Version->is_native)
gdr-makepatches7
gdr-merge-conflicts
gdr-merge
gdr-newupstream
gdr-unprocessable
t2u-email
It is of course possible that those failures might be masking further
problems.
> The dgit test suite might also be failing I guess.
The autopkgtests and the in-tree test suite are the same tests with a
different hat on.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
