[20:08] <tsimonq2> wxl: merged! \o/ https://code.launchpad.net/~tsimonq2/livecd-rootfs/lubuntu-next-image/+merge/301202
[20:08] <tsimonq2> wxl: one down, one to go :)
[20:08] <wxl> cool
[20:08] <wxl> i didn't even see the response
[20:09] <wxl> slangasek got sick of waiting on infinity and just did it? :)
[20:09] <tsimonq2> XD yep
[20:09] <wxl> daang
[20:10] <wxl> i have to say it's rather strange
[20:10] <wxl> adam is usually very on top of things
[20:10]  * tsimonq2 nods
[20:10] <tsimonq2> wxl: we even get our own version XD 2.423
[20:10] <wxl> oooooh
[20:10] <tsimonq2> !info livecd-rootfs yakkety
[20:10] <tsimonq2> wxl: we just have to wait :P
[20:12] <tsimonq2> wxl: what happens when the images are spun up? do you think it would be good to announce something?
[20:12] <wxl> tsimonq2: get all the testcases taken care of
[20:12] <wxl> tsimonq2: then start testing!
[20:12] <wxl> tsimonq2: then finalize the choices on applications
[20:12] <wxl> tsimonq2: make new testcases
[20:13] <wxl> tsimonq2: test more
[20:13] <wxl> tsimonq2: then make it lubuntu :)
[20:14] <wxl> tsimonq2: we also need to discuss what to do with lxde. i mean we shouldn't really do two images. i don't think. maybe we should have lubuntu-lxde-core/desktop? i don't know. more thinking here.
[20:19] <tsimonq2> yeah
[20:20] <tsimonq2> wxl: the question is, will LXQt be *default* for 16.10 or will we just have an extra LXQt set of images?
[20:20] <tsimonq2> wxl: our plan was the latter, right?
[20:20] <wxl> tsimonq2: i suspect the latter. we have a lot of work to do still.
[20:20] <wxl> i think decisions on the applications alone will take us a whole cycle.
[20:20] <wxl> like seriously.
[20:21] <tsimonq2> yeah
[20:22] <tsimonq2> wxl: let me whip up a step-by-step proposal detailing our transition to LXQt. Then, if you like it and the rest of the team likes it, we can refer to it in the future.
[20:22] <tsimonq2> wxl: and it will at least be a for-sure roadmap
[20:22] <wxl> tsimonq2: sounds good. would be nice in the form of a blueprint. there's probably already one there you can just edit
[20:22] <tsimonq2> wxl: good idea
[20:23] <wxl> tsimonq2: i think you should put a date on there for people to refer to. maybe i'm stepping out here, but i'd advise putting 17.10 as the plan.
[20:23] <wxl> tsimonq2: as i don't necessarily support the notion of releasing new features in an LTS and it's too late for 16.10
[20:24] <tsimonq2> wxl: why not 17.04?
[20:24] <wxl> tsimonq2: new features in an LTS can be a problematic matter. people depend on an LTS being absolutely rock solid. if we're not 100% sure of that, it will create a riot.
[20:25] <tsimonq2> wxl: 17.04 is not an LTS...
[20:25] <wxl> izznot?
[20:25] <wxl> oh
[20:25] <wxl> it's not :)
[20:25] <wxl> yeah right
[20:25] <wxl> derp
[20:25] <tsimonq2> wxl: 18.04 is, :P
[20:25] <tsimonq2> hehehehehehe :)
[20:25] <wxl> so yes maybe 17.04 might be good. if we can make it there.
[20:25] <tsimonq2> alright I'll plan this out
[20:26] <wxl> i think it will take us several weeks just to figure out each application. i'm not freaking kidding.
[20:26] <tsimonq2> yeah
[20:34] <tsimonq2> wxl: so for a work item, do you think it would be smart or excessive to specify a work item for each LXQt blueprint we have?
[20:34] <wxl> tsimonq2: i kind of think so.
[20:35] <tsimonq2> wxl: E: Invalid option. Please specify either "smart" or "excessive"
[20:35] <tsimonq2> XD
[20:35] <wxl> smart
[20:35] <tsimonq2> k
[20:38] <tsimonq2> wxl: is there any specific order we should decide on things, and if so, what do you suggest?
[20:38] <tsimonq2> (applications for LXQt)
[20:39] <wxl> tsimonq2: i'm not sure it matters too much. but if we get the "easy" ones first it might allow us to test them while we work on the "hard" ones (like the browser)
[20:39] <tsimonq2> ok
[20:40] <tsimonq2> wxl: so there's "Approved" and "Discussion" blueprints
[20:40] <tsimonq2> wxl: we only need to decide on "Discussion" ?
[20:40] <wxl> tsimonq2: yes, but i didn't think we had decided on ANY :O
[20:40] <tsimonq2> wxl: https://blueprints.launchpad.net/lubuntu-next
[20:40] <wxl> soooo might want to run those past gilir to be sure
[20:40] <tsimonq2> wxl: well obviously LXQt :P
[20:41] <wxl> bah launchpad's updating
[20:41] <tsimonq2> not for me...
[20:42] <wxl> now it works
[20:42] <wxl> ugh all those should be renamed to z-series then i guess
[20:43] <tsimonq2> wxl: but what about Discussion/Approved
[20:43] <tsimonq2> s/Approved/Approved?/g
[20:43] <wxl> assume that approved is approved but check with gilir for certainty
[20:45] <tsimonq2> ok
[20:46] <tsimonq2> wxl: I'm struggling, what should I start with, and given the blueprint's current status, what's the due date
[20:46] <tsimonq2> s/date/date?/g grrrrrr
[20:47] <wxl> like i said
[20:47] <wxl> start with the easy stuff :)
[20:47] <wxl> your guess is as good as mine, really
[20:47] <tsimonq2> well you said browser is hard
[20:47] <tsimonq2> ¯\_(ツ)_/¯
[20:47] <wxl> yeah there's that
[20:48] <tsimonq2> wxl: due date?
[20:49] <wxl> tsimonq2: well, we'd HOPE to do z cycle, eh?
[20:49] <tsimonq2> wxl: well are we going to allocate a week or two for each or are we going to set one due date for all?
[20:50] <wxl> well at this point let's make a proposal based on what we think is best
[20:51] <wxl> i think if we give us a week or so it gives us time to argue it and the ability to focus on just one thing at a time
[20:51] <wxl> we can use it as an opportunity to get the community to engage
[20:52] <tsimonq2> ok
[20:52] <wxl> we need to submit the proposal to the community and make sure they accept it, too
[20:52] <wxl> so we need to be willing to change it
[20:53] <wxl> and of course we need gilir's backing
[20:54] <tsimonq2> yeah
[20:57] <wxl> lunch
[20:59] <tsimonq2> me too :P
[21:32] <tsimonq2> wxl: so Julien responded
[21:33] <tsimonq2> wxl: he said: "It was approved at some point, but if you have a better idea, you can add it to the discussion"
[21:33] <tsimonq2> wxl: I also asked him about the poll, he said that he can't look now, but he'll let me know later
[21:45] <tsimonq2> wxl: slangasek approved and the crontab is in production!
[21:45] <tsimonq2> \o/
[21:57] <tsimonq2> hey yofel, LXQt image gets generated tomorrow! \o/
[21:58] <yofel> \o/
[21:58] <tsimonq2> I remember you saying something about that...
[21:58] <tsimonq2> thought I would let you know :)


[12:04] <Joro> hello
[12:04] <Joro> I installed english german dictionary but the symbols of german alphabet don't show up
[12:05] <Joro> can you help me with that
[12:05] <Joro> I installed german in language support but still no fix
[12:05] <Joro> the dictionary is elcombri translator
[12:06] <Joro> you know how german has letters with two dots above the letter these signs appear with question marks
[12:06] <Joro> otherwise the menus are ok with those letters
[12:06] <Joro> but the words in the dictionary are not
[12:15] <DJones> Joro: Which version of Ubuntu are you using?
[12:18] <Joro> 14.10
[12:18] <Joro> in wine they appear
[12:19] <DJones> 14.10? Are you certain, 13.10 has only just been released, and 14.04 is only just being developed
[12:20] <DJones> If its the development version of 14.04, it might be something thats still being worked on
[12:24] <DJones> If its 13.10 or earlier and not the development version of 14.04, you'll get more response in #ubuntu
[12:26] <Joro> 14.04
[12:26] <Joro> yes
[12:26] <Joro> sorry
[12:26] <Joro> just used 13.10 for longer
[12:26] <Joro> Djones
[12:27] <DJones> Heh, I've not started using 14.04 yet, hopefully somebody else here can help though
[12:28] <Joro> if it is the same with 13.10 can you do something about it
[12:30] <DJones> I've not had any experience with that type of error, I was just checking that you were in the right channel because I hadn't seen any questions about 14.04 here yet
[12:30] <DJones> Can't test the issue for you as I'm not Ubuntu at the minute
[13:42] <BluesKaj> Hey folks
[16:31] <SuperLag> Curious... how long into the development cycle of a new release do the splash screens and version info get updated to reflect the new version?
[16:32] <penguin42> pretty late normally
[19:43] <SuperLag> Wow. A desktop with a quad-core i7, 32GB of RAM. One VM open in Workstation that's allocated 2GB of RAM. Thunderbird. Chrome with 2 tabs. Terminal with 2 windows. (all of that to say the load is relatively little) And clicking on the Terminal icon in the lauch area... where Unity shows the two windows animation... slow as molasses.
[19:45] <penguin42> SuperLag: I guess that's a bug then - I'd use vmstat to see if it's memory related at all (I doubt it unless you've got 30GB of dirty write data currently queued up to a slow device)
[19:46] <penguin42> SuperLag: and maybe top/perf to see where the times going - but it might just be a simple bug or a GL problem
[19:46] <SuperLag> https://paste.ubuntu.com/6412377
[19:47] <SuperLag> penguin42: I do have the VM running on an HDD.
[19:47] <SuperLag> is on an SSD
[19:47] <SuperLag> / is on an SSD, that is
[19:48] <SuperLag> /usr/local, /home, and /opt are on the HDD, as well as all the VMs
[19:48] <SuperLag> I was thinking of adding a second SSD for the HDD to use for write caching.
[19:48] <penguin42> well plenty of free memory, not much read/writing going on - a bit of writing but not vast
[19:48] <SuperLag> but I've never done anything like that before, and don't know how... I've read one post that outlines it
[19:49] <FernandoMiguel> SuperLag: maybe 3D animation issue
[19:49] <SuperLag> I have dual displays, and when it's drawing the two windows, it has one on each display
[19:51] <SuperLag> the animation I'm referring to is if you have multiple windows from the same app open, and you click on the icon to show all open windows.... the Linux answer to OS X's Expose.
[19:51] <SuperLag> add to that I have two widescreen displays turned into a vertical orientation
[19:52] <SuperLag> ATI RV610 for video
[19:52] <SuperLag> using the radeon driver
[19:54] <penguin42> I wonder if you're just hitting a corner case where the driver sucks?  e.g. try dropping down to a single display or try rotating them?
[19:57] <SuperLag> it was definitely improved
[19:57] <SuperLag> but still quite slow
[19:57] <SuperLag> maybe I should get a new enough card that I can use the Catalyst drivers? :)


