[00:15] -queuebot:#ubuntu-release- New binary: mypaint [riscv64] (noble-proposed/universe) [2.0.1-10] (ubuntustudio)
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [amd64] (noble-proposed) [2.0.1-10]
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [armhf] (noble-proposed) [2.0.1-10]
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [riscv64] (noble-proposed) [2.0.1-10]
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [arm64] (noble-proposed) [2.0.1-10]
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [s390x] (noble-proposed) [2.0.1-10]
[00:31] -queuebot:#ubuntu-release- New: accepted mypaint [ppc64el] (noble-proposed) [2.0.1-10]
[00:34] <vorlon> Eickmeyer: there you go
[00:35] <Eickmeyer> 😁
[00:36] <Eickmeyer> Yep, turnaround time on that was pretty quick after a quick back-and-forth on the upstream.
[01:34] -queuebot:#ubuntu-release- New binary: gcc-14-cross-ports [arm64] (noble-proposed/universe) [1ubuntu1] (i386-whitelist)
[02:01] <mwhudson> vorlon: thanks for the debian-cd reviews btw
[03:34] -queuebot:#ubuntu-release- New binary: gcc-14-cross-ports [ppc64el] (noble-proposed/universe) [1ubuntu1] (i386-whitelist)
[04:37] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (jammy-proposed) [1:22.04.19]
[06:00] <pushkarnk> Would it be possible (and is it correct) to remove ldap-account-manager from the excuses blocking Perl? One of the binary packages in it is blocked on a PHP-related dependency mismatch, the other binary package which is Perl-based seems to be having no issues. I wonder why this should block Perl. See bug 2051559
[06:00] -ubottu:#ubuntu-release- Bug 2051559 in ldap-account-manager (Ubuntu) "New dependency - php-psr-log -  is unsatisfiable on noble" [Undecided, New] https://launchpad.net/bugs/2051559
[06:03] <pushkarnk> nvm, I checked the latest report and it has been removed
[06:17] <vorlon> Eickmeyer: just to check, were you still planning to do a livecd-rootfs ppa build somewhere for ubuntu-image testing?
[06:18] <vorlon> pushkarnk: yeah I reran the tests with correct triggers
[06:20] <pushkarnk> ack, thanks!
[06:29] <ginggs> i've been through the python3.12-default / perl-5.38 collisions (at the bottom of both trackers), i.e. claws-mail, freeradius, fungw, etc.
[06:30] <ginggs> most are not blocked by python3.12 (they don't build extensions for 3.12 only)
[06:31] <ginggs> the ones that are blocked have previous versions built with perl 5.38 and not python3.12, which we might be able to restore?
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/glgrib/1.0-3build2
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/graphviz/2.42.2-7build4
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/libsbml/5.20.2+dfsg-2build1
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/libsolv/0.7.27-2build1
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/mapserver/8.0.1-2build3
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/openbabel/3.1.1+dfsg-9ubuntu1
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/pcp/6.1.1-1build2
[06:31] <ginggs> https://launchpad.net/ubuntu/+source/zbar/0.23.93-1
[06:32] <ginggs> in addition to those collisions, glgrib is blocked on a new eccodes upload which FTBFS on some architectures
[06:34] <ginggs> and uwsgi is blocked on a new glusterfs upload which no longer builds on armhf
[07:31] <vorlon> so I'm retrying all tests that are currently marked as 'in progress' because they seem to have been lost somewhere along the way, they don't show up on https://autopkgtest.ubuntu.com/running (cc: paride)
[07:31] <vorlon> ... except a bunch of them queued and now I'm getting 403s
[07:33] <vorlon> because I got randomly bounced to the other backend invalidating my cookie, yay
[07:47] -queuebot:#ubuntu-release- New: accepted gcc-14-cross-ports [amd64] (noble-proposed) [1ubuntu1]
[07:47] -queuebot:#ubuntu-release- New: accepted gcc-14-cross-ports [ppc64el] (noble-proposed) [1ubuntu1]
[07:47] -queuebot:#ubuntu-release- New: accepted gcc-14-cross-ports [arm64] (noble-proposed) [1ubuntu1]
[07:47] -queuebot:#ubuntu-release- New: accepted gcc-14-cross-ports [s390x] (noble-proposed) [1ubuntu1]
[09:24] -queuebot:#ubuntu-release- New source: qatengine (noble-proposed/primary) [1.5.0-0ubuntu1]
[09:31] <paride> thanks for the heads-up vorlon, looking
[09:47] <vorlon> doko: hmm the latest version of gfortran in Debian seems to be missing the alternative for f95?  noticed because I can't build cmor for time_t :/
[10:01] <doko> vorlon: fixed in the VCS. will upload tomorrow
[10:01] <vorlon> doko: cheers
[10:13] -queuebot:#ubuntu-release- Packageset: Added gdm3 to ubuntu-desktop in jammy
[10:13] -queuebot:#ubuntu-release- Packageset: Added gdm3 to ubuntu-desktop in mantic
[10:13] -queuebot:#ubuntu-release- Packageset: Added gdm3 to ubuntu-desktop in noble
[10:54] <tchavadar> Hello all, it seems like flash-kernel update that includes Xilinx KD240 support in jammy is blocked due to freeze (https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#:~:text=31%3A25%202024-,flash%2Dkernel%20(3.104ubuntu17%20to%203.104ubuntu18),-Migration%20status%20for). Is it possible to approve it? I have provided test resilts from Canonical QA in the related LP bug.
[11:43] <kxuan1> Hi! We tries to fix a typo in alsa-ucm-conf package. It causes the alsa does not work on OEM's devices. But in proposed-migration, I found that the package has been freezed. Could someone help us to merge the patch into jammy? Thanks!
[11:45] <kxuan1> Link: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327
[11:45] -ubottu:#ubuntu-release- Launchpad bug 2049327 in alsa-ucm-conf (Ubuntu Mantic) "`alsactl init` unable to initialze audio device on G700" [Undecided, Fix Committed]
[11:46] <LocutusOfBorg> thanks sergiodj for libvirt!
[12:08] <rbasak> RAOF: did you release neutron in Focal earlier, and if so, did you get an OOPS?
[12:08] <rbasak> mfo: ^
[12:19] <ginggs> tchavadar: you want an SRU vanguard, and today that's rbasak
[13:20] -queuebot:#ubuntu-release- Unapproved: ltrace (focal-proposed/main) [0.7.3-6.1ubuntu1 => 0.7.3-6.1ubuntu1.1] (core)
[13:21] <tchavadar> rbasak: can you please check if the SRU for flash-kernel to jammy is ok to be released?
[13:23] <rbasak> tchavadar: this is bug 2037407 I think?
[13:23] -ubottu:#ubuntu-release- Bug 2037407 in flash-kernel (Ubuntu Mantic) "[SRU] Add support for AMD-Xilinx Kria KD240" [Undecided, Fix Committed] https://launchpad.net/bugs/2037407
[13:23] <tchavadar> rbasak: yes correct it is about 2037407
[13:24] <rbasak> tchavadar: the bug description mentions expected testing of ZCU 102, 104, 106, 111 for example, and that doesn't appear to have been done?
[13:26] <tchavadar> rbasak: let me check with canonical QA if we have availability on those devices and if the package has been tested on those boards
[13:26] <rbasak> tchavadar: thanks. The SRU team's expectation is that the test plan agreed in the bug is completed and there's a report in the bug that confirms the agreed plan was carried out with the appropriate version numbers reported.
[13:27] <rbasak> tchavadar: it's incorrect to mark the bug verification-done until that's done.
[13:29] <tchavadar> rbasak: let me mark it back to needs-verification, seems like I forgot to check ZCU results, I have asked QA to provide them if possible
[13:43] <Eickmeyer> vorlon: That's the plan and on my radar today.
[14:01] -queuebot:#ubuntu-release- Unapproved: qemu (jammy-proposed/main) [1:6.2+dfsg-2ubuntu6.16 => 1:6.2+dfsg-2ubuntu6.17] (ubuntu-server, virt)
[14:28] -queuebot:#ubuntu-release- Unapproved: cinder (jammy-proposed/main) [2:20.3.1-0ubuntu1 => 2:20.3.1-0ubuntu1.1] (openstack)
[15:08] <leokolb> Todays iso builds have not updated the cdiimage site .. http://cdimage.ubuntu.com - all flavors also affected..
[15:19] <tsimonq2> qa-help ^^^
[15:21] <Skia> ack, we'll have a look, thanks
[15:21] <tsimonq2> <3
[15:22] <leokolb> (y)
[16:06] <Skia> we'll have a closer look tomorrow, but for now, there is no obvious failure in the logs, so maybe some kind of transiant network issue or else. If it keeps failing tomorrow, we'll dig deeper.
[16:08] <leokolb> tks
[17:00] -queuebot:#ubuntu-release- New source: qatzip (noble-proposed/primary) [1.1.2-0ubuntu1]
[17:20] -queuebot:#ubuntu-release- Unapproved: apache2 (jammy-proposed/main) [2.4.52-1ubuntu4.7 => 2.4.52-1ubuntu4.8] (i386-whitelist, ubuntu-server)
[17:21] <sergiodj> LocutusOfBorg: I decided to go ahead an upload it even with the regression, which shouldn't impact anything other than live migrations
[17:21] <vorlon> the 20240131 daily image directories are all present on the rsync source
[17:21] <vorlon> I've attempted to re-trigger the frontends to pull (`sync-mirrors`)
[17:23] <vorlon> I got 4 inbound rsync connections in response to the trigger
[17:24] <vorlon> for releases and torrent. not for cdimage
[17:26] <vorlon> RT opened
[17:29] <vorlon> tsimonq2, Skia: the QA team does not have operational oversight of cdimage.u.c; not sure if there is some process that's been discussed which resulted in a qa ping here
[17:55] <Eickmeyer> vorlon: livcd-rootfs building in https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa for a test.
[17:58] -queuebot:#ubuntu-release- New binary: ruby3.2 [amd64] (noble-proposed/universe) [3.2.3-1] (no packageset)
[17:58] <leokolb> As with other daily ISO's - todays Lubuntu iso failed to update the http://cdimage.ubuntu.com/lubuntu/daily-live/current/ website the build was successful
[18:01] -queuebot:#ubuntu-release- New binary: ruby3.2 [ppc64el] (noble-proposed/universe) [3.2.3-1] (no packageset)
[18:03] -queuebot:#ubuntu-release- New binary: ruby3.2 [armhf] (noble-proposed/universe) [3.2.3-1] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: ruby3.2 [s390x] (noble-proposed/universe) [3.2.3-1] (no packageset)
[18:25] -queuebot:#ubuntu-release- New: accepted ruby3.2 [amd64] (noble-proposed) [3.2.3-1]
[18:25] -queuebot:#ubuntu-release- New: accepted ruby3.2 [ppc64el] (noble-proposed) [3.2.3-1]
[18:25] -queuebot:#ubuntu-release- New: accepted ruby3.2 [armhf] (noble-proposed) [3.2.3-1]
[18:25] -queuebot:#ubuntu-release- New: accepted ruby3.2 [s390x] (noble-proposed) [3.2.3-1]
[18:50] <vorlon> Eickmeyer: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/edubuntu-preinstalled/
[18:51] <Eickmeyer> vorlon: +1
[19:11] <Eickmeyer> vorlon: Yep, same error.
[19:13] <vorlon> upils: ^^
[19:13] <Eickmeyer> https://launchpadlibrarian.net/712105193/buildlog_ubuntu_noble_arm64_raspi_edubuntu-preinstalled_BUILDING.txt.gz
[19:13] <vorlon> Eickmeyer: oh; but the log says 'ubuntu-image 3.2 from Canonical** installed
[19:14] <vorlon> which is the stable version?
[19:14] <Eickmeyer> Right, I'm trying to figure out why it didn't pull from edge.
[19:14] <vorlon> ok
[19:17] <Eickmeyer> vorlon: My change was in line 27 of live-build/auto/build: 	LB_UBUNTU_IMAGE_CHANNEL="${LB_UBUNTU_IMAGE_CHANNEL:-edge}"
[19:17] <vorlon> Eickmeyer: sorry, I'm not in a position to dig into the code on this right now
[19:17] <Eickmeyer> No worries, I'll keep digging
[19:17] <vorlon> I have 800 more packages to upload to Debian experimental
[19:17] <Eickmeyer> Ew.
[19:18]  * Eickmeyer has been getting debian-multimedia emails about that.
[19:51] <Eickmeyer> vorlon: It didn't pull from livecd-rootfs my PPA.: `Get:164 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 livecd-rootfs arm64 24.04.25 [118 kB]` - that should be a launchpad address and the version number is wrong.
[19:51] <vorlon> ah well then
[19:51] <vorlon> I'll look in a bit to try to work out what I missed, since EXTRA_PPAS didn't do it
[19:52] <Eickmeyer> Sounds good. :)
[19:53] <vorlon> oh. did I trigger it too soon before publication, maybe
[19:53] <vorlon> trying again
[20:04] <Eickmeyer> ack
[20:25] <Eickmeyer> vorlon: Failed again, everything looks correct. `ubuntu-image (edge) 3.2+snap2 from Canonical** installed`
[20:25] <Eickmeyer> https://launchpadlibrarian.net/712120981/buildlog_ubuntu_noble_arm64_raspi_edubuntu-preinstalled_BUILDING.txt.gz
[20:25] <Eickmeyer> upils: ^
[20:26] <vorlon> Eickmeyer: ok then.  please be sure to post this to the bug also
[20:26] <Eickmeyer> vorlon: thanks
[20:27] <upils> sadly I still need to investigate more to understand what is still using the /dev in the chroot
[20:27] <vorlon> upils: does your code detect and recursively unmount any submounts?
[20:28] <vorlon> my initial read was that something that's part of edubuntu was mounting a sub-fs that we don't see mounted by default in Ubuntu
[20:28] <vorlon> but the discussion I saw seemed to focus on questions of whether /dev itself was in use and being unmounted correctly
[20:28] <upils> no, and this is likely the next step, because I suspect the installation of some package is mounting something in /dev
[20:29] <vorlon> yes, that was what it initially looked like to me
[20:30] <upils> but also a couple of other things were problematic (like unmouting in the wrong order, bind mounting, etc.)
[20:31] <upils> but yeah I will fix the code to look for submounts
[20:37] <upils> and fun fact: this is the same error, but not at the same state of the build. Because now the install_packages is succeeding (even if /dev cannot be properly unmounted) but then when the preseed_image step tries to mount again it fails
[20:38] <upils> mount is such a marvelous thing :D
[21:25] <vorlon> fwiw one of two cdimage.ubuntu.com frontends is fixed
[21:25] <vorlon> and IS is working on the other
[21:48] <vorlon> right well it looks like all the frontends *did* sync, but now syncing is broken again
[21:50] -queuebot:#ubuntu-release- Unapproved: apache2 (mantic-proposed/main) [2.4.57-2ubuntu2.2 => 2.4.57-2ubuntu2.3] (i386-whitelist, ubuntu-server)
[22:42] <rbasak> RAOF: o/ did you see my ping above about neutron?
[23:20] -queuebot:#ubuntu-release- New binary: python-build [amd64] (noble-proposed/universe) [1.0.3-1] (i386-whitelist)
[23:35] -queuebot:#ubuntu-release- New: accepted python-build [amd64] (noble-proposed) [1.0.3-1]