/srv/irclogs.ubuntu.com/2024/10/14/#ubuntu-release.txt

-queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (jammy-proposed/main) [1:0.9.6.2~0.22.04.7 => 1:0.9.6.2~0.22.04.8] (desktop-core)09:13
rbasakubuntu-archive: please stop phasing for netplan.io due to bug 2084444. It's already been cut to 0%, but we need to make sure it doesn't restart itself.11:31
-ubottu:#ubuntu-release- Bug 2084444 in netplan.io (Ubuntu Jammy) "juju can not parse new 50-cloud-init.yaml properly after netplan 0.107 under 22.04" [Critical, New] https://launchpad.net/bugs/208444411:31
-queuebot:#ubuntu-release- Unapproved: grub2-signed (oracular-proposed/main) [1.209 => 1.209.1] (core) (sync)13:53
-queuebot:#ubuntu-release- Unapproved: grub2-unsigned (oracular-proposed/main) [2.12-5ubuntu5 => 2.12-5ubuntu5.1] (core) (sync)13:53
mkukrican someone look at 2084104? (windows 10 dual boot broken in oracular grub)14:04
bdmurrayrbasak: How was it "cut to 0%"?14:10
bdmurrayIt looks like it is still at 0% right now given https://launchpad.net/ubuntu/jammy/amd64/libnetplan-dev/0.107.1-3ubuntu0.22.04.1 . However, it's possible that the phased-updater may continue to bump the percentage if it doesn't think there is a regression. I don't recall the code exactly but had some doubts in this area.14:15
bdmurrays/some doubts/some recent doubts/14:15
bdmurrayWell actualy git commit 4f255204d577939f2f795dff627c4a99ced385b5 of ubuntu-archive-tools was a change to the phased-updater for just this situation14:18
bdmurrayOkay, I think I see now the phasing stopped due to an error (see the phased-updates reports) and so the concern is that it might start phasing again. I'll stop the phasing to be really sure.14:22
bdmurrayI've done my bit https://pastebin.ubuntu.com/p/fc7d6P3x6H/14:26
bdmurrayIDK whether or not it will really all work. Somebody who wants to doulbe check could read the phased-updater code to sort out if my change to the phased-updater percentage was recorded.14:29
bdmurrayMy using the same LP API query.14:29
bdmurrayIt's a holiday here but "if you still have a problem, and no one else can help, and if you know how to find me" ...14:31
-queuebot:#ubuntu-release- Unapproved: pillow (noble-proposed/main) [10.2.0-1ubuntu1 => 10.2.0-1ubuntu1.1] (desktop-core)15:24
Skiamy understanding of this line (https://git.launchpad.net/ubuntu-archive-tools/tree/phased-updater#n757) is that it prevents further phasing if the pup is 0, which it now is. Multiple local runs of the phased-updater (with additional local logging) show that this path is indeed taken for netplan.io on jammy, so I would tend to say that it's safe for now, as long as we don't delete the problem from the15:29
Skiaerror tracker (which shouldn't happen)15:30
SkiaIt's a bit of a shame that we don't have access to the `phased-updates.log` file next to the html report, that would help figure out things like that (but would be even better with additional logging)15:30
bdmurrayI think it should take the code path at line 684 though so that somebody can't accidentally override the error as a false positive.15:32
bdmurrayThe phased-updates.log file is on ubuntu-archive-toolbox IIRC15:33
Skiado you have the link?15:33
Skiabdmurray: code path line 684 was not taken in my local run15:34
bdmurrayhttps://git.launchpad.net/ubuntu-archive-tools/tree/phased-updater#n68415:34
Skiathis path has a log, and it didn't show locally15:34
Skiaa link to the logs on ubuntu-archive-toolbox :-)15:35
bdmurrayOh no, I don't think they are in ~/public/15:35
Skiathat's why I said it would be useful15:35
bdmurrayI wonder what `pbs[0].creator_link` is15:36
Skiathat would help confirm that manual stop was taken into account15:36
bdmurrayI agree now that I don't have access to the server. ;-)15:36
Skiapbs[0].creator_link is https://api.launchpad.net/devel/~ubuntu-archive-robot apparently15:39
=== cpaelzer_ is now known as cpaelzer
Skiahttps://api.launchpad.net/devel/ubuntu/+archive/primary/+binarypub/21503379315:41
rbasakbdmurray, Skia: thank you! I'm not really familiar with this but I think I heard someone mention in an unrelated thread that some package had stopped phasing due to error reports and then the error reports dwindled, causing phasing to restart by itself. That may be a complete misunderstanding though. But that's why I asked for the phasing stop regardless.15:47
Skiayes, as far as I know now, it could happen, because the phased-updater doesn't seem to see the manual stop15:48
rbasakubuntu-archive opinions on bug 2084444 please? No revert, and some pocket copying instead, as slyon is requesting?15:51
-ubottu:#ubuntu-release- Bug 2084444 in netplan.io (Ubuntu Jammy) "juju can not parse new 50-cloud-init.yaml properly after netplan 0.107 under 22.04" [Critical, New] https://launchpad.net/bugs/208444415:51
Skiabdmurray: I understand from these lines (https://git.launchpad.net/launchpad/tree/lib/lp/soyuz/model/publishing.py#n1206) that your override was simply not taken into account, because it was a no change. Thus, no publishing history were added, and the phased-updater was unable to see that there was a manual override. In any case, the phased updater is only looking at the very first publishing15:54
Skiahistory, and I'm not sure of the ordering, but if the oldest comes first, you would be ignored anyway 🙃15:54
vorlonrbasak: +1 from me; it's a national holiday here however so I would prefer to just take direction from you on the specifics and just do the button-clicking16:09
-queuebot:#ubuntu-release- Unapproved: accepted boost1.83 [sync] (noble-updates) [1.83.0-2.1ubuntu3]16:11
vorlonahasenack_: libboost-url1.83.0 moved to main now in noble-updates16:12
rbasakvorlon: thanks! So assuming you can't see a problem with doing this, please go ahead and copy src:netplan.io: 1) from jammy-updates back to jammy-proposed, and then 2) (downgrading) from jammy-security to jammy-updates.16:12
rbasakOr do we need to test that first in any way?16:13
rbasakI don't see that we would, since that's what was there before and apt won't downgrade.16:13
vorlonI don't see any testing that needs to be done.  in some cases we have to worry about problems with uninstallability due to partial upgrades but I don't think that will apply here16:14
vorlonrbasak: copies done16:15
rbasakThanks!16:15
jamespagethankyou vorlon much appreciated :)16:15
slyonthank you vorlon and rbasak for helping with this!16:20
* bdmurray feels left out16:25
=== fuseteam1 is now known as fuseteam
=== fuseteam1 is now known as fuseteam
rbasak<rbasak> bdmurray, Skia: thank you!16:52
rbasakYou may feel thanked :-)16:52
-queuebot:#ubuntu-release- Unapproved: s390-tools (jammy-proposed/main) [2.20.0-0ubuntu3.3 => 2.20.0-0ubuntu3.4] (core)17:23
=== fuseteam1 is now known as fuseteam
=== pushkarnk1 is now known as pushkarnk
-queuebot:#ubuntu-release- Unapproved: rejected sssd [source] (jammy-proposed) [2.6.3-1ubuntu3.4.22.04.1]18:11
mkukriubuntu-sru, there is grub2-{un}signed for oracular in unapproved19:04
mfomkukri, ack, thanks for the ping; i'll add it to the list.19:05
-queuebot:#ubuntu-release- Unapproved: accepted s390-tools [source] (jammy-proposed) [2.20.0-0ubuntu3.4]19:31
-queuebot:#ubuntu-release- Unapproved: s390-tools (jammy-proposed/main) [2.20.0-0ubuntu3.3 => 2.20.0-0ubuntu3.4] (core)19:34
mfomkukri, o/ just FYI, oracular's unapproved queue apparently hasn't yet been handed over to the SRU team, so I can't process the grub2-{un,}signed uploads.22:56
-queuebot:#ubuntu-release- Unapproved: razercfg (noble-proposed/universe) [0.42+ds-4ubuntu0.1 => 0.42+ds-4ubuntu0.2] (no packageset)23:26
mfoRAOF, hey Chris o/ this ^ is an incremental fix for noble-proposed, in case you have SRU review cycles yet. :) thanks!23:28
RAOFI'm back, but vanguard day for me is tomorrow :)23:29
mfoRAOF, Ah! Didn't you have shifts on Tuesdays? Or is it just a temporary change?23:30
RAOFI celebrate western-hemisphere Tuesday :)23:31
mfoRAOF, Haha, roger. Thanks for clarifying!23:34
-queuebot:#ubuntu-release- Unapproved: accepted razercfg [source] (noble-proposed) [0.42+ds-4ubuntu0.2]23:37

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!