/srv/irclogs.ubuntu.com/2022/08/30/#ubuntu-release.txt

arraybolt3[m]sarnold: The only reason it's really important that I can see is that it does possibly leave a user without Wi-Fi if they intuitively decide to go back and enable update installation rather than doing it after the install. It's not as big a deal as I initially thought, thankfully, and it may not even be a release blocker, though I can see this biting quite a few individuals (myself included, I found it by accident!).00:08
sarnoldarraybolt3[m]: it comes up often enough that *clearly* people use it :)00:08
vorlonarraybolt3[m]: is it a regression? :)00:09
sarnoldwe should put a transcript of using the installer in the CD liner notes, like the openbsd folks do :) then people would know what stages do what things, where to look for specific things, and they might not need to spend time exploring!00:09
arraybolt3[m]vorlon: I don't know, I can check the focal.4 ISO to find out (and since it's Ubuntu Desktop I can probably grab older ones).00:10
vorlonarraybolt3[m]: seems like it's unlikely to be a regression and therefore not a release blocker; but it would be good to know for sure00:10
arraybolt3[m]I remember it worked in Kubuntu, but it uses a slightly different Ubiquity thingy.00:11
arraybolt3[m]OK, not a regression. Focal.4 Ubuntu has the same problem.00:38
vorlonarraybolt3[m]: thanks for checking00:40
-queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (jammy-proposed) [1:41.7-0ubuntu0.22.04.5]01:09
-queuebot:#ubuntu-release- New: accepted haskell-what4 [amd64] (kinetic-proposed) [1.3-2]06:46
xnoxvorlon:  basically at this point i'm not sure if we want to demote-to-proposed the linux-restricted-[modules|signatures]-[oem-5.17|intel-iotg] or if we should respin them alone, or if we should remove them.07:58
xnoxand some people were not sure about iotg kernel roadmap for kinetic07:59
sil2100Whoops09:17
sil2100Everyone! There will most probably be a respin of 20.04.5. Apparently we're pulling in quite a bit of the 5.13 kernel into the images, mostly becasue of the nvidia-390 driver (which is not available for 5.15 from what I see)09:24
sil2100apw, klebers: ^ asking the kernel team if I can simply rip out the 390 bits from debian-cd09:25
schopinubuntu-release: could I get an ACK on LP: #1986984 (tzdata) please?09:33
ubottuLaunchpad bug 1986984 in tzdata (Ubuntu Kinetic) "[FFe] tzdata 2022c update" [Undecided, Confirmed] https://launchpad.net/bugs/198698409:33
xnoxsil2100:  we have done fudging with regexp which version numbers of nvidia stuff to include in CDs before. When we had too few / too many nvidias.09:34
xnoxsil2100:  doko: may i request assistance with v5.19 kernel migration in kinetic with $ ./demote-to-proposed --dry-run -d ubuntu -s kinetic -m "v5.19 kernel migration LP:#1987870 and LP:#1987869" linux-restricted-modules-oem-5.17 linux-restricted-signatures-oem-5.17 linux-restricted-modules-intel-iotg linux-restricted-signatures-intel-iotg09:35
ubottuLaunchpad bug 1987870 in linux-restricted-signatures-intel-iotg (Ubuntu) "Demote to proposed LRM portions of intel-iotg" [Undecided, Triaged] https://launchpad.net/bugs/198787009:35
ubottuLaunchpad bug 1987869 in linux-restricted-signatures-oem-5.17 (Ubuntu) "Demote to proposed LRM portions of linux-oem-5.17" [Undecided, Triaged] https://launchpad.net/bugs/198786909:35
xnoxall v5.19 kernels are ready to migrate; but are entagled via LRM / nvidia with the two kernels that are not ready. Demoting prebuilt LRM for those two kernels, will enable all other kernels to migrate, and we will resolve LRM status of these two kernels a bit later. In the mean time they will simply use dkms.09:36
xnoxcc: vorlon ^^^^09:38
dokoxnox: apw not online?09:41
xnoxdoko: on holidays09:43
lan3yanyone know if someone's looking into this issue which Azure are raising? https://status.azure.com/en-gb/status // https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/198811910:10
ubottuLaunchpad bug 1988119 in systemd (Ubuntu) "Update to systemd 237-3ubuntu10.54 broke dns" [Undecided, Confirmed]10:10
=== lan3y is now known as laney
laneybah stupid nick10:10
laneysil2100: ^- sorry to invoke you as the 'human router' :D getting some slight heat due to this and I don't know Nishit Majithia's nick to find them on irc10:20
LocutusOfBorgmigrating libghc-diagrams-core-dev/1.5.0-1/amd64 to testing makes libghc-diagrams-dev/1.4-5/amd64 uninstallable10:21
LocutusOfBorgvorlon, ^^ this is quite strange, not shown on tracker10:22
LocutusOfBorgbut on excuses10:22
LocutusOfBorgrebuilding it10:22
laney(happy to execute a rollback to the previous version)10:23
sil2100laney: hey! Lemme look ;)10:28
laney10:28
sil2100laney: so Nishit's IRC handle is nishit_, I see him on #ubuntu-devel10:30
sil2100I think I even chatted with him today!10:30
laneycheers, let's move over there10:31
=== juliank is now known as jak
=== jak is now known as juliank
-queuebot:#ubuntu-release- Builds: Ubuntu WSL [Focal 20.04.5] (2955461583) has been added10:54
-queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.54 => 237-3ubuntu10.54] (core) (sync)10:57
laney^- going to accept that systemd sync, it's part of what we discussed above11:38
laneyI did my copies with --auto-approve :-)11:38
-queuebot:#ubuntu-release- Unapproved: accepted systemd [sync] (bionic-proposed) [237-3ubuntu10.54]11:39
sil2100laney: hahah! Yes, thanks ;)12:02
icey[m]hey sil2100 - not sure what the best way to move https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1967139 forward; there seem to be bugs already filed to deal with the translate-toolkit issue breaking the autopkgtest12:17
ubottuLaunchpad bug 1967139 in python-cheroot (Ubuntu Jammy) "unable to enable ceph-mgr dashboard module" [High, Fix Committed]12:17
xnoxdoko:  thank you for demotion; but it made intel-iotg LRM migrate back straight away because you closed the bug; which has the block-proposed-kinetic set on it.13:41
xnoxdoko:  reopened the bug report, can you please demote intel-iotg again please?13:41
xnoxand do not close the bug report, such that it stays in -proposed =)13:41
schopinCould someone from the release team grant the FFe for tzdata? LP: #198698414:36
ubottuLaunchpad bug 1986984 in tzdata (Ubuntu Kinetic) "[FFe] tzdata 2022c update" [Undecided, Confirmed] https://launchpad.net/bugs/198698414:36
schopinsil2100: ^14:37
LocutusOfBorgdo we really need FFe for tzdata?14:39
LocutusOfBorgbtw why do we need such icu autogenerated files?14:40
tumbleweedyes, but you'll get it easily :)14:41
sil2100schopin: dune!14:42
sil2100Dune™14:42
schopinthanks :)14:44
schopinLocutusOfBorg: from what I gathered, it has something to do with PHP? The version introducing them wasn't mentioned in the changelog, and I didn't look much further.14:49
fnordahlOur latest kinetic openvswitch upload is stuck on the netplan.io autopkgtest for armhf. When running this test on a armhf system manually it succeeds. Is there any way to enable debug in the CI so that we can see what's going on in there? The artifacts provided does not provide enlightenment https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/armhf15:00
slyonfnordahl: I think it's missing the OVS kernel module on the LXD container host inside the autopkgtest infrastructure: https://launchpad.net/ubuntu/+source/netplan.io/0.105-0ubuntu215:04
slyonunfortunately that netplan update is stuck behind the pandoc build15:04
slyon(on armhf)15:04
vorlonLocutusOfBorg: haskell-diagrams removed15:07
fnordahlslyon thx alot for that, I did indeed load the module prior to running the test. So I guess we just have to wait until the netplan 0.105-0ubuntu2 package comes through then?15:08
slyonfnordahl: yes, that's why the test passes on all architectures but armhf. The module can be loaded inside the test on qemu (all but armhf), but the test doesn't have controll over the LXD container host (armhf)15:21
slyonfnordahl: that new upload should most probably resolve that situation, by skipping the test if OVS is not ready on the host15:22
LocutusOfBorgsigh pandoc15:26
slyonLocutusOfBorg: ^ indeed! I think that pandoc armhf build is running in cycles.... I saw it reaching "[214 of 214]" this morning and then starting over at "[  1 of 214]" :/15:29
slyoncc vorlon ^15:29
LocutusOfBorgslyon, its normal15:29
LocutusOfBorgit does two runs from 1 to 21415:30
slyonohh, OK15:30
LocutusOfBorgone is foo the other is bar don't remember the differences15:30
vorlonslyon: right, it's annoying15:30
LocutusOfBorgannoying is an euphemism :)15:30
vorlonbut more annoying, it turns out the armhf ghc is WAY slower in Ubuntu than in Debian15:30
LocutusOfBorgsomewhere it regressed on armhf only15:30
slyonso maybe one more day to get it resolved :)15:30
LocutusOfBorg^^ yes that one I was mentioning15:30
LocutusOfBorgI tried hard to understand why and I badly failed15:31
LocutusOfBorglooks like it slowly regressed during build, not that much15:31
LocutusOfBorgbtw pandoc failed in Debian on armhf... :)15:32
LocutusOfBorghaddock: panic! (the 'impossible' happened)15:33
LocutusOfBorgPlease report this as a GHC bug:  https://www.haskell.org/ghc/reportabug15:33
LocutusOfBorgso it would be *really* funny to wait a couple of days and see it fail15:33
LocutusOfBorgvorlon, what about, restore old pandoc, build what needed and put this one back?15:34
vorlonI would like this current pandoc build to get to the end, maybe it succeeds for us15:35
LocutusOfBorgvorlon, you have time to remove/copy/restore before the build finishes :D15:35
LocutusOfBorgin one hour we can retry what needs pandoc on armhf and restore15:35
LocutusOfBorgand yes, that "the impossible happened" is probably some ENOMEM15:36
-queuebot:#ubuntu-release- Unapproved: wireguard-linux-compat (bionic-proposed/universe) [1.0.20201112-1~18.04.1 => 1.0.20201112-1~18.04.4] (kernel-dkms)15:36
LocutusOfBorglast pandoc took 8h to build on armhf15:38
=== rharper_ is now known as rharper
vorlonmwhudson: did a gir-to-d fix ever happen?16:17
vorlonmwhudson: there was a new upload the same day as your last mailing list post but, er, the built package still depends on the old libphobos216:18
vorlonoh! no, this is because we bumped again from libphobos2-ldc-shared99 to libphobos2-ldc-shared10016:20
-queuebot:#ubuntu-release- New binary: openvdb [armhf] (kinetic-proposed/universe) [9.1.0-7ubuntu1] (ubuntustudio)16:24
-queuebot:#ubuntu-release- New binary: openvdb [riscv64] (kinetic-proposed/universe) [9.1.0-7ubuntu1] (ubuntustudio)16:46
bdmurrayschopin, LocutusOfBorg the icu information in tzdata is sort of documented here https://wiki.ubuntu.com/StableReleaseUpdates#tzdata it was something xnox added IIRC16:46
vorlonhttps://launchpad.net/ubuntu/+source/gir-to-d/0.22.0-3build1/+build/24325999 lovely, the whole ldc stack is broken again17:06
vorlonlooks like dh-dlang may have changed to pull in DEB_BUILD_CFLAGS and isn't filtering out bits unknown to ldc17:07
bdmurraysil2100: Is there somewhere in the ISO tracker you'd expect ISO test results for an offline install of Ubuntu with nvidia drivers? I'm not seeing an obvious test case for that.17:28
=== kees_ is now known as kees
sil2100bdmurray: huh? What about this? http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257539/testcases/1718/results19:00
bdmurraysil2100: I was not using UEFI but did that test now19:01
sil2100I think we really need to update the description of that test case, since it confuses people19:01
bdmurrayI plan to review the test cases before 22.10.19:01
bdmurrays/review/review and update/19:02
sil2100Thanks!19:02
sil2100Hey everyone! I'll be doing a one-off test image build of Ubuntu Desktop with -proposed enabled in a moment. I'll switch the tracker to point to the previous image once it's built19:04
sil2100I want this test image  to see if the kernel spin fixed the situation or not19:04
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220830)20:10
-queuebot:#ubuntu-release- New binary: mir-core [amd64] (kinetic-proposed/universe) [1.1.111-1] (no packageset)20:12
-queuebot:#ubuntu-release- New binary: mir-core [arm64] (kinetic-proposed/universe) [1.1.111-1] (no packageset)20:13
-queuebot:#ubuntu-release- New: accepted mir-core [amd64] (kinetic-proposed) [1.1.111-1]20:55
-queuebot:#ubuntu-release- New: accepted mir-core [arm64] (kinetic-proposed) [1.1.111-1]20:55
mwhudsonvorlon: oh no, the debian maintainer promised an upload but i don't know if it happened21:11
mwhudson(following up on +1 things is apparently not my strongest ability currently :-/)21:11
arraybolt3Just popped in, any testing in specific that needs done?21:26
-queuebot:#ubuntu-release- Unapproved: cloud-init (jammy-proposed/main) [22.2-0ubuntu1~22.04.3 => 22.3-13-g70ce6442-0ubuntu1~22.04.1] (core, ubuntu-cloud)21:30
-queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [22.2-0ubuntu1~20.04.3 => 22.3-13-g70ce6442-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)21:30
-queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [22.2-0ubuntu1~18.04.3 => 22.3-13-g70ce6442-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)21:31
vorlonmwhudson: yeah it apparently did happen, same day as your message - but I never noticed because then also another ldc lib transition happened21:37
mwhudsonvorlon: ah21:37
blackboxswbdmurray: not sure how your SRU vanfuage afternoon is looking. We've queued a cloud-init SRU upload in response to RAOF's review on Friday (needing to include a postinst script) and we've sync'd changes for two potential bug fixes found and fixed before our SRU unapproved upload was accepted https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/198731822:33
ubottuLaunchpad bug 1987318 in cloud-init (Ubuntu) "sru cloud-init (22.3 update) Bionic, Focal, Jammy" [Undecided, In Progress]22:33
blackboxsw*SRU vanguard*. /me tries facing the keyboard before typing22:33
bdmurrayI have an appointment this afternoon but will try and look at it when I return22:36
vorlonhaskell-abstract-par/armhf: 40 minutes to build on the buildd.  2 minutes to build in a lxd container in canonistack :/22:43
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220829.1)22:59
mwhudsonvorlon: wait what23:00
vorlonyeah23:00
vorlonso what's different23:00
mwhudsonwell container vs schroot but well23:01
mwhudsonkernel version?23:01
mwhudsonRAM available?23:01
vorlonyeah not sure23:01
vorlonthe canonistack instance has 4GiB RAM but I thought that's what launchpad is running also23:02
mwhudsoni think buildd vms have 8GiB23:03
vorlonwell then low memory on the buildds shouldn't be the cause23:03
mwhudsonindeed23:03
mwhudsonand if having more memory is making the build slower ...23:04
sarnoldI thought builders had 16 gigs but I can't remember the name of the package that dumps information about its runtime environment in its build logs..23:05
vorlonprocenv?23:05
sarnoldYAY that sounds right!23:05
vorlonlast uploaded in 2020 though :)23:05
sarnoldoh dagnabbit23:05
sarnoldMemTotal:        8167540 kB23:06
mwhudsonwell 10 minutes of the build on launchpad is installing build deps23:06
* vorlon nods23:06
mwhudson23 Aug 03:39:09 ntpdate[1947]: adjust time server 10.211.37.1 offset 0.004258 sec23:07
mwhudson| haskell-abstract-par 0.3.3-11build1 (armhf)  Tue, 23 Aug 2022 03:48:31 +0000 |23:07
sarnold*this* time I'm writing procenv down. Wish me luck next time I want it :)23:07
mwhudsonoh wait no that's just updating the chroot23:07
vorlonthat's still 30m vs 223:07
mwhudsonyeah23:08
mwhudsondo these machines just have really slow disk?23:11
mwhudsonbut it's similar hardware to canonistack aiui23:11
vorlonhttps://launchpadlibrarian.net/619656500/buildlog_ubuntu-kinetic-armhf.haskell-abstract-par_0.3.3-11build1_BUILDING.txt.gz shows 5.4.0-124-generic and I'm running 5.4.0-125-generic23:12
mwhudsonprobably should get someone launchpaddy involved23:12
vorlondisk slowness doesn't explain it being a ghc-specific problem23:12
mwhudsonrather than us just guessing23:12
vorlonyeah I've asked in MM ~Launchpad23:13
mwhudsontrue and it definitely seems mich worse with haskell stuff23:13
vorlonthe entire haskell-abstract-par build tree is 27M23:13
vorlonand glib-d ftbfs because gir-to-d is emitting non-unique constructors, hurray23:23
-queuebot:#ubuntu-release- New sync: appstream-generator (kinetic-proposed/primary) [0.8.8-1]23:43
-queuebot:#ubuntu-release- New: rejected appstream-generator [sync] (kinetic-proposed) [0.8.8-1]23:47

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