[03:00] <RAOF_tmp> vorlon:  Aaah. libfwupdplugin5 doesn't have any non-fwupd rdepends, but is explicitly seeded, which is why that SRU breaks image builds?
[03:01] <RAOF_tmp> (Why is it explicitly seeded? I would have thought fwupd would be explicitly seeded, and then the relevant libfwupdplugin would get pulled in as a dependency?)
[03:02] <RAOF_tmp> FWIW, I thought https://bugs.launchpad.net/ubuntu/+source/protobuf-c/+bug/1956617/comments/24 made it pretty clear that the protobuf-c MIR is good to go in focal and jammy.
[04:11] <amurray> RAOF_3: hey chris, could you please promote intel-microcode from -proposed to -updates for B/F/J for LP: #1984166 (as in previous security updates, I would like to release this first to -updates and wait for it to be fully phased and will then publish it to -security) - thanks
[04:15] <RAOF_3> amurray: I would love to, but those SRUs haven't been verified yet?
[04:16] <amurray> gah apologies - will update the bug report with details
[04:20] <amurray> RAOF_3: ok I've updated the bug report - please let me know if you need any other details
[04:21] <vorlon> RAOF_3: not explicitly seeded, but germinate tags all dependent packages with the Task: field when it expands the seed, and the image building machinery installs by task which means all packages in the archive with that field get installed
[04:22] <vorlon> there is discussion about not using the tasks for image builds going forward, but that doesn't help us now
[04:22] <RAOF_3> Nope, that looks good :)
[04:22] <RAOF_3> vorlon: Ah, that makes more sense.
[06:40] -queuebot:#ubuntu-release- Unapproved: libvirt (jammy-proposed/main) [8.0.0-1ubuntu7.1 => 8.0.0-1ubuntu7.2] (ubuntu-server, virt)
[08:06] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu (focal-proposed/main) [19.1.0-1 => 19.1.0-1ubuntu0.1] (desktop-core)
[08:16] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu [source] (focal-proposed) [19.1.0-1ubuntu0.1]
[08:28] <fossfreedom> Hi all. Me being a numpty here ... budgie-extras on kinetic isn't migrating. For an unknown reason to me it's a i386 regression test (??) and it is failing on a systemd crash. I am not sure how to proceed to resolve. Help please :) https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/b/budgie-extras/20220908_103557_276ee@/log.gz
[08:33] <juergh> sil2100, when you have some cycles, could you release linux-firmware in jammy -proposed?
[08:34] <RikMills> fossfreedom: I suspect that is related to the 'kernel hang around udev' that was mentioned as an ongoing issue with x86 test runners
[08:36] <RikMills> there are a couple of retries of the test pending in the queues, so hopefully that will pass on one of those
[08:36] <sil2100> juergh: sure! Let me start with that. Wanted to do a pass on the -proposed pocket anyway
[08:38] <fossfreedom> RikMills: cheers for the info. Will monitor over the next few days.
[09:05] -queuebot:#ubuntu-release- Unapproved: mmdebstrap (jammy-proposed/universe) [0.8.4-1 => 0.8.4-1ubuntu0.1] (no packageset)
[09:27] <RikMills> sil2100: could I perhaps get an ack on LP: #1989274
[09:27] <RikMills> we have done a frameworks FFe at this time for at least the last 6 releases I think
[09:35] -queuebot:#ubuntu-release- Unapproved: sudo (jammy-proposed/main) [1.9.9-1ubuntu2 => 1.9.9-1ubuntu2.1] (core, i386-whitelist)
[09:37] <juergh> sil2100, ta!
[09:45] <sil2100> RikMills: let me just finish some plumbing business and get to it!
[09:45] <RikMills> ty :)
[10:33] <ricotz>  hello :), it seeems to x86 autopkgtests are processed quite slowly? the queue doesn't look that large though
[11:17] <seb128> ricotz, https://irclogs.ubuntu.com/2022/09/09/%23ubuntu-release.html#t16:38
[11:19] <ricotz> seb128, ah, I see :( -- "amd64 autopkgtests are hindered by a regression in the base image, there's a kernel hang around udev as yet unexplained"
[11:35] <seb128> ricotz, unsure if that is reported and where though
[12:24] <sil2100> cpaelzer: hey! I have a question re: the MIR for protobuf-c for jammy. I have found an MIR bug for this source package and I see it has been approved for kinetic, but is it possible to get it promoted for jammy? Or does the package version there need some adjustments first?
[12:24] <sil2100> (https://bugs.launchpad.net/ubuntu/+source/protobuf-c/+bug/1956617)
[12:25] <sil2100> cpaelzer: asking as recently we accepted the new fwupd SRU which now depends on libprotobuf-c1, which is still in universe for jammy
[12:25] <sil2100> And this (possibly) causes all of our daily images to FTBFS
[12:29] <sil2100> RikMills: done o/
[12:30] <cpaelzer> sil2100: it was reviewed on the level of jammy and everyone agreed that jammy is fine for a promotion of libprotobuf-c1, so yes it should be ok there
[12:30] <cpaelzer> sil2100: IIRC it was even discussed for Focal, but I'm not sure about the state there without rechecking - do you need just J or J+F now?
[12:31] <cpaelzer> sil2100: yes also valid for Focal if you already look at both
[12:32] <sil2100> cpaelzer: thank you for the confirmation! :)
[12:32] <sil2100> I'll promote the one in jammy and guess the one in focal-proposed then (since I see it's a version with some MIR related fixes)
[12:32] <cpaelzer> yeah we asked to carry back some of the improvments
[12:33] <cpaelzer> +e
[12:37] <RikMills> sil2100: thanks!
[12:56] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-515 (jammy-proposed/restricted) [515.65.01-0ubuntu0.22.04.2 => 515.65.01-0ubuntu0.22.04.3] (i386-whitelist)
[12:56] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-515 (focal-proposed/restricted) [515.65.01-0ubuntu0.20.04.1 => 515.65.01-0ubuntu0.20.04.2] (i386-whitelist)
[12:56] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (focal-proposed/main) [1:0.9.0~0.20.04.7 => 1:0.9.0~0.20.04.8] (desktop-core, ubuntu-server)
[13:05] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (jammy-proposed/main) [1:0.9.6.1 => 1:0.9.6.2~0.22.04.1] (desktop-core)
[13:31] <sil2100> paride: hey! Finally reviewed/accepted the auto-upgrade-testing package o/
[13:31] <sil2100> Apologies for the wait, I got completely side-tracked last week
[13:31] -queuebot:#ubuntu-release- New: accepted auto-upgrade-testing [source] (kinetic-proposed) [0.3]
[13:33] -queuebot:#ubuntu-release- New binary: auto-upgrade-testing [amd64] (kinetic-proposed/none) [0.3] (no packageset)
[13:37] <paride> sil2100, no problem at all, thank you!
[13:46] -queuebot:#ubuntu-release- New: accepted auto-upgrade-testing [amd64] (kinetic-proposed) [0.3]
[13:54] <rs2009> hey sil2100, would be great if you could take a look at plymouth-theme-ubuntu-unity and unity-indicator-appearance in the kinetic new queue
[13:58] -queuebot:#ubuntu-release- Unapproved: systemd (jammy-proposed/main) [249.11-0ubuntu3.5 => 249.11-0ubuntu3.6] (core, i386-whitelist)
[14:03] <sil2100> rs2009: okay, checking
[14:03] <sil2100> rs2009: which one should I look at first? Since I won't have time to review both today
[14:14] <Eickmeyer[m]> sil2100: plasma-distro-release-notifier is in source NEW and FFe is bug 1989263
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted wireguard-linux-compat [source] (bionic-proposed) [1.0.20201112-1~18.04.4]
[15:17] -queuebot:#ubuntu-release- New: accepted mir [armhf] (kinetic-proposed) [2.9.0-0ubuntu1]
[15:21] -queuebot:#ubuntu-release- New: accepted rust-crdts [sync] (kinetic-proposed) [7.2.0+dfsg-1]
[15:24] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [sync] (kinetic-proposed) [3.2.0+dfsg-2]
[15:35] <bdmurray> FTR I've opened bug 1989258 and the kernel team (in separate communications) has suggested a workaround I'll try implementing today.
[15:36] <vorlon> Eickmeyer[m]: fyi CC0-1.0 is shipped in base files and you can include it by reference in debian/copyright instead of reproducing the full text (plasma-distro-release-notifier)
[15:36] <bdmurray> This is in regards to the amd64 / i386 backlog
[15:37] <vorlon> Eickmeyer[m]: wrong use of Vcs-Git in debian/control; you are pointing at an upstream repository that does not include packaging.  This should always point to a VCS branch for the package
[15:38] -queuebot:#ubuntu-release- New binary: wxwidgets3.2 [amd64] (kinetic-proposed/none) [3.2.0+dfsg-2] (no packageset)
[15:38] -queuebot:#ubuntu-release- New binary: wxwidgets3.2 [s390x] (kinetic-proposed/none) [3.2.0+dfsg-2] (no packageset)
[15:38] -queuebot:#ubuntu-release- New binary: wxwidgets3.2 [armhf] (kinetic-proposed/none) [3.2.0+dfsg-2] (no packageset)
[15:39] -queuebot:#ubuntu-release- New binary: wxwidgets3.2 [arm64] (kinetic-proposed/none) [3.2.0+dfsg-2] (no packageset)
[15:40] -queuebot:#ubuntu-release- New binary: wxwidgets3.2 [ppc64el] (kinetic-proposed/none) [3.2.0+dfsg-2] (no packageset)
[15:41] -queuebot:#ubuntu-release- Unapproved: sosreport (jammy-proposed/main) [4.3-1ubuntu2 => 4.4-1ubuntu1.22.04.1] (ubuntu-desktop, ubuntu-server)
[15:43] <vorlon> Eickmeyer[m]: it appears you're depending on update-notifier-common and relying on this to pull in python3-update-manager indirectly (update-notifier-common -> update-manager-core -> python3-update-manager); I think you should have a direct dependency here in case package relationships change in the future
[15:45] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [source] (kinetic-proposed) [20220521-0ubuntu1]
[15:46] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [amd64] (kinetic-proposed) [3.2.0+dfsg-2]
[15:46] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [armhf] (kinetic-proposed) [3.2.0+dfsg-2]
[15:46] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [s390x] (kinetic-proposed) [3.2.0+dfsg-2]
[15:46] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [arm64] (kinetic-proposed) [3.2.0+dfsg-2]
[15:46] -queuebot:#ubuntu-release- New: accepted wxwidgets3.2 [ppc64el] (kinetic-proposed) [3.2.0+dfsg-2]
[15:47] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [amd64] (kinetic-proposed/none) [20220521-0ubuntu1] (no packageset)
[15:47] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [s390x] (kinetic-proposed/none) [20220521-0ubuntu1] (no packageset)
[15:48] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [arm64] (kinetic-proposed/none) [20220521-0ubuntu1] (no packageset)
[15:48] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [ppc64el] (kinetic-proposed/none) [20220521-0ubuntu1] (no packageset)
[15:48] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [armhf] (kinetic-proposed/none) [20220521-0ubuntu1] (no packageset)
[15:58] <Eickmeyer[m]> vorlon: So, should it depend directly on python3-update-manager, is that what you're suggesting in the future?
[16:00] <vorlon> Eickmeyer[m]: yes
[16:00] <vorlon> rather than assuming that a dependency on update-notifier-common will pull in python3-update-manager
[16:01] -queuebot:#ubuntu-release- New: accepted unity-indicator-appearance [source] (kinetic-proposed) [1.2]
[16:01] -queuebot:#ubuntu-release- Unapproved: rejected systemd [source] (jammy-proposed) [249.11-0ubuntu3.6]
[16:01] <Eickmeyer[m]> vorlon: Ok, sounds good. I can make that change in another upload. I didn't realize it needed only the python3 component.
[16:02] <vorlon> Eickmeyer[m]: I'm not saying you should drop the existing dependency - I don't know if it's needed or not - but there is a python script and it should depend on the packages providing the modules it imports
[16:03] <vorlon> Eickmeyer[m]: also fyi: I: plasma-distro-release-notifier: hardening-no-bindnow [usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/distroreleasenotifier.so]
[16:03] -queuebot:#ubuntu-release- New binary: unity-indicator-appearance [amd64] (kinetic-proposed/none) [1.2] (no packageset)
[16:04] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [amd64] (kinetic-proposed) [20220521-0ubuntu1]
[16:04] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [armhf] (kinetic-proposed) [20220521-0ubuntu1]
[16:04] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [s390x] (kinetic-proposed) [20220521-0ubuntu1]
[16:04] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [arm64] (kinetic-proposed) [20220521-0ubuntu1]
[16:04] <Eickmeyer[m]> vorlon: Thanks for the clarification. And... interesting... I'll have to figure out 1) what that means, and 2) how to fix that.
[16:04] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [ppc64el] (kinetic-proposed) [20220521-0ubuntu1]
[16:04] <teward> isn't that provided by setting the hardening flags to +all in d/rules?
[16:04] <teward> coulda sworn it was
[16:04] <vorlon> should be yes
[16:05] <Eickmeyer[m]> d/rules is pretty much empty in this case.
[16:05] <teward> still sets up the environment proper.
[16:05] -queuebot:#ubuntu-release- New: accepted unity-indicator-appearance [amd64] (kinetic-proposed) [1.2]
[16:06] <vorlon> export DEB_BUILD_OPTIONS=hardening=+all
[16:06] <Eickmeyer[m]> I can add that to d/rules along with the fix to d/control in a new upload.
[16:07] -queuebot:#ubuntu-release- New binary: plasma-distro-release-notifier [riscv64] (kinetic-proposed/universe) [20220521-0ubuntu1] (no packageset)
[16:07] -queuebot:#ubuntu-release- New: accepted plasma-distro-release-notifier [riscv64] (kinetic-proposed) [20220521-0ubuntu1]
[16:09] -queuebot:#ubuntu-release- New sync: haskell-token-bucket (kinetic-proposed/primary) [0.1.0.1-12]
[16:19] <rs2009> vorlon: would be great if you could take a look at plymouth-theme-ubuntu-unity in the NEW queue for kinetic
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (jammy-proposed) [249.11-0ubuntu3.6]
[16:38] <vorlon> rs2009: yes, already have it downloaded and will get to it shortly
[17:21] <vorlon> rs2009: a bit inconsistent to state in debian/copyright that the software is distributed under GPLv2 or later, and to ship a copy of GPLv3 as LICENSE
[17:22] <vorlon> rs2009: also, you appear to have an unnecessary separate 'Files: debian/*' block in debian/copyright, given that it's the same copyright and license so is covered by the 'Files: *' block
[17:22] <rs2009> vorlon: oops, didn't realize that :facepalm: I'll update the copyright file
[17:22] <vorlon> rs2009: why do you have a Replaces: line referencing a version of plymouth that's older than any supported Ubuntu release?
[17:23] <vorlon> (it's also probably wrong, I wouldn't expect this package to ship any files that plymouth used to ship)
[17:25] <vorlon> rs2009: debian/postrm should really be split between debian/prerm and debian/postrm; the alternatives should be removed before the package contents have been removed from disk.  I guess you were following some other plymouth theme package as a reference - which one?
[17:26] <rs2009> vorlon: ah, I actually didn't package this theme (muqtxdir from the Yaru team did). Guess I'll update the packaging and make all these changes
[17:27] -queuebot:#ubuntu-release- New: accepted plymouth-theme-ubuntu-unity [source] (kinetic-proposed) [22.10]
[17:28] -queuebot:#ubuntu-release- New binary: plymouth-theme-ubuntu-unity [amd64] (kinetic-proposed/none) [22.10] (no packageset)
[17:32] <vorlon> rs2009: and in fact, lintian warns about this ;) W: plymouth-theme-ubuntu-unity: postrm-removes-alternative "update-alternatives             --remove" [postrm:17]
[17:33] -queuebot:#ubuntu-release- New: accepted plymouth-theme-ubuntu-unity [amd64] (kinetic-proposed) [22.10]
[17:59] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [sync] (kinetic-proposed) [0.1.0.1-12]
[18:02] -queuebot:#ubuntu-release- New binary: haskell-token-bucket [amd64] (kinetic-proposed/none) [0.1.0.1-12] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: haskell-token-bucket [arm64] (kinetic-proposed/none) [0.1.0.1-12] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: haskell-token-bucket [s390x] (kinetic-proposed/none) [0.1.0.1-12] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: haskell-token-bucket [ppc64el] (kinetic-proposed/none) [0.1.0.1-12] (no packageset)
[18:03] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [amd64] (kinetic-proposed) [0.1.0.1-12]
[18:04] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [ppc64el] (kinetic-proposed) [0.1.0.1-12]
[18:04] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [arm64] (kinetic-proposed) [0.1.0.1-12]
[18:04] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [s390x] (kinetic-proposed) [0.1.0.1-12]
[18:04] -queuebot:#ubuntu-release- New binary: haskell-token-bucket [armhf] (kinetic-proposed/none) [0.1.0.1-12] (no packageset)
[18:05] -queuebot:#ubuntu-release- New: accepted haskell-token-bucket [armhf] (kinetic-proposed) [0.1.0.1-12]
[18:25] -queuebot:#ubuntu-release- New source: vmware-nsx (kinetic-proposed/primary) [17.0.0+git2022091214.0253265f7-0ubuntu1]
[18:41] <rs2009> vorlon: was checking if the Ubuntu Unity tasks exist, and looks like the ^ubuntu-unity-live task doesn't exist, even though the others like ~ubuntu-unity-desktop do
[18:43] <rs2009> do I need to do anything on my side to create the task? (the live seed does exist in the repo)
[18:43] <coreycb> ubuntu-archive: hi, please can you reject vmware-nsx from the new queue in kinetic?
[18:45] -queuebot:#ubuntu-release- New: rejected vmware-nsx [source] (kinetic-proposed) [17.0.0+git2022091214.0253265f7-0ubuntu1]
[18:46] <apw> coreycb, ^
[18:47] <coreycb> thank you apw
[19:43] <vorlon> rs2009: sorry, I don't immediately see anything that explains to me why the ubuntu-unity-live task isn't appearing in the archive
[20:15] <LocutusOfBorg> vorlon, roll back ghc? WDYT?
[20:16] <vorlon> LocutusOfBorg: I don't think I knew there was a ghc to roll back?
[20:17] <vorlon> LocutusOfBorg: anyway, I did say I don't think it's worth rebuilding the world to get fix armhf performance
[20:19] <LocutusOfBorg> yep, this is why I asked to kick it out from proposed :)
[20:19] <LocutusOfBorg> I'll commit on debian git
[20:20] <LocutusOfBorg> so on next debian sync we will have the performance boost
[20:23] <LocutusOfBorg> btw ghc on armhf is not building anymore vorlon
[20:23] <vorlon> oh?
[20:23] <LocutusOfBorg> simple no change rebuild
[20:23] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/24337009
[20:23] <LocutusOfBorg> goes sigkill from linker
[20:23] <vorlon> hngh
[20:23] <LocutusOfBorg> so, this is also why I tried unregisterised builds
[20:24] <LocutusOfBorg> and they worked really nice
[22:08] <bdmurray> I've added a workaround to the amd64 autopkgtest instances now and the queue should start being processed more quickly
[22:08] <vorlon> \o/
[22:40] -queuebot:#ubuntu-release- New sync: haskell-copilot-theorem (kinetic-proposed/primary) [3.10-1]
[22:40] -queuebot:#ubuntu-release- New sync: haskell-filtrable (kinetic-proposed/primary) [0.1.6.0-1]
[22:40] -queuebot:#ubuntu-release- New sync: haskell-list (kinetic-proposed/primary) [0.6.1-1]
[22:40] -queuebot:#ubuntu-release- New sync: haskell-snap-server (kinetic-proposed/primary) [1.1.2.0-2]
[22:40] -queuebot:#ubuntu-release- New sync: haskell-rfc5051 (kinetic-proposed/primary) [0.2-1]
[23:02] -queuebot:#ubuntu-release- New binary: wireplumber [amd64] (kinetic-proposed/main) [0.4.11-4] (ubuntu-desktop)