I'm on +1 maintenance this week, but I'm out Wednesday/Thursday and I'm not
sure whether I'll get back to this on Friday, so sending a status report
now.
Took a first stab at a commandline tool to make it easier to open and/or
claim update-excuse bugs. There are update-excuse bugs open now for all
packages in testing > 124 days. I've raised an
[MP](https://code.launchpad.net/~vorlon/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/444677)
against ubuntu-dev-tools for it, to get early feedback.
This also means you can ignore the rest of this email unless you're
interested in the gory details, because everything I touched is checkpointed
in an update-excuse bug :)
* revisited `kgb-bot` and `libpoe-component-server-simplehttp-perl`.
Errors as inscrutable as before. Opened an [update-excuses
bug](https://bugs.launchpad.net/bugs/2023574).
* revisited `ruby-rackup`, which I had looked at before lunar release
and determined should not be fixed because it depended on new
`ruby-rack` from Debian experimental. `ruby-rack` 3.0.0-1 has since
been synced, but itself FTBFS. Turns out this was because of a change
in `ruby3.1` to pull in a new upstream version of the CGI module.
`ruby-rack` was patched for this in unstable but not experimental.
Forward-ported the patch and uploaded `ruby-rack`, which should also
unstick `ruby-rackup` once its build-dependency is available. [LP:
#2023576](https://bugs.launchpad.net/bugs/2023576)
* `wtforms-alchemy`: another one that was carried over because it was
too late in the lunar cycle to resolve. Merged
`python-sqlalchemy-utils` 0.38.2-2 from unstable. This also takes care
of `wtforms-json`. [LP:
#2013156](https://bugs.launchpad.net/bugs/2013156)
* `libprotocol-http2-perl`: revisited. Confirmed the issue in a local
environment. Opened an [update-excuses
bug](https://bugs.launchpad.net/bugs/2023586) but didn't dig further.
* `wine-development`: build regressed on arm64. Also regressed in
[Debian](https://buildd.debian.org/status/package.php?p=wine%2ddevelopment).
Package in the lunar release pocket FTBFS on *all* architectures. And
in Debian the package is marked as [not suitable for a stable
release](https://bugs.debian.org/988246). So I've removed and blacklisted
the package.
* `maven-verifier`: Had previously reported this issue to
[Debian](https://bugs.debian.org/1037064). Found that updating the version
number in the test xml is insufficient to get this to build. Leaving this
for someone more conversant with Java build systems.
* `libclamunrar`: requires a newer `clamav`, which the Server Team is
targeting for next month. Opened a task on [LP:
#2018063](https://bugs.launchpad.net/bugs/2018063) and tagged update-excuse.
* `jruby`: autopkgtest regression, but hadn't been retried since
January. Triggered a retry. Newly passes on amd64, still fails on
armhf/ppc64el/s390x. No further analysis.
* `pywebdav`: [LP: #2018702](https://bugs.launchpad.net/bugs/2018702) already
identified two necessary fixes for the failing autopkgtests but there are
other failures, reported to upstream. Not digging further.
* `ojalgo`: package using network resources at build time. Debian had a
patch already to disable network-dependent tests, but it appears it was
incomplete with respect to the current source. Uploaded a fix and forwarded
to Debian. [LP: #2023591](https://bugs.launchpad.net/bugs/2023591)
* `nvidia-graphics-drivers-418-server`: this package has been blocked in
-proposed since October 2022. However, the January upload of the package
appears to have fixed the reason for the block (failure to build with newer
kernels). I've removed the `block-proposed` tags to let it migrate.
* `r-cran-rstan`: build runs out of memory on 32-bit systems, upstream bug
reports that it works when building with boost 1.81 headers instead of boost
1.74. The boost 1.81 transition is coming this Debian cycle, not sure if it's
a good idea to move `r-cran-bh` to boost 1.81 ahead of this. Opened a Debian
bug. Debian maintainer fixed. Retried `r-cran-rstan` build against new
`r-cran-bh` but it still runs out of memory. Tracking in
[Debian](https://bugs.debian.org/1037439).
* `shaarli`: this was added to the sync blocklist on 2023-02-10 (which is
something I recognized because I was the one who blocked it, someone else
would've probably had to dig quite a bit to find this out) but unfortunately
a version had synced to lunar-proposed on 2023-01-29 that went unnoticed and
didn't get removed. Removed it now.
* `pushpin`: Shengjing filed a removal bug for the out-of-date architectures
the other week as part of his +1 maintenance shift, but there was a question
about riscv64 removal due to this not being a Debian architecture. More
information clarified that a new (transitive) build-dependency is broken
on riscv64, so this is appropriate to remove. [LP:
#2021594](https://launchpad.net/bugs/2021594)
* `libmail-dmarc-perl`: various tests fail because they require network
access. Uploaded hackish fix and forwarded to Debian.
* `rust-ahash`: autopkgtests for the new version fail in both Debian and
Ubuntu. Bug has already been reported in Debian with no response from the
maintainer. Removed from -proposed.
* `zulucrypt`: autopkgtests have regressed in Ubuntu; they aren't being
run in Debian because they require machine-level isolation. Bug filed in
Debian.
* `ruby-jekyll-remote-theme`: failing network-dependent tests at build time.
Talked with Lucas about how best to fix such things for ruby packages, he
says he will take care of it via Debian.
* `intelrdfpmath`: Ubuntu's compiler is stricter than Debian's at the moment,
and this fails to build because of using sprintf() without bounds checking.
Fixed to use snprintf(), you should never use sprintf(). However,
-Werror=format-truncation fires even with snprintf(), so disable this error
as well. Uploaded and forwarded to Debian.
* `ruby-jekyll-github-metadata`: more network-based tests. Disabled in
debian/ruby-tests.rake, uploaded, forwarded to Debian.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
