+1 Maintenance report (August 25-29)

Pre-Release Discussion +1 Maintenance
1

+1 Maintenance report (August 25-29)

I started off the week using retry-autopkgtest-regressions --blocks <package> to retry the autopkgtests blocking the following packages:

  • python3-defaults
  • qemu
  • initramfs-tools
  • dh-cargo

I looked through update_excuses and found several packages that were FTBFS or failing autopkgtests, checked in Debian for similar bug reports, used import-bug-from-debian <bug #> to import them into Launchpad, then tagged them update-excuse, and ftbfs if needed.

Work-needed items

I filed bug reports for these, but didn’t get to investigating.

  • afdko FTFBS since plucky
  • indicator-sound FTBFS since plucky

Full logs

afdko (3.6.2+dfsg1-1 to 4.0.1+dfsg1-2build2): FTBFS everywhere
This seems to build fine in Debian, but already FTBFS in plucky.
I filed a bug, but did not investigate further.

indicator-sound (12.10.2+18.10.20180612-0ubuntu7 to 12.10.2+18.10.20180612-0ubuntu9): FTBFS everywhere
This is an Ubuntu-only package, and also already FTBFS in plucky.
I filed a bug, but did not investigate further.
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/2121367

parser (- to 3.5.1-2build2): FTBFS everywhere
I imported the bug from Debian, which was already fixed there.

After confirming that the package builds in questing-proposed, I sync’d it.
https://launchpad.net/ubuntu/+source/parser/3.5.1-3

fsspec (2025.3.0-1 to 2025.3.2-1): new tests try to access the internet
These tests were already skipped during the build, so I skipped them during the autopkgtest too.
https://launchpad.net/ubuntu/+source/fsspec/2025.3.2-1ubuntu1
I also filed a bug in Debian, requesting the same.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112069

mp4h (1.3.1-17 to 1.3.1-17.2): FTBFS on s390x-only
This one was carried over from plucky. The build succeeded when LTO was disabled. This package was already in lto-disabled-list for arm64 and ppc64el, so I changed it to ‘any’.
https://launchpad.net/ubuntu/+source/lto-disabled-list/67
Unfortunately, mp4h now FTBFS with GCC 15, so a follow-up upload was needed, but it should become sync-able again soon.
https://launchpad.net/ubuntu/+source/mp4h/1.3.1-17.2ubuntu1

crun (1.20-1syncable1 to 1.21-1ubuntu1): autopkgtest regression on arm64 only
This was a follow-up to the work of @bdrung and @bryce in:

I decided to skip the failing test only on arm64, and confirmed that it worked in a PPA.
https://launchpad.net/ubuntu/+source/crun/1.21-1ubuntu2

django-auditlog (3.2.0-1 to 3.2.1-1): missing build on amd64
The new version of this package was unable to build because it added a dependency on python3-pytzdata, which was removed from Ubuntu.

I confirmed that django-auditlog was able to build without this dependency, and that its autopkgtests still passed in a PPA.
https://launchpad.net/ubuntu/+source/django-auditlog/3.2.1-1ubuntu1

libxml2 transition
There were some packages that still had hardcoded dependencies on the old libxml2 package. I used reverse-depends libxml2 -a source which showed the following:

Reverse-Testsuite-Triggers
==========================
* soupsieve

Reverse-Build-Depends
=====================
* bookworm
* librdf-trine-node-literal-xml-perl
* python-ethtool
* shotwell

These had all been fixed in Debian. After confirming that the packages build in questing-proposed, I sync’d:

  • soupsieve
  • bookworm
  • librdf-trine-node-literal-xml-perl
  • python-ethtool

The package shotwell has an Ubuntu delta and cannot be sync’d, so I merged the change from Debian instead.
https://launchpad.net/ubuntu/+source/shotwell/0.32.10-1ubuntu4

reverse-depends libxml2 -a source now shows:

No reverse dependencies found

:tada:

2 Likes