[00:05] <waveform> jawn-smith, given the hour I'm going to run a curtailed set of tests -- little need to re-test the audio stack, flash-kernel etc. when none of that has changed. I'm most concerned with anything networking related and in particular whether either eth or wifi fail/succeed on first boot (and subsequent reboot)
[00:05] <tsimonq2> I'm marking Lubuntu ready at approx 1:00 UTC.
[00:07] <waveform> okay, confirmation from jawn-smith and myself that 3B+ is fixed so I'll throw caution to the wind and remove that from the release notes
[00:07] <Eickmeyer> tsimonq2: That's incredibly specific. :P
[00:07] <jawn-smith> waveform: Confirmed that eth0 came up successfully on the Pi 3B+ on the arm64 image
[00:08] <jawn-smith> Have you looked at armhf?
[00:08] <jawn-smith> I'm doing that now
[00:08] <waveform> got cards flashing now but I'm also testing first boot eth on a few more boards (2B and 3B)
[00:15] -queuebot:#ubuntu-release- Builds: Ubuntu Cinnamon Desktop amd64 [Mantic Final] has been marked as ready
[00:15] <ItzSwirlz> tgabjs
[00:16] <ItzSwirlz> *thanks!
[00:17] <jawn-smith> armhf seems to still be affected...
[00:20] <jawn-smith> wait my sha256sum doesn't match
[00:28] <waveform> armhf appears fixed on mine (and the hashes do match for me, so I'm guessing you might have an old image there? Check /lib/systemd/network/10-raspi-eth0.link to be certain)
[00:28] <waveform> oh, let me be sure I'm running the armhf card -- switching cards too quickly here
[00:29] <waveform> nope, that's one of my arm64 cards ... just a mo
[00:32] <waveform> oh, that's unusual -- just checked the manifests; the arm64 raspi server image has ubuntu-raspi-settings 23.10.6 (http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/mantic-preinstalled-server-arm64+raspi.manifest), while the armhf one has 23.10.5 (http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/mantic-preinstalled-server-armhf+raspi.manifest)
[00:32] <waveform> that would explain why the armhf image didn't work for you
[00:33] <waveform> yes, just checked the armhf image I just flashed and the .link file is indeed the old one
[00:34] <waveform> vorlon, any idea why the armhf build picked up the old version of ubuntu-raspi-settings while the arm64 build picked up the new one?
[00:39] <jawn-smith> yeah I confirmed it's the old version on armhf
[00:40] <waveform> well, at this stage I'm basically happy with the arm64 server images -- all the network tests check out there and nothing else should have changed. armhf looks like it needs ... something kicking, possibly just a re-spin? But I'm not going to be around for that to finish; better if I head offline now to try and start earlier tomorrow (in case armhf can be rebuilt by then)
[00:41] <waveform> many thanks for all the help!
[00:43] <jawn-smi1> maybe it wasn't published in armhf when the image was built?
[00:46] <vorlon> it's an arch: all package so it would have published simultaneously in both
[00:46] <jawn-smi1> apt-cache policy for the armhf image shows it has 23.10.5 instead of the new 23.10.6
[00:47] <vorlon> yes I checked the manifest and it's wrong
[00:47] <vorlon> jawn-smith: if only ubuntu-image in the livefs build log was telling me what it was doing
[00:47] <jawn-smi1> is it the new ubuntu-image?
[00:47] <vorlon> I will respin
[00:47] <vorlon> jawn-smi1:
[00:47] <vorlon> jawn-smi1: yes
[00:49] <jawn-smi1> --debug :)
[00:49] <vorlon> jawn-smi1: huh you'd think someone would've put that in livecd-rootfs
[00:50] <jawn-smi1> pretty sure that's the flag. been a little while and I refactored the logging shortly before I stopped looking at it all day every day
[00:50] <jawn-smi1> unless you're being sarcastic and that's already in livecd-rootfs
[00:50] <vorlon> it's not in the invocation in livecd-rootfs ;)
[00:51] <jawn-smi1> there are definitely a few flags to show lots more information from the builds
[00:54] <vorlon> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/mantic/cpc/+build/511090
[00:56] <jawn-smi1> there's a --verbose and --debug flag that both increase the logging
[00:56] <jawn-smi1> beyond what's in that log
[00:56]  * vorlon nods
[00:56] <vorlon> jawn-smi1: yeah this is largely just whinging on my part
[00:57] <vorlon> fwiw ubuntu-image --verbose isn't
[00:57] <jawn-smi1> isn't verbose?
[00:57] <vorlon> yeah
[00:57] <vorlon> [8] germinate
[00:57] <vorlon> [9] create_chroot
[00:58] <jawn-smi1> hmm, maybe that's just the normal logging level then. I remember basing it off of some ubuntu wiki page that said how much logging to do with each flag
[00:59] <vorlon> --debug looks better tho
[01:00] <jawn-smi1> excellent
[01:00] <vorlon> haha yeah we are calling --verbose, it just doesn't seem any different than the default
[01:01] <jawn-smi1> yeah I think it is the default
[01:01] <jawn-smi1> now that you mention it
[01:01] <jawn-smi1> I gotta sign off for the night, but I can test some more tomorrow
[01:19] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Mantic Final] has been marked as ready
[01:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Mantic Final] has been updated (20231012)
[01:45] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Mantic Final] has been marked as ready
[06:34] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop (Legacy) amd64 [Mantic Final] has been marked as ready
[06:34] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Mantic Final] has been marked as ready
[06:51] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Mantic Final] has been marked as ready
[07:13] <waveform> ah lovely, I see armhf has been re-spun and the manifest looks correct now -- I'll set it downloading here and get to testing after the school run
[08:13] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Mantic Final] has been marked as ready
[08:16] -queuebot:#ubuntu-release- Builds: Upgrade Lubuntu amd64 [Mantic Final] has been marked as ready
[08:17] -queuebot:#ubuntu-release- Builds: Upgrade Lubuntu amd64 [Mantic Final] has been updated (20231009)
[08:38] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-17 (mantic-release/universe) [1:17.0.2-1~exp1ubuntu2 => 1:17.0.2-1~exp1ubuntu2.1] (i386-whitelist) (sync)
[08:51] -queuebot:#ubuntu-release- Unapproved: casparcg-server (mantic-proposed/multiverse) [2.3.3+dfsg-3ubuntu1 => 2.3.3+dfsg-3.1] (no packageset) (sync)
[08:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Mantic Final] has been marked as ready
[08:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Mantic Final] has been marked as ready
[08:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Mantic Final] has been marked as ready
[08:51] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Mantic Final] has been marked as ready
[08:52] -queuebot:#ubuntu-release- Unapproved: accepted casparcg-server [sync] (mantic-proposed) [2.3.3+dfsg-3.1]
[08:54] <utkarsh2102> !isitout
[08:54] <utkarsh2102> whaaaaaat
[08:54] <ogayot> :D
[08:56] <utkarsh2102> anyway..
[08:56] <utkarsh2102> RELEASE DAYYYYYYYYYYYYYYYYY!
[08:59] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-17 [sync] (mantic-release) [1:17.0.2-1~exp1ubuntu2.1]
[09:49] <philroche> release-team: RE post release/NN opening: Heads up that myself and toabctl are leading the NN opening on the Ubuntu cloud side. Please ping once you have any info.
[09:50] <utkarsh2102> ack, perfect, we'll do once we have something 😭
[10:29] <waveform> okay, armhf raspi server testing done (arm64 raspi server testing was mostly finished last night, but now also finished), and the arm64 raspi desktop testing is also done -- we're good to go
[10:29] <waveform> (and I've updated the rpi-imager JSON MP with the new hashes)
[10:31] <utkarsh2102> yay, thank you, waveform!
[10:32] <utkarsh2102> I'm marking both of them as "ready"
[10:32] <waveform> yeah, I tried marking them in the iso tester but it doesn't seem to do anything for me
[10:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Mantic Final] has been marked as ready
[10:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Mantic Final] has been marked as ready
[10:41] <waveform> desktop raspi can also be marked "ready"
[10:50] <bdmurray> waveform: roger that good buddy
[10:53] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Mantic Final] has been marked as ready
[10:58] <waveform> bdmurray, and for later on the rpi-imager JSON merge is here: https://code.launchpad.net/~waveform/meta-release/ubuntu/+merge/453335
[11:03] <kajiya> 3.
[11:04] <kajiya> Sorry that was the cat xD
[11:24] <sil2100> We will be starting the release shortly, please be sure to mark your images as ready!
[11:28] -queuebot:#ubuntu-release- Unapproved: terminus (mantic-proposed/universe) [2.3.1-1ubuntu1 => 2.3.1-1ubuntu2] (no packageset)
[11:29] -queuebot:#ubuntu-release- Unapproved: accepted terminus [source] (mantic-proposed) [2.3.1-1ubuntu2]
[11:41] <jbicha> sil2100: please mark Ubuntu Desktop & Legacy amd64 as ready
[11:41] <utkarsh2102> seb128: hey there, how do you feel about marking Ubuntu Desktop images as "ready"?
[11:41] <utkarsh2102> hahahaha
[11:41] <utkarsh2102> jbicha: thank you!
[11:42] <utkarsh2102> done!
[11:43] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop (Legacy) amd64 [Mantic Final] has been marked as ready
[11:45] <utkarsh2102> we still want to test the nvidia stuff for Ubuntu Desktop
[11:45] <utkarsh2102> jbicha: did you test the nvidia bits, too?
[11:45] <jbicha> utkarsh2102: no, I do not have Nvidia hardware
[11:46] <utkarsh2102> fair, thanks
[11:46] <utkarsh2102> we'll wait for that to be done and then we'll make it as "ready"
[11:51] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Mantic Final] has been marked as ready
[11:51] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Mantic Final] has been marked as ready
[11:51] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Mantic Final] has been marked as ready
[11:59] <schopin> I just finished a round of nvidia tests.
[12:04] <bdmurray> schopin: I interpret that to mean they passed.
[12:08] <utkarsh2102> schopin: it'd be nice if you can also update the testcases accordingly? :)
[12:09] <schopin> utkarsh2102: I thought I did so?
[12:10] <utkarsh2102> ah, looking..
[12:11] <schopin> TL;DR: release the minotaur.
[12:11] <utkarsh2102> okeydoke, I see you there - http://iso.qa.ubuntu.com/qatracker/milestones/449/builds/288369/testcases/1771/results
[12:13] <bdmurray> \o/
[12:16] <utkarsh2102> bdmurray: we have green lights for Desktop from jbicha and schopin. Tell me when you want me to pull the trigger.
[12:17] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Mantic Final] has been marked as ready
[12:18] <utkarsh2102> THANK YOU!
[12:18] <seb128> Ukikie, hey, +1 from me as well for desktop
[12:18] <utkarsh2102> you probably meant me but that's alright :P
[12:18] <seb128> yes, tab completion is hard, right? ;-)
[12:18] <seb128> Ukikie, sorry :p
[12:19] <utkarsh2102> the publishing has already started \o/
[12:19] <seb128> \o/
[12:20] <utkarsh2102> okeydoke, time for cloud images
[12:21] <utkarsh2102> mjdonis, kajiya: hey! can you start the process of building and publishing cloud images?
[12:21] <utkarsh2102> cpc-help^ :)
[12:21] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Mantic Final] has been marked as ready
[12:21] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Mantic Final] has been marked as ready
[12:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Mantic Final] has been marked as ready
[12:22] <kajiya> utkarsh2102 on it 👀
[12:22] <utkarsh2102> kajiya: thanks, let me know once that's done! \o/
[13:00] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu amd64 [Mantic Final] has been marked as ready
[13:02] <jawn-smith> waveform: Is there any other testing you want me to do? Looks like you're "good to go" according to the scrollback
[13:02] <waveform> nope, we're good! Thanks :)
[13:07] <jawn-smith> Cool, now I'll just sit here and wait for my Pi5 while contemplating emailing Gordon again
[13:19] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Server amd64 [Mantic Final] has been marked as ready
[13:48] -queuebot:#ubuntu-release- Unapproved: keystone (lunar-proposed/main) [2:23.0.0-0ubuntu1 => 2:23.0.1-0ubuntu1] (openstack)
[13:58] -queuebot:#ubuntu-release- Unapproved: keystone (jammy-proposed/main) [2:21.0.0-0ubuntu1 => 2:21.0.1-0ubuntu1] (openstack)
[14:14] <luna-> 23.10 time :)
[14:22] <sil2100> Almost!
[14:22] <luna-> sil2100: ah i upgraded my test Virtualbox VM with apt but guess its not fully released when an iso and announcment email is out etc?
[14:23] <luna-> but its today atleast i think
[14:28] <bdmurray> it will be today
[14:31] <coconut> no it is
[14:31] <coconut> http://cdimage.ubuntu.com/ubuntu/releases/23.10/release/
[14:31] <luna-> coconut: i think that still misses files as it just have the legacy installer and RISC-V
[14:32] <luna-> but should relax and not disturb the release team
[14:32] <coconut> oh
[14:32] <coconut> thank you
[14:32] <luna-> guessing there will be more there later during the day
[14:32] <mjdonis> release-team cloud download images are public now @ http://cloud-images.ubuntu.com/releases/mantic/release/ and http://cloud-images.ubuntu.com/minimal/releases/mantic/release/ and are also present in streams
[14:39] <utkarsh2102> oh lovely!
[14:42] <LocutusOfBorg> !isitout
[14:42] <LocutusOfBorg> ubottu, wanna join #ubuntu-release-party?
[14:46] <sil2100> Mirrors syncing!
[14:54] <Eickmeyer> The person who usually updates the bot for this has been AWOL for a bit, so we're not likely to see the bot updated for !isitout.
[15:02] <tomreyn> How about we just tell Ubottu that: !no,  isitout is <reply> For all I know, the latest Ubuntu release is $curStableNum ($curStableLong). You can double-check this on the https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce Archives and subscribe for future release notifications.
[15:04] <Eickmeyer> I like that. :)
[15:11] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (mantic-proposed/main) [1:23.10.10 => 1:23.10.11] (core)
[15:13] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (lunar-proposed/main) [1:23.04.6 => 1:23.04.7] (core)
[15:15] <sil2100> Images are syncing!
[15:15] <mclemenceau> !isitout
[15:22] <tomreyn> !isitout
[15:24] <tomreyn> ^ hope that's ok with everyone, if not, please ask for it to be changed in #ubuntu-bots or #ubuntu-ops
[15:26] <utkarsh2102> tomreyn: oooooooooooooooooh, thanks!
[15:26] <utkarsh2102> it's definitely much better
[15:29] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (lunar-proposed) [1:23.04.7]
[15:29] <tomreyn> Glad you two like it.
[16:00] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (jammy-proposed/main) [1:22.04.17 => 1:22.04.18] (core)
[16:05] <luna-> https://releases.ubuntu.com/23.10/ubuntu-23.10-desktop-amd64.iso
[16:08] <Eickmeyer> luna-: Don't. This channel is the one that publishes those, so there's no reason for you to do that.
[16:28] <utkarsh2102> fingers crossed, heh
[16:38] <utkarsh2102> Hey there! As you note, we're happy to announce the new and shiny Ubuntu 23.10, codenamed Mantic Minotaur. Happy release! 🎉
[16:41] <Eickmeyer> utkarsh2102: Email sent to ubuntu-announce@?
[16:43] <utkarsh2102> Eickmeyer: doing that..
[16:44] <Eickmeyer> utkarsh2102: Thought so. :)
[17:10] <tumbleweed> congrats!
[17:15] <ricotz> \o/
[17:15] <xnox> sil2100: do we have a new name yet?
[17:15] <xnox> tumbleweed: tah
[17:16] <ricotz> ahasenack, hello :), is it possible to let libreoffice/lunar-proposed transition "earlier" again?
[17:17] <utkarsh2102> xnox: not yet, no
[17:18] <ahasenack> ricotz: I'm off today, I swapped my SRU day with robie and did my shift yesterday
[17:19] <ricotz> ahasenack, ah, I see, have a nice day then :)
[17:22] <ricotz> rbasak, hello :), it would be great to have libreoffice transition out of lunar-proposed, would you be available for that?
[17:45] <Eickmeyer> Well, don't know about all of you, but I'm going to sleep for a week. (j/k). See most of you in Riga.
[17:57] <mdeslaur> congrats! :)
[18:35] <rs2009> !isitout
[18:36] <rs2009> aw well
[18:37] <Eickmeyer> rs2009: Check /topic, and scrollback. It's out.
[18:38] <Eickmeyer> Feel free to do your release announcement stuff. :)
[18:38] <Eickmeyer> email just isn't out yet and the variables on the bot haven't been updated.
[20:36] <utkarsh2102> o/
[20:52] <guiverc> utkarsh2102, I've not seen ML post yet  (or did I just miss it)
[20:52] <utkarsh2102> guiverc: we have a thing holding it up, it should be there soon
[20:52] <guiverc> thanks... :)
[21:06] <tsimonq2> utkarsh2102: What's the process for a new codename these days anyway?
[21:07] <tsimonq2> utkarsh2102: I loved when Mark would make a witty announcement, but I get it if he doesn't quite have the time these days. :)
[21:07] <utkarsh2102> tsimonq2: you know as much as I/we know, really :/
[21:07] <utkarsh2102> that is, nothing at all about the new codename
[21:07] <utkarsh2102> as soon as I hear something about it, I'll definitely let you know, as I promised ;)
[21:08] <tsimonq2> Thanks again for that :)
[21:08]  * tsimonq2 looks over at local lintian, vim, debootstrap, debscripts, calamares-settings-ubuntu, calamares, lxqt-powermanagement, and lubuntu-meta, ready for NN ;)