[00:03] <vorlon> bryceh: "previously we'd disabled these arches in the package's dep8 tests" - where was this disabling done? history on https://autopkgtest.ubuntu.com/packages/s/symfony/jammy/armhf shows tests previously passing, and then beginning to fail, with no change in the symfony version number
[00:06] <vorlon> bryceh: "upstream lacks 32-bit hardware to reproduce" lame, we aren't running the tests on 32-bit hardware either, they're running in 32-bit containers on 64-bit hardware
[00:07] <RAOF> utkarsh2102: Oh, also: Is there already an RC bug filed against cmark-gfm in Debian?
[00:07] <utkarsh2102> RAOF: there is!
[00:07] <utkarsh2102> with a different title but the same thing
[00:07] <utkarsh2102> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003964
[00:09] <utkarsh2102> RAOF: I'll take care of the Debian side of things tomorrow as it's already late for me; 5:40 AM here, heh.
[00:09] <utkarsh2102> But that's because I promised cpaelzer that I'll have this unblocked for him this morning. :D
[00:10] <RAOF> utkarsh2102: Uuuuh. Go to bed! :)
[00:12] <vorlon> bryceh: your series tasks on LP: #1931913 may have been reversed?
[00:13] <vorlon> (they ought to all be closed now, anyway)
[00:17] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.36 => 2.664.37] (desktop-core, i386-whitelist)
[00:18] -queuebot:#ubuntu-release- New: accepted fbtftp [amd64] (jammy-proposed) [0.5-2]
[00:18] -queuebot:#ubuntu-release- New: accepted mypy-protobuf [amd64] (jammy-proposed) [3.1.0-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [arm64] (jammy-proposed) [2.1.1+dfsg-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [ppc64el] (jammy-proposed) [2.1.1+dfsg-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [s390x] (jammy-proposed) [2.1.1+dfsg-1]
[00:18] -queuebot:#ubuntu-release- New: accepted moviepy [amd64] (jammy-proposed) [1.0.3-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [armhf] (jammy-proposed) [2.1.1+dfsg-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [amd64] (jammy-proposed) [2.1.1+dfsg-1]
[00:18] -queuebot:#ubuntu-release- New: accepted openh264 [riscv64] (jammy-proposed) [2.1.1+dfsg-1]
[00:31] <utkarsh2102> vorlon, RAOF: hey, when I upload 0.29.0.gfm.2-1ubuntu.really.0.29.0.gfm.0, LP won't accept it because
[00:31] <utkarsh2102> File cmark-gfm_0.29.0.gfm.2.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents.
[00:31] <utkarsh2102> which is true because I want to roll back the version but it's using the newer orig.tar. How do I deal with this situation? :)
[00:38] <utkarsh2102> RAOF: hey, I added a new comment to LP: #1958235 and going to bed now! \o
[00:38] <utkarsh2102> thank you for your assistance. Take a look at this if you get time^ \o/
[00:45] <vorlon> utkarsh2102: 0.29.0.gfm.2~really.0.29.0.gfm.0-0ubuntu1
[02:29] <xnox> ubuntu-archive AA https://people.canonical.com/~ubuntu-archive/nbs.html looks stuck not sure who can fix it
[02:31] <xnox> from https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt i am confused how come -linux-headers-5.13.0-19/i386 is still published, or why nvidia-graphics-drivers-470 is not migrating
[03:00] <xnox> apw:  i think NBS report is stuck; and i think britney chose not to delete 5.13.0-19-generic kernel fully when migrating v5.15 src:linux
[03:01] <xnox> https://launchpad.net/ubuntu/jammy/amd64/linux-headers-5.13.0-19-generic => looks published
[03:01] <xnox> where as for example https://launchpad.net/ubuntu/jammy/amd64/linux-headers-5.15.0-16-generic was deleted
[03:01] <xnox> it feels like we need to do NBS package removal of src:linux version 5.13.0-19.19 from jammy release.
[03:02] <xnox> it feels that said phantom kernel is also what is preventing nvidia-graphics-drivers-470 from migrating
[06:25] -queuebot:#ubuntu-release- New binary: pypy3 [amd64] (jammy-proposed/universe) [7.3.7+dfsg-4] (no packageset)
[11:14] <cjwatson> xnox: The NBS report is failing with https://paste.ubuntu.com/p/j9yGtGrp7P/, if anyone would care to look
[12:19] <LocutusOfBorg> hello xnox, can we sync fakeroot maybe?
[12:19] <LocutusOfBorg> all the patches have been integrated in new upstream release, except for the "Force testsuite on riscv64" change in rules file
[12:23]  * LocutusOfBorg has merge ready
[12:24]  * LocutusOfBorg https://launchpad.net/%7Ecostamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/13213030/+listing-archive-extra
[13:04] <xnox1> LocutusOfBorg:  we do need to force testsuite on ubuntu, because we turn off testsuites by default on riscv64 but that is very bad when fakeroot breaks
[13:06] <xnox1> and maybe we need to drop the <!nocheck> annotations?
[13:07] <xnox1> or maybe we can just force sync it.
[13:16] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-settings [source] (focal-proposed) [470.57.01-0ubuntu0.20.04.3]
[13:16] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-settings [source] (impish-proposed) [470.57.01-0ubuntu3.1~0.21.10.1]
[13:18] <cpaelzer> bdmurray: thank you for rejecting my wrong approach to attack the xen build issues
[13:19] <cpaelzer> bdmurray: the (now hopefully better) case is https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1958389 now hoping for some support by people with access to the builders and/or doko for the involved binutils
[13:20] <xnox1> apw:  https://people.canonical.com/~ubuntu-archive/NBS/ all of the 5.13 things in jammy release can be removed that are listed there. Looking into why NBS report doesn't who them.
[13:21] <xnox1> however nvidia-graphics-drivers-470 did migrate
[13:22] -queuebot:#ubuntu-release- Unapproved: rejected xf86-video-armsoc-endlessm [source] (focal-proposed) [1.4.1-0ubuntu8~20.04]
[13:26] <xnox> sil2100:  could you please add easy hint "pycuda nvidia-cuda-toolkit" ? they need to migrate together, but they are not tried to migrate together.
[13:49] <apw> xnox, linux-aws is at that version?  its not NBS
[13:49] <apw> xnox, it needs rebuilding as it depends on something which is nbs, but not itself nbs
[13:54] <xnox> apw:  i meant the generic & lowlatency 5.13 19.19 kernels. the cloud kernels are still 5.13 in jammy-release
[13:55] <xnox> apw:  where do you see aws? I don't see aws in https://people.canonical.com/~ubuntu-archive/NBS/
[13:55] <apw> linux-headers-5.13.0-1005-aws mainlibssl1.1
[13:56] <xnox> apw:  in the file listings of https://people.canonical.com/~ubuntu-archive/NBS/ the filenames that are zero in size have no reverse deps.
[13:56] <xnox> and can be removed.
[13:57] <xnox> the 1005-aws is not a file name in the NBS dir, and hence it's a real package that is not an NBS one.
[13:58] <xnox> but in addition to zero length files in that dir, the rest of 5.13.0-19 (the ones that came from src:linux) can go as well, as they simply only depend/reverse-depend from the other leaf src:linux original packages.
[13:58] <xnox> need to look into fixing the report.
[13:58] <xnox> one of these state files is tripping up nbs report.
[15:14] <LocutusOfBorg> xnox, so will you take it or can I merge?
[15:14] <LocutusOfBorg> I mean, don't we know in some minutes if fakeroot breaks? :)
[15:37] <xnox> LocutusOfBorg: yes you can merge it
[15:37] <xnox> well, on riscv64 it's more like hours, and yeah, it was pain
[15:37] <xnox> cause one couldn't built a working fakeroot
[16:01] <LocutusOfBorg> ack syncd and merged
[18:57] <bdmurray> paride: Have you verified the fix for bug 1952093?