the things I worked on.
mariadb autopkgtests fails since DST change
===========================================
This was mentioned by tjaalton on matrix. I scheduled
migration-reference tests so that it would not block other packages,
and filed a bug in Debian:
https://bugs.debian.org/1101831
mkdocstrings and friends migration
==================================
Picking up from pushkarnk's work in the previous +1 shift, I pinged
ubuntu-archive for reviewing the NEW package mkdocs-get-deps (thanks
schopin!). I then sponsored pushkarnk's upload of mkdocstrings (LP:
#2105963) breaking the circular dependency, and retried builds and
autopkgtests until the set of nine packages migrated.
saods9 migration
================
saods9's own autopkgtests were failing since a recent sync from
Debian. I merged a change from the previous version in Ubuntu
allowing output to stderr in the tests.
mpv migration
=============
python-mpv's autopkgtests were failing since the recent merge of mpv
from Debain. I sync'd python-mpv from Debian to fix the tests.
esys-particle
=============
esys-particle was removed during the Python 3.13 transition due to
failing autopkgtests, apparently due to changes in environment
variables with Open MPI 5. I attempted to fix the autopkgtests, but
then ran into bigger problems, and filed a bug in Debian:
https://bugs.debian.org/1101992
ck build hanging on arm64
=========================
Recent builds of ck were failing on arm64 without producing a log.
This was also seen during the first plucky test rebuild (LP:
#2097833). The version that previously built successfully, was no
longer able to build. Newer versions autosync'd from Debian had the
same problem. I noticed that the Debian maintainer had already
disabled build-time tests on all architectures, except amd64, i386 and
arm64, so I simply disabled the tests on arm64 to avoid wasting
further resources.
libmaus2 migration
==================
libmaus2 no longer builds on arm64. I requested removal of the arm64
binaries of libmaus2 and its reverse-dependency biobambam2 (which were
also removed from Debian) in LP: #2106240
python-django-debug-toolbar migration
=====================================
The new version of python-django-debug-toolbar caused the autopkgtests
of django-graphiql-debug-toolbar to regress. I sync'd
django-graphiql-debug-toolbar to fix the tests.
prometheus-nextcloud-exporter migration
=======================================
prometheus-nextcloud-exporter 0.8.0-1 was failing its own autopktests
for 49 days. I sync'd 0.8.0-2 from Debian to fix the tests.
meep and meep-mpi-default migration
===================================
The recent syncs of these packages stopped building on armhf. I was
about to file a bug requesting removal of the binaries, but found that
jbicha had already filed LP: #2106128
partclone migration
===================
Debian stopped building partclone on big-endian architectures. I
filed LP: #2106325 requesting removal of the s390x binaries.
last-align migration
====================
Debian stopped building last-align on 32-bit architectures, so I
requested removal of the armhf binaries in LP: #2106331
The new version of last-align also caused a regression in nanook,
which was removed from Debian testing. I updated LP: #2103924
requesting removal of nanook.
libperl-critic-community-perl migration
=======================================
libperl-critic-community-perl causes the autopkgtests of
libperl-critic-freenode-perl, which is expected since it replaces that
package. It seemed to me that we shouldn't allow this migration until
the corresponding change is made in Lintian, so I filed LP: #2106180
with my findings.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
