This was technically my second +1 shift, but the first one was post-feature freeze last cycle which tends to be quiet. I mostly focused on items that were blocking the migration of pytest, as well as some miscellaneous FTBFS issues.
Sponsorship needed:
- sip-tester: Merge into ubuntu/devel : lp2134582 : lp:~uralt/ubuntu/+source/sip-tester : Git : Code : sip-tester package : Ubuntu
- This package was failing to build on ppc64el due to the new C standards introduced by GCC15 turning some string overflow warning into an error. Thankfully the issue was due to overzealous optimization and can be fixed by dropping the optimization level for ppc64el only, instead of lowering the C standard being used.
- Bug #2134582 “sip-tester: FTBFS on ppc64el with GCC15” : Bugs : sip-tester package : Ubuntu
- courier-unicode: https://code.launchpad.net/~uralt/ubuntu/+source/courier-unicode/+git/courier-unicode/+merge/497371
- This package was also failing to build on ppc64el but this time due to a symbols issue. There is a new version in Debian experimental with a number of symbols related changes, but syncing that would have started a transition ahead of Debian and appeared to fail to build on ppc64el for Ubuntu anyway.
- We used to carry delta for this package which fixed the aforementioned symbols problem, but it appears this delta was lost in the past cycle. My MP reintroduces the dropped delta.
- Bug #2134963 “courier-unicode: FTBFS on ppc64el” : Bugs : courier-unicode package : Ubuntu
- zict: Merge into debian/sid : lp2134546 : lp:~uralt/ubuntu/+source/zict : Git : Code : zict package : Ubuntu
- This is a trivial merge pulling in a new version of
zictwhich addresses breaking changes by the new version ofpytest. - Bug #2134546 “Merge zict 3.0.0-4 from Debian unstable for resolu...” : Bugs : zict package : Ubuntu
- This is a trivial merge pulling in a new version of
Full log:
spectral-cube: this package had regressed its autopkgtests againstjoblib/1.5.2-1due to some breaking changes in the latter and was keeping it from migrating. Upstream had already addressed the changes so I cherry-picked the fix.- Once
joblibis allowed to migrate, it will most likely need a patch to update it for the newpytestversion. I will submit an MP for this next week. - https://bugs.launchpad.net/ubuntu/+source/spectral-cube/+bug/2135015
- Once
python-throttler: this package had both regressed againstpytest/8.4(which introduced some breaking changes when dealing withasynctests) as well as being FTBFS againstpython3.14. Neither of these are addressed upstream yet so I wrote a small patch to update theasynctests as necessary.python-parameterized: this package had long had tests that have been skipped due to relying on theyieldkeyword, which had been unsupported bypytestsince version 4. As of version 8.4.0, usage ofyieldstarted being treated as an error. I removed the previously skipped tests.- I unblocked
python-trio’s migration. The new version requiredpytestto be updated which was not reflected in the test triggers. Using the proposed version of both packages was enough for tests to pass. - I also ran a full retry of all current autopkgtest regressions which fixed a couple dozen failures and removed some of the (many, many) blockers of
python3-defaults.
Thanks to @ginggs for sponsoring these changes.