Re: +1 maintenance report
On Fri, May 19, 2023 at 05:53:54PM +0200, Benjamin Drung wrote: > * Follow-up on Lukas Märdian +1 shift: matplotlib 3.6.3-1 was not > synced. My sync was rejected: "same version already has published > binaries in the destination archive". I did a fake sync by uploading > 3.6.3-1fakesync1 with only the version number changed. For future reference, copy-package from lp:ubuntu-archive-tools lets you resuscitate source packages with their binaries, in this case by doing: copy-package -b -s lunar-proposed --to-suite mantic-proposed -e 3.6.3-1 \ matplotlib -- 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
+1 maintenance report
Hi folks! I was on +1 maintenance this week from May 15-19. It was a shorter week due to Ascension Day on Thursday. You can find the previous +1 report from @xypron here: https://lists.ubuntu.com/archives/ubuntu-devel/2023-May/042566.html Note for the next plus +1 shift: git-annex and cryfs could be investigated further (see below). ### follow-ups ### I started by looking at the previous +1 reports and if there were things to work on: * Sponsored aespipe fix for @xypron (LP: #2019319) from last week's shift * Added tag 'update-excuse' to @xypron's bugs #2019319, #2019195, #2019079, #2019219, #2018702, #2018713 * Follow-up on Lukas Märdian +1 shift: matplotlib 3.6.3-1 was not synced. My sync was rejected: "same version already has published binaries in the destination archive". I did a fake sync by uploading 3.6.3-1fakesync1 with only the version number changed. ### syncs ### * Synced several packages for @enr0n (Ubuntu delta was merged in Debian): bug 2019241, bug 2019242, bug 2019243, and bug 2019245 * Sponsored sync requests from https://reports.qa.ubuntu.com/reports/sponsoring/: - docker-registry (LP: #2019532) - brewtarget (LP: #2018647) ### NBS ### https://ubuntu-archive-team.ubuntu.com/nbs.html is emtpy. Nothing to do here. ### kanboard ### kanboard fails to build due to the missing php-pimple build dependency. php-pimple was removed from the archive in LP: #1931913. We are blocking the sync until we are able to sync the PSR stack back with Debian. Since we are still waiting, I requested (in bug #1931913) to remove kanboard until then. ### mps-youtube ### mps-youtube 2.9.4-1 fails to build from source due to failing unit tests, because some dependencies are missing (at least pip; probably also python-pkg-resources, see Debian bug #832087). There are four open release critical bugs in Debian for mps-youtube. A look upstream indicates that there is more work needed to get it running (see https://github.com/mps-youtube/yewtube/issues/1143). There is an active fork named yewtube. So I requested to remove mps-youtube (LP: #2019754) ### libclamunrar ### The binary package libclamunrar11 1.0.0-2 depends on libclamav11 which requires clamav >= 1.0 to provide it. I poked the server team to sync/merge the new clamav version. They have the merge on their radar (see bug #2018063). ### flask-appbuilder ### flask-appbuilder 4.1.4+ds-3build1 fails to build from source against python3-flask-sqlalchemy 3.0.3-1. I tried to update the package to 4.3.1 (plus the upstream commits until 2023-05-16) to make it work with flask 2.2.2, but this is not enough. I filed a bug against Ubuntu and Debian (see bug #2019860) and requested to remove the package until it is made to work with flask-sqlalchemy 3.0 (LP: #2019862). ### python-ansible-pygments ### Sponsored fix for @ogayot directly in Debian: https://salsa.debian.org/python-team/packages/python-ansible-pygments/-/merge_requests/1 ### golang-github-crowdsecurity-go-cs-bouncer ### golang-github-crowdsecurity-go-cs-bouncer build depends on golang- github-crowdsecurity-crowdsec-dev (>= 1.4.2). crowdsec fails to build. This is caused by vendored sources in docker.io. I found https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1946376 for it and added golang-github-crowdsecurity-go-cs-bouncer as affected as well. Lucas Kanashiro from the server team is working on splitting the docker.io library (use no vendoring) from the application (use vendoring for easier backporting). ### git-annex ### git-annex fails to build with "requires dynamic R_X86_64_PC32 reloc against 'UtilityziYesod_widgetFilezuw_closure' which may overflow at runtime". I opened bug #2019992 for it without further investigation. ### golang-github-tdewolff-parse ### Autopkgtest for golang-github-tdewolff-minify 2.12.4-1 on amd64 fails. golang-github-tdewolff-minify 2.12.4-2 fixed the failure with the new golang-github-tdewolff-parse version. I retried the test with specifying the new version. ### stress-ng ### Bug report #2019079 already described the pthread test case failure on armhf and pointed to an upstream commit that fixes it. I tested the fix in a PPA and uploaded 0.15.07-1ubuntu1. Then I noticed that I falsely assuming that the armhf test in my PPA succeeded. The pthread test case did not crash any more, but did not exit any more and it ran into the autopkgtest timeout. I found another stress-pthread upstream commit that fixes an endian issue. Adding this second patch made the autopkgtest succeed. I uploaded 0.15.07-1ubuntu2, reported the success upstream on https://github.com/ColinIanKing/stress-ng/issues/283 and submitted the changes to Debian. ### cryfs ### cryfs fails to build from source due to failing test. C++ exception with description "Error calling mlock. Errno: 12" thrown in the test body. `errno 12` says: ENOMEM 12 Cannot allocate memory. I opened bug #2019853 for it, but did not investigate further. @ogayot pointed out that kitty had a sim
Re: incoming change to task handling in livecd-rootfs in mantic
On Fri, May 19, 2023 at 11:38:22AM +0100, Iain Lane wrote:
> On Fri, May 19, 2023 at 09:05:28PM +1200, Michael Hudson-Doyle wrote:
> > After a few rounds of fixups, this change passed all tests and has now
> > migrated to release, so the next round of mantic image builds will be built
> > with it. Let me know if you see anything strange in them!
> Really nice, great work. This has been long overdue, glad it finally got
> sorted out.
> Although the backslash line was one of my favourite lines of code in the
> archive and I'll be sad to see it go. :-)
> I was reminded of
> https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921862
> When reading this thread. tl;dr is that it's not (was not at the time)
> possible to seed new packages post-release because germinate isn't being
> run for -updates in the publisher so the newly-seeded packages don't get
> Task headers. Would that be any more possible to achieve now? (For
> seeding only: *un*seeding is more gnarly, it involves knowing how to
> have -updates override release.)
The effect of this change is that we're not dependent any longer on the
Task: headers in the archive, so I *think* both addition and removal of
packages from the seeds will now be honored.
However, we're currently invoking germinate with "-d $SUITE" and I think we
need to change this to "-d ${SUITE},${SUITE}-updates" (with an added
${SUITE}-proposed when building with PROPOSED=1) to get germinate to look at
all the right pockets.
--
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
Re: incoming change to task handling in livecd-rootfs in mantic
On Fri, May 19, 2023 at 09:05:28PM +1200, Michael Hudson-Doyle wrote: > After a few rounds of fixups, this change passed all tests and has now > migrated to release, so the next round of mantic image builds will be built > with it. Let me know if you see anything strange in them! Really nice, great work. This has been long overdue, glad it finally got sorted out. Although the backslash line was one of my favourite lines of code in the archive and I'll be sad to see it go. :-) I was reminded of https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921862 When reading this thread. tl;dr is that it's not (was not at the time) possible to seed new packages post-release because germinate isn't being run for -updates in the publisher so the newly-seeded packages don't get Task headers. Would that be any more possible to achieve now? (For seeding only: *un*seeding is more gnarly, it involves knowing how to have -updates override release.) Cheers! -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] 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
Re: incoming change to task handling in livecd-rootfs in mantic
On Mon, 15 May 2023, 09:47 Michael Hudson-Doyle, < michael.hud...@canonical.com> wrote: > Hi all, > > I've just uploaded a change[1] to livecd-rootfs that changes how the > "add_task" function works. > > It switches away from using the "Task" headers in the archive's package > lists to find the packages (and snaps) that make up a task to reading the > information directly from the output of germinate. > > I originally wrote this because I wanted to make an image from a rebuild > archive (which don't have Task headers) but it also makes the handling of > tasks that much more direct and hopefully a touch less confusing -- for > example, changes to seeds will be reflected in image builds without having > to wait for an archive publication cycle (it also removes two sequence of > six consecutive backslashes from the source, which has to be a win). > > Now this _should_ not result in any changes to the contents of images -- > I've tested a few builds before landing and it all looks fine -- but to be > sure we will hold this new version of livecd-rootfs in proposed until we > have done a bunch more test images. > Hi again, After a few rounds of fixups, this change passed all tests and has now migrated to release, so the next round of mantic image builds will be built with it. Let me know if you see anything strange in them! Cheers, mwh Cheers, > mwh > > [1] > https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/425047 > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
