Friday 4 June 2021

+1 maintenance report

+1 Maintenance Report
Dan Bungert, Jun-03-2021 - Jun-04-2021

This go round I tried to focus more on moving a larger set of packages forward
and depend more on upstream to help debug issues. A lot of the time was thus
transforming autopkgtest failures and generating more generic failure
scenarios.

### thin ###

I decided to start by continuing on this one, which mwhudson and sarnold had
looked at previously.
The new (failing) version adds file lib/rack/handler/thin.rb

debian? one failure in CI that still has logs and it doesn't look similar
upstream? no relevant bugs I could find
previous version? Problem since v1.8.0, v1.7.2 is fine, assume it's related
to the thin.rb above
hirsute? yes, with v1.8.0

I let this one test in the background but quite frankly forgot about it as I
investigated ...

### prometheus ###

Worked once in January, and has failing since.
https://github.com/prometheus/prometheus/issues/8403
https://github.com/prometheus/prometheus/pull/8538

Golang 1.16 related, and since fixed upstream.

Filed
https://bugs.launchpad.net/ubuntu/+source/prometheus/+bug/1930752
so that this info would be shown in the update-excuses report.

### picolibc ###

No builds had been attempted for a while.
Fails with some exciting macro expansion magic.
../../../newlib/libc/include/ssp/ssp.h:47:52: error: expected declaration specifiers or '...' before numeric constant
47 | #define __ssp_bos0(ptr) __builtin_object_size(ptr, 0)
| ^
../../../newlib/libc/include/ssp/string.h:52:7: note: in expansion of macro '__ssp_bos0'
52 | ((__ssp_bos0(dst) != (size_t)-1) ? \
| ^~~~~~~~~~
[...]

I was able to reproduce the issue as well based on upstream code and an amd64
target, so I opened an issue there:
https://github.com/picolibc/picolibc/issues/127

### golang-yaml.v2 ###

This one was listed as blocking some other packages, so I dug into them first.

### golang-github-nicksnyder-go-i18n.v2 ###

go-i18n seems to have been bit by a change in the error text in golang 1.16.

filed bug upstream:
https://github.com/nicksnyder/go-i18n/issues/259
opened:
https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776

I debated sending a MP with a fix, but there were multiple solutions to
the problem and none of them seemed to hard, so I decided to let
upstream handle it in a way they prefer.

### golang-github-prometheus-common ###

Another prometheus related package, with similar results - issue fixed
upstream, we just need to pick up the new version someday.

https://github.com/prometheus/common/issues/267
fixed in 10e1378a4a94394e5671c529b7d87833c2b70d13

Filed this to track:
https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772

### back to golang-yaml.v2 ###

Now with a belief that yaml.v2 was unrelated to the test failures on
promethus-common and i18n.v2, I came back to yaml.v2, where I could see
test failures locally that I couldn't find a record of in ubuntu/debian
autopkgtest.

That failure had to do with dh-golang copying source around, where it ran into
a conflict where it tried to copy a directory to where a symlink to said
directory already existed. A simple fix to trim the symlinks that dh-golang
wanted gone anyway improved the situation and got yaml.v2 building for me.

MP opened:
https://salsa.debian.org/go-team/packages/dh-golang/-/merge_requests/17
debbug opened:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989477
launchpad opened against golang-yaml.v2:
https://bugs.launchpad.net/ubuntu/+source/golang-yaml.v2/+bug/1930928

### nodejs vs node-d3-transition ###

LocutusOfBorg had investigated this and opened an issue upstream:
https://github.com/d3/d3-transition/issues/126

There hadn't been much movement on that, so I decided to generalize the bug a
bit and reproduce the issue with non-Ubuntu nodejs infrastructure. I wasn't
able to see an amd64 failure in that case, but could consistently see an arm64
failure on a different test. Existing upstream bug updated with this info.

-Dan

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel