+1 maintenance report (week 20)

Thu May 19 15:57:07 UTC 2022

Hi folks!

Here's my report for the week starting May 16th 2022.

I have been working on some old (100+ days) migrations and a few (TIL) 
universe merges, as we're still early in the cycle and the Debian 
auto-sync is open. Furthermore, I've had a look at the sponsorship queue 
for patches that are affecting kinetic. And we had an interesting 
discussion about an exotic "1.0.1-3willsync1" version string (read 
below: gnudatalanguage).

### pipewalker ###

pipewalker / 0.9.4-5

Couldn't reporduce failure locally in LXD container, but happens inside 
a qemu test environment (for Ubuntu and Debian).

Keep xvfb server running during test, to avoid failure in qemu 
autopkgtest by passing the "-s -noreset" argument to xvfb-run in 
debian/test/control. Migrated.

https://bugs.debian.org/1011126

### python-omegaconf ###

python-omegaconf / 2.1.0~rc1-2

This package is in very bad shape and requires an online connection for 
its build to succeed, FTBFS otherwise. IMO this is a candidate for 
future removal... I've filed a bug in Debian about it.

https://bugs.debian.org/1011139

### pysdl2 ###

pysdl2 / 0.9.9+dfsg1-2

Tagging the LP bug report "update-excuse" to make it show up in 
update_excuses and connect the dots with the upstream work that @ogayot 
has already done. Upstream seems to be interested in fixing the issue.

https://bugs.launchpad.net/ubuntu/+source/pysdl2/+bug/1973355

https://github.com/py-sdl/py-sdl2/issues/227

### isc-dhcp ###

isc-dhcp / 4.4.1-2.3ubuntu3 vs systemd

Cannot reproduce locally / in Canonistack arm64, running an armhf LXD 
container. So I retriggered the test a couple of times, as it seems to 
be flaky (i.e. dependent on the load of the armhf infrastructure on 
autopkgtest.u.c). Still doesn't pass on the infrastructure. Might needs 
some bigger investigation.

### fwupd ###

fwupd / 1.7.7-1

autopkgtest failure on arm64, due to /dev/mtd0 being present on 
autopkgtest.u.c (only for arm64). I've worked with upstream to detect 
the proper testing setup (using the "mtdram" module) and submitted a 
debdiff, increasing the test-coverage on the way. Migrated.

https://pad.lv/1973598

https://github.com/fwupd/fwupd/pull/4641

### checkinstall ###

checkinstall / 1.6.2+git20170426.d24a630-3ubuntu1

Universe merge. Dropping glibc 2.33+ fix from the Ubuntu delta, as it 
was applied in Debian. Migrated.

https://bugs.debian.org/996478

### lua-dbi ###

lua-dbi / 0.7.2-3ubuntu1

Universe merge. Keeping the existing Ubuntu delta, as it still FTBFS 
without the mysql-8.0 patch. Migrated.

### swaylock ###

swaylock / 1.6-2

Universe merge. It's a sync actually, as the Ubuntu delta is applied in 
the new upstream release. Migrated.

### aplus-fsf ###

aplus-fsf / 4.22.1-10.2

Universe merge. It's a sync actually, all of the Ubuntu delta has been 
applied in Debian. Migrated.

### ganeti-instance-debootstrap ###

ganeti-instance-debootstrap / 0.16-7ubuntu1

Universe merge. Carrying forward the Ubuntu delta. Migrated.

### python-ulmo ###

python-ulmo / 0.8.8+dfsg1

Fails on autopkgtest.u.c infrastructure, due to the proxy environment. 
Some of the tests require an online connection to download certain 
files. Upstream implemented mocking capabilities for some of those 
tests, but the tests/files/ directory, containing the mock data, is 
being removed during the DFSG repack. So we can't do much more than to 
disable some more tests that require an online connection. Migrated.

https://bugs.debian.org/1011225

### bluebird-gtk-theme ###

