[00:07] -queuebot:#ubuntu-release- New binary: safe-vdash [riscv64] (mantic-proposed/universe) [0.8.5-2] (no packageset)
[00:39] -queuebot:#ubuntu-release- New binary: safe-vdash [amd64] (mantic-proposed/universe) [0.8.5-2] (no packageset)
[02:09] -queuebot:#ubuntu-release- New: accepted s390-tools [s390x] (mantic-proposed) [2.28.0-0ubuntu2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [arm64] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [ppc64el] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [s390x] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [amd64] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [riscv64] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted safe-vdash [armhf] (mantic-proposed) [0.8.5-2]
[02:09] -queuebot:#ubuntu-release- New: accepted weston [amd64] (mantic-proposed) [12.0.1-1]
[02:09] -queuebot:#ubuntu-release- New: accepted weston [armhf] (mantic-proposed) [12.0.1-1]
[02:09] -queuebot:#ubuntu-release- New: accepted weston [riscv64] (mantic-proposed) [12.0.1-1]
[02:09] -queuebot:#ubuntu-release- New: accepted weston [arm64] (mantic-proposed) [12.0.1-1]
[02:09] -queuebot:#ubuntu-release- New: accepted weston [s390x] (mantic-proposed) [12.0.1-1]
[02:10] -queuebot:#ubuntu-release- New: accepted weston [ppc64el] (mantic-proposed) [12.0.1-1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [amd64] (mantic-proposed) [9.25.5-1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [armhf] (mantic-proposed) [9.25.5-1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [riscv64] (mantic-proposed) [9.25.5-1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [arm64] (mantic-proposed) [9.25.5-1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [s390x] (mantic-proposed) [9.25.5-1ubuntu1]
[02:10] -queuebot:#ubuntu-release- New: accepted kiwi [ppc64el] (mantic-proposed) [9.25.5-1ubuntu1]
[04:51] <nkshirsa> tjaalton, o/
[04:51] <nkshirsa> tjaalton, vorlon, o/ either of you around?
[07:13] <tjaalton> nkshirsa: just ask
[07:30] <nkshirsa> tjaalton, thanks.. about https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2028327/comments/3 , I don't see that autopkgtest failure in focal at least.. and other stable releases dont seem to report a failure at least yet.. unless they're still running the autopkgtests..
[07:30] -ubottu:#ubuntu-release- Launchpad bug 2028327 in sosreport (Ubuntu Bionic) "[sru] sos upstream 4.5.6" [Undecided, In Progress]
[07:31] <nkshirsa> there is an autopkgtest regression on focal for ppc64el which I am trying to understand, but lunar/jammy dont report autopkgtest regressions in https://ubuntu-archive-team.ubuntu.com/proposed-migration and bionic hasn't been pushed to proposed as yet..
[07:35] <tjaalton> ok?
[07:40] <nkshirsa> so I'm trying to understand where Andreas saw that failing test for new module loaded, was it on bionic.. or lunar, and do I assume that the reason I haven't seen any lunar autopkgtest regression reported yet is because its still running the lunar tests?
[07:41] <tjaalton> you should probably ask him
[07:41] <tjaalton> it's not getting released on a friday anyway
[07:41] <tjaalton> so I'm not able to do anythingn
[07:42] <nkshirsa> ok thanks
[09:44] <foxtrot> Howdy, just mentioning here that the ARM64 daily desktop image for mantic seems to boot to a login display with no obvious correct username/password combo. During the bootlog I see mentions of the ubuntu user not existing, like "passwd: User 'ubuntu' does not exist." I also tried the daily from 21/07/23 but it seems like that one is also broken and doesn't even show GDM.
[09:44] <foxtrot> I'm booting the images inside of the VMware fusion preview fwiw
[12:44] <tjaalton> paride: hi, there's a linux-firmware regression on amdgpu (lp:2029396, affects jammy and lunar) that needs to be reverted
[12:44] -ubottu:#ubuntu-release- Launchpad bug 2029396 in linux-firmware (Ubuntu) "20230323.gitbcdcfbcf-0ubuntu1.4 borks amdgpu" [Undecided, Confirmed] https://launchpad.net/bugs/2029396
[12:45] <tjaalton> it requires newer 6.2.1x than what we have
[12:45] <tjaalton> mantic is fine
[12:45] <tjaalton> and yes, quite silly that fw depends on kernel fixes..
[12:50] <paride> oh no
[12:55] <paride> tjaalton, well, OK. I'm adding the bug to the relevant places for the point release
[12:55] <paride> tjaalton, do you have a rough ETA for the jammy upload?
[12:55] <tjaalton> "soon"
[12:57] <tjaalton> in an hour or so I think
[12:57] <paride> tjaalton, great, and thanks for the heads-up.
[13:02] -queuebot:#ubuntu-release- Unapproved: linux-firmware (lunar-proposed/main) [20230323.gitbcdcfbcf-0ubuntu1.4 => 20230323.gitbcdcfbcf-0ubuntu1.5] (core, kernel)
[13:06] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu3.16 => 20220329.git681281e4-0ubuntu3.17] (core, kernel)
[13:06] <tjaalton> there, I'll review now
[13:21] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (lunar-proposed) [20230323.gitbcdcfbcf-0ubuntu1.5]
[13:22] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (jammy-proposed) [20220329.git681281e4-0ubuntu3.17]
[13:23] <tjaalton> paride: these are now headed to -proposed
[13:47] <paride> tjaalton, but not yet uploaded, correct?
[13:49] <tjaalton> uploaded and reviewed
[13:49] <tjaalton> as you can see from above ^
[13:49] <tjaalton> :)
[13:59] <paride> oh nice, I wasn't seeing it in unapproved because it's approved already
[14:42] <juliank> o/
[14:42] <juliank> jammy dist-upgrader tarball has bad signature
[14:43] <juliank> I fetched the tarball and signature with rsync to rule out network hickups and it remains bad
[14:43] <juliank> Seems they were created yesterday
[14:43] <juliank> This breaks 20.04->22.04 upgrades
[14:48] -queuebot:#ubuntu-release- New source: gnome-tour (mantic-proposed/primary) [44.0-0ubuntu1]
[14:50] <enr0n> juliank: hm, I just tried do-release-upgrade and do-release-upgrade --proposed from a focal container and it worked OK
[14:51] <juliank> enr0n: yes the proposed tarball is fine
[14:51] <juliank> enr0n: thanks for mentioning, I'm gonna use that for upgrading
[14:51] <enr0n> juliank: np, but the regular upgrade worked for me too, i.e. without the --proposed flag.
[14:52] <juliank> hmm
[14:54] <juliank> I think my lxd is dead
[14:54] <juliank> I'll go try on laptop #3
[14:54] <juliank> Literally working on 3 machine at once
[14:54]  * tsimonq2 hands juliank a KVM
[14:55] <juliank> enr0n: my container at my remotely sshed into laptop also works fine, huh
[14:56] <juliank> I switched terminal tab on laptop and that works fine too now
[14:56] <juliank> WEIRD
[14:57] <juliank> (running gpg --verify manually)
[15:10] -queuebot:#ubuntu-release- New source: gnome-tour (mantic-proposed/primary) [44.0-0ubuntu2]
[16:03] <vorlon> ItzSwirlz: hi, what's going on with cinnamon pulse vs pipewire (LP: #2020007)?  This issue is now almost 3 months old and there hasn't been a successful daily build of ubuntucinnamon since
[16:03] -ubottu:#ubuntu-release- Launchpad bug 2020007 in cinnamon (Ubuntu) "cinnamon-settings-daemon Recommends: pulseaudio which conflicts with pipewire" [High, Triaged] https://launchpad.net/bugs/2020007
[16:06] <vorlon> nkshirsa: for reference, https://ubuntu-archive-team.ubuntu.com/proposed-migration is the view for the devel series; you need https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html (it's also linked from https://ubuntu-archive-team.ubuntu.com/pending-sru.html)
[16:35] <tjaalton> paride: lunar was tested already, and it worked. wonder if it would cover jammy too as they ship identical blobs
[16:51] -queuebot:#ubuntu-release- Packageset: Added mate-common to i386-whitelist in mantic
[22:57] <ItzSwirlz> vorlon: sorry, i just looked at this msg now. I see in the livefs it chooses pulseaudio instead of pipewire-pulse, though the recommends for csd take either
[22:58] <ItzSwirlz> In mantic, the latest upload from 7-29, and I checked it a few mins ago and just in case I will again, the recommends is 'pulseaudio | pipewire-pulse'. Maybe its possible we can tell the builder to pick pipewire?
[22:59] <vorlon> ItzSwirlz: if this were caused by an alternative dep/recommends that takes either pipewire or pulseaudio, it shouldn't cause the build to fail with a conflict. I'll take a look, but what has changed since my analysis on that bug in May saying that cinnamon->blueman->pulseaudio-module-bluetooth needed fixing also?
[23:00] <vorlon> (the 'cinnamon' source package task that's still open)
[23:00] <ItzSwirlz> o
[23:00] <vorlon> ItzSwirlz: also, is there an email address where you want build failure notifications sent for cinnamon?
[23:00] <ItzSwirlz> yeah that might be it, but in the latest livefs build, i searched it and blueman wasn't mentioned
[23:00] <ItzSwirlz> vorlon, YES, itzswirlz2020@outlook.com
[23:00] <vorlon> thanks
[23:00] <ItzSwirlz> Please send all build failures of all ubuntucinnamon related packages to them
[23:00] <ItzSwirlz> the more my email is flooded the more ill notice it
[23:00] <ItzSwirlz> tysm
[23:00] <vorlon> yes, on error apt doesn't show the full dependency chain that lead to the conflict
[23:01] <ItzSwirlz> well ig its worth trying to see if taking out blueman will work
[23:01] <ItzSwirlz> let me check something first
[23:03] <ItzSwirlz> So in an email thread I had with myself, Fabio Fantoni and the maintainer of blueman, he suggested the solution to the bug you just linked by adding "libspa-0.2-bluetooth | pulseaudio-module-bluetooth" instead
[23:04] <ItzSwirlz> So, sorry, I thought the issue currently came down to csd, I was just about to patch it when i saw it was fine and then i logged on
[23:05] <ItzSwirlz> could we.. remove the blueman recommends in cinnamon? That might be easier
[23:05] <vorlon> you can, it's your flavor
[23:06] <ItzSwirlz> upstream doesnt even have it as a dep https://github.com/linuxmint/cinnamon/blob/master/debian/control
[23:06] <ItzSwirlz> im going to yeet the recommend then
[23:06] <ItzSwirlz> (or a recommend)
[23:12] <ItzSwirlz> version 5.8.4-1ubuntu1.1 or 5.8.4-1ubuntu2
[23:13] <vorlon> ItzSwirlz: where was this thread you mentioned?  On the Launchpad bug I see that suggestion from Fabio, but I don't see comment from the Debian blueman maintainer and I don't see a bug report open about this in Debian at https://bugs.debian.org/src:blueman
[23:13] <vorlon> 5.8.4-1ubuntu2
[23:13] <ItzSwirlz> vorlon, it was a private email, i can forward it to you
[23:13] <vorlon> did Christopher comment?
[23:14] <vorlon> it would be best if blueman did drop pulseaudio in favor of pipewire, even if that is no longer blocking for cinnamon
[23:14] <ItzSwirlz> yes
[23:15] <vorlon> note that both cinnamon and cinnamon-desktop-environment appear to Recommend: blueman, and both of these packages are pulled into ubuntucinnamonso you'll need to update both
[23:16] <vorlon> my analysis before stopped at the first revdep
[23:16] <ItzSwirlz> yeah i just hate dealing with patch fuzz
[23:18] <ItzSwirlz> uhh i did pull-lp-source and dch says the first patch i made to drop the xdg-desktop-xapp-portal but i dont see it in d/patches
[23:19] <vorlon> debian/patches is for patches against upstream source, not changes to the debian/ directory
[23:34] <ItzSwirlz> o
[23:39] <ItzSwirlz> im so stupid
[23:41] <ItzSwirlz> added the diff for cinnamon
[23:41] <ItzSwirlz> doing -de
[23:41] <ItzSwirlz> ah, it's still at 5.6.0.. i should probably requestsync that
[23:41] <ItzSwirlz> oh nvm, it's not there yet
[23:44] <ItzSwirlz> Both patches are now attached! I also have a lot of free time this next week
[23:48] -queuebot:#ubuntu-release- Unapproved: mozc (jammy-backports/main) [2.26.4220.100+dfsg-5.2 => 2.28.4715.102+dfsg-2.2~bpo22.04.1] (input-methods, ubuntu-desktop)