+1 maintenance report

[Michael Hudson-Doyle]

Hi all,

My +1 shift this week (good timing after the glibc migration unclogged
things a bit).

I started by scrolling about halfway down excuses and seeing what I found.

The first thing I found was radicale, which was failing its own tests but
they passed when I tried to reproduce locally so I retried. It still fails
so I assumed without any real evidence that this is going to be down to
proxy nonsense, which it was. I uploaded a simple change and got it right
on the second try and it migrated.

xorg-server: 9base was apparently still waiting for test results on ppc64el
after 20 odd days. I retried this from the autopkgtest result page, and it
migrated.

monero has some odd linker error on riscv64. I retried it and it failed
again.

pmdk ftbfs on amd64, apparently because the version of valgrind used does
not know about the clone3 syscall. There are a few valgrind commits around
glibc 2.34 which I cherry-picked and uploaded. Once this was built and
published, a retry of pmdk succeeded and it migrated.

pmemkv was in depwait due to libpmemobj-cpp failing to build with valgrind
complaints. My valgrind fixes above fixed this everywhere apart from
ppc64el, not sure what's going on there. pmemkv built on amd64 and arm64
now but is still in depwait for ppc64el.

New version of imx-code-signing-tool falls foul of -fcommon default.

kdiff3 ftbfs due to gcc-11. It's fixed upstream so I cherry-picked the
patch and uploaded it and it migrated.

golang-golang-x-net was blocked on a few packages having trouble with
proxies, which Sergio seemed to have fixed in his shift so I retried them.
In addition it was blocked by golang-github-smartystreets-assertions on
s390x which has a test that fails on s390x with Go 1.16 or newer (
https://github.com/smartystreets/assertions/issues/42) so a hint is
probably appropriate. I filed
https://code.launchpad.net/~mwhudson/britney/+git/hints-ubuntu/+merge/408185,
which got merged and then golang-golang-x-net migrated.

secsipidx was failing to build from source due to the change to Go 1.16 by
default. This is now the default in Debian sid too so I fixed this in
Debian (by adding GO111MODULE=off to rules), synced it and it migrated
without fuss.

I looked into why go was segfaulting in the snapd/ppc64el autopkgtests and
it turns out this was a grotty problem that had already been fixed
upstream: https://go-review.googlesource.com/c/go/+/328110. Impish already
had the fix but the snapd tests use my Go snap and that hadn't been updated
yet, so I updated the snap. This issue is going to get fixed in the kernel
too, so it isn't going to have the impact I feared it might.

It might not strictly count as +1 duties but I looked into a bug involving
the snapd autopkgtests https://bugs.launchpad.net/snapd/+bug/1943077 and
filed a proposed fix https://github.com/snapcore/snapd/pull/10757. This got
merged so the tests should start passing again when this hits the stable
channel.

Cheers,
mwh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20210910/195e1316/attachment.html>