[04:38] <r4y> I want to know if there is a program just to view what the bit rate of each individual audio file is as a list of files?
[04:41] <r4y> Never mind, Rhythmbox does what I was asking for.
[04:41] <r4y> Does Banshee?
[12:50] <duanedesign> mmll./14


[00:00] <arraybolt3> You can look at the diff between `spinner` (/usr/share/plymouth/themes/spinner) and the ubuntucinnamon-spinner theme and see exactly what changed between the two.
[00:00] <arraybolt3> Or better yet, I can provide that diff:
[00:00] <tsimonq2> ubuntu-release: Speaking of fixes, Ubuntu Unity takes two minutes to log out, I have a tested fix in hand, will target for SRU because doing before release means an Ubuntu Desktop and Edubuntu respin.
[00:01] -queuebot:#ubuntu-release- Unapproved: borgbackup (noble-proposed/universe) [1.2.7-2build3 => 1.2.8-1] (no packageset) (sync)
[00:01]  * sil2100 twitches on the floor
[00:01] <sil2100> ;)
[00:01] <tsimonq2> hang in there sil2100, almost there ;)
[00:03] <arraybolt3> https://termbin.com/hcrh
[00:04] <arraybolt3> sil2100: ^ that's everything different between `spinner` and `ubuntucinnamon-spinner`. In short, branding differs, some effects that were enabled in ubuntucinnamon-spinner before the change are preserved, the password box is moved down to where it doesn't look like a disaster (and that change was taken from the also known-good `bgrt` theme), and that's it.
[00:05] <arraybolt3> `spinner` should be at /usr/share/plymouth/themes/spinner on all Ubuntu 24.04 desktop systems, and `bgrt` at /usr/share/plymouth/themes/bgrt, so these are files that were part of Ubuntu being reused in Ubuntu.
[00:05] <Eickmeyer> I'm considering bug 2037015 RC for Edubuntu Raspberry Pi. Unfortunately, I have no way to contact Daniel about it.
[00:05] -ubottu:#ubuntu-release- Bug 2037015 in webkit2gtk (Ubuntu) "Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install" [Medium, In Progress] https://launchpad.net/bugs/2037015
[00:05] -queuebot:#ubuntu-release- Unapproved: accepted borgbackup [sync] (noble-proposed) [1.2.8-1]
[00:06] <arraybolt3> Eickmeyer: I have a Pi 4. Downloading image now.
[00:06] <sil2100> Ok, let me check that out in a moment. For now I want to start prepublishing since this is someting we need to do a bit earlier, but of course I'd still advertise for 0-day SRUs
[00:06] <jbicha> Eickmeyer: it's not possible for webkit2gtk to block the release now. It takes like 3 days to build on riscv64
[00:06] <Eickmeyer> jbicha: That's just too bad. It's RC.
[00:06] <Eickmeyer> sil2100: It can't be 0-day. Affects oem-config.
[00:07] <jbicha> you're welcome to update the release notes
[00:07] <Eickmeyer> jbicha: no
[00:07] <sil2100> Eickmeyer: I mentioned arraybolt3's part
[00:07] <Eickmeyer> sil2100: Oh.
[00:07] <sil2100> I didn't check your bug yet!
[00:07] <waveform> that's release noted for the main ubuntu desktop on pi :D
[00:07] <sil2100> waveform: thank you
[00:07] <Eickmeyer> waveform: Edubuntu will have no 24.04.1 for Pi.
[00:07] <Eickmeyer> We have to get it right the first time.
[00:08] <sil2100> Eickmeyer: oh, why no .1?
[00:08] <arraybolt3> Eickmeyer: Do you mean no 24.04? Is there no chance of having a 24.04.1?
[00:08]  * arraybolt3 goes speed-hunting for my micro-HDMI cable
[00:08] <Eickmeyer> sil2100: This is our first image for Pi. We aren't allowed to have an LTS for it.
[00:08] <vorlon> arraybolt3: ok so why does fixing the positioning of the passphrase prompt involve changes to all of the graphical assets
[00:08] <vorlon> Eickmeyer: that's a rule for flavors not for architecturse
[00:08] <jbicha> does pi require oem-config for everyone?
[00:09] <Eickmeyer> vorlon: That's what bdmurray told me.
[00:09] <waveform> jbicha, for desktop
[00:09] <waveform> because the new installer doesn't handle pre-installed images (yet)
[00:09] <arraybolt3> vorlon: I explained to sil2100 earlier that it was because I'm taking a known-good theme and re-customizing it so that it replaces a known-bad theme.
[00:09] <waveform> arraybolt3, if you want a preview of what the install slides look like: https://launchpadlibrarian.net/723951216/slide-corruption-2.jpg
[00:09] <arraybolt3> ubuntucinnamon-spinner is out of date in multiple ways and had no fewer than *three* bugs in it, one of which I only discovered from fixing the other two.
[00:10] <arraybolt3> In the interest of fixing everything and also playing it safe, I copied the `spinner` theme, fixed the passphrase prompt positioning the same way that the `bgrt` theme in Ubuntu does it, reapplied Ubuntu Cinnamon branding to it, and then uploaded that.
[00:10] <jbicha> Eickmeyer: that sounds like it looks bad but does it only affect the slideshow part of the installer?
[00:10] <arraybolt3> There should be no chance of that being bad *unless* ubuntu cinnamon's customizations (which were there before I touched the package) cause problems, and those I will not touch because I am not the Cinnamon flavor lead.
[00:11] <waveform> and here's my release note regarding it https://discourse.ubuntu.com/t/noble-numbat-release-notes/39890#raspberry-pi-104 (largely copied from mantic)
[00:11] <Eickmeyer> jbicha: Yes, but first-touch experiences are kindof a big thing. It's kindof like a first impression when you walk in the door for an interview.
[00:11] <arraybolt3> waveform, Eickmeyer Is there any point in me testing RPi then? If this is a known issue and already diagnosed, I could probably use my time better elsewhere.
[00:12] <Eickmeyer> arraybolt3: It's a known issue already diagnosed with a fix ready to go.
[00:12] <arraybolt3> kk
[00:12] <arraybolt3> but it sounds like 24.04.1 might be something you're allowed to do anyway, so that's good hopefully
[00:13] <Eickmeyer> arraybolt3: I hope, but it seems the release team members have kindof given me mixed messages about it.
[00:13] <jbicha> Eickmeyer: so there's https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20 but like I said it's too late for tomorrow's release
[00:13] -ubottu:#ubuntu-release- Merge 20 in webkit-team/webkit "Convert disable-dmabuf-nvidia.patch to disable-dmabuf.patch" [Opened]
[00:13] <Eickmeyer> jbicha: Edubuntu can release later if need-be.
[00:14] <vorlon> arraybolt3: ok.  I come down on the side that you should only be making the minimum necessary fix at this point and not changing other things "just in case".  But as sil2100 is currently around I'm going to let him make the final call
[00:14] <Eickmeyer> But I'm fuming about this.
[00:15] <jbicha> it's ANZAC day so not really possible to reach Daniel now. Daniel doesn't have upload rights for Ubuntu anyway
[00:15] <Eickmeyer> jbicha: Somebody, anybody. I can get a core dev if I need one.
[00:16] <sil2100> vorlon, arraybolt3: my initial recommendation would be "0-day SRU", but if the affected flavors still insist on doing it then second recommendation would be the 'very minimal fix' :)
[00:16] <jbicha> I'm probably the core dev you need, let me take a look
[00:16] <Eickmeyer> sil2100: Regarding the plymouth issue, I can speak to that. There was an accessibility issue (font too small) that was changed that I'm for. (I'm a secondary contact for Cinnamon).
[00:17] <vorlon> sil2100: we're talking about a single affected flavor, we have a flavor contact who's signed off on fixing this, I'm fine with doing the ubuntucinnamon respin for it but I'm not going to overrule you
[00:17] <vorlon> sil2100: we do have the release management capacity to get it done in time for morning, and the flavor contact signoff *implies* they're committing the testing capacity
[00:18] <Eickmeyer> I certainly am. I can test in the morning and this evening if need be.
[00:18] <vorlon> "in the morning" is too late
[00:18] <arraybolt3> I also have testing capacity here for tonight.
[00:18] <vorlon> the release goes out on UK time
[00:18] <arraybolt3> I did all of the needed testing for Cinnamon just a bit ago and that's how I found this. It didn't take long, I can do it again before going to bed.
[00:19] <Eickmeyer> Somebody told me that flavors have the ability to delay if necessary.
[00:19] <vorlon> Eickmeyer: I think bdmurray told you "no LTS for pi" before he and I had discussed and AFAIK he is not insisting on that rule
[00:19] <sil2100> Yes, as I said I'm fine with both the options, so I agree with vorlon. Of course I still *recommend* 0-day SRUs, but I'm fine with a fix and best the minimal fix. Because this could cause the flavor to be released late
[00:19] <sil2100> arraybolt3: is it possible to get the minimal-change version of the fix by any chance? :)
[00:19] <vorlon> Eickmeyer: you have the ability to defer final signoff and publication of the release, but you don't have an open-ended carte blanche to make changes to the noble release pocket
[00:19] <Eickmeyer> vorlon: Ok. In that case, jbicha, I'm fine with RN'ing the corruption since there will be a 24.04.1 of Edubuntu Rpi.
[00:19] <utkarsh2102> ok, time to sleeeeep for me. If you want me to look at anything in the morning, please let me know.
[00:20] <utkarsh2102> vorlon, sil2100^
[00:20] <sil2100> utkarsh2102: ok, gnite!
[00:20] <vorlon> utkarsh2102: ack, good night
[00:20] <arraybolt3> sil2100, vorlon: I like the minimal fix rule. I think though that this is a minimal fix, but not in the normal direction. The alternative is to tweak a theme with known problems to fix the visible problems and hope that doesn't leave more problems. If anything's going to cause damage, the "usual minimal fix" is going to be it. It will come with a lower *regression* potential but a higher
[00:20] <arraybolt3> (potentially much higher) total bug potential.
[00:20] <Eickmeyer> vorlon: That's all I mean.
[00:20] <arraybolt3> I'm willing to go with the usual minimal fix, but know in advance I think this is a bad idea.
[00:21] <arraybolt3> (The fix is minimal if you look at the spinner theme, which is known to be good, and then see what I changed.)
[00:21] <arraybolt3> which diff I shared as https://termbin.com/hcrh
[00:21] <jbicha> the Pi installer doesn't use ubuntu-desktop-provision currently, right? u-d-p is cool because it installs updates before first boot
[00:21] <Eickmeyer> sil2100, vorlon: Switching to Cinnamon hat: I trust arraybolt3's judgement on this.
[00:21] <Eickmeyer> jbicha: Correct.
[00:21] <Eickmeyer> jbicha: It's completely oem-config, therefore ubiquity in nature.
[00:22] <arraybolt3> anyway, I'l lstart prepping the usual minimal fix for now and we'll see where things go.
[00:22] <sil2100> arraybolt3, Eickmeyer: re: the theme, ok
[00:22] <vorlon> jbicha: so where is ubuntu-desktop-provision for the pi, I wanted this for 24.04.0 :P
[00:22] <vorlon> jbicha: oh, by ubuntu-desktop-provision you mean ubuntu-desktop-bootstrap
[00:23] <vorlon> sorry, yes, we're talking about the first boot experience here on preinstalled images
[00:23] <dbungert> 3 snaps from 1 repo problems
[00:23] <jbicha> vorlon: that's not me 🙈
[00:23] <Eickmeyer> vorlon: I think that's a question for waveform :)
[00:23] <vorlon> Eickmeyer: it's not
[00:23] <Eickmeyer> Oh?
[00:23]  * arraybolt3 watches an installer pingpong between teams
[00:23] <vorlon> it's a question for the Ubuntu Desktop Team which is why I was tweaking jbicha
[00:23] <sil2100> arraybolt3: makes sense - just please please please triple check it if everything's fine. Did you test the upload already somehow on a live system?
[00:23]  * waveform is staying studiously quiet...
[00:23] <vorlon> (who is also not responsible for delivery)
[00:23] <arraybolt3> sil2100: I tested this on an installed system with disk encryption enabled and it looked fine to me. I'll do one more reboot and watch it like a hawk just in case.
[00:24] <Eickmeyer> I think It's eventually going to be gnome-initial-setup, is it not jbicha ?
[00:24] <sil2100> arraybolt3: since we won't have time for a respin of the package without delaying!
[00:24] <sil2100> arraybolt3: ok, so is the right thing in the queue right now?
[00:24] <arraybolt3> It is.
[00:24] <sil2100> arraybolt3: then reviewing again, thank you for all the context and discussion o/
[00:25] <jbicha> Eickmeyer: um, I guess we're still using g-i-s for 24.04 LTS but there's a goal for a new Flutter app to replace g-i-s for 24.10 or so
[00:25] <vorlon> right, I'm afk for dinner now.  I'll be back in roughly an hour.  I still have the baton for triggering {l,k}ubuntu respins once calamares migrates and publishes
[00:25] <arraybolt3> Thanks for your patience with me and for hashing it out!
[00:25] <arraybolt3> btw I did just do another check and it looks perfect from what I can tell.
[00:25] <Eickmeyer> vorlon: bon appetit
[00:26] <sil2100> vorlon: o/
[00:27] <sil2100> Ok, accepting
[00:28] -queuebot:#ubuntu-release- Unapproved: accepted ubuntucinnamon-artwork [source] (noble-proposed) [24.04.1]
[00:28] <arraybolt3> ta!
[00:30] <Eickmeyer> Ubuntu Studio and Edubuntu (all archs) completely tested and marked as ready.
[00:30] <sil2100> vorlon: we'll need to respin cinnamon once that lands
[00:30] <sil2100> Eickmeyer: \o/
[00:30] <sil2100> \o\
[00:30] <sil2100> /o/
[00:30] <Eickmeyer> sil2100: Now do the ASCII Macarena.
[00:30] <sil2100> ...too tired
[00:31] <Eickmeyer> LOL
[00:31] <sil2100> I used up all my strength just now
[00:31] <Eickmeyer> I don't blame you. Quite late in your tz.
[00:31] <Eickmeyer> (or... early?)
[00:31] <utkarsh2102> sil2100: does it need an unblock, too?
[00:31] <sil2100> Yes, it is done
[00:31] <utkarsh2102> super!
[00:32] <waveform> does this mean I get to delete another bit of the "known issues" release notes? Or are we not re-spinning the main pi desktop images
[00:32] <Eickmeyer> waveform: afaik, not respinning because I dropped my protest.
[00:33] <waveform> okay, no prob -- sorry, having trouble keeping track at this time!
[00:35] <waveform> incidentally, the last I heard was that the pre-installed images were *not* going to be using g-i-s in place of oem-config because it can't handle what's required, and that there'll be a flutter app for this at some point (but then I also heard there'll be a flutter app to replace oem-config this cycle and I didn't quite believe that either https://code.launchpad.net/~waveform/ubiquity/+git/ubiquity/+merge/452559 )
[00:37] <Eickmeyer> waveform: Yep, that's what I heard too. Alas...
[00:37] <Eickmeyer> Ope, that's from October!
[00:37] -queuebot:#ubuntu-release- Unapproved: gnome-session (noble-proposed/main) [46.0-1ubuntu4 => 46.0-1ubuntu4.1] (ubuntu-desktop)
[00:38] <Eickmeyer> arraybolt3: Were you going to mark bug 2063379 as "Fix Committed"?
[00:38] -ubottu:#ubuntu-release- Bug 2063379 in ubuntucinnamon-artwork (Ubuntu) "Disk decryption prompt is broken" [Undecided, New] https://launchpad.net/bugs/2063379
[00:38] <tsimonq2> ubuntu-release: hi yes gnome-session is me, I'm personally neutral on whether it goes in as a 0-day SRU or a full-fledged 7-day SRU
[00:38] <tsimonq2> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383
[00:38] -ubottu:#ubuntu-release- Launchpad bug 2063383 in gnome-session (Ubuntu Noble) "[SRU] Ubuntu Unity takes 90 seconds to log out" [High, Confirmed]
[00:39] <Eickmeyer> 90 secs? yeesh.
[00:39] <tsimonq2> The alternative to it being an SRU is respinning and retesting all of Edubuntu and Ubuntu Desktop with a very, very small margin of error
[00:40] <tsimonq2> so ... no :P
[00:40] <Eickmeyer> tsimonq2: It's already resolved. :P
[00:40] <Eickmeyer> tsimonq2: Oh, nvm.
[00:41] <Eickmeyer> Here I was, keeping up and changing hats like crazy and the ONE TIME... smh...
[00:41] <tsimonq2> hah
[00:42] <tsimonq2> calamares started migrating to the release pocket a min ago \o/
[00:42] <jbicha> Eickmeyer: since webkit2gtk can't be a 0-day, let's wait until Debian accepts the merge request. Won't be until at least next week because of the holiday
[00:43] <Eickmeyer> jbicha: Yeah, a 0-day wouldn't affect oem-config anyhow, so anytime between now and August is good for 24.04.1.
[00:44] <wxl> OH
[00:44] <wxl> time to trigger respins tsimonq2 ?
[00:44] <tsimonq2> wxl: slow publisher can be slow
[00:45] <wxl> bah
[00:45] <tsimonq2> shouldn't be too much else in this publisher run though, that's the good news
[00:45] <tsimonq2> I just have no idea how long it takes the internal mirrors to update, so probably better if vorlon pokes
[00:46] <tsimonq2> (If I'm the one to respin, I usually give it like an hour after all the binaries are published in the release pocket, zero idea if that's overly cautious or just sane.)
[00:47] <jbicha> ubuntu-release: please unblock rust-alacritty. It's not actually seeded but it's a terminal app so germinate/whatever gets confused
[00:52] <Eickmeyer> tsimonq2: IME, that's sane. I've seen respins with the wrong stuff in the manifest unless I've waited an hour.
[00:52] <wxl> yikes well i'm out for now
[00:53] <sil2100> jbicha: wait, so seeded-in-ubuntu is wrong by saying cinnamon?
[00:53] <jbicha> sil2100: yes 🤷
[00:54] <sil2100> jbicha: ...but I see it in the cinnamon manifest
[00:55] <sil2100> alacritty, from rust-alacritty source, is in the squashfs of cinnamon
[00:56] <jbicha> sil2100: ok, but reverse-depends shows virtually nothing pulls it in. My upload fixes a serious issue for those who use the app https://launchpad.net/ubuntu/+source/rust-alacritty/0.13.2-1ubuntu1
[00:57] <sil2100> It is a seeded package. A serious issue != release blocking issue. Adding another unblock to the list of unblocks is not something I would prefer to happen at this stage
[00:58] <jbicha> Eickmeyer: is /usr/bin/alacritty in a new Cinnamon install? is it in the live environment?
[00:58] <Eickmeyer> jbicha: I'll have to check, I don't run it regularily.
[00:58] <jbicha> it'll take me at least 10 minutes to download
[00:59] <Eickmeyer> jbicha: I'll have it in about a minute from my server.
[01:01] <sil2100> Ok, so I need to take at least a quick nap, but I will be in an hour or two
[01:02] <Eickmeyer> jbicha: Confirmed the presence of /usr/bin/alacritty
[01:02] <Eickmeyer> sil2100: Have a good snooze.
[01:02] <jbicha> Eickmeyer: is it still there after install?
[01:02] <Eickmeyer> I'll give it a quick install and find out.
[01:06] <tsimonq2> "* Chose alacritty out of x-terminal-emulator to satisfy libfile-desktopentry-perl"
[01:08] <Eickmeyer> ^ That would point to yes for the manifest.
[01:09] <arraybolt3> Pretty sure allacritty is installed on the cinnamon system here
[01:09] <arraybolt3> can't spell
[01:09] <arraybolt3> It is indeed.
[01:09]  * jbicha looks disapprovingly at germinate
[01:10] <arraybolt3> Eickmeyer: about that bug... yeah I probably should, I forget to do that stuff
[01:10] <Eickmeyer> arraybolt3: Indeed. Wasn't sure if it was intentional or not, but yeah, you should be in the habit of doing that. When it hits the release pocket, it'll fix-release itself, but yeah.
[01:11] <Eickmeyer> jbicha: I didn't check Edubuntu for alacritty.
[01:12] <jbicha> Eickmeyer: no need, germinate just doesn't like Ubuntu Cinnamon
[01:12]  * Eickmeyer shakes fist at germinate
[01:12] <arraybolt3> What's fun is that Ubuntu Cinnamon has GNOME Terminal installed too
[01:13] <arraybolt3> so there are two terminal emulators in it
[01:13] <jbicha> yes but what about second terminal?
[01:13] <arraybolt3> "don't think he knows about second terminal, jbicha"
[01:13] <Eickmeyer> ...he doesn't know about second terminal!
[01:13] <Eickmeyer> HAHAHAHAHAHA JINX arraybolt3
[01:14] <arraybolt3> What about text editors? Browsers? Games and utilities? File managers, system monitors! He knows about them doesn't he? "I wouldn't count on it."
[01:14] <Eickmeyer> XD
[01:14] <arraybolt3> yes I was an LotR addict for a while
[01:15] <Eickmeyer> arraybolt3: Glad for the font fix. The "Remove the installation media and press ENTER" is barely readable on my screen.
[01:15] <arraybolt3> oof. Glad we caught it :D
[01:16] <jbicha> ItzSwirlz: hi, did you know that Ubuntu Cinnamon ships Alacritty in addition to GNOME Terminal?
[01:18] <vorlon> calamares is migrated but not yet published
[01:19] <vorlon> Eickmeyer: UbuntuStudio marked as ready> uh but there's a calamares change in flight, which also means an UbuntuStudio respin
[01:19] <arraybolt3> Ubuntu Studio doesn't use Calamares anymore.
[01:19] <Eickmeyer> vorlon: Negative, no calamareis... ^
[01:19] <arraybolt3> It's using ubuntu-desktop-provision.
[01:20] <Eickmeyer> vorlon: Remember your branch in livecd-rootfs? ubuntustudio-shellfish-allergy?
[01:20] <vorlon> Eickmeyer: oh, sorry, that's ubuntu-unity not UbuntuStudio, why was I thinking otherwise?
[01:20] <Eickmeyer> vorlon: It's been a long release.
[01:20] <vorlon> Eickmeyer: oh - software-properties-qt is orthogonal to calamares, that's the confusion
[01:21] <Eickmeyer> Ah, yes.
[01:21] <Eickmeyer> BTW, that fix works, I tested it.
[01:21] <Eickmeyer> GGs tsimonq2 ^
[01:21] <vorlon> which means, hrm, I'm not sure there's been coordination with Ubuntu Unity folks wrt the fact that a respin is coming for calamares
[01:21] <vorlon> given the impact it's clear it needs to happen
[01:22] <arraybolt3> rs2009: ^
[01:22] <vorlon> but did anyone give rs2009 a heads-up?
[01:22] <Eickmeyer> I believe someone was talking to him on Matrix?
[01:22] <arraybolt3> I didn't know that Unity was going to require a respin. We didn't *need* to do it for the beta release last time IIRC...
[01:22] <tsimonq2> I pinged him a few hours ago, let me try again elsewhere
[01:22] <arraybolt3> So I didn't bring his attention to it.
[01:23] <jbicha> the alacritty issue only affects Wayland sessions (so not Ubuntu Cinnamon). Please consider adding it to the 0-day SRU list. I believe you're respinning for ubuntucinnamon-artwork but I understand if you want to limit the unblocks now
[01:23] <tsimonq2> arraybolt3: This was a fix to a Calamares module all three flavors use :)
[01:23] <arraybolt3> you're right
[01:23] <arraybolt3> sigh
[01:23] <jbicha> the alacritty issue also fixes its ftbfs
[01:24] <vorlon> arraybolt3: beta is a little flexible; release requires all flavors to be on the same page wrt the contents of the release pocket
[01:25] <arraybolt3> kk
[01:25] <vorlon> but also, the issue is quite severe and would affect all flavors
[01:37] <arraybolt3> So far it looks like both rs2009 and Maik are not available.
[01:37] <arraybolt3> I know rs2009 said something in this channel about Tobiyo also being a point of contact
[01:38] <arraybolt3> I just pinged them and they responded immediately:
[01:38] <arraybolt3> Tobiyo Kuujikai
[01:38] <arraybolt3> feel free to respin
[01:38] <arraybolt3> i think both maik and rudra are asleep right now
[01:38] <arraybolt3> but i'll pass the message on
[01:38] <arraybolt3> yes that's me
[01:38] <vorlon> right, so they don't get a choice in respinning or not, the point here is that they be aware that retesting is needed
[01:39] <arraybolt3> kk. Then they should now be aware. I'll do the testing myself if necessary.
[01:40] <arraybolt3> btw Ubuntu MATE looks to be just about over the line
[01:40] <arraybolt3> I'm doing the last required testcase now
[01:49] <vorlon> waiting for rmadison to stop lying to me that there is no calamares in -proposed and old calamares in release
[02:02] <arraybolt3> Ubuntu MATE is all tested out.
[02:03] <arraybolt3> And the straggler is once again Kylin, so...
[02:03] <arraybolt3> *starts zsync*
[02:22] <vorlon> ubuntucinnamon-artwork has migrated, but that also won't hit until yet another subsequent publisher run
[02:24] <tsimonq2> $ rmadison --suite noble calamares calamares | 3.3.5-0ubuntu4 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
[02:24] <tsimonq2> \o/
[02:28] <vorlon> yep, spinning now
[02:28] <vorlon> klunitÿbuntu respinning
[02:29] <tsimonq2> hahahahahah
[02:29] <Eickmeyer> LOL
[02:29] <jbicha> vorlon: could you let qwertone through the NEW queue?
[02:32] <arraybolt3> did someone just call all my hard work kludgebuntu?!
[02:33] <Eickmeyer> No. klunitÿbuntu.
[02:33] <vorlon> jbicha: .
[02:33] -queuebot:#ubuntu-release- New: accepted qwertone [amd64] (noble-proposed) [0.4.0-1ubuntu1]
[02:33] -queuebot:#ubuntu-release- New: accepted qwertone [ppc64el] (noble-proposed) [0.4.0-1ubuntu1]
[02:33] -queuebot:#ubuntu-release- New: accepted qwertone [armhf] (noble-proposed) [0.4.0-1ubuntu1]
[02:33] -queuebot:#ubuntu-release- New: accepted qwertone [s390x] (noble-proposed) [0.4.0-1ubuntu1]
[02:34] -queuebot:#ubuntu-release- New: accepted qwertone [arm64] (noble-proposed) [0.4.0-1ubuntu1]
[02:34] -queuebot:#ubuntu-release- New: accepted qwertone [riscv64] (noble-proposed) [0.4.0-1ubuntu1]
[02:38] <arraybolt3> actually it was tsimonq2 who did the hard work of fixing the GRUB bug, so nvm :P
[03:01] -queuebot:#ubuntu-release- Unapproved: pdfgrep (noble-proposed/universe) [2.1.2-1build3 => 2.2.0-0.1] (no packageset) (sync)
[03:02] -queuebot:#ubuntu-release- Unapproved: pgpcre (noble-proposed/universe) [0.20190509-6 => 0.20190509-7] (no packageset) (sync)
[03:04] -queuebot:#ubuntu-release- Unapproved: poco (noble-proposed/universe) [1.11.0-4.1build2 => 1.13.0-6] (no packageset) (sync)
[03:04] -queuebot:#ubuntu-release- Unapproved: sipgrep (noble-proposed/universe) [2.1.0-2build3 => 2.2.0-2] (no packageset) (sync)
[03:04] <tsimonq2> Confirmed the OEM boot entry works on the latest Lubuntu daily 🎉
[03:06] -queuebot:#ubuntu-release- Unapproved: accepted pgpcre [sync] (noble-proposed) [0.20190509-7]
[03:06] -queuebot:#ubuntu-release- Unapproved: accepted sipgrep [sync] (noble-proposed) [2.2.0-2]
[03:06] -queuebot:#ubuntu-release- Unapproved: accepted poco [sync] (noble-proposed) [1.13.0-6]
[03:06] -queuebot:#ubuntu-release- Unapproved: accepted pdfgrep [sync] (noble-proposed) [2.2.0-0.1]
[03:19] -queuebot:#ubuntu-release- New binary: poco [amd64] (noble-proposed/universe) [1.13.0-6] (no packageset)
[03:20] -queuebot:#ubuntu-release- New binary: poco [s390x] (noble-proposed/universe) [1.13.0-6] (no packageset)
[03:21] -queuebot:#ubuntu-release- New binary: poco [armhf] (noble-proposed/universe) [1.13.0-6] (no packageset)
[03:21] -queuebot:#ubuntu-release- New binary: poco [ppc64el] (noble-proposed/universe) [1.13.0-6] (no packageset)
[03:23] -queuebot:#ubuntu-release- Unapproved: glycin-loaders (noble-proposed/universe) [0.1.2+dfsg-2 => 1.0.1+dfsg-0ubuntu1] (no packageset)
[03:25] -queuebot:#ubuntu-release- New binary: poco [arm64] (noble-proposed/universe) [1.13.0-6] (no packageset)
[03:25] -queuebot:#ubuntu-release- Unapproved: accepted glycin-loaders [source] (noble-proposed) [1.0.1+dfsg-0ubuntu1]
[03:27] -queuebot:#ubuntu-release- Unapproved: loupe (noble-proposed/universe) [45.3-2build1 => 46.2-0ubuntu1] (no packageset)
[03:30] -queuebot:#ubuntu-release- Unapproved: accepted loupe [source] (noble-proposed) [46.2-0ubuntu1]
[03:36] <rs2009> hey everyone, just to confirm, I'm aware the Unity ISO's being respun +1
[03:37] <sil2100> o/
[03:37] <sil2100> I still see we didn't respin Cinnamon, so let me do that
[03:42] <sil2100> Ok, rebuild started
[03:48] <Eickmeyer> sil2100: I'll keep an eye out, ready to test.
[03:51] <sil2100> Eickmeyer: thank you o/
[03:51] <Eickmeyer> sil2100: Hope you had a good nap.
[03:52] <arraybolt3> So... I would be able to knock out Kylin all by myself, buuuut it turns out that now that there is no maybe-ubiquity screen, there's also no easy way to get the live environment out of Chinese! So someone who is fluent in Chinese (i.e., not myself) will need to figure that out. I'm sure the UI is beautiful if you know the language, but I can't hardly tell Chinese and hieroglyphs from each
[03:52] <arraybolt3> other :P
[03:53] <Eickmeyer> arraybolt3: I wouldn't worry about it.
[03:53] <arraybolt3> anyways, once I'm done with the install tests, I'll pivot to Ubuntu Unity since it's not gotten any testing so far.
[03:54] <arraybolt3> Eickmeyer: It's been a concern at least twice in the past? Kylin is notoriously bad at getting testers it seemed.
[03:54] <Eickmeyer> arraybolt3: Sadly, and I hate to sound callous, but that's up to them.
[03:55] <arraybolt3> true
[04:00] <arraybolt3> Pivoting to Ubuntu Unity now.
[04:01] -queuebot:#ubuntu-release- Unapproved: amberol (noble-proposed/universe) [0.10.3-2build1 => 0.10.3-3ubuntu1] (no packageset)
[04:06] -queuebot:#ubuntu-release- Unapproved: accepted amberol [source] (noble-proposed) [0.10.3-3ubuntu1]
[04:24] <Eickmeyer> Testing Cinnamon...
[04:27] <tsimonq2> Starting on Kubuntu. I plan on marking Lubuntu as ready if guiverc reports back with positive results on his pending tests. :)
[04:29]  * guiverc warns many of those installs are on old box; slow spinning rust drive etc..  (where issue with grub bug occurred)
[04:29] <tsimonq2> I still have enough coffee to last me a while, no worries ;)
[04:32] <tsimonq2> Can confirm OEM works in Kubuntu, too. That last minute debian-cd + {k,l}ubuntu-installer-prompt combo worked!
[04:34] -queuebot:#ubuntu-release- Unapproved: aardvark-dns (noble-proposed/universe) [1.4.0-5 => 1.6.0-1ubuntu1] (no packageset)
[04:36] -queuebot:#ubuntu-release- Unapproved: accepted aardvark-dns [source] (noble-proposed) [1.6.0-1ubuntu1]
[04:40] -queuebot:#ubuntu-release- Unapproved: lincity-ng (noble-proposed/universe) [2.10.1-1 => 2.10.2-1] (no packageset) (sync)
[04:41] -queuebot:#ubuntu-release- Unapproved: accepted lincity-ng [sync] (noble-proposed) [2.10.2-1]
[04:41] -queuebot:#ubuntu-release- Unapproved: libtranscript (noble-proposed/universe) [0.3.3-1 => 0.3.3-1.1] (no packageset) (sync)
[04:41] -queuebot:#ubuntu-release- Unapproved: baycomepp (noble-proposed/universe) [0.10-17 => 0.10-18] (no packageset) (sync)
[04:42] -queuebot:#ubuntu-release- Unapproved: ganglia (noble-proposed/universe) [3.7.2-6.1build3 => 3.7.2-7] (no packageset) (sync)
[04:42] <Eickmeyer> Cinnamon done testing. Would mark as ready, but unable as ItzSwirlz  hasn't added me to ~ubuntucinnamon-release.
[04:43] <Eickmeyer> Plymouth works as expected.
[04:45] -queuebot:#ubuntu-release- Unapproved: accepted ganglia [sync] (noble-proposed) [3.7.2-7]
[04:46] -queuebot:#ubuntu-release- Unapproved: accepted baycomepp [sync] (noble-proposed) [0.10-18]
[04:46] -queuebot:#ubuntu-release- Unapproved: accepted libtranscript [sync] (noble-proposed) [0.3.3-1.1]
[04:52] <Eickmeyer> Pinged him on Matrix to mark as ready, but if ubuntu-release wants to mark Ubuntu Cinnamon as ready, feel free.
[04:54] <tsimonq2> ubuntu-release: Another release blocker bug found in Calamares. When installing in OEM mode, /home/oem is now owned by root, apparently.
[04:54] <tsimonq2> Simple, one-line chown fix to my understanding, arraybolt3 is working on a bug report with details, I'm going to meet him in the middle, testing the fix.
[04:56] -queuebot:#ubuntu-release- New binary: poco [riscv64] (noble-proposed/universe) [1.13.0-6] (no packageset)
[04:58] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403
[04:58] -ubottu:#ubuntu-release- Launchpad bug 2063403 in calamares-settings-ubuntu (Ubuntu) "/home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable" [Critical, Triaged]
[04:59] <tsimonq2> utkarsh2102, sil2100 etc ^^^^^^
[04:59] <arraybolt3> Preparing fix now.
[05:00] <arraybolt3> ubuntu-release: this will require *another* klunitÿbuntu respin, but it will not require total retests after the respins, so I'm going to continue testing of the existing ISOs after preparing the fix so that this goes as smoothly as possible.
[05:08] <rs2009> +1 from me
[05:37] -queuebot:#ubuntu-release- Unapproved: calamares-settings-ubuntu (noble-proposed/universe) [1:24.04.38 => 1:24.04.39] (lubuntu, ubuntustudio)
[05:38] <arraybolt3> ubuntu-release: ^ Fix for the aforementioned OEM-mode-crippling bug. Thank you for your help! tsimonq2: you have something to test now :) I tested this fix in Kubuntu only as a smoke test, OEM configuration mode starts normally and the user can exit OEM configuration mode and the system can be set up properly after that.
[05:41] <tsimonq2> I can confirm the fix for Kubuntu works, testing for Lubuntu and Ubuntu Unity now, will report back with results
[05:56] <tsimonq2> This fixes the bug for Lubuntu, this is a release blocker for us.
[05:58] <tsimonq2> Rudra +1ed above for Ubuntu Unity, double checking that, Kubuntu has not officially asked for this respin but I expect to hear more when people wake up
[06:00] <tsimonq2> Ubuntu Unity works, updating the bug report as such
[06:10] <guiverc> tsimonq2, if you want to edit https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043 , it mentions on bug https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060897 that "fix committed - needs confirmation" ... alas fix FAILED; so remove the committed/confirmation message maybe.
[06:10] -ubottu:#ubuntu-release- Launchpad bug 2060897 in xubuntu-meta (Ubuntu) "Xubuntu installation failed: RuntimeError: aborting install since no mirror is usable" [Undecided, In Progress]
[06:13] <tsimonq2> guiverc: Sure, could you update the bug?
[06:13] <vorlon> tsimonq2: I will review calamares-settings-ubuntu for acceptance. However, calling a "release blocker" something that invalidates a feature that AIUI it had not occurred to anyone until 24 hours before the release deadline should even exist in the image, and forces respins of 3 flavors, is going to be subject to negotiation with the European squad when they come online.  Per discussion this
[06:13] <vorlon> afternoon, the OEM changes for calamares flavors were accepted opportunistically with the understanding that if the implementation is incomplete, it's not a release blocker to fix or roll back.
[06:14] <vorlon> reviewed + accepted so it can build and so that this does not cause further delays waiting for that once a final decision is made
[06:14] -queuebot:#ubuntu-release- Unapproved: accepted calamares-settings-ubuntu [source] (noble-proposed) [1:24.04.39]
[06:17] <arraybolt3> vorlon: This feature has existed for an extended period of time in the images, has had an immense level of effort poured into it to make it work, and was broken because of a small accident that had further-reaching consequences than expected. It's my fault, I'm the one who broke it, and I've been so tied up in work elsewhere in Ubuntu and in my dayjob that this slipped through.
[06:18] <arraybolt3> We've had web browser breakage slip through until the last minute before in the past, this is the same sort of thing. I'm really sorry that I let this happen, and really hope we can move forward. The fix is very simple, small, and tested to be effective.
[06:18] <tsimonq2> It is true that OEM support has been on the images for an extended period of time this cycle, it wasn't written in the span of 24 hours. The boot entry and some of the glue, yes, but this is not a regression as a result of those fixes.
[06:19] <arraybolt3> The OEM feature that tsimonq2 worked on was simply increasing the visiblity of the feature. The feature itself has existed for two or three months.
[06:19] <arraybolt3> Losing it would be a bit like Ubuntu Desktop switching back to Ubiquity the day before release.
[06:19] <vorlon> arraybolt3: that doesn't change the fact that the previous fix for calamares oem mode that we accepted was an opportunistic pick-up.  This is not a release blocker and it's at the discretion of the European squad to decide whether to move forward with the change for 24.04 GA and managing the resulting work on release day
[06:19] <arraybolt3> (not that severe but not far from it)
[06:20] <arraybolt3> vorlon: You're not seeing it. The previous fix for calamares oem mode has no bearing on this.
[06:20] <arraybolt3> The two fixes are entirely unrelated and deal with totally different parts of the same thing.
[06:20] <vorlon> ok you're saying that prior to the [kl]ubuntu-installer-prompt fixes, oem mode existed but was not exposed as a boot option
[06:20] <arraybolt3> tsimonq2's opportunistic fix did not break the feature, an earlier fix for a different issue did. The feature itself has existed without the boot menu entry for a long time.
[06:20] <tsimonq2> vorlon: Correct
[06:20] <arraybolt3> Correct. It was exposed as an application menu entry.
[06:20] <vorlon> but was reachable from the live environment
[06:20] <vorlon> ok
[06:20] <arraybolt3> Yep.
[06:21] <vorlon> that's a fair point
[06:22] <arraybolt3> So this is a long-planned feature breaking at the worst possible time. I know exactly what went wrong to get here, and have planned steps to take to prevent this from repeating.
[06:22] <vorlon> still means you're identifying as a release blocker a feature that is not identified as a required test case on the ISO tracker for these images and is only being caught day-of with implications across three flavors. The final call is still going to be to Europe, I'm off duty by the time it matters. sil2100 bdmurray ginggs
[06:22] <tsimonq2> https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300298/testcases/1305/results
[06:22] <tsimonq2> OEM is a required test case for Kubuntu on the tracker, at least
[06:22] <arraybolt3> so it is on the ISO tracker for Kubuntu.
[06:23] <vorlon> ah
[06:24] <vorlon> this regressed post-beta?
[06:24] <arraybolt3> Correct.
[06:24] <arraybolt3> to be exact it regressed last Friday.
[06:25] <arraybolt3> (that's when the change was uploaded that resulted in the issue.)
[06:27] <vorlon> so wxl marked the OEM test case for beta as 'passed' despite none of https://iso.qa.ubuntu.com/qatracker/milestones/452/builds/299277/testcases/1305/results working as written
[06:27] <guiverc> sorry I think I linked the wrong bug... let me check tsimonq2
[06:28] <arraybolt3> vorlon: That's true. Most of the test cases on the ISO tracker are horrifically out of date, I think even Ubuntu Desktop's testcases.
[06:28] <vorlon> no
[06:28] <arraybolt3> The feature worked as intended at beta time.
[06:28] <vorlon> we take regular MPs to update the test cases
[06:28] <guiverc> Yeah sorry.. ignore my last ^^^   my mistake mixing up bugs.
[06:29] <vorlon> and if people are signing off saying a test is good without following the test case, WHAT ARE YOU DOING
[06:29] <arraybolt3> vorlon: https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300274/testcases/1758/results well this certainly doesn't look like ubuntu-desktop-provision to me
[06:29] <arraybolt3> smells like Ubiquity.
[06:29] <arraybolt3> and that's the core test case for Ubuntu Desktop - install (entire disk).
[06:29] <locutusofborg> bdrung, looks like graa
[06:29] <locutusofborg> graham uploaded with allow-stderr
[06:30] <arraybolt3> or is it? hmm, maybe I read too fast
[06:30]  * guiverc read bug as being https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624   sorry..
[06:30] -ubottu:#ubuntu-release- Launchpad bug 2060624 in grub2 (Ubuntu) "lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice" [Undecided, New]
[06:30] <tsimonq2> guiverc: no worries
[06:30] <vorlon> well, then I have the same harsh criticism of whoever's been submitting 'passed' test results *there* without following the test case
[06:30] <arraybolt3> nope, you're right, Ubuntu Desktop's testcase looks right. I got confused because of flavor testcases.
[06:30] <vorlon> ok
[06:32] <arraybolt3> But basically, this is collectively the result of a long period of the ISO tracker falling into disrepair combined with the most hectic cycle we've had in a long time from what I hear. The fact is the flavors do need to update their testcases, there are an astounding number of out-of-date testcases on that list and everyone who works closely with the flavors knows it. That isn't good. We
[06:32] <arraybolt3> have to fix it. It's too late to fix it now.
[06:32] <arraybolt3> And I should have tested the upload that resulted in this regression before it got this late.
[06:33] <arraybolt3> So this is a whole bunch of failures on the part of multiple parties. We just need help to all get through this wreckage victorious and then clean up the mess early on next cycle.
[06:33] <vorlon> $ cd ubuntu-manual-tests
[06:33] <vorlon> $ git log | grep -c Date:.*2022
[06:33] <vorlon> 59
[06:33] <vorlon> $ git log | grep -c Date:.*2023
[06:33] <vorlon> 59
[06:33] <vorlon> $ git log | grep -c Date:.*2024
[06:33] <vorlon> 20
[06:33] <vorlon> $
[06:34] <vorlon> this is NOT an issue of the iso tracker being in disrepair.
[06:34] <arraybolt3> sorry, it's 1:34 AM here so I'm not phrasing things great.
[06:34] <arraybolt3> I mean the collective testcases of most (all?) the flavors falling into disrepair.
[06:40] <guiverc> arraybolt3, Lubuntu's is the worst (ie. ours)... I very much rely on our discourse checklist (i can easily see what tests were done last; iso.qa only shows current ISO).. so I'm not sure we should comment overall
[06:42] <arraybolt3> I think we need to get used to the fact that the Release Team is doing things better + stricter, and we need to get used to doing the same. Our internal checklist is nice, but we need *something* to be different. Our current way of doing things got us, well, here.
[06:43] <tsimonq2> Funny enough, it's been on our TODO list since like ... 2018 to get that in sync. We've just let it fall behind the other stuff.
[06:43] <arraybolt3> Worst-case scenario OEM installation won't work until 24.04.1, but that is still a pretty bad way for things to go.
[06:43] <tsimonq2> Especially when a tested fix is in hand.
[06:44] <sil2100> If we get this in and respin, who will be around to do the image verification, testing and sign-off on all the 3 flavors?
[06:44] <sil2100> And when?
[06:44] <arraybolt3> Simon can sign off on Lubuntu and Kubuntu. rs2009 is up for signin off on Ubuntu Unity it looks like.
[06:45] <arraybolt3> I'll just skip sleep tonight if needed to get these dern things tested :P
[06:45] <arraybolt3> I'm not about to let three flavors lose a highly valuable new feature because I dropped the ball six days ago if I can help it.
[06:45] <tsimonq2> I'll stay up as well, count me in.
[06:46] <arraybolt3> And on that note, I have more installs to do prior to the respin, so I'm going to flash an ISO and be back in a sec.
[06:47] <arraybolt3> alright, flash in progress
[06:47]  * guiverc is up for running Lubuntu testing  (not secure-uEFI, but I'm sure we'll get that done)
[06:47] <tsimonq2> riscv64 is done for calamares-settings-ubuntu, which means we're waiting on publisher runs
[06:48] <arraybolt3> I can do secure-UEFI, my testing desktop supports it.
[06:54] <arraybolt3> sil2100: also the respin will not incur a whole lot of extra testing work. It will mandate three additional installs, that's it. The code change affects *only* the oem installation mode and has no chance of affecting any other installation mode.
[06:55] <arraybolt3> So as long as OEM installation works on all flavors (one install of work), the change works and we're good. AIUI tsimonq2 already did that testing and it works.
[06:55] <vorlon> "three additional installs" the expectation is that all required test cases are re-run for each image.  Flavor leads *can* bypass this and sign off the images anyway, at their own peril
[06:56] <vorlon> yes you're changing one line of code specific to oem mode.  cosmic rays etc
[06:59] <arraybolt3> That's a valid point. I don't think we'll redo every single test (approximately 20+ of them), but testing more than just OEM mode after the respin makes good sense.
[07:03] <tsimonq2> calamares-settings-ubuntu binaries published in -proposed
[07:03] <sil2100> I'll leave it up to you (the leads) to decide what testing is required, but of course I'd be recommending re-doing the recommended ones
[07:03] <arraybolt3> sil2100: Absolutely. We have three testers here, we can do that.
[07:04] <sil2100> s/recommended/mandatory/
[07:04] <arraybolt3> I'm really sorry again for getting us here, and I will work to help fix the problems we're seeing here.
[07:10] <arraybolt3> Make that four testers, we have some backup coming in (thank you wxl!)
[07:11] <sil2100> I put the unblock in place, but I will further discuss this with the rest of the team when I make my way to the office in a few minuts
[07:11] <sil2100> *minutes
[07:11] <tsimonq2> Thank you sil2100!
[07:13] <tsimonq2> Looks like Britney may be crashing...
[07:16] <tsimonq2>   File "/home/ubuntu-archive/proposed-migration/code/b2/britney2/policies/autopkgtest.py", line 184, in fetch_db
[07:16] <tsimonq2>     if http_code and os.path.getsize(new_file) != int(f.getheader('content-length')):
[07:16] <tsimonq2> TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'
[07:16] <tsimonq2> At first glance, seems related to this commit: https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/commit/?id=b7807106233ad1230211626e4288232ee09a9c02
[07:16] -ubottu:#ubuntu-release- Commit b780710 in ~ubuntu-release/britney/+git/britney2-ubuntu "Fix: autopkgtest now returns content-length header again HEAD master"
[08:06] <arraybolt3> Looks like calamares-esttings-ubuntu just migrated?
[08:07] <sil2100> It is in flight as we speak (type)
[08:08] <sil2100> I will keep watching for it to be fully published and kick off lubuntu, kubuntu and ubuntu unity (calamares flavors)
[08:11] <sil2100> So I would like to start releasing images in like 3-ish hours. In the unlikely case that the 3 flavors are still not ready, I'll proceed with releasing all the ready ones anyway! I'll still be around to publish the rest, if needed
[08:11] <arraybolt3> Thank you so much. I will dutifully stay awake to get the testing done.
[08:11] <sil2100> But I'd appreciate if we could aim for an ASAP testing run once the images are built. And plz no more last minute regression fixes, my poor heart might not survive that ;p
[08:12] <lotuspsychje> arraybolt3: if you need help testing iso's you can always ask in #ubuntu-next volunteers can also help
[08:12] <arraybolt3> +1
[08:13] <arraybolt3> lotuspsychje: not a bad idea
[08:13] <mkukri> when should we expect an ISO with this?
[08:13] <arraybolt3> but yes, this should (indeed, needs to) be the last big thing.
[08:22] <sil2100> mkukri: with what?
[08:22] <sil2100> NO MORE FINDING BUGS
[08:22] <guiverc> :)
[08:22] <arraybolt3> with calamares-settings-ubuntu I think he means
[08:24] <mkukri> yea, i just wanted to give a quick test to the install_devices fix
[08:24] <mkukri> no more bugs, pinky promise :)
[08:46] <sil2100> Still waiting for the package to fully publish on ftpmaster
[08:46] <arraybolt3> np, still here
[08:54] <sil2100> Why is it so sloooow
[08:54]  * sil2100 is poking the LP team to check the publisher
[08:55]  * guiverc thinks about watched kettles never boiling...
[09:05] <paride> sil2100, Ubuntu Base ppc64el test result submitted (pass)
[09:05] <utkarsh2102> paride: ready to be marked "ready" on the tracker?
[09:05] <utkarsh2102> or you're just referring to the passing tests only
[09:06] <paride> utkarsh2102, I think they're ready to be ready to marked ready.
[09:06] <utkarsh2102> paride: super, can you do the honors?
[09:06] <paride> utkarsh2102, doing so
[09:07] <utkarsh2102> sweet!
[09:18] <utkarsh2102> ItzSwirlz: hey! can you please look at the Cinnamon images and confirm they look good and they're "ready"?
[09:18] <utkarsh2102> https://iso.qa.ubuntu.com/qatracker/milestones/453/builds
[09:23] <sil2100> I don't know why the publisher is so slow
[09:24] <sil2100> The LP team couldn't find anything particularly scary
[09:28] <sil2100> Yes! It's on ftpmaster now!
[09:28] <sil2100> arraybolt3, others: I am kicking off the 3 images, kubuntu, lubuntu and unity o/
[09:29] <utkarsh2102> nice
[09:30] <guiverc> o/
[09:31] <arraybolt3> woot!
[09:33] <bdmurray> apw: Did you finish your surgery yesterday regarding meta packages?
[09:55] <sil2100> arraybolt3, others: images slowly appearing o/
[09:55] <guiverc> i see Lubuntu ISO on iso.qa.ubu :)
[09:55] <arraybolt3> awesome, zsyncing it now
[10:02] <arraybolt3> seems as though the ISO tracker picked up on the new Kubuntu ISO but it's not yet on cdimage. /me waits a bit on that front while proceeding elsewhere
[10:03] <sil2100> I think the mirrors can take a bit
[10:10] <sil2100> arraybolt3: ok, I see it on my mirror at least
[10:11]  * guiverc  sees kubuntu iso also (now)
[10:11] <arraybolt3> awesome, I'll give the zsync another shot
[10:13] <arraybolt3> not here for me yet
[10:13] <arraybolt3> arraybolt3@kf-XE:~/ISOs/Kubuntu/Noble$ zsync http://cdimage.ubuntu.com/kubuntu/daily-live/20240425.1/noble-desktop-amd64.iso.zsync
[10:13] <arraybolt3> failed on url http://cdimage.ubuntu.com/kubuntu/daily-live/20240425.1/noble-desktop-amd64.iso.zsync
[10:13] <arraybolt3> could not read control file from URL http://cdimage.ubuntu.com/kubuntu/daily-live/20240425.1/noble-desktop-amd64.iso.zsync
[10:13] <arraybolt3> that's using the command copy-pasted from the ISO tracker
[10:14]  * guiverc wonders if just temporary issue, try again in a min or two arraybolt3  ... hold on
[10:15]  * guiverc has a zsync running.. it's calculating current. will see if it starts
[10:15] <arraybolt3> ah now it's working
[10:15] <arraybolt3> well hey, better to be faster than the server than to be slower when you're in a time crunch
[10:26] <sil2100> Please keep me up to date on the progress of testing o/
[10:26] <sil2100> And remember about marking your flavors as ready
[10:26] <arraybolt3> So far we have nine tests "in flight" in Lubuntu and one done, and I'm wrapping up a second
[10:27] <sil2100> Someone needs to mark, for instance, cinnamon as ready. Who is the lead in charge right now who can do it? Remembering that we need to have an ACK from a flavor lead
[10:28] <arraybolt3> sil2100: Eickmeyer is officially authorized to mark an image as "ready" but lacks the proper permissions in LP. He gave the Release Team a formal ACK a bit ago on that front.
[10:28] <arraybolt3> (for Ubuntu Cinnamon)
[10:28] <sil2100> o/
[10:28] <arraybolt3> 04:52:53      Eickmeyer │ Pinged him on Matrix to mark as ready, but if ubuntu-release wants to mark Ubuntu Cinnamon as ready, feel free.
[10:28] <sil2100> Ok, let me ekhm, read the backlog. I can mark it as ready then
[10:29] <sil2100> Thank you
[10:30] <arraybolt3> The cdimage infra is being very flaky though - the zsync file for Kubuntu was absent, then present but with no ISO file, now it's absent again.
[10:30] <arraybolt3> and now it's present again
[10:30] <arraybolt3> lol
[10:31] <arraybolt3> but the ISO still doesn't seem to be there
[10:32] <sil2100> I have no idea how weirdly the cdimage mirror syncing works
[10:37] <arraybolt3> Ubuntu Unity seems to have landed, I'm pulling it now. Kubuntu is still taking its time to show up for unknown reasons.
[10:43] <arraybolt3> Multitasking a Lubuntu installation and an Ubuntu Unity live ISO session test.
[10:43] <arraybolt3> So far we have four passed Lubuntu installation tests (including OEM installations) and one passed live session test.
[10:46] <arraybolt3> lol, note to self, -enable-kvm is important when using QEMU
[10:50] <sil2100> Xubuntu Minimal needs getting marked as well!
[10:50] <arraybolt3> bluesabre is finishing up on that one
[10:50] <sil2100> Will be starting the publishing in around 30 minutes
[10:50] <bluesabre> I'm working on it!
[10:50] <sil2100> bluesabre: \o/
[10:51] <arraybolt3> Kubuntu's ISO finally showed up, so I'll be pulling it shortly
[10:51] <sgmoore> morning, kuuntu lead here, what do I need to do?
[10:51] <arraybolt3> already has one running and one passed test
[10:51] <sgmoore> Kubuntu even
[10:52] <arraybolt3> sgmoore: how are the release notes coming?
[10:52] <sgmoore> done
[10:52] <arraybolt3> perfect. If you want to, testing would be quite helpful (we had an emergency last-minute respin due to a fatal bug in the OEM installation mode).
[10:52] <sgmoore> you bet
[10:53] <arraybolt3> So far me, leo, and guiverc2 have attacked it full-force and are making rapid progress on Lubuntu, Kubuntu, and Ubuntu Unity.
[10:54] <arraybolt3> Found a bug to SRU in Lubuntu, our keymap-layout.png needs updated in our Plymouth theme too. 0-day SRU at worst, ignorable for right now.
[10:57] <arraybolt3> Pivoting to Ubuntu Unity, doing two install tests there.
[11:14] <arraybolt3> The OEM fix is proving to be good for Ubuntu Unity as well.
[11:20] <arraybolt3> Ubuntu Unity has one installation test remaining on it (which I am doing now), and then it should be ready to be marked as "Ready".
[11:21] <sgmoore> still downloading :(
[11:21] <arraybolt3> I'm testing away over here, so no worries
[11:21] <sgmoore> thank you
[11:29] <arraybolt3> sil2100: update on testing, Lubuntu has eight passed tests and three still in flight, Ubuntu Unity has two passed tests and one in flight (and installing), Kubuntu has four passed tests, two in-flight, and three more mandatory ones to go.
[11:33] <utkarsh2102> arraybolt3: nice
[11:33] <arraybolt3> Ubuntu Unity now has zero remaining mandatory tests. rs2009: care to look at it and see if it's ready to mark as ready?
[11:33] <utkarsh2102> let me/us know once things are ready to be marked on the tracker
[11:34] <arraybolt3> kk, I think Unity is ready. The critical bugfix and several other corner cases were tested in my two installs, and everything installer-related is great. There are some bugs to SRU, but nothing huge like we've been battling all day and into the night and the next day.
[11:38] <sil2100> arraybolt3: thank you!
[11:42] <sil2100> I'm starting the publishing dance, will wait with kubuntu, lubuntu and unity or course
[11:45] <arraybolt3> kk. Shouldn't take too long there though, there's two installs left on Lubuntu it looks like, and I'm finishing up two remaining Kubuntu installs (one to prep for auto-resize and one to actually test it).
[11:59] <sil2100> rs2009: are you around for signing off on the unity images?
[12:04] <arraybolt3> sil2100: all mandatory test cases for Kubuntu passed!
[12:05] <arraybolt3> Lubuntu also has all mandatory test cases passed but there are still two in-progress installs there.
[12:14] <sgmoore> sil2100: Kubuntu lead here signing off on Kubuntu image
[12:14] <sil2100> \o/
[12:14] <sgmoore> arraybolt3: Thank you for all your help.
[12:15] <sil2100> Still would love someone from unity to sign off unity
[12:15] <sil2100> And waiting for lubuntu
[12:15] <arraybolt3> Lubuntu is still in progress, our QA lead has a couple of installs going and is being bottlenecked partially by slow Internet. It's coming though, and everything to this point has succeeded.
[12:19] <guiverc> last of Lubuntu running now..
[12:22] -queuebot:#ubuntu-release- Unapproved: netavark (noble-proposed/universe) [1.4.0-4 => 1.6.0-1ubuntu1] (no packageset)
[12:26] -queuebot:#ubuntu-release- Unapproved: accepted netavark [source] (noble-proposed) [1.6.0-1ubuntu1]
[12:33] <tsimonq2> Lubuntu is ready.
[12:34] <sil2100> Awesome!
[12:34] <sil2100> Ok, now just unity. I'll start publishing kubuntu and lubuntu in the meantime
[12:35] <arraybolt3> *deep sigh of relief*
[12:37] <jcm__> What's the deal with unity?
[12:37] <arraybolt3> rs2009 hasn't shown up to officially ACK it yet.
[12:38] <arraybolt3> Testing-wise, it was fine.
[12:38] <sil2100> Did rs2009 delegate someone to make that call in his absence?
[12:38] <arraybolt3> (at least for a .0 release - there are a bunch of things that I'll probably be working on fixing in it and other flavors LATER after recovering from this :P)
[12:38] <arraybolt3> sil2100: Maik and fuseteam, I believe (the latter of whom is here)
[12:39] <sil2100> fuseteam: o/
[12:39] <sil2100> Can someone reach out to them via matrix as well just-in-case?
[12:39] <arraybolt3> doing now
[12:40] <sil2100> Thank you
[12:40] <arraybolt3> also sil2100 I believe sgmoore gave you permissino to mark Kubuntu as ready.
[12:41] <sgmoore> I did
[12:41] <sil2100> Yes, Kubuntu is done o/
[12:41] <sgmoore> hooray!
[12:41] <arraybolt3> ah kk, didn't see it at first
[12:41] <sil2100> Well, mirrors not yet enabled tho
[12:42] <arraybolt3> oh guess what, Rudra is awake
[12:42] <fuseteam> oh dang how i miss the ping, henlo
[12:43] <sil2100> woohoo!
[12:43] <sil2100> :
[12:43] <arraybolt3> Ubuntu Unity is now marked as ready \o/
[12:43] <fuseteam> yay hype o/
[12:43] <arraybolt3> "Break the dam! Release the river!"
[12:43] <sil2100> This is wonderful news, thank you everyone
[12:44] <utkarsh2102> nice
[12:44] <rs2009> I really should be check IRC more often :facepalm:
[12:45] <rs2009> s/should be check/should check/g
[12:45] <arraybolt3> Thanks to everyone who made this possible!
[12:45] <arraybolt3> rs2009: hey, it all worked out.
[12:45] <rs2009> can tell :D
[12:46] <arraybolt3> (Also the Matrix Council and Canonical IS is still working on Matrix-to-IRC bridging. We keep hoping it will be next week, but one of these days it'll happen)
[12:48] <fuseteam> hmm not sure if my thunderbird give notifs correctly for irc, i'll probably look into that for next time
[13:23] <sil2100> Thank you everyone for your hard work this release! I think it was the most bumpy one we had so far
[13:24] <sil2100> But I feel like a lot of love went into this one, with a LOT of activity from many dedicated people
[13:24] <sgmoore> Thank you too sil2100 It was a wild ride my first go as Kubuntu lead lol
[13:28] <kajiya_> Congratulations everyone :) And thank you for all the hard work , I feel like this one's been nuts XD
[13:31] <sil2100> sgmoore: first ride, already the deep water experience!
[13:31] <sil2100> kajiya_: oh yes, but we all made it somehow ;)
[13:39] <jbicha> sil2100: could y'all consider rust-alacritty for a 0-day?
[13:59] <bluesabre> So... we made it?
[13:59] <tsimonq2> We made it. :)
[14:00] <bluesabre> 🎉
[14:01] <tsimonq2> kajiya_: "Most turbulent cycle for Lubuntu since 18.10" that's for sure :)
[14:27] <tsimonq2> Everyone ready for the Qt 6 megatransition next cycle??? :D :D :D
[14:27] <Eickmeyer> ubuntu-release: How does the release team feel about flavors pushing out their release announcements prior to the official release announcement email? Historically, this has been considered a *bad idea* as we've been told to wait for that as a signal that the mirrors have properly propogated.
[14:30] <tsimonq2> *propagated
[14:30] <Eickmeyer> Spell check couldn't keep up. :P
[14:33] <tsimonq2> utkarsh2102: Let me know when we have a codename :)
[14:35] <sil2100> tsimonq2: oh my, megatransition - love it already
[14:35] <bdmurray> Eickmeyer: It's still a bad idea
[14:35] <Eickmeyer> bdmurray: I thought so.
[14:35] <Eickmeyer> tsimonq2: ^
[14:36] <schopin> tsimonq2: well, the good thing is that now we're all grizzled veterans when it comes to huge transitions :)
[14:37] <tsimonq2> sil2100, schopin: hahaha fair enough :)
[14:38] <tsimonq2> I'm going to start doing some checks for exactly how many packages will be affected; ballpark/off the top of my head we're talking at least 50 source NEW packages, probably a nice handful of binary NEW packages. I expect, meh around 500-600 packages between Lubuntu, Kubuntu, and Studio to be affected
[14:39] <schopin> tsimonq2: are you planning on doing it through Debian?
[14:39] <tsimonq2> schopin: Already in progress :)
[14:39] <schopin> Oh, nice.
[14:40] <schopin> I didn't see anyone grumble about it on OFTC, but I might not be in the relevant channels.
[14:41] <tsimonq2> https://salsa.debian.org/qt-kde-team/issue-tracker/-/issues/71
[14:43] <tsimonq2> It'll likely need to be done in this order... Qt 6.6.2 transition, KDE Frameworks 6 sync party + source NEW fun, then Plasma and LXQt become separate efforts in this respect.
[14:44] <jbicha> tsimonq2: that Salsa project appears to limit viewing issues to developers or something
[14:44] <tsimonq2> orly? hmmm
[14:45] <Eickmeyer> The KDE team does that habitually.
[14:45] <tsimonq2> "50 of 83 checklist items completed"
[14:45] <tsimonq2> ok, so almost there... the remaining source packages shouldn't get *too* difficult
[14:46] <jbicha> Eickmeyer: Debian Social Contract #3 🤷
[14:46] <Eickmeyer>  ¯\_(ツ)_/¯
[14:46] <tsimonq2> Long game on this one is, Kubuntu, Ubuntu Studio, and Lubuntu are Wayland + Qt 6 by 24.10's release so we can spend the three cycles after that with the bug hammer.
[14:47] <jbicha> tsimonq2: are y'all going to keep an xorg option for 24.10 or is too early to ask?
[14:48] <tsimonq2> jbicha: Plasma 6 upstream doesn't support xorg, and I'm firm on Lubuntu being Wayland-only next cycle.
[14:48] <tsimonq2> Plus, I keep hearing rumors that we want X11 out of the archive in the 25.10 cycle
[14:48] <Eickmeyer> I don't listen to rumors.
[14:48] <vorlon> jbicha: you synced a package the day of release that introduces NEW binaries.
[14:48] <vorlon> jbicha: I am rejecting the binaries now.
[14:49] <jbicha> vorlon: thank you. sorry
[14:49] <jbicha> tsimonq2: depending on what you mean by removing X11, that sounds impossible
[14:49] <tsimonq2> Indeed.
[14:49] -queuebot:#ubuntu-release- New: rejected poco [amd64] (noble-proposed) [1.13.0-6]
[14:49] -queuebot:#ubuntu-release- New: rejected poco [armhf] (noble-proposed) [1.13.0-6]
[14:49] -queuebot:#ubuntu-release- New: rejected poco [riscv64] (noble-proposed) [1.13.0-6]
[14:49] <jbicha> the libraries will still be available at least
[14:50] -queuebot:#ubuntu-release- New: rejected poco [arm64] (noble-proposed) [1.13.0-6]
[14:50] -queuebot:#ubuntu-release- New: rejected poco [s390x] (noble-proposed) [1.13.0-6]
[14:50] -queuebot:#ubuntu-release- New: rejected poco [ppc64el] (noble-proposed) [1.13.0-6]
[15:02] <bluesabre> When's the release announcement expected? Some flavors have already released theirs, and Xubuntu always gets left in the dust and releases late. Trying to schedule myself appropriately.
[15:06] <vorlon> if the images are published to your satisfaction, you can send a release announcement to your community at any time. I don't know the exact timing of the announcement from London's side, I expect "soon"
[15:06] <tsimonq2> Eickmeyer: ^
[15:07] <Eickmeyer> vorlon: That's contrary to what bdmurray was saying earlier. Can we get some official clarification?
[15:07] <vorlon> fwiw our checklists says the torrents aren't all validated yet as working. andersson1234 is working on this
[15:07] <Eickmeyer> Historically, this has been considered a *bad idea* as we've been told to wait for that as a signal that the mirrors have properly propogated.
[15:08] <vorlon> Eickmeyer: well if some flavors have already sent announcements, <shrug>
[15:09] <vorlon> "the mirrors have properly propagated" we have 4 internal frontends for cdimage.ubuntu.com and we don't actually have anything in our release checklist that checks that they're all in sync :P bdmurray
[15:09] <Eickmeyer> vorlon: My motivation is to make sure flavors are on the same page in the future. Seems that they don't understand the cons vs the pros of announcing early.
[15:11] <Eickmeyer> tsimonq2: ^ RE: torrents
[15:14] <bdmurray> London has announced
[15:14] <tsimonq2> Eickmeyer: I just don't think it's productive to admonish flavors for publishing the announcement when they are ready. I'm sick and tired of this meaningless debate. As you do remember, the alternative is having someone give us all a flag time, which doesn't work well with timezones.
[15:14] <tsimonq2> bdmurray: thank you :)
[15:14] <tsimonq2> Eickmeyer: publish your announcements now, London is out, have you published your announcements yet?
[15:15] <Eickmeyer> tsimonq2: I wasn't admonishing! I was just trying to make sure we're on the same page! Yikes!
[15:15] <tsimonq2> don't "yikes" me, you do this every time, I get admonished for publishing Lubuntu when I see the ISOs are published
[15:15] <tsimonq2> every. time.
[15:16] <Eickmeyer> tsimonq2: Then you're reading too much into it and/or have a guilty conscience.
[15:17] <tsimonq2> Eickmeyer: No, *you're* the one reading too much into it.
[15:19] <andersson1234> vorlon: I've not necessarily been testing the noble torrents. I've been documenting/investigating an appropriate way to validate them going forward. Though I can partially validate all our noble torrents right now
[15:20] <vorlon> andersson1234: well the card for validating them is assigned to you so if you're not validating perhaps you should pass the card off to someone who will? :)
[15:22] <andersson1234> I can validate them now :)
[15:31] <andersson1234> all torrents validated except from amd64 - details on card
[15:48] <utkarsh2102> thanks
[15:50] <lotuspsychje> tnx to all devs, great job & great release!
[15:50] <tsimonq2> 🎉🎉
[15:50] <fnordahl> \o/
[15:50] <lotuspsychje> cookies & scotch for you guys :p
[15:50] <ogra_> yay !
[15:50] <ogra_> congrats !
[15:55] <Eickmeyer> You guys can all party, but I think I'm with the release team when I say "Gee, that bed looks real good."
[15:55] <sgmoore> lol
[15:55] <lotuspsychje> :p
[15:56] <lotuspsychje> 'im going to the hotel..and sleep for a month' (HEAT 1995 quote)
[15:58] <tsimonq2> I'll sleep when the megatransition is done ;P
[16:00] <Eickmeyer> tsimonq2: So... sometime in September. Got it. 👍
[16:00] <Eickmeyer> (and not even then)
[16:56] <ELFrederich> hey, congrats on the release.  Any idea when it'll be released for WSL?  This just has jammy still... https://cloud-images.ubuntu.com/wsl/releases/
[16:59] <philroche> ELFrederich: I will check now. It will be the https://cloud-images.ubuntu.com/wsl/noble/20240423/ image though once promoted. It has also been submitted to microsoft for inclusion in the store
[17:08] <tjaalton> release team; any chance getting ipu6-dkms in noble-proposed soon? it would be useful to have available for the next kernel sru cycle
[17:11] <philroche> ELFrederich: done. Now promoted to https://cloud-images.ubuntu.com/wsl/releases/noble/current/
[17:14] <ELFrederich> philroche, thanks. I don't use the Microsoft Store.  I just `wsl --import noble instances\noble images\ubuntu-noble-wsl-amd64-wsl.rootfs.tar.gz`
[17:15] <ELFrederich> today is new WSL VM day, even more exciting than new sponge day!
[17:16] <jchittum> ELFrederich -- what's your use case for doing that? generally speaking, that is _not_ a supported method. if you're pulling from cloud-images.ubuntu.com, the images there are only for testing purposes
[17:17] <jchittum> the official releases of WSL only come from the store
[17:18] <ELFrederich> jchittum, I like taking snapshots, restoring from snapshots, etc.  That's how a get a new "fresh" install.
[17:18] <jchittum> ok. just be aware that those images are for testing. they are untested before reaching that site
[17:19] <ELFrederich> jchittum, okay, good to know.
[17:20] <ELFrederich> as far as I'm aware, there's no way using the store to get more than one VM of say 22.04 running at the same time.  All the stuff I find online says to export your existing filesystem and import it as a new VM.
[17:27] <tjaalton> vorlon: my question above ^, is it too early to get ipu6-drivers (not -dkms) in noble-proposed so that it could make it in the next/first kernel sru cycle for noble?
[17:29] <tjaalton> it took forever to get a snapshot that actually works, so it's not like there's a chance of regressing things as the current version is just not working
[17:29] <tjaalton> AFAIK
[17:29] <vorlon> tjaalton: can this wait until my SRU shift tomorrow? I have some release follow-through to work on today
[17:29] <tjaalton> vorlon: I guess so!
[17:29] <tjaalton> thanks
[18:08] -queuebot:#ubuntu-release- Packageset: 26 entries have been added or removed
[18:13] <vorlon> ^ this is innocuous, germinate is uselessly picking up some more source packages that only build arch: all binaries into the i386 whitelist
[19:08] -queuebot:#ubuntu-release- Packageset: Removed nvidia-graphics-drivers-550-server from i386-whitelist in focal
[19:08] -queuebot:#ubuntu-release- Packageset: Added spirv-llvm-translator-18 to i386-whitelist in focal
[19:08] -queuebot:#ubuntu-release- Packageset: Added openjdk-23 to i386-whitelist in jammy
[19:08] -queuebot:#ubuntu-release- Packageset: Added spirv-llvm-translator-18 to i386-whitelist in jammy
[19:23] -queuebot:#ubuntu-release- Packageset: Removed openjdk-20 from i386-whitelist in focal
[19:23] -queuebot:#ubuntu-release- Packageset: Removed openjdk-20 from i386-whitelist in jammy
[19:23] -queuebot:#ubuntu-release- Packageset: Removed openjdk-20 from i386-whitelist in noble
[19:23] -queuebot:#ubuntu-release- Packageset: Added openjdk-23 to i386-whitelist in focal
[19:23] -queuebot:#ubuntu-release- Packageset: Added openjdk-23 to i386-whitelist in mantic
[19:23] -queuebot:#ubuntu-release- Packageset: Added spirv-llvm-translator-18 to i386-whitelist in mantic
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-18 from i386-whitelist in focal
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-19 from i386-whitelist in focal
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-16 from i386-whitelist in jammy
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-16 from i386-whitelist in mantic
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-18 from i386-whitelist in mantic
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-16 from i386-whitelist in noble
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-18 from i386-whitelist in noble
[19:38] -queuebot:#ubuntu-release- Packageset: Removed openjdk-19 from i386-whitelist in noble
[19:53] -queuebot:#ubuntu-release- Packageset: Removed openjdk-22 from i386-whitelist in focal
[19:53] -queuebot:#ubuntu-release- Packageset: Removed openjdk-13 from i386-whitelist in jammy
[19:53] -queuebot:#ubuntu-release- Packageset: Removed openjdk-22 from i386-whitelist in jammy
[19:53] -queuebot:#ubuntu-release- Packageset: Removed openjdk-13 from i386-whitelist in mantic
[19:53] -queuebot:#ubuntu-release- Packageset: Removed openjdk-13 from i386-whitelist in noble


