| Eickmeyer | rbasak: rationalle was that github has a much higher capacity. Honestly, I don't know when tsimonq2 will get back to working on it; his activity level has dropped significantly. | 00:02 |
|---|---|---|
| Eickmeyer | Right now it no-ops as the request has been blocked on the LP side. | 00:03 |
| Eickmeyer | Effect is that it simply doesn't report time until EOL. | 00:03 |
| rbasak | Eickmeyer: right, so if you make it no-op in an SRU, then that won't be a regression to existing behaviour, and will relieve the pressure on the firewall. | 00:03 |
| Eickmeyer | rbasak: Had a better idea, possible stroke of genius. I could take the json file it's searching for and throw it in its installation directory and have the QNetworkRequest(QUrl(QStrinLiteral be a QUrl(fromLocalFile which then can look for the .json file locally. | 00:19 |
| Eickmeyer | Even a file:/// url would work. | 00:20 |
| sarnold | .. just so long as you remember to shove an SRU into the works two weeks before :) | 00:21 |
| Eickmeyer | sarnold: Uh.... bug 2039492...? | 00:22 |
| -ubottu:#ubuntu-release- Bug 2039492 in plasma-distro-release-notifier (Ubuntu Oracular) "[SRU] plasma-distro-release-notifier gets EOL data from git.launchpad.net" [Critical, In Progress] https://launchpad.net/bugs/2039492 | 00:22 | |
| Eickmeyer | 'tis ongoing. ;) | 00:23 |
| rbasak | Eickmeyer: that sounds like a great stopgap - thanks! | 00:27 |
| sarnold | Eickmeyer: and does that file give a decent end date meaning no further sru is necessary? | 00:28 |
| Eickmeyer | sarnold: Correct. The file would be specific for the release, I could put it in the /debian directory. | 00:30 |
| sarnold | some of my DNS pals publish machine-readable data on "you're fine" or "upgrade recommended" or "upgrade mandatory" via DNS (of course :) -- https://github.com/PowerDNS/pdns/blob/master/docs/secpoll.zone -- that way, a single UDP packet serves for the request and a single UDP packet serves for the response, and it'll be served right from memory, maybe even from the packetcache | 00:30 |
| sarnold | Eickmeyer: nice | 00:30 |
| Eickmeyer | rbasak: If you're still there, reject the uploads for jammy-proposed and noble-proposed of plasma-distro-release-notifier if you haven't done so already. I've almost got this wrapped-up. | 00:44 |
| === FuturePi- is now known as Fufu | ||
| -queuebot:#ubuntu-release- Unapproved: plasma-distro-release-notifier (jammy-proposed/universe) [20220915-0ubuntu0.22.04.1 => 20220915-0ubuntu0.22.04.2] (no packageset) | 01:31 | |
| -queuebot:#ubuntu-release- Unapproved: plasma-distro-release-notifier (noble-proposed/universe) [20220915-0ubuntu6 => 20220915-0ubuntu6.1] (no packageset) | 01:35 | |
| Eickmeyer | ubuntu-sru: please reject that plasma-distro-release-notifer for noble. Doesn't have the eol.json file. | 01:37 |
| RAOF | Both of them? ;) | 01:38 |
| RAOF | (There are two in the noble queue) | 01:38 |
| Eickmeyer | RAOF: Yeah. Actually, the jammy one too. Has the wrong eol.json file too. | 01:39 |
| Eickmeyer | The first one needs to be rejected per discussion with rbasak above. | 01:39 |
| Eickmeyer | RAOF: To clarify, all current uploads of plasma-distro-release-notifer in noble and jammy need to be rejected. | 01:45 |
| RAOF | Doned! | 01:52 |
| -queuebot:#ubuntu-release- Unapproved: rejected plasma-distro-release-notifier [source] (jammy-proposed) [20220915-0ubuntu0.22.04.2] | 01:52 | |
| -queuebot:#ubuntu-release- Unapproved: rejected plasma-distro-release-notifier [source] (noble-proposed) [20220915-0ubuntu6.1] | 01:52 | |
| -queuebot:#ubuntu-release- Unapproved: rejected plasma-distro-release-notifier [source] (jammy-proposed) [20220915-0ubuntu0.22.04.2] | 01:52 | |
| -queuebot:#ubuntu-release- Unapproved: rejected plasma-distro-release-notifier [source] (noble-proposed) [20220915-0ubuntu6.1] | 01:52 | |
| Eickmeyer | RAOF: Thanks! I'll have those incoming shortly. I was just working too quickly. | 01:53 |
| Eickmeyer | Trying to fix an unintentional DoS issue I caused with LP's git infra. | 01:53 |
| -queuebot:#ubuntu-release- Unapproved: plasma-distro-release-notifier (jammy-proposed/universe) [20220915-0ubuntu0.22.04.1 => 20220915-0ubuntu0.22.04.2] (no packageset) | 01:59 | |
| -queuebot:#ubuntu-release- Unapproved: plasma-distro-release-notifier (noble-proposed/universe) [20220915-0ubuntu6 => 20220915-0ubuntu6.1] (no packageset) | 02:01 | |
| Eickmeyer | ubuntu-sru: Ok, those should do it for bug 2039492 ^ . Fixes the LP git DoS issue I unintentionally caused (and am profoundly embarrassed by). As such marked it critical for Jammy and Noble since the fix will relieve the firewall pressure. | 02:04 |
| -ubottu:#ubuntu-release- Bug 2039492 in plasma-distro-release-notifier (Ubuntu Noble) "[SRU] plasma-distro-release-notifier gets EOL data from git.launchpad.net" [Critical, In Progress] https://launchpad.net/bugs/2039492 | 02:04 | |
| RAOF | Eickmeyer: I'm not sure that test case is sufficient? How do we know that plasma-distro-release-notifier is actually _working_? | 02:07 |
| Eickmeyer | RAOF: On 22.04, the pop-up is active now. All one has to do is try the live ISO. | 02:08 |
| Eickmeyer | The only thing missing is the EOL date because there's no way to duplicate it since it has no way to retrieve the file since it's been firewalled by the LP team. | 02:09 |
| RAOF | Ah, good. | 02:10 |
| RAOF | Maybe the test case for Noble should be to install the thing, edit the on-disc json to trigger it, and then check that it's triggered? | 02:12 |
| Eickmeyer | Yeah, that's not a bad idea. | 02:13 |
| Eickmeyer | RAOF: Edited the test case. | 02:17 |
| -queuebot:#ubuntu-release- Unapproved: accepted plasma-distro-release-notifier [source] (noble-proposed) [20220915-0ubuntu6.1] | 02:30 | |
| -queuebot:#ubuntu-release- Unapproved: accepted plasma-distro-release-notifier [source] (jammy-proposed) [20220915-0ubuntu0.22.04.2] | 02:34 | |
| -queuebot:#ubuntu-release- Unapproved: wsl-setup (jammy-proposed/main) [0.2 => 0.5.4~22.04] (no packageset) | 06:17 | |
| -queuebot:#ubuntu-release- Unapproved: wsl-setup (noble-proposed/main) [0.5.3~24.04 => 0.5.4~24.04] (no packageset) | 06:18 | |
| -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (jammy-proposed/main) [2.765.49 => 2.765.50] (desktop-core, i386-whitelist) | 06:19 | |
| -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (jammy-proposed/main) [1.481.3 => 1.481.4] (core) | 06:19 | |
| -queuebot:#ubuntu-release- New source: golang-1.23 (jammy-proposed/primary) [1.23.1-1~22.04] | 06:21 | |
| -queuebot:#ubuntu-release- New source: golang-1.23 (noble-proposed/primary) [1.23.1-1~24.04] | 06:21 | |
| -queuebot:#ubuntu-release- New binary: rpi-eeprom [arm64] (oracular-proposed/main) [24.0-1ubuntu1] (raspi) | 09:37 | |
| -queuebot:#ubuntu-release- New binary: rpi-eeprom [armhf] (oracular-proposed/main) [24.0-1ubuntu1] (raspi) | 09:37 | |
| juliank | Well, https://errors.ubuntu.com/problem/bec283ce0655c0e0c7612ffc47880a4042641f3f is obviously true, and it's a new crash but it's the old algoritm running again with new line numbers | 09:49 |
| juliank | Anyway, the point is, resume phasing please :) | 09:57 |
| Skia | juliank: you can now open an MP against https://code.launchpad.net/~ubuntu-sru/ubuntu-archive-tools/phased-update-overrides and ping an SRU team member to merge it to resume the phasing | 10:11 |
| doko | LocutusOfBorg: are you going to address the ocaml-re autopkg test failures? | 11:09 |
| -queuebot:#ubuntu-release- New: accepted rpi-eeprom [arm64] (oracular-proposed) [24.0-1ubuntu1] | 11:10 | |
| -queuebot:#ubuntu-release- New: accepted rpi-eeprom [armhf] (oracular-proposed) [24.0-1ubuntu1] | 11:11 | |
| mdeslaur | is 22.04.5 coming out today? when can I release security updates? | 11:20 |
| LocutusOfBorg | doko, yes | 11:31 |
| LocutusOfBorg | not sure if by reverting part of the upload, or waiting for upstream | 11:31 |
| upils | jbicha, I have a patch for mplayer (see https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/2080493). I ended up fixing the flags as you suggested because the current the patch to make it work with gcc-14 is not ready (I tried and the build failed). Would you like to review it or should I subscribe a specific team? | 12:24 |
| -ubottu:#ubuntu-release- Launchpad bug 2080493 in mplayer (Ubuntu) "FTBFS with gcc-14" [Undecided, Confirmed] | 12:24 | |
| === mfo_ is now known as mfo | ||
| upils | jbicha, unless I missed some, it looks like every remaining package in the ffmeg transition is in one of the 2 batchs to be removed now. Can I help in any other way? | 12:59 |
| upils | oh wait, I in fact missed xmms2 | 13:00 |
| -queuebot:#ubuntu-release- Unapproved: adsys (noble-proposed/main) [0.14.1ubuntu0.24.04.1 => 0.14.2~24.04] (no packageset) | 13:35 | |
| -queuebot:#ubuntu-release- Unapproved: adsys (jammy-proposed/main) [0.14.1~22.04 => 0.14.2~22.04] (no packageset) | 13:36 | |
| kanashiro | uwsgi is not migrating to the release pocket and blocking ruby3.2 removal because of this | 13:38 |
| kanashiro | https://chat.debianbrasil.org.br/file/3/WpwsB99cDPa9TrNw | 13:38 |
| kanashiro | it seems that my last upload to move to ruby3.3 did not build those binaries which are available in oracular/universe | 13:39 |
| kanashiro | https://launchpad.net/ubuntu/+source/uwsgi/2.0.26-2ubuntu2 | 13:39 |
| kanashiro | if you check the diff I did not remove anything related to that | 13:39 |
| kanashiro | I am struggling to understand what happened here | 13:40 |
| kanashiro | those binaries have different versions in the release pocket | 13:40 |
| kanashiro | uwsgi-plugin-mongo | 2.0.24+2ubuntu8+0.0.9build4 | oracular/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x | 13:41 |
| kanashiro | uwsgi-plugin-luajit | 2.0.22+4+0.0.8build2 | oracular/universe | amd64, arm64, armhf, s390x | 13:41 |
| kanashiro | uwsgi-plugin-php | 2.0.23+1build2+0.0.15build4 | oracular/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x | 13:41 |
| ginggs | kanashiro: uwsgi-plugin-{mongo|luajit|php} are from different source packages | 13:47 |
| kanashiro | yeah, just noticed that :) | 13:47 |
| kanashiro | I thought all plugins were provided by src:uwsgi | 13:48 |
| kanashiro | ginggs can you spot an issue here? I just tried the php plugin locally and it builds fine and autopkgtest also passes with the uwsgi from -proposed | 13:55 |
| ginggs | kanashiro: i think uwsgi-plugin-{mongo|luajit|php} just require no-change rebuilds against the new uwsgi.h | 13:57 |
| kanashiro | ack, I'll do that | 13:58 |
| ginggs | kanashiro: you can confirm with a local build and diffoscope | 13:59 |
| kanashiro | ok | 13:59 |
| -queuebot:#ubuntu-release- New source: dotnet9 (oracular-proposed/primary) [9.0.100-9.0.0~rc1-0ubuntu1] | 14:09 | |
| doko | cjwatson: just curious, there are rust-* packages having a Built-Using: rustc ... attribute. why is python3-pydantic-core lacking that? | 14:40 |
| -queuebot:#ubuntu-release- New sync: arianna (oracular-proposed/primary) [24.05.2-1] | 14:41 | |
| -queuebot:#ubuntu-release- New: accepted arianna [sync] (oracular-proposed) [24.05.2-1] | 14:52 | |
| -queuebot:#ubuntu-release- New: accepted dotnet9 [source] (oracular-proposed) [9.0.100-9.0.0~rc1-0ubuntu1] | 14:52 | |
| cjwatson | doko: I guess debcargo adds that and pydantic-core uses pybuild + maturin instead | 14:57 |
| cjwatson | doko: I can try to figure out how to add it, though I want to get the current version into testing first. Can you file a Debian bug? | 14:58 |
| -queuebot:#ubuntu-release- New binary: arianna [amd64] (oracular-proposed/none) [24.05.2-1] (no packageset) | 14:58 | |
| -queuebot:#ubuntu-release- New binary: arianna [arm64] (oracular-proposed/none) [24.05.2-1] (no packageset) | 14:59 | |
| -queuebot:#ubuntu-release- New binary: arianna [armhf] (oracular-proposed/none) [24.05.2-1] (no packageset) | 14:59 | |
| doko | cjwatson: I was just curious, because timo just found an issue with an older rust binary that started to segfault without rebuilding | 15:00 |
| cjwatson | doko: I really have only very limited idea how the Rust toolchain works; I only got into this at all because stuff I care about was under threat of autoremoval and nobody else seemed to be dealing with it | 15:01 |
| doko | yeah, sorry, I was just picking up your pydantic work ... | 15:02 |
| -queuebot:#ubuntu-release- New: accepted arianna [amd64] (oracular-proposed) [24.05.2-1] | 15:02 | |
| -queuebot:#ubuntu-release- New: accepted arianna [armhf] (oracular-proposed) [24.05.2-1] | 15:02 | |
| -queuebot:#ubuntu-release- New: accepted arianna [arm64] (oracular-proposed) [24.05.2-1] | 15:02 | |
| cjwatson | Maybe I can just call into dh_cargo somehow | 15:02 |
| doko | apparently we have only 62 binary packages having binaries written in rust, but 500+ rust libraries ... | 15:04 |
| -queuebot:#ubuntu-release- New sync: xwaylandvideobridge (oracular-proposed/primary) [0.4.0-1] | 15:07 | |
| RikMills | ubuntu-archive: please accept kdsoap-ws-discovery-client from NEW. This is needed to restore smb support in dolphin file manager after transition to Plasma 6 | 15:12 |
| RikMills | ^^^ LP: #2080527 | 15:13 |
| -ubottu:#ubuntu-release- Launchpad bug 2080527 in dolphin (Ubuntu) "smb protocol missing in dolphin" [Undecided, Fix Committed] https://launchpad.net/bugs/2080527 | 15:13 | |
| === mateus-morais6 is now known as mateus-morais | ||
| === klebers_ is now known as klebers | ||
| -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [23.1.2-0ubuntu0~18.04.1 => 23.1.2-0ubuntu0~18.04.2] (edubuntu, ubuntu-cloud, ubuntu-server) | 16:16 | |
| -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [21.1-19-gbad84ad4-0ubuntu1~16.04.2 => 21.1-19-gbad84ad4-0ubuntu1~16.04.5] (edubuntu, ubuntu-cloud, ubuntu-server) | 16:17 | |
| === sforshee_ is now known as sforshee | ||
| ahasenack | hi release team, the mystery around https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356 was finally solved by someone (see last comments) | 17:26 |
| -ubottu:#ubuntu-release- Launchpad bug 2078356 in python3-defaults (Ubuntu Oracular) "python3 preinst failure to run pre-rtupdate hooks" [High, Confirmed] | 17:26 | |
| ahasenack | oracular is also affected | 17:26 |
| ahasenack | thinking about an upload prior to beta, python migrations tend to be long, with lots of dep8 errors | 17:26 |
| ahasenack | so I don't know if it could be done before beta freeze on monday, or even if the migration would be done by next thursday | 17:27 |
| jbicha | ahasenack: there was a python3-defaults upload earlier today, you could probably get QA to cancel those autopkgtests if you reupload | 17:32 |
| Eickmeyer | ubuntu-sru: Hi! Just verified the fix for bug 2039492 which is the unintentional DoS on git.lp.net that I caused. Right now the problem is mitigated by a firewall rule blocking the file from being accessed on LP, but this fix needs to be released ASAP to relieve the firewall pressure. | 17:32 |
| -ubottu:#ubuntu-release- Bug 2039492 in plasma-distro-release-notifier (Ubuntu Noble) "[SRU] plasma-distro-release-notifier gets EOL data from git.launchpad.net" [Critical, Fix Committed] https://launchpad.net/bugs/2039492 | 17:32 | |
| ahasenack | Eickmeyer: checking | 17:40 |
| ahasenack | hm, 0 days aging | 17:48 |
| Eickmeyer | ahasenack: Yes. I wouldn't normally ask for this but it's an infra problem. | 17:48 |
| ahasenack | but there is a deny in place already | 17:48 |
| ahasenack | https://git.launchpad.net/plasma-distro-release-notifier/plain/eol.json?h=eol is a 403 | 17:49 |
| ahasenack | let me ask launchpad if it's an immediate problem still | 17:49 |
| ahasenack | the bug is from october 2023 | 17:51 |
| Eickmeyer | ahasenack: Yes, because we knew about it, but was shelved because, per cjwatson, there wasn't an unusual spike. Once 24.04.1 hit, the spike hit and started to cause performance problems. | 17:53 |
| ahasenack | understood | 17:54 |
| Eickmeyer | Also, tsimonq2's activity has slowed dramatically. The goal was to use distro-info-data but that never came to full fruition. | 17:54 |
| ahasenack | I'm asking in launchapd if the current blocks in place have alleviated the problem, or if we should really risk such a rushed sru | 17:54 |
| ahasenack | Eickmeyer: what is the impact on the affected ubuntu distros with the block that is in place now? | 17:55 |
| ahasenack | do they just complain something failed, and try again later? visible crashes? | 17:55 |
| Eickmeyer | The effect is that there's no EOL countdown. Other than that, they are still told that they have an upgrade to 24.04.1 (only 22.04 users are impacted currently). | 17:56 |
| Eickmeyer | However, it's still hitting the URL in question, and getting a 403 response. | 17:56 |
| Eickmeyer | Basically pressure on the firewall. | 17:57 |
| ahasenack | which is an apache/nginx/frontend response, so not impacting git per se which is much heavier | 17:57 |
| Eickmeyer | Indeed. | 17:57 |
| ahasenack | Eickmeyer: I spoke with launchpad, they think it's faring well, and there is no need to rush it now, with the block in place | 18:11 |
| ahasenack | I'll subscribe to the bug, though, and told them to either comment there, or find me personally, if something changes | 18:12 |
| Eickmeyer | ahasenack: ack, that's fine if they don't think it's causing a problem. I did a rush job on their advice. | 18:12 |
| ahasenack | Eickmeyer: and that was the info you had at that moment, understandable | 18:12 |
| ahasenack | thanks for bringing it up | 18:13 |
| Eickmeyer | np. I'm just glad I can fix my own mistakes, or at least mitigate them. | 18:13 |
| ahasenack | hah :) | 18:13 |
| ahasenack | don't worry | 18:13 |
| Eickmeyer | And now I know what I'm going to get harassed for at The Hauge: accidentally DDoS-ing LP. 😅 | 18:14 |
| ahasenack | just one more story on top of many others to be discussed at a bar in some future date | 18:14 |
| Eickmeyer | Right?!? | 18:14 |
| arraybolt3 | Does anyone know how all the 22.04.5 flavor images got set as ready even though not fully tested? | 18:54 |
| arraybolt3 | ubuntu-release: ^ | 18:56 |
| === john-cabaj1 is now known as john-cabaj | ||
| -queuebot:#ubuntu-release- New: accepted golang-1.23 [source] (noble-proposed) [1.23.1-1~24.04] | 19:22 | |
| -queuebot:#ubuntu-release- New: accepted golang-1.23 [source] (jammy-proposed) [1.23.1-1~22.04] | 19:25 | |
| -queuebot:#ubuntu-release- Unapproved: accepted wsl-setup [source] (noble-proposed) [0.5.4~24.04] | 19:27 | |
| -queuebot:#ubuntu-release- Unapproved: accepted wsl-setup [source] (jammy-proposed) [0.5.4~22.04] | 19:30 | |
| -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (jammy-proposed) [2.765.50] | 19:31 | |
| -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (jammy-proposed) [1.481.4] | 19:34 | |
| -queuebot:#ubuntu-release- New binary: golang-1.23 [amd64] (jammy-proposed/universe) [1.23.1-1~22.04] (no packageset) | 19:51 | |
| -queuebot:#ubuntu-release- New binary: golang-1.23 [arm64] (noble-proposed/universe) [1.23.1-1~24.04] (no packageset) | 19:56 | |
| -queuebot:#ubuntu-release- New binary: golang-1.23 [arm64] (jammy-proposed/universe) [1.23.1-1~22.04] (no packageset) | 19:56 | |
| -queuebot:#ubuntu-release- New binary: golang-1.23 [armhf] (noble-proposed/universe) [1.23.1-1~24.04] (no packageset) | 19:56 | |
| utkarsh2102 | hello hello | 20:04 |
| -queuebot:#ubuntu-release- Unapproved: squid (noble-proposed/main) [6.6-1ubuntu5.1 => 6.10-0ubuntu0.24.04.1] (ubuntu-desktop, ubuntu-server) | 20:06 | |
| utkarsh2102 | okay, I'm going to answer the few unanswered things and shepherd a few things forward for 22.04.5 and Oracular. | 20:13 |
| utkarsh2102 | tjaalton: hey, are you around? Kernel freeze is today - can you please send an announcement or something? | 20:14 |
| utkarsh2102 | paride: ok, mail approved, we're all good now for 22.04.5, no? | 20:24 |
| utkarsh2102 | i'll do the rest of the things i'm assigned :) | 20:24 |
| paride | utkarsh2102, we are! | 20:24 |
| utkarsh2102 | yay | 20:24 |
| paride | utkarsh2102, and thanks for getting the email approved | 20:25 |
| utkarsh2102 | thank you for leading the milestone, great stuff! <3 | 20:25 |
| Eickmeyer | !cookie | paride | 20:25 |
| ubottu | paride: Wow! You're such a great helper, you deserve a cookie! | 20:25 |
| Eickmeyer | Seems sarcastic, but it's not. | 20:26 |
| paride | heh! thanks Eickmeyer | 20:26 |
| -queuebot:#ubuntu-release- New binary: golang-1.23 [riscv64] (jammy-proposed/universe) [1.23.1-1~22.04] (no packageset) | 20:26 | |
| utkarsh2102 | haha, aw | 20:28 |
| utkarsh2102 | nice | 20:28 |
| utkarsh2102 | !cookie | paride | 20:28 |
| ubottu | paride: Wow! You're such a great helper, you deserve a cookie! | 20:28 |
| Eickmeyer | !botsnack | 20:32 |
| ubottu | Yum! Err, I mean, APT! | 20:32 |
| utkarsh2102 | ubuntu-sru: hey, jammy is unfrozen now! | 20:39 |
| utkarsh2102 | go crazy with the SRUs, y'all :D | 20:39 |
| ahasenack | utkarsh2102: thx | 20:39 |
| utkarsh2102 | paride: hey, can you update the topic to add the Doc String freeze? | 20:58 |
| paride | utkarsh2102, looking | 20:58 |
| utkarsh2102 | Â Â Â Â Documentation String Freeze & Kernel Feature Freeze | 20:58 |
| === ChanServ changed the topic of #ubuntu-release to: Released: 24.04 LTS Noble Numbat | Archive: Documentation String Freeze, Kernel Feature Freeze, Feature Freeze, UI Freeze | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or scotch | melius malum quod cognoscis | infinity, you are missed | ||
| paride | utkarsh2102, ^^ that good? or is it too redundant? | 21:01 |
| utkarsh2102 | it's good, can you please put it in order? | 21:02 |
| utkarsh2102 | Feature, UI, Doc String, Kernel Feature | 21:02 |
| === ChanServ changed the topic of #ubuntu-release to: Released: 24.04 LTS Noble Numbat | Archive: Feature Freeze, UI Freeze, Documentation String Freeze, Kernel Feature Freeze | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or scotch | melius malum quod cognoscis | infinity, you are missed | ||
| paride | ^^ done | 21:03 |
| utkarsh2102 | !cookie | paride | 21:03 |
| ubottu | paride: Wow! You're such a great helper, you deserve a cookie! | 21:03 |
| paride | two times in a row does seem sarcastic :P | 21:03 |
| paride | calling it a day! | 21:04 |
| utkarsh2102 | hehe | 21:04 |
| utkarsh2102 | take care, good night, paride o/ | 21:04 |
| utkarsh2102 | ok, email for doc string freeze has been sent | 21:19 |
| utkarsh2102 | needs to be moderated, hmmm | 21:19 |
| -queuebot:#ubuntu-release- New binary: fuse3 [amd64] (oracular-proposed/main) [3.14.0-7ubuntu1] (i386-whitelist) | 21:20 | |
| utkarsh2102 | ok, mail is out, yay | 21:22 |
| utkarsh2102 | I think I am done with almost everything i had | 21:23 |
| utkarsh2102 | oh wait | 21:23 |
| utkarsh2102 | arraybolt3: hey, you had asked something | 21:23 |
| arraybolt3 | utkarsh2102: I did indeed | 21:32 |
| utkarsh2102 | arraybolt3: hey hey | 21:49 |
| utkarsh2102 | like for .1, we mostly just went ahead with .5. all the images were smoke-tested, yes. | 21:50 |
| arraybolt3 | kk, as long as nothing went wrong, I'm happy :) | 21:51 |
| utkarsh2102 | it wasn't a perfect release and we had a lot of things on fire | 21:51 |
| utkarsh2102 | but we managed to somehow just do it | 21:51 |
| arraybolt3 | I'm fine with the lesser testing (we've tested the sap out of that OS like five times already), just wanted to make sure nothing was going awry | 21:51 |
| utkarsh2102 | we release-note'd few things | 21:51 |
| utkarsh2102 | arraybolt3: yes, in general & ideally, we want all the flavour leads to mark their stuff as ready | 21:52 |
| utkarsh2102 | but with .1 release & its shenanigans and then .5, we were a bit too swamped to carry that back & forth but we did ensure they're smoke tested | 21:52 |
| utkarsh2102 | i also analyzed all the manifests to see there's nothing in the diff that's crazy | 21:52 |
| arraybolt3 | +1 | 21:53 |
| utkarsh2102 | in the sense, no new random/unexplainable packages are being installed for .5 and so on.. | 21:53 |
| arraybolt3 | and yeah, my hair | 21:53 |
| arraybolt3 | 's on fire too so | 21:53 |
| arraybolt3 | the extra free time from not having to do all the testing is welcome :) | 21:53 |
| utkarsh2102 | hehe nice | 21:54 |
| utkarsh2102 | but we'd like to do this better from next time | 21:54 |
| utkarsh2102 | _ideally_ | 21:54 |
| utkarsh2102 | two things to note are | 21:54 |
| utkarsh2102 | - kylin, studio, mate, and budgie .5 images have two packages removed: libwpe-1.0-1 & libwpebackend* but I guess that's fine. | 21:55 |
| utkarsh2102 | - mate .5 image also seems to be removing hwdata but that's also fine I guess. | 21:55 |
| utkarsh2102 | why are they removed - whether it was dependency issues, seed changes, or whatever - I don't know | 21:55 |
| utkarsh2102 | but they don't look like crazy to me, hehe | 21:55 |
| -queuebot:#ubuntu-release- Unapproved: wireless-regdb (noble-proposed/main) [2022.06.06-0ubuntu2 => 2024.07.04-0ubuntu1~24.04.1] (core, kernel) | 22:34 | |
| jbicha | the wpe* stuff is no longer used in webkit2gtk 2.44.*, which was a security update | 22:58 |
| guiverc | paride, ML (22.04.5) link to https://discourse.ubuntu.com/t/contribute/26 which says at top page is replaced; please go elsewhere (not ideal) | 23:52 |
| utkarsh71 | jbicha: ah thanks | 23:53 |
| utkarsh71 | makes sense | 23:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!