+1 maintenance shift, July 4-8. July 4 is a national holiday in the US, so this was a short cycle.
I focused on working through the packages on the update_excuses page in reverse-age order, and either fixing or ensuring that there is a linked update-excuse bug. At the end of the rotation, there are only 6 source packages that have been stuck in -proposed for over 200 days without a new upload, and each of these packages has a linked update-excuse bug now. An additional 11 source packages have been in -proposed for between 140 and 200 days. Only one of these has an open update-excuse bug; most of these I found difficult to add any useful information on, as discussed below. gitlab-ci-multi-runner clarified the language in the linked update-excuse bug. Filed https://bugs.debian.org/1014427 about the undeclared build-deps, since it's a bug in Debian as well. Further, the package fails to build in Debian for unrelated reasons even if we fix the incompatibility with Ubuntu's docker stack (which I was not able to immediately figure out, Debian and Ubuntu currently have golang-github-docker-docker-dev from the same upstream branch) so I've removed the package from -proposed. gcc-defaults-mipsen not migrating because gcc-11-cross-mipsen isn't building, but things are in better shape than they were last time I looked at this in the jammy cycle. But cross-toolchain-base-mipsen seems to be built differently in Debian than Ubuntu, resulting in file conflicts. I've opened LP: #1980779 for tracking this. racket-mode autopkgtests failing on armhf and arm64. They are also failing on armhf in Debian testing so I would consider having us ignore this failure, but the arm64 autopkgtest failure is seen only in Ubuntu. However, I also noticed that the release version of racket-mode had autopkgtest results where no tests were run. If I ran the tests from the -proposed source package against the release version of the binary packages, the tests also failed. Hinted this package through since these test failures are not a regression. gitbrute failing to build on ppc64el with a weird error about the resulting go binary's build ID having the wrong length. Closer inspection shows that the package is build-depending on gccgo-go instead of the default golang-go for no reason that can be discerned from the changelog. Switching the package to build using golang-go fixes the build failure. Uploaded, and forwarded to Debian at https://bugs.debian.org/1014434. libbpp-phyl regresses bppsuite autopkgtests on arm64 and s390x. This is a Debian-only update with no upstream changes, so seems to a problem of a misbuilt library on these archs. Rebuilding libbpp-phyl on s390x with current gcc still shows the failure. The last working build was done two years ago; rebuilding with gcc-9 also still shows the failure. So I tried building with DEB_BUILD_OPTIONS=optimize=-lto and this fixed the test failures, so uploaded. sphde the first thing I noticed with this package is that the Debian changes all relate to fixing a build failure with newer compilers, but that the ftbfs report didn't flag that this is a package whose buildability had regressed. Had a chat with Graham about this, neither of us is clear on why it's not showing as a regression; I think this is a bug in the ftbfs report though. So then I tried to reproduce this in an arm64 VM (with an armhf container) and saw very confusing behavior because the testsuite doesn't clean up the directory after itself. Eventually succeeded in establishing some reproducibility, and uploaded the package with the necessary set of patches disabled to get this building everywhere. Filed https://bugs.debian.org/1014496 upstream. mbdyn FTBFS in Debian and Ubuntu, not in Debian testing; removed the broken package from -proposed. materialize buggy also in Debian, build-depends on a non-existent package (https://bugs.debian.org/1012320). Added to extra-removals in the sync-blacklist; possibly the first time this has been done with a binary package but it should work. aspectc++ RC-buggy in Debian, not in testing and not in the release pocket, so removed from -proposed leaving it to Debian to fix. libtickit-widget-scrollbox-perl blocked by a block-proposed bug from February (LP: #1962411) about autopkgtests having regressed, which is a condition we can't handle directly in proposed-migration. Re-triggered tests to see if they work any better now than before, since they are now passing in Debian; they passed, so the bug is now closed to let the package migrate. radare2 build-depends on freebsd-glue, which is RC-buggy in Debian. This was blacklisted in Ubuntu as a 'kfreebsd' package but I don't think that's correct, as the package exists to provide a userspace glue layer on Linux. I've un-blacklisted it, but also removed radare2 and added it to extra-removals since it won't be buildable until/unless someone fixes freebsd-glue for the current gcc. roundcube https://bugs.debian.org/1000642 was fixed in Debian, but only in experimental. Manually synced the experimental version; it's a release-candidate version but that's better than the existing version in kinetic failing to build or run with the currently-shipped php (LP: #1950326). bist was meant to be removed from jammy-proposed when removed from jammy. Corrected this oversight now! ruby-psych previously removed because it build-depends on jruby which is incompatible with ruby3.0. There's been no fixed jruby in Debian but there's been another upload of ruby-psych; remove it again and add it to extra-removals to bring back if jruby gets fixed. lomiri-app-launch build-depends on libmirclient-dev, which is still present in Debian but has been removed from Ubuntu and isn't coming back (per the Mir developers, and Canonical is upstream for Mir). lomiri-app-launch was removed from -proposed once before; removing it again. indi-sbig blocked because libsbig isn't in the release pocket. libsbig has a broken build that builds a -dev package even if the runtime library package can't be built. Uploaded the trivial fix, removed the binaries from unsupported archs, forwarded to https://bugs.debian.org/1014499. rally-openstack there was an open update-excuse bug, LP: #1907228, which no longer applies. However, the current package fails to build. It does not fail to build in Debian. I didn't investigate further so didn't bother opening a new update-excuse bug which would show nothing more than the build log output. gnunet-fuse FTBFS because uses a non-standard pthread function call which is obsolete since glibc 2.34. As per <https://nxmnpg.lemoda.net/3/pthread_mutexattr_setkind_np>, pthread_mutexattr_settype() should be used instead. There is a newer gnunet-fuse in Debian experimental but it still hasn't fixed this, so made the trivial change, uploaded, forwarded to https://bugs.debian.org/1014501. pydantic FTBFS in a non-obvious way. Not reproducible in Debian. Skipped. mlucas the binary is completely broken on ARM platforms because there's architecture-specific code that tries to check /proc/cpuinfo, but it does it wrong, resulting in a syscall of: openat(AT_FDCWD, "$HOME/.mlucas.d//proc/cpuinfo", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) There are many, many things wrong with this, but fundamentally it's wrong for the code to be using its mlucas_fopen() wrapper instead of just calling fopen(). Patched, and sent to https://bugs.debian.org/1014547. Unfortunately, after fixing the obvious bug, the arm64 build still fails with deeper test failures. tiledarray build-depends on libbtas-dev, which is nowhere in Debian or Ubuntu. Filed https://bugs.debian.org/1014548. libsass symbols file differences on ppc64el due to building with -O3. Fixed and sent to https://bugs.debian.org/1014552. sqlmodel all the tests fail at build time. This package uses pytest, so I checked whether the new upstream version of pytest from unstable would fix the build. It did not. Did not investigate further than this. golang-github-likexian-gokit previously removed from Ubuntu because it failed to build in both Debian and Ubuntu (https://bugs.debian.org/995329). It still fails to build everywhere, so removing again. mlton package has self-build-depends and was removed from the archive a while ago due to bugginess. Verified that the new version could be built with the previous version that was removed, so requested a bootstrap build from the Launchpad team and this is now built. For the moment it's amd64-only; if there's interest we could also bootstrap it on armhf from the previous Ubuntu binaries, and on other archs from the Debian binaries, but I'm not sure whether it would be worth the effort or if this would just be a maintenance burden in the future, so I've deferred that for now. gdb-avr missing build-dependency (https://bugs.debian.org/1010451). This is also a build failure in the release pocket, so I've uploaded the fix. massivethreads strange error about sched_yield symbol already being defined. Had to call in Michael Hudson-Doyle's support on this one, to find a solution that works around glibc 2.34's use of assembly in redefining pthread_yield in the system headers. Uploaded and forwarded to https://bugs.debian.org/1014566. mysql-workbench this package fails to build in Debian and Ubuntu, and also is marked in Debian as unreleasable due to upstream policies (https://bugs.debian.org/923347). Removed from -proposed and blacklisted. dpf-plugins not migrating because an Ubuntu-specific upload restricted the architecture list. Checked with Erich, who will update it to be Architecture: any again. muscle all archs aside from amd64 FTBFS. Debian has removed the binaries for these archs, letting the amd64 package migrate to testing. Removed these binaries for muscle, and its reverse-dependency theseus, to let it migrate. Also hinted theseus to let it in despite autopkgtest failures on architectures where it no longer has binaries. qwertone build-depends on obsolete versions of rust gtk packages; removed from -proposed and release. https://bugs.debian.org/1002148. dioptas build-depends on python3-pyepics, which is currently in Debian NEW. Skipped, assuming this will take care of itself this cycle. libobject-pad-slotattr-trigger-perl, libobject-pad-slotattr-lazyinit-perl, libobject-pad-slotattr-isa-perl, libobject-pad-slotattr-final-perl broken with current perl and has been removed from Debian and from release but was left behind in -proposed. Removed now. lava depends on a newer python3-bpfcc than we have; and bpfcc needs bpftool which isn't built as a separate package from the Ubuntu kernel packaging. Filed LP: #1981089 to request an update to the kernel packaging. libeconf some combination of newer glibc and/or newer gcc in Ubuntu vs Debian causes a build failure from build-time static analysis of the code getting a false positive of a format string overflow. Suppress the compiler warning, submitted to https://bugs.debian.org/1014604 node-grunt-timer build-depends on node-functional.js which FTBFS because it's missing a build-dependency on gulp, but even when adding the build-dependency, the build fails looking for gulp-jshint which is nowhere to be found. Filed https://bugs.debian.org/1014605 and removed node-functional.js which needs sourceful fixes from Debian. Leaving node-grunt-timer itself in -proposed for now. ghdl Failing to build on armhf. The current build log is misleading, the package now fails to build on all archs because the source is not compatible with llvm 14 (Debian is still at llvm 13 by default but Ubuntu has moved to llvm 14). https://bugs.debian.org/1010539 documents the armhf build failure, which Debian hasn't taken any decision on yet. Since the package also fails to build on all archs in Ubuntu due to an Ubuntu-specific incompatibility, I've left this alone for now. tpot Build-depends on scikit-learn >= 1.0, which needed merged from Debian. Force-synced scikit-learn, since it's unclear that any of the remaining delta is still needed (mostly cherry-picks from upstream). But the new scikit-learn FTBFS on multiple architectures in Debian, impacting us (but not on ppc64el, which was the cause of the previous Ubuntu delta!). Also, after updating scikit-learn, tpot still fails to build; this build failure is reproducible in Debian, so filed https://bugs.debian.org/1014618. firmware-microbit-micropython FTBFS with a segfault in the arm cross-toolchain. The segfaulting bit of the toolchain is lto1, which shouldn't be run when targetting arm given that arm is a non-LTO architecture generally. Also this didn't show up in the archive rebuild as a build failure. The only relevant difference between the archive rebuild success, and the current failure, was libstdc++-arm-none-eabi; that package is stuck in -proposed right now due to significant autopkgtest failures, basically the same lto1 crash everywhere. This turns out to be caused by a change in the packaging to include dpkg-buildflags at build time - which unfortunately pulls in the flags for the build architecture (amd64) instead of for the target architecture. Patched this to use the build flags for armhf instead, but this should probably be adjusted further. Uploaded libstdc++-arm-none-eabi, submitted upstream to https://bugs.debian.org/1014619, and successfully rebuilt firmware-microbit-micropython after this change. rockhopper Dep-wait on igv, because igv is in multiverse and rockhopper is in universe. In Debian, igv has moved to main, so I've moved it to universe in Ubuntu as well, clearing the dep-wait. I also had a look at some NBS blockers. spice-gtk: build-depends on libphodav-2.0-dev; phodav unfortunately doesn't provide an unversioned -dev package name. Attempting to do a straight replacement of the build-dep in debian/control didn't work, the package fails to build - but it also appears to fail to build without this change. Left this alone for now. libsrt1.4-gnutls: uploaded a round of no-change rebuilds for the reverse-dependencies. osmcoastline: stuck in -proposed and blocking libgdal30 transition because pandoc is out of date on armhf and s390x, and no solution seems to be forthcoming. osmcoastline has no reverse-dependencies, so removed the armhf and s390x binaries from the release pocket to let this migrate. kdb: blocking libicu70 removal because the arm64 build failed to upload. Retriggered the build. xjig: blocks removal of libnetpbm10-dev; updating the build-dep to libnetpbm11-dev is not sufficient, nor is adjusting include paths. This package builds using xmkmf and hasn't had a maintainer upload since 2013. Bug filed at https://bugs.debian.org/1014623 and package removed from kinetic. unfortunately this is insufficient to remove libnetpbm10-dev, because astrometry.net also build-depends on it and needs porting, and has substantial reverse-dependencies so we can't just remove it. Skipping this for now. python-rocksdb: blocks librocksdb6.11 removal; FTBFS in Debian and Ubuntu, reported at https://bugs.debian.org/1012074 and no reverse-dependencies, so removed from kinetic. -- 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/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