[00:52] <Shayan> hello
[00:59] <TheP0keB055> Hi
[06:44] <CommanderSync> Hey!
[07:32] <Rai> HELP
[07:33] <Rai> JOIN
[07:36] <RAI_> hi
[07:38] <RAI_> hii divasura
[07:42] <Ekajaya740> we
[07:42] <Ekajaya740> divasura
[07:42] <Ekajaya740> njing
[07:42] <Ekajaya740> we wibu
[07:42] <divasura> coeg
[07:42] <Ekajaya740> oi rai
[07:42] <divasura> hi
[07:43] <Ekajaya740> rai-san
[07:43] <divasura> hai rai-chan
[07:43] <Ekajaya740> njing
[07:43] <Ekajaya740> coegsura
[07:43] <Ekajaya740> hello
[07:44] <Ekajaya740> Yok gelud
[07:44] <Ekajaya740> gelud
[07:45] <Ekajaya740> hello smashing
[10:06] <sai_> hai
[10:08] <chinna_> hi
[10:54] <DhruvPower> Hi, I am Dhruv Due to travel I was not able to complete the task on time ,therefore can the deadline be extended till tomorrow morning as I have only 1 hour left after which this task will expire. Looking forward for your reply Thanks for the help.
[16:34] <nishantparhi> how do i delete a pull request
[16:35] <nishantparhi> if i close a pull request then its getting deleted but when i create a new pull request then the old one comes angsin