bluebird-gtk-theme / 1.3-3

Universe merge. Discussed with @jbicha, as one of the Debian uploaders, 
about applying the change to the Debian package and dropping the Ubuntu 
delta. The change was already accepted in the upstream project, pending 
a new release (since a few years). Sponsored into Debian, thank you 
Jeremy! Synced.

https://paste.ubuntu.com/p/thBHTMCgvt/

https://github.com/shimmerproject/Bluebird/commit/12af472e008100153429c88eff8cd3d546b017e9

https://salsa.debian.org/desktop-themes-team/bluebird-gtk-theme/-/commit/14b12202668ce87c66230aa094a802e8fb8e5382

### resolvconf ###

resolvconf / 1.91ubuntu1

Universe merge. Carrying forward the Ubuntu delta, as it was rejected 
(not needed) in Debian. Migrated.

### wmctrl ###

wmctrl / 1.07-7ubuntu1

Sponsored from the ~ubuntu-sponsors queue and forwarded to Debian. Migrated.

https://bugs.launchpad.net/debian/+source/wmctrl/+bug/1961969

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011233

### tuptime ###

tuptime / 5.1.0

Sponsored a sync from the ~ubuntu-sponsors queue, dropping the Ubuntu 
delta, which has been applied in Debian. Migrated.

https://bugs.launchpad.net/ubuntu/+source/tuptime/+bug/1973632

### opensbi ###

opensbi / 1.0-4

Sponsored a sync from the ~ubuntu-sponsors queue, dropping the Ubuntu 
delta, which has been applied in Debian. Migrated.

https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1973700

### gnudatalanguage ###

gnudatalanguage / 1.0.1-3maysync1

Sponsored a debdiff from the ~ubuntu-sponsors queue.

We had an interesting discussion about the version string of this 
upload: Initially a version of "1.0.1-3willsync1" was suggested, as the 
fix was already committed in Debian (Salsa) but not yet uploaded. We 
wanted it to sync automatically, as soon as the upload happens in Debian 
and therefore avoided an "ubuntuX" version string [0]. BUT: 
"-3willsync1" > "-3ubuntu1" or another potential, future "ubuntuX" 
version, so if we'd need to add another patch, which might not 
necessarily auto-sync, we cannot override the "willsync1" version with 
an "ubuntuX" version. That's a problem and could lead to ugly version 
strings.

We needed a version that does not contain the word "ubuntu", so it can 
be auto-synced, once the committed patch is uploaded into Debian. But at 
the same time we needed it to be bigger than the current version 
(1.0.1-3build2) and want it to be smaller than a potential, future 
"1.0.1-3ubuntu1" version. I came up with the following:

1.0.1-3build2 < 1.0.1-3maysync1 < 1.0.1-3ubuntu1 => 1.0.1-3maysync1

PS: "1.0.1-3~willsync1" might have been another option, but that's in 
conflict (i.e. smaller than) the current "-3build2" version string.

https://bugs.launchpad.net/ubuntu/+source/gnudatalanguage/+bug/1973377

### libcrypt-openssl-rsa-perl ###

libcrypt-openssl-rsa-perl / 0.32-2

Sponsored a sync from the ~ubuntu-sponsors queue, dropping the Ubuntu 
delta, which has been applied in Debian.

https://bugs.launchpad.net/ubuntu/+source/libcrypt-openssl-rsa-perl/+bug/1974135

### wget ###

wget / 1.21.3-1ubuntu1

Sponsored a merge from the ~ubuntu-sponsors queue. Carrying forward the 
Ubuntu delta.

https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1974046

### xscreensaver ###

xscreensaver / 6.02+dfsg1-2ubuntu1

Sponsored a merge from the ~ubuntu-sponsors queue that has been provided 
by the Debian maintainer. Carrying forward the Ubuntu delta.

https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1961634

Cheers,

   Lukas

[0] https://git.launchpad.net/ubuntu-archive-tools/tree/auto-sync#n566