[00:07] <vorlon> ok
[00:27] -queuebot:#ubuntu-release- Unapproved: yt-dlp (mantic-proposed/universe) [2023.09.24-2 => 2023.10.07-1] (no packageset) (sync)
[00:50] <vorlon> xnox: LP: #2038567 is still open on the 23.10 milestone bug list, shouldn't this be closed?
[00:50] -ubottu:#ubuntu-release- Launchpad bug 2038567 in linux (Ubuntu) "Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature" [Critical, Triaged] https://launchpad.net/bugs/2038567
[00:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Mantic Final] (20231008.1) has been added
[01:10] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-ubuntu-dock (mantic-proposed/main) [87ubuntu1 => 87ubuntu2] (ubuntu-desktop)
[01:41] <wgrant> git.launchpad.net should be stable now.
[02:14] <vorlon> SUBPROJECT=live for-project ubuntu-server cron.daily-live --live ok ok I get it
[02:15] <vorlon> I think I've managed now to manually kick off rebuilds off all the images still missing (including Lubuntu, which appears to have caught up).  had to do it manually.
[02:15] <vorlon> i.e. retriggering through the ISO tracker was not working
[02:30] <tsimonq2> vorlon: Thanks for the reviews and rebuild. :)
[02:52] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop (Legacy) amd64 [Mantic Final] (20231009) has been added
[02:59] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Mantic Final] (20231009) has been added
[03:00] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Mantic Final] (20231009) has been added
[03:08] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Mantic Final] (20231009) has been added
[03:10] -queuebot:#ubuntu-release- Builds: Edubuntu Desktop amd64 [Mantic Final] (20231009) has been added
[03:19] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Mantic Final] (20231009) has been added
[03:31] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Mantic Final] (20231009) has been added
[03:55] <vorlon> still waiting for arm64+x13s; ubuntu-server amd64 and riscv64 (because riscv64).  Otherwise that should be the complete set
[03:56] <vorlon> and I don't think I know how to post 'upgrade' test cases to the tracker, none of the obvious ways work
[03:56] <vorlon> oh, also ubuntu-server s390x
[04:12] <vorlon> xnox: ok, I see none of the kernels have migrated yet.  I had been under the impression they had.  And they all appear to be blocked by kernel-testing at the moment.  So when do we expect these to be let in?
[04:18] -queuebot:#ubuntu-release- Unapproved: yaru-theme (mantic-proposed/main) [23.10.0-0ubuntu1 => 23.10.0-0ubuntu2] (ubuntu-desktop)
[04:31] <vorlon> Eickmeyer: this cinnamon upload appears to include a change to portal handling, unrelated to the issue you describe.  And the package as uploaded is not suitable for the SRU queue.  Gonna need a signoff from ItzSwirlz here
[04:34] <Eickmeyer> vorlon: Agreed, seems to be a no-op as the portal handling isn't even used as it's not installed per the removed recommends (the Debian package has the required recommends to make it actually work), but yes. Unfortunately, I doubt we'll hear much from ItzSwirlz before morning as it's 12:34am there.
[04:35] <vorlon> well, all images are going to get a respin for the kernels when they finally land, so no time really lost
[04:35] <Eickmeyer> Yep.
[04:36] <Eickmeyer> For that I'm grateful. This lowlatency kernel is very, VERY nice. The kernel team did a very nice job!
[04:41] -queuebot:#ubuntu-release- New: accepted python-cogapp [sync] (mantic-proposed) [3.3.0-3]
[04:41] -queuebot:#ubuntu-release- New: accepted ruby-immutable-ruby [sync] (mantic-proposed) [0.1.0-2]
[04:41] <vorlon> W: libpisp source: binary-nmu-debian-revision-in-source 1.0.0-0ubuntu23.10.1
[04:41] <vorlon> go home, lintian, you're bitrotted
[04:41] <Eickmeyer> LOL
[04:42] <vorlon> xnox, juergh: you're going to have to explain to me why a new shared library is worth pushing into mantic before release with no reverse-dependencies (libpisp)
[04:42] -queuebot:#ubuntu-release- New binary: python-cogapp [amd64] (mantic-proposed/none) [3.3.0-3] (no packageset)
[04:42] -queuebot:#ubuntu-release- New binary: ruby-immutable-ruby [amd64] (mantic-proposed/none) [0.1.0-2] (no packageset)
[04:43] -queuebot:#ubuntu-release- New: accepted python-cogapp [amd64] (mantic-proposed) [3.3.0-3]
[04:44] -queuebot:#ubuntu-release- New: accepted ruby-immutable-ruby [amd64] (mantic-proposed) [0.1.0-2]
[06:59] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Mantic Final] (20231009) has been added
[06:59] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Mantic Final] (20231009) has been added
[06:59] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Mantic Final] (20231009) has been added
[08:04] -queuebot:#ubuntu-release- Unapproved: xterm (mantic-proposed/universe) [384-1ubuntu1 => 385-1ubuntu1] (i386-whitelist)
[08:05] -queuebot:#ubuntu-release- New binary: etlcpp [amd64] (mantic-proposed/universe) [20.37.2+dfsg-1] (no packageset)
[08:06] -queuebot:#ubuntu-release- Unapproved: rejected irssi [source] (mantic-proposed) [1.4.5-1ubuntu1]
[08:07] -queuebot:#ubuntu-release- Unapproved: boost1.74 (mantic-proposed/main) [1.74.0+ds1-22ubuntu1 => 1.74.0+ds1-23ubuntu1] (core, i386-whitelist)
[08:16] -queuebot:#ubuntu-release- Unapproved: accepted yt-dlp [sync] (mantic-proposed) [2023.10.07-1]
[08:24] <philroche> @release-team The Canonical Public Cloud team have currently decided not to send a representative to London for release activities but we have engineer in UK who can travel if required. Cross TZ Canonical Public Cloud team release leads are mjdonis and kajiya__
[08:36] <seb128> hey release team, any chance you could still accept the yaru-themes upload in the mantic queue? It fixes the shell UI not properly respecting the selected theme which we would like to fix for release
[08:36] <sil2100> philroche: thanks for the heads up! We'll be in touch, we also have Utkarsh here
[08:36] <seb128> and  gnome-shell-extension-ubuntu-dock if possible
[08:42] <LocutusOfBorg> boost1.74 is a build failure fix^
[08:43] <LocutusOfBorg> bdmurray, ^^ reject if you don't agree
[08:45] <LocutusOfBorg> I understand the timing is bad :(
[08:52] <LocutusOfBorg> can you please blacklist ghc sync?
[08:56] <seb128> LocutusOfBorg, what's the rational? also we are frozen for release now so nothing is going to autosync
[08:56] <seb128> sil2100, did you/release see my ask ^?
[08:56] <LocutusOfBorg> seb128, rationale is that I don't want it to be syncd for nn
[08:56] <LocutusOfBorg> :)
[08:57] <seb128> LocutusOfBorg, what you wish and what is right might be different things :p
[08:57] <seb128> LocutusOfBorg, joke aside I'm not adding things to the blocklist with an explanation of why we don't want them
[08:57] <bdmurray> LocutusOfBorg: Please reread the Final Freeze email as the body of the email changed this cycle
[08:58] <sil2100> seb128: hey! Yes, need to look into the actual changes, what's the severity of the bugs there?
[08:58] <LocutusOfBorg> seb128, the reason is: in Debian the haskell transition is really at a stuck point, and there is a chicken and egg issue that canonical is already ware
[08:58] <bdmurray> LocutusOfBorg: We could possibly do boost as an early SRU and then it could still be copied to NN
[08:59] <LocutusOfBorg> bdmurray, or just reject :)
[08:59] <LocutusOfBorg> seb128, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051493
[08:59] -ubottu:#ubuntu-release- Debian bug 1051493 in src:ghc "ghc: FTBFS with a GHC newer than 9.0.2" [Serious, Open]
[08:59] <LocutusOfBorg> this is the chicken and egg. short story, we need to implement hadrian build system for ghc, otherwise it will be a sad story
[08:59] <LocutusOfBorg> so, better blacklist ghc until this is sorted out, to avoid real painful opening
[09:00] <seb128> sil2100, the yaru one it makes the shell not respect the theme color which is quite visible. It's a target of opportunity though, we would like to see it fixes if we are going to respin but if not a SRU would be fine I guess, not having the glitch might avoid us to bad PR
[09:01] <seb128> sil2100, basically if you pick an accent color in the installer (let's say green) after installation your applications are green but the shell UI is still orange
[09:01] <seb128> so people who will try the release will notice on first login, unsure what impact that will have on mantic desktop reviews
[09:01] -queuebot:#ubuntu-release- Unapproved: rejected boost1.74 [source] (mantic-proposed) [1.74.0+ds1-23ubuntu1]
[09:02] -queuebot:#ubuntu-release- Unapproved: rejected xterm [source] (mantic-proposed) [385-1ubuntu1]
[09:02] <seb128> sil2100, the dock one is mostly avoiding stacking of deprecated API warning in the journal
[09:03] <sil2100> Okay, let me accept the yaru one then, I think the risk is relatively small and I think it won't have problems migrating, right?
[09:04] -queuebot:#ubuntu-release- Unapproved: accepted yaru-theme [source] (mantic-proposed) [23.10.0-0ubuntu2]
[09:04] <LocutusOfBorg> bdmurray, please forward it me again, I think I can't find it :/ sorry
[09:10] <bdmurray> LocutusOfBorg: Its in the archive https://lists.ubuntu.com/archives/ubuntu-devel-announce/2023-October/001340.html
[09:10] <LocutusOfBorg> I was reading ubuntu-release, this explains thanks
[09:15] <seb128> sil2100, indeed
[09:15] <seb128> sil2100, thanks
[09:23] <utkarsh2102> release weeeeek! 🎉
=== bdmurray changed the topic of #ubuntu-release to: Released: 23.04 Lunar Lobster, 22.04.2 Jammy Jellyfish | Archive: Final Freeze | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or whiskey | melius malum quod cognoscis | infinity, you will be missed
[09:28] <utkarsh2102> thank you, bdmurray!
[09:40] <juliank> apw: So I figured out why shim-signed failed, it was just that we didn't have a shim binary copy in the PPA for mantic lol (because we built it in kinetic), it should be ready for signing nowÖ: https://bugs.launchpad.net/canonical-signing-jobs/+bug/2038815
[09:41] <utkarsh2102> super stupid but where do we get a "official" list of participating flavours for this release? :)
[09:41] <apw> juliank, heh, ok ...
[09:41] <utkarsh2102> super stupid because I sent out the beta announcement and other emails so I should know :)
[09:42] <juliank> I'll leave it up to the release team whether to ship that on the image or drop it into -updates
[09:43] <juliank> (once it passed through signing)
[09:50] <utkarsh2102> juliank: thanks, super, just let us/me know here (or MM thread) once it's ready ready, please?
[11:10] <philroche> release-team Is there any further manual verification required for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038567 and mantic kernel 6.5.0-9 in -proposed before you make a decision on when/if to migrate to -release?
[11:10] -ubottu:#ubuntu-release- Launchpad bug 2038567 in lxd (Ubuntu) "Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature" [High, Triaged]
[11:12] -queuebot:#ubuntu-release- Unapproved: rust-zvariant-derive (mantic-proposed/universe) [3.14.0-2 => 3.15.0-1] (no packageset) (sync)
[11:12] -queuebot:#ubuntu-release- Unapproved: accepted rust-zvariant-derive [sync] (mantic-proposed) [3.15.0-1]
[11:15] <seb128> sil2100, I got a stack of langpack upload rejection on 'tar.xz exists but has different contents' errors, I guess you know about it but mentioning it in case still
[11:15] <utkarsh2102> philroche: many thanks, looking into it..
[11:20] <xnox> bdmurray: sil2100: utkarsh2102: all kernels for https://kernel.ubuntu.com/reports/kernel-stable-board/?cycle=d2023.10.05 are now unblocked
[11:20] <xnox> please hint/migrate them, and they likely all need to migrate together with nvidia (ndg-535 & ndg-535-server) due to LRM entaglement.
[11:21] <utkarsh2102> wooooooooooooot!
[11:21] <xnox> i would think we need to bump forceskip test hint of raspi kernel version
[11:21] <xnox> and also do lowlatency forceskiptest
[11:23] <utkarsh2102> xnox: git+ssh://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu ;)
[11:24] <xnox> hm
[11:24] <xnox> raspi was already bumped by vorlon
[11:25] <xnox> raspi just needs unblock
[11:30] <juliank> apw: will you get to the shim-signed signing job today?
[11:30] <juliank> and are you at release sprint and can teach someone there?
[11:30] <juliank> "pair signing"
[11:37] <xnox> bdmurray: utkarsh2102: https://code.launchpad.net/~xnox/britney/+git/hints-ubuntu/+merge/453132 i think that's what we need for everything to migrate
[11:38] <xnox> https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#linux-meta-lowlatency
[11:38] <xnox> due to rt test subtests known regressions
[11:38] <utkarsh2102> \o/
[11:43] <sil2100> seb128: yes, it's my bad, I didn't disable weekly builds
[11:46] <seb128> ack
[12:04] <sil2100> xnox: merged and pushed!
[12:06] <sil2100> xnox: hopefully this will also migrate the nvidia packages, right?
[12:07] <sil2100> ...looking at the update_excuses page, it should!
[12:33] <dbungert> fossfreedom_: please consider bumping ubuntu-desktop-provision.  There are some fixes I suggest merging including logfile cleanups.  We found stuff being logged unintentionally - notably wifi PSKs.  Also a fix related to codec handling.
[12:35] <fossfreedom_> dbungert: thats usually done by the bot rather than manually when that runs.
[12:37] <xnox> sil2100: all kernels migrated but riscv, as it too triggers test on all arches on which riscv kernel does not exist https://code.launchpad.net/~xnox/britney/+git/hints-ubuntu/+merge/453133
[12:37] <xnox> bdmurray: ^
[12:46] <fossfreedom_> dbungert: I kicked dependabot - it throws a test failure.  Has there been a curtin bump as well that I need to update in snapcraft.yaml ?
[12:49] <apw> juliank, i might be there, not sure yet.  i have half taught one person
[12:49] <apw> juliank, and it should be in the pipe shortly
[13:01] <dbungert> fossfreedom_: yes, bump curtin
[13:02] <dbungert> after mantic I would like feedback about this process so we can ponder how to make this smoother
[13:03] <fossfreedom_> if you are at riga happy to chat dbungert
[13:03] <dbungert> yes, I will be at riga, that would be great
[13:06] <xnox> bdmurray: sil2100: riscv people asking if we can still upload linux-firmware https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546 ? (which i guess affects all images, but will make wifi work on a riscv board)
[13:06] -ubottu:#ubuntu-release- Launchpad bug 2038546 in linux-firmware (Ubuntu Mantic) "/lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64" [High, Confirmed]
[13:06] <xnox> and other ubuntu-release team ^
[13:16] <sil2100> xnox: can someone upload it to the queue?
[13:16] <sil2100> I mean, I worry about this as it's a regression from jammy/kinetic
[13:17] <sil2100> So I'm thinking that maybe we should have this in -proposed at least
[13:18] <sil2100> xnox: how long does migration of linux-firmware take usually? How many tests are triggered, what is the build time on riscv64
[13:27] <ginggs> sil2100, xnox: I only see one Reverse-Testsuite-Triggers for linux-firmware, and that is linux-firmware-raspi which takes around 10 minutes to run
[13:27] <sil2100> I think the main blockers for this will be the riscv64 build time
[13:28] <sil2100> ginggs, xnox: would one of you be so kind and to sponsor this for mantic?
[13:28] <sil2100> xypron: ^
[13:28] <ginggs> linux-firmware takes about 1.5 hours to build on riscv64
[13:29] <ginggs> juergh: are you able to upload this?
[13:35] -queuebot:#ubuntu-release- Unapproved: rejected mono-tools [sync] (mantic-proposed) [4.2-3.2]
[13:36] -queuebot:#ubuntu-release- Unapproved: rejected accerciser [sync] (mantic-proposed) [3.42.0-1]
[13:38] <mapreri> bdmurray: I noticed that http://cdimages.ubuntu.com/releases/20.04.6/release/ contains the 20.04.5 images, instead of the .6.  Also the /20.04/ directory points to the .5 still.
[13:41] <xnox> sil2100: can you check if we can ship this one too, or not? https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2037224
[13:41] -ubottu:#ubuntu-release- Launchpad bug 2037224 in HWE Next "Multiple RTL8851BE BT stability issues" [Undecided, New]
[13:41] <xnox> cause it is staged at https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/+git/linux-firmware/+ref/mantic
[13:44] <sil2100> xnox: can we have just the riscv64 one alone?
[13:45] <xnox> ok
[13:45] <sil2100> Since I think updating binary blobs is something I'd prefer doing after release
[13:45] <xnox> cc: ^ juergh will try to apply both in git for future sru; and merge in upload that is release fix only
[13:54] -queuebot:#ubuntu-release- Unapproved: nix (mantic-proposed/universe) [2.16.1+dfsg-3 => 2.16.1+dfsg-3ubuntu1] (no packageset)
[13:55] -queuebot:#ubuntu-release- Unapproved: accepted nix [source] (mantic-proposed) [2.16.1+dfsg-3ubuntu1]
[14:00] -queuebot:#ubuntu-release- Unapproved: atop (mantic-proposed/universe) [2.9.0-1 => 2.9.0-1ubuntu1] (no packageset)
[14:01] -queuebot:#ubuntu-release- Unapproved: accepted atop [source] (mantic-proposed) [2.9.0-1ubuntu1]
[14:05] -queuebot:#ubuntu-release- Unapproved: apport (mantic-proposed/main) [2.27.0-0ubuntu4 => 2.27.0-0ubuntu5] (core, i386-whitelist)
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (mantic-proposed) [2.27.0-0ubuntu5]
[14:26] -queuebot:#ubuntu-release- Unapproved: linux-firmware (mantic-proposed/main) [20230919.git3672ccab-0ubuntu2 => 20230919.git3672ccab-0ubuntu2.1] (core, kernel)
[14:27] <jpeisach> sil2100, vorlon signing off on cinnamon upload
[14:27] <jpeisach> all god
[14:27] <ItzSwirlz> sorry, bouncer is acting up.
[14:27] <ItzSwirlz> You should be able to see this message now - I approve cinnamon upload
[14:30] -queuebot:#ubuntu-release- Unapproved: accepted cinnamon [source] (mantic-proposed) [5.8.4-3ubuntu1]
[14:30] <ginggs> ItzSwirlz: thanks, ^
[14:30] <juergh> ginggs, xnox sil2100 updated linux-firmware uploaded
[14:30] <ginggs> juergh: thanks, looking...
[14:33] <bdmurray> mapreri: Could you open a bug about cdimage and we'll look at it after 23.10?
[14:33] <sil2100> mapreri: .6 was only spun for a smaller subset of images, desktop ones mostly, so there's no .6 images there. The publishing scrips created the .6 symlink which I guess we can remove
[14:33] <sil2100> But that's really not the time for that
[14:34] <bdmurray> https://bugs.launchpad.net/ubuntu-cdimage/
[14:34] <sil2100> I really don't care about 20.04 this week ;p
[14:36] <xnox> juergh: thank you
[14:40] <ginggs> juergh: the changes in your upload are a bit different to those in the debdiff attached to LP: #2038546
[14:40] -ubottu:#ubuntu-release- Launchpad bug 2038546 in linux-firmware (Ubuntu Mantic) "/lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64" [High, Confirmed] https://launchpad.net/bugs/2038546
[14:41] <ginggs> the debdiff only changes exclude.fwinfo for riscv64, your upload changes all architectures
[14:41] <juergh> ginggs, yes because the debdiff is an incomplete fix
[14:42] <ginggs> also the debdiff only removes cypress/*-sdio.bin, leaving cypress/*-pcie.bin
[14:44] <ginggs> but your upload removes cypress/cyfmac4356-pcie.bin and cypress/cyfmac43570-pcie.bin in addition
[14:45] <tsimonq2> vorlon (or someone from ubuntu-release), mdeslaur (or someone from ubuntu-security): Given https://github.com/curl/curl/discussions/12026 - should we expect respins on Wednesday?
[14:46] <tsimonq2> (And given someone from ubuntu-security has surely already looked at the extent of this, what is the impact?)
[14:46] <juergh> ginggs, rats missed those two. let me check and re-upload if necessary
[14:47] <ginggs> juergh: ta!
[14:53] <xnox> tsimonq2: why? it doesn't affect our ability to securely get or install updates; from this point forward fixes need to affect ability to install or get updates; hence the wifi fix is for "unable to get updates"
[14:53] <xnox> for example.
[14:57] <tsimonq2> xnox: The release isn't "minted" yet, and the release pocket is still open. I don't know how ubuntu-security handles updates like this in Final Freeze, especially with something as ubiquitous as curl, so that's why I'm asking :)
[14:57]  * tsimonq2 is allowed to ask stupid questions sometimes ;)
[14:58] <juergh> ginggs, so these two pcie files should actually be included as well (i.e. dropped from the exclude files). the kernel references the files so they are required if relevant HW is attached. whether that makes sense for the platform is a different story.
[14:58] <utkarsh2102> perhaps the bug should be updated with that reasoning.
[14:58] <utkarsh2102> juergh^ :)
[14:58] <juergh> will do
[15:01] <ginggs> juergh: ack, so only cypress/cyfmac54591-pcie.bin should remain in the exclude file?
[15:03] <juergh> ginggs, yes
[15:04] <ginggs> juergh: thanks for clearing that up!
[15:05] -queuebot:#ubuntu-release- Unapproved: shim-signed (mantic-proposed/main) [1.55 => 1.56] (core) (sync)
[15:05] <juliank> utkarsh2102: ^ fixed shim-signed (thanks apw!)
[15:06] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.49 => 2.664.50] (desktop-core, i386-whitelist)
[15:08] <utkarsh2102> juliank: wooooooooooot!
[15:10] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (mantic-proposed) [20230919.git3672ccab-0ubuntu2.1]
[15:14] <xnox> releasing pc-kernel as linux is migrating
[15:14] <xnox> $ cranky promote-snap mantic:linux:pc-kernel
[15:14] <xnox> Released 'pc-kernel' revision 1459 to channels: '23.10/stable'
[15:14] <xnox> Released 'pc-kernel' revision 1460 to channels: '23.10/stable'
[15:15] <dbungert> what is cranky?
[15:16] <kanashiro> sil2100 if you have time today could you please take a look at the docker-{buildx,compose-v2} SRUs? They are ready to land
[15:21] <sil2100> kanashiro: I am sorry but I most likely won't have time for my SRU shift today, the 23.10 release prep is taking far more of my time than I expected
[15:28] <kanashiro> no problem, I can wait for the next vanguard :)
[15:31] <vorlon> LocutusOfBorg: "of which Canonical is already aware" hmm then why did the request to blacklist not come from "Canonical"? :)
[15:38] <LocutusOfBorg> adrien, ^^
[15:38] <LocutusOfBorg> I had to search on irc logs, my memory is not good as years ago...
[15:38]  * utkarsh2102 is happy to bribe sil2100 on kanashiro's behalf, specifically when sil2100 is sitting right in front of me :P
[15:39] <kanashiro> thanks utkarsh2102 ! :P
[15:39] <vorlon> juliank: I don't think there are any other AAs at the release sprint ftr
[15:39] <LocutusOfBorg> I remember adrien trying to get it bootstrapped (hadrian), but failed so far. Until we have it better blacklist/blocklist
[15:41] <LocutusOfBorg> what I'm saying is that Debian/Ubuntu should have been using hadrian already since few releases, but nobody cared (except for adrien) to do the migration work
[15:43] <adrien> LocutusOfBorg: what did I do?
[15:43] <LocutusOfBorg> adrien, you tried to move to hadrian ghc build process
[15:44] <LocutusOfBorg> now, Debian has that chicken and egg issue with ghc not being able to build itself
[15:44] <LocutusOfBorg> I asked to blocklist it from sync for a while, until Debian settles it down
[15:44] <LocutusOfBorg> do you agree?
[15:44] <mapreri> bdmurray, sil2100: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2038841
[15:44] -ubottu:#ubuntu-release- Launchpad bug 2038841 in Ubuntu CD Images "cdimage links for 20.04 wrongly links to 20.04.6" [Undecided, New]
[15:45] <adrien> I don't have a strong opinion on the matter since I didn't pay close attention to this recently but I think it has been causing troubles for debian due to the breadth of reverse-dependencies
[15:45] <adrien> I remember seeing a postgres migration being blocked by that due to bindings, or something similar to that
[15:46] <adrien> and I was glad ubuntu wasn't impacted too :P
[15:47] <juliank> vorlon: archive admins? ~canonical-signing people are what matters :D
[15:47] <vorlon> seb128: ^^ that seems like a pretty compelling reason to me to block ghc syncs at NN opening; do you want to follow it through or shall I?
[15:47] <vorlon> juliank: and who do you think canonical-signing is
[15:48] <juliank> OK OK
[15:48] <juliank> I would have expected sil2100 to be at the release sprint
[15:49] <juliank> :D
[15:49] <juliank> Also that's what the context tells me
[15:51] <LocutusOfBorg> also, usually we wait ghc transition to start until the Debian one settles down. I asked debian to accept haskell-hadrien or whatever is called from new queue, but we will need a new ghc w.r.t. the one currently in sid :/
[15:53] <vorlon> juliank: <smacks forehead> yes he's AA.  This venn diagram is confusing
[15:54] <sil2100> Ok, sorry guys, but I lost a context here as I was battling various stuff
[15:54] <sil2100> What is this all about the AA?
[15:54] <juliank> sil2100: vorlon just forgot you are one
[15:55] <juliank> >D
[15:55] <vorlon> sil2100: juliank had suggested earlier during the day that apw should train you on canonical-signing stuff for the shim-signed update while you were on the same island. But it's done now, so no longer relevant
[15:55] <juliank> also mz kezboard lazout is in US somehow
[15:55] <sil2100> ...any action items for me then? ;)
[15:55] <juliank> I can submit signing request for 2.12 backports uploads but *after* the release
[15:55] <juliank> Then you can go do those together in Riga
[15:56] <juliank> I have 20.04 and 22.04, but unsquashfs on 18.04 is too old to run the test suite
[15:56] <juliank> and 16.04 I haven't approached yet
[15:57] <juliank> All of them are proof of concept, just gathering the changes needed while bored
[15:57] <juliank> Need to write a script to automate backporting
[15:57] <sil2100> juliank: btw. the shim-signed bit, how critical is it to have it for release?
[15:57] <juliank> sil2100: you can't dpkg-reconfigure shim-signed without it basically
[15:57] <juliank> sil2100: but the installer doesn't seem to do that so ...
[15:58] <vorlon> correct.  It does not need to be in the release pocket
[15:58] <vorlon> it's only that upgrades from jammy to mantic without it (which don't happen until after lunar EOLs) will fail
[15:58] <juliank> I'd 0day SRU it unless you happen to be building updated squashfs images either how
[15:59] <sil2100> I'll accept it as we're anyway waiting for migration of a few other fixes, we have no candidate images yet
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [sync] (mantic-proposed) [1.56]
[15:59] <vorlon> juliank: does cd-boot-images-* formally need an update due to versioned build-deps?
[15:59] <sil2100> If it migrates, then good, if not, it stays in proposed
[15:59] <sil2100> Ah, shit, cd-boot-images
[16:00] <vorlon> it should be a no-op change wrt the binary contents used on the images
[16:00] <juliank> vorlon: Well the policy ignores it
[16:00] <juliank> I don't worry about them
[16:00] <vorlon> it's also trivial to fix
[16:00] <juliank> I think the signature has changed?
[16:00] <juliank> Due to signing services limitations
[16:00] <sil2100> ah, so shim-signed is not a hard-versionned dep
[16:00] <vorlon> juliank: is the shim we put in cd-boot-images-* dual-signed?
[16:01] <juliank> ah no it isn't
[16:01] <juliank> so nothing changed
[16:01] <vorlon> ok and sil2100 is correct, build-deps not broken anyway
[16:01] <juliank> I ... will make it a hard build-dep next cycle
[16:01] <vorlon> heh
[16:01] <juliank> I made u-boot-sifive one this cycle
[16:02] <juliank> Basically the files that land in the image (essentially Built-Using) should be hard, so we don't accidentally rebuild with a newer image of a component other than the one we are updating
[16:02] <juliank> Like I was updating images for grub and barely noticed sifive got bumped since last upload because it was unversioned
[16:02] <juliank> Also I want to move cd-boot-images-* into some template and autogenerate them
[16:03] <vorlon> xnox, juergh: no one has answered wrt libpisp being worth getting in this week without any revdeps in the archive, so I'm not going to prioritize and possibly rush a sourceful NEW review of it
[16:03] <juliank> Kind of considerung stuffing grub2-signed into the grub2 package and autogenerating a source package from a debian/rules target too
[16:03] <juliank> like we generate grub2-unsigned
[16:04] <juliank> Gives you central place for changelogs but no way to respin for -signed only packaging changes (hence not useful for shim)
[16:04] <juliank> It's a shame launchpad has no signed template support
[16:05] <juliank> Debian is a lot easier
[16:05] <juliank> I just go upload grub2 and all the signed bits happen automagically
[16:05] <juliank> Ubuntu have to update 7 packages
[16:05] <juliank> I think it's 7, I may be off by one or two
[16:06] <juliank> grub2, grub2-unsigned, grub2-signed and all the cd-boot-images
[16:06] <sil2100> vorlon: hey
[16:06] <vorlon> juliank: I think these musings would be better somewhere else than #ubuntu-release during release week however
[16:06] <juliank> sorry!
[16:07] <vorlon> perhaps somewhere more permanent ;)
[16:07] <vorlon> s/permanent/persistent/
[16:07] <sil2100> vorlon: so I was struggling today to get the DDTP translations updated, all the scripts in the tooling are python2 based and fail in random places
[16:07] <sil2100> vorlon: I was unable to pull in new Debian translations so far nor generate new ones - I did refresh the pot files however
[16:07]  * juliank will eventually write a fo123 - autogenerated boot signing artefact debs
[16:08] <sil2100> vorlon: I see you uploaded the last ddtp-translations package, even though I don't see the lunar po bzr repository (only the pot one)
[16:08] <dbungert> juliank: if I sbuild cd-boot-images-amd64 /usr/share/cd-boot-images-amd64/images/boot/grub/efi.img doesn't match the current cd-boot-images-amd64 one - thoughts?
[16:09] <vorlon> dbungert: isn't efi.img the el-torito image containing the bootloader?
[16:09] <juliank> it's some mkfs.msdos
[16:09] <vorlon> and thus a filesystem with timestamps we don't care about
[16:09] <dbungert> OK
[16:10] <juliank> I guess still a bug it ignores SOURCE_DATE_EPOCH (or maybe we don't set it :D)
[16:10] <juliank> A bug to report in debian and forget about :D
[16:10] <sil2100> vorlon: do you have an env or set of updated tooling to update the DDTP translations?
[16:10] <vorlon> sil2100: I must have followed directions from somewhere else to make this happen; or else I muddled my way through and didn't write it down
[16:10] <vorlon> sil2100: let me see if I ran my mouth on IRC 6 months ago
[16:11] <vorlon> (about this specifically, I mean)
[16:11] <sil2100> vorlon: thanks ;) Since the instructions tell to use tooling that's python2 based and after some mods some of it works but some things seem to require a bit more porting
[16:13] <vorlon> sil2100: IRC points to https://warthogs.atlassian.net/browse/RTMP-825 points to https://bazaar.launchpad.net/~mvo/apt-ddtp-tools/trunk/view/head:/UbuntuChecklist which seems to be the same thing that is in the current checklist.  So if that's what you followed, I bet I just ran it in a focal chroot
[16:14] <vorlon> it's just strange that I didn't kvetch about it in the process
[16:14] <sil2100> ...maybe that makes more sense indeed
[16:14] <vorlon> well focal won't last forever, we'll need to update it eventually.  Just seems likely that's what I did to unblock :)
[16:18] <vorlon> sil2100: so, I'm afk now for a bit, but let me know if you want me to pick this up from you today
[16:18] <utkarsh2102> seb128: hey, gnome-shell-extension-ubuntu-dock is not something that we (release team) are planning to accept, so we're going to let it be in the queue and consider this for a 0-day SRU.
[16:19] <sil2100> vorlon: will do! I'll screw it and run it in focal for now, but we'll really have to migrate it properly at some point. If I don't manage to do it, I'll give you a ping to continue :_
[16:37] <seb128> utkarsh2102, hey, wfm
[16:37] <utkarsh2102> thanks! I've also commented on the bugs.
[16:37] <seb128> I assumed so when Lukasz accepted yaru and not the dock this morning
[16:42] <xnox> vorlon: hi, we believe it is pointless. as pipewire is not seeded.
[16:42] <xnox> vorlon: and thus updated pipewire and libpispi can be done as sru, when we actually test it with pi5 the right cable and the right camera. and there are interesting new api/abi introduced in pipewire itself (for all "providers") which makes it more concerning to land now.
[16:43] <xnox> also feel free to just reject libpispi, as probably it needs to be uploaded fresh into natty anyway
[16:46] -queuebot:#ubuntu-release- Unapproved: sqlmap (mantic-proposed/universe) [1.7.9-1 => 1.7.10-1] (no packageset) (sync)
[16:46] -queuebot:#ubuntu-release- Unapproved: poedit (mantic-proposed/universe) [3.3.2-2 => 3.4-1] (no packageset) (sync)
[16:46] -queuebot:#ubuntu-release- Unapproved: udiskie (mantic-proposed/universe) [2.4.2-1 => 2.5.0-1] (no packageset) (sync)
[16:47] -queuebot:#ubuntu-release- Unapproved: accepted poedit [sync] (mantic-proposed) [3.4-1]
[16:47] -queuebot:#ubuntu-release- Unapproved: accepted udiskie [sync] (mantic-proposed) [2.5.0-1]
[16:47] -queuebot:#ubuntu-release- Unapproved: accepted sqlmap [sync] (mantic-proposed) [1.7.10-1]
[16:54] -queuebot:#ubuntu-release- Unapproved: nvidia-tegra-defaults (jammy-proposed/universe) [1.2~22.04 => 1.3~22.04.1] (no packageset)
[16:58] <utkarsh2102> fwiw, the freeze block is in place now!
[16:58] <utkarsh2102> \o/
[17:00] <Eickmeyer> brrrr....
[17:03]  * tsimonq2 passes utkarsh2102 a jacket :)
[17:05] <utkarsh2102> hah
[17:25] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-tegra-defaults [source] (jammy-proposed) [1.3~22.04.1]
[17:31] <dbungert> fossfreedom_: we are working through ubuntu-desktop-provision PRs, I broke command-not-found, fix incoming
[17:32] <fossfreedom_> Ah. OK.
[17:39] <sil2100> vorlon: ...I don't know why but the DDTP update from Debian takes ages for me
[17:39] <utkarsh2102> (drop it :P)
[17:39] <vorlon> sil2100: are you on ipv6
[17:40] <sil2100> I think it's slow actually doing translation thingies, not on anything networking related
[17:40] <sil2100> Runnint the translations2po stuff and it's just sooo slooo
[18:12] -queuebot:#ubuntu-release- Builds: Upgrade Edubuntu amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Lubuntu amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu MATE amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Studio amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade UbuntuKylin amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Kubuntu amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Server amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Xubuntu amd64 [Mantic Final] (20231009) has been added
[18:13] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu amd64 [Mantic Final] (20231009) has been added
[19:26] <vorlon> respinning the world
[19:27] <vorlon> picks up new kernels, new subiquity, new linux-firmware, new ubuntu-desktop-installer
[19:28] <vorlon> fossfreedom_: there is a subiquity bugfix that applies to all installers based on it, we encourage you to respin ubuntu-desktop-installer for it (wrong permissions on apt sources.list after install) so I'll hold off on respinning Budgie for right now
[19:29] <fossfreedom_> OK. Going to poke dependabot on ubuntu-budgie-installer to pick up the latest
[20:23] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Mantic Final] has been updated (20231009.1)
[20:25] <fossfreedom_> vorlon have built and done a smoke test install. /etc/apt/sources.list is 0644. If that is what is expected then great. Please kick a build for our two iso's. Cheers.
[20:28] -queuebot:#ubuntu-release- Builds: Xubuntu Minimal amd64 [Mantic Final] has been updated (20231009)
[20:49] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop (Legacy) amd64 [Mantic Final] has been updated (20231009)
[20:54] <vorlon> fossfreedom_: kicking it now, thanks! (and legacy was already built since this was a subiquity-specific change)
[20:55] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Mantic Final] has been updated (20231009.1)
[21:05] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Mantic Final] has been updated (20231009)
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Mantic Final] has been updated (20231009)
[21:13] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Mantic Final] has been updated (20231009.1)
[21:14] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Mantic Final] has been updated (20231009)
[21:15] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop (Legacy) amd64 [Mantic Final] has been updated (20231009.1)
[21:20] -queuebot:#ubuntu-release- Builds: Ubuntu Cinnamon Desktop amd64 [Mantic Final] has been updated (20231009)
[21:20] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Mantic Final] has been updated (20231009)
[21:31] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Mantic Final] has been updated (20231009)
[21:37] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Mantic Final] has been updated (20231009.2)
[21:44] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Mantic Final] has been updated (20231009)
[22:16] <Eickmeyer> vorlon: I see Edubuntu somehow exploded into oversized land with this latest spin.
[22:18] -queuebot:#ubuntu-release- Unapproved: dkms (mantic-proposed/main) [3.0.11-1ubuntu10 => 3.0.11-1ubuntu11] (i386-whitelist, ubuntu-desktop)
[22:24] <fossfreedom_> vorlon: I note on boot of the iso I can see "development branch" before lightdm kicks in. Is this expected?
[22:27] <fossfreedom_> Eickmeyer: in your manifest you have one heck of a load of fonts ... expected?
[22:29] <Eickmeyer> fossfreedom_: WRT Edubuntu or Ubuntu Studio? Because either way, the answer is yes. There's a whole metapackage for fonts.
[22:29] <fossfreedom_> Edubuntu ... fair enough if expected
[22:29] <Eickmeyer> The thing is this is a recent (past 24 hours) development, probably just kernel crawl.
[22:30] <Eickmeyer> Prior spin wasn't oversized.
[22:32] <xnox> vorlon: bdmurray: dkms drops depends on two gcc, in favour of just the one gcc. now that all kernels migrated and nvidia server drivers got removed. It might reduce the number of gcc's installed on live media (either the pool, or the live layer)
[22:35] <Eickmeyer> xnox: To you and team: great job on the lowlatency kernel this release. It's behaving wonderfully in my testing. :)
[22:36] <vorlon> guh what collation order gets used on the builders for the manifest files, 'join' complains about the files being out of order. :|
[22:37] <mwhudson> i think the snaps get appended
[22:37] <vorlon> fossfreedom_: uhm I would not expect anything saying 'development branch'.  Is that what you see when you change to VT3?
[22:37] <vorlon> mwhudson: it's complaining about openjdk
[22:39] <mwhudson> it looks like it's just whatever sorting dpkg-query does
[22:40] <mwhudson> but my first point stands too i think, the snap: lines are at the end so it's likely that join would complain about that if it didn't complain about anything else first
[22:40] <vorlon> sure
[22:42] <vorlon> Eickmeyer: manifests and list files show no irregularities; it just happens to have crept across the line, from 5994471424 to 6002016256
[22:42] <vorlon> Eickmeyer: so unless you want to jettison something...
[22:42] <Eickmeyer> vorlon: Nah, kinda thought it was a creep like that. If you wanna add another 100MB, that'd probably solve the issue.
[22:43] <vorlon> (and I'm not really considering xnox's dkms, that's something that would've been lovely to have last week)
[22:43] <fossfreedom_> vorlon yep vt3 says development branch on install as well
[22:43] <vorlon> fossfreedom_: this is concerning; tracking this donw
[22:43] <Eickmeyer> Can confirm, everything is saying development branch for me on installed systems.
[22:45] <fossfreedom_> Also I note /etc/apt/sources.list is 0664 on the legacy iso and 0644 on the new iso. Any concerns with these two different values?
[22:45] <Eickmeyer> That 0664 looks suspicious.
[22:46] <vorlon> fossfreedom_: none particularly.  644 is what we want, but writability by root group isn't generally a security hole
[22:46]  * Eickmeyer is no longer suspicious
[22:47] <vorlon> well I see no base-files update in mantic since the release opened
[22:48] <vorlon> so that looks like a checklist fail
[22:48] <Eickmeyer> That'd do it.
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+icicle [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive2 [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Mantic Final] has been updated (20231009.1)
[22:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64 [Mantic Final] has been updated (20231009.1)
[22:50] <vorlon> so yeah we'll be respinning the world for base-files again
[22:51] <Eickmeyer> *dead or alive intensifies*
[22:52] <vorlon> fossfreedom_: thanks for the quick eye
[22:52] <vorlon> and for escalating it
[22:56] -queuebot:#ubuntu-release- Unapproved: base-files (mantic-proposed/main) [13ubuntu1 => 13ubuntu2] (core, i386-whitelist)
[22:57] <vorlon> ok now I have to consider dkms
[22:59] <vorlon> yeah I'll ram it through
[22:59] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (mantic-proposed) [3.0.11-1ubuntu11]
[23:01] <vorlon> accidental whitespace introduced in base-files, reuploading
[23:01] -queuebot:#ubuntu-release- Unapproved: rejected base-files [source] (mantic-proposed) [13ubuntu2]
[23:02] -queuebot:#ubuntu-release- Unapproved: base-files (mantic-proposed/main) [13ubuntu1 => 13ubuntu2] (core, i386-whitelist)
[23:04] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (mantic-proposed) [13ubuntu2]
[23:33] -queuebot:#ubuntu-release- Unapproved: network-manager-strongswan (mantic-proposed/universe) [1.6.0-2ubuntu1 => 1.6.0-2.1] (no packageset) (sync)
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-strongswan [sync] (mantic-proposed) [1.6.0-2.1]
[23:45] -queuebot:#ubuntu-release- Unapproved: rust-webp (mantic-proposed/universe) [0.2.5-1 => 0.2.6-1] (no packageset) (sync)
[23:46] -queuebot:#ubuntu-release- Unapproved: accepted rust-webp [sync] (mantic-proposed) [0.2.6-1]
[23:46] <xnox> vorlon: so we can fix i386 pool nvidia installs https://code.launchpad.net/~xnox/debian-cd/+git/debian-cd/+merge/453181
[23:48] <vorlon> xnox: pushed.
[23:49] <xnox> tah, off to sleep then