[14:10] <ticky> Hey guys, is there any reason in particular that while trying to update my Ubuntu ARM installation it hangs on "Removing libappindicator0.1-cil from Mono"?
[14:59] <ticky> Anyone know why apt hangs on "Removing libappindicator0.1-cil from Mono"?
[14:59] <infinity> Are you sure it's hung, and not just taking a stupidly long time?
[15:00] <infinity> But if it is, it's almost certainly not apt, but perhaps something executed in the prerm of that package
[15:00] <ticky> I can't be certain, but it appears to be hung.
[15:00] <ticky> How would I work out the issue?
[15:01] <ticky> mono is using 99% cpu.
[15:01] <ticky> and has been for about an hour. :/
[15:02] <infinity> RIght, so it's something mono-ish being called from the prerm of that package.
[15:02] <infinity> If you're looking for the quick workaround, you can probably kill mono and just carry on.
[15:02] <infinity> But it would be lovely if you filed a bug.
[15:03] <ticky> ok, what do I need to supply for the bug report?
[15:03] <infinity> It may not be reproducible, mind you.  But if you file a bug and it's a one-off thing we and you can't reproduce, no big deal.  If we can reproduce it, then we can figure out WTF happened.
[15:03] <infinity> *hand wavy*
[15:04] <infinity> Honestly, something like "while removing libappindicator0.1-cil, mono spins at 99% usage for an hour on armel" is probably enough for someone to try it out.
[15:04] <ticky> fair enough.
[15:05] <infinity> Others will claim you need to include the keys to your car and send your first born in the mail, but whatever.  Bugs like this are near impossible to find if not reproducible, and if reproducible, we can get the info we need locall.
[15:05] <infinity> locally, too.
[15:06] <ticky> hmm. It seems to happen when installing assemblies to Mono, too.
[15:07] <infinity> That's a larger problem, then.
[15:07] <infinity> And we'd definitely want a bug.  One where we might even ask for more info if we can't reproduce. :P
[15:10] <ticky> Would it be a problem that I'm using it in an almost definitely unsupported manner? :P
[15:12] <infinity> Perhaps. :P
[15:13] <infinity> I've also heard that mono on ARM may have some "issues", but I've not personally looked into what those are just yet.
[15:13] <ticky> Hm.
[15:14] <ticky> I don't actually know what this library is a dependency for, but it's very likely it's not for anything I'm actually wanting to use on this system. Is there a way to force apt to just remove it?
[15:17] <infinity> Well, you can just bypass the prerm by editing the offending line in /var/lib/dpkg/info/<package>.prerm
[15:17] <infinity> And the trying to remove it again.
[15:39] <ticky> hmm.
[15:42] <ticky> infinity: there doesn't seem to be much I can do, the script only does one thing, and that's the one thing that's hanging.
[15:49] <ticky> Can I make dpkg just ignore that package? :x
[18:37] <infinity> ticky: You can just no-nop the script (sorry, been travelling, spotty connectivity)
[18:37] <infinity> ticky: no-op*
[20:16] <armin76> Martyn: hi :)
[20:17] <Martyn> hey there armin