Hi, Here is my +1 report from this week.
### zeal missing builds on several arches LP: #2006621 The latest Debian upload restricted the arches to where qtwebengine5 is available[1]. We need to remove zeal on those arches. The LP above is a removal request. ### openlibm FTBFS on armhf LP: #2006501 Debian already has a fix committed, but has not released for a few months now. I verified the fix works for us, and proposed uploading the fix with a `maysync` version to allow the next Debian upload to autosync. I am still looking for a sponsor for this patch. ### libvbz-hdf-plugin FTBFS LP: #2006390 This FTBFS because some symbols listed in debian/libvbz-hdf-plugin0.symbols are missing from the compiled library. This .symbols file was added in the most recent upload, and from what I can tell, these specific symbols may have been added by mistake. I discussed with the Debian maintainer and they agreed it would be better to just not have a .symbols file in this case. The fixed version has synced, and successfully built in -proposed. ### python-structlog FTBFS LP: #2006634 FTBFS due to a test that has a different outcome on python 3.11. The upstream has a larger commit for python 3.11 support, so I took the relevant change. Sent to Debian, and thanks to Simon Quiqley for sponsoring in Ubuntu. ### aseba missing builds LP: #2006617 This package went from Architecture: any, to specifying a subset which excludes s390x and ppc64el[2]. It still builds fine on these arches, so I sent a patch to Debian to re-enable. It was accepted, and the latest upload has since synced and migrated. ### mmc-utils FTBFS on ppc64el LP: #2006505 Upstream already had a patch for this, but Debian has not released a new upstream version. I provided an Ubuntu patch cherry-picking the upstream patch, and forwarded to Debian to make them aware. Thanks to Sergio (sergiodj) for sponsoring. ### minizinc FTBFS on ppc64el LP: #2006489 This FTBFS on ppc64el due to a narrowing conversion in libboost1.74-dev. There is an upstream bug/PR to fix the issue, but it has been stale for a year now. The fix should be simple, but I didn't think it made sense to upload a new boost1.74 at this stage in the cycle. ### lockdown depwait LP: #2006776 This package still depends on dh-systemd[3]. It was previously removed in Hirsute, and has not been updated since, except for the no-change rebuild NMU that caused it to sync to lunar-proposed. Upstream looks abandoned[4], so maybe we should remove and add it to the sync blacklist too? I also checked if several packages should be added to big_package, as per Brian's request[5], and I opened a PR for those changes. Thanks, Nick [1] http://launchpadlibrarian.net/617552161/zeal_1:0.6.1+git20220714+6fee23-1_1:0.6.1+git20220714+6fee23-2.diff.gz [2] https://salsa.debian.org/science-team/aseba/-/commit/d5ad0ce97c814ccac777cf5ee86eeaaf4b5a9bac [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958587 [4] https://gitlab.com/taggart/lockdown [5] https://lists.ubuntu.com/archives/ubuntu-devel/2023-February/042453.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
