[00:29] -queuebot:#ubuntu-release- Unapproved: yt-dlp (noble-backports/universe) [2024.09.27-1~bpo24.04.1 => 2024.11.18-1~bpo24.04.1] (no packageset)
[01:09] -queuebot:#ubuntu-release- New: accepted pantalaimon [amd64] (plucky-proposed) [0.10.5-3]
[01:09] -queuebot:#ubuntu-release- New: accepted puppet-agent [amd64] (plucky-proposed) [8.10.0-2]
[01:09] -queuebot:#ubuntu-release- New: accepted qgis [amd64] (plucky-proposed) [3.34.13+dfsg-1]
[01:09] -queuebot:#ubuntu-release- New: accepted qgis [armhf] (plucky-proposed) [3.34.13+dfsg-1]
[01:09] -queuebot:#ubuntu-release- New: accepted paraview [amd64] (plucky-proposed) [5.13.1+dfsg-9]
[01:09] -queuebot:#ubuntu-release- New: accepted qgis [arm64] (plucky-proposed) [3.34.13+dfsg-1]
[01:09] -queuebot:#ubuntu-release- New: accepted python-mt940 [amd64] (plucky-proposed) [0.6.0-2]
[01:09] -queuebot:#ubuntu-release- New: accepted qgis [ppc64el] (plucky-proposed) [3.34.13+dfsg-1]
[01:09] -queuebot:#ubuntu-release- New: accepted qgis [s390x] (plucky-proposed) [3.34.13+dfsg-1]
[01:09] -queuebot:#ubuntu-release- New: accepted rocblas [arm64] (plucky-proposed) [5.5.1+dfsg-7]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [amd64] (plucky-proposed) [1.44.2-2]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [armhf] (plucky-proposed) [1.44.2-2]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [riscv64] (plucky-proposed) [1.44.2-2]
[01:09] -queuebot:#ubuntu-release- New: accepted vg [amd64] (plucky-proposed) [1.59.0+ds-0.1]
[01:09] -queuebot:#ubuntu-release- New: accepted rocblas [amd64] (plucky-proposed) [5.5.1+dfsg-7]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [arm64] (plucky-proposed) [1.44.2-2]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [s390x] (plucky-proposed) [1.44.2-2]
[01:09] -queuebot:#ubuntu-release- New: accepted rocblas [ppc64el] (plucky-proposed) [5.5.1+dfsg-7]
[01:09] -queuebot:#ubuntu-release- New: accepted vg [arm64] (plucky-proposed) [1.59.0+ds-0.1]
[01:09] -queuebot:#ubuntu-release- New: accepted rust-broot [ppc64el] (plucky-proposed) [1.44.2-2]
=== hgwbzjezmokhepyv is now known as axpphndmpygoodzy
=== axpphndmpygoodzy is now known as georgiag
[04:35] -queuebot:#ubuntu-release- New binary: qt6-tools [s390x] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[04:40] -queuebot:#ubuntu-release- New binary: qt6-tools [ppc64el] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[04:41] -queuebot:#ubuntu-release- New binary: qt6-tools [armhf] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[04:42] -queuebot:#ubuntu-release- New binary: qt6-tools [arm64] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[04:43] -queuebot:#ubuntu-release- New binary: qt6-tools [amd64] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[07:52] -queuebot:#ubuntu-release- New binary: qt6-tools [riscv64] (plucky-proposed/universe) [6.7.2-6] (no packageset)
[08:39] <mkukri> hi ubuntu-sru,  i think pillow for noble can be released now
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [amd64] (plucky-proposed) [6.7.2-6]
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [armhf] (plucky-proposed) [6.7.2-6]
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [riscv64] (plucky-proposed) [6.7.2-6]
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [arm64] (plucky-proposed) [6.7.2-6]
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [s390x] (plucky-proposed) [6.7.2-6]
[08:57] -queuebot:#ubuntu-release- New: accepted qt6-tools [ppc64el] (plucky-proposed) [6.7.2-6]
=== pushkarnk1 is now known as pushkarnk
[09:11] <zhsj> ubuntu-sru: please remove golang-1.23 from focal new queue, i will follow a toolchain sru rule, to ask someone to do binary copy to focal new queue, from a -security only ppa.
[09:12] <zhsj> and the zip sru for noble and oracular is ready to release.
[10:39] <mkukri> ubuntu-archive i also have https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/2086841
[10:39] -ubottu:#ubuntu-release- Launchpad bug 2086841 in cd-boot-images-riscv64 (Ubuntu) "Please remove cd-boot-images-* from plucky" [Undecided, New]
[11:09] -queuebot:#ubuntu-release- New: rejected golang-1.23 [source] (focal-proposed) [1.23.1-1~20.04]
[11:52] -queuebot:#ubuntu-release- Unapproved: dns-root-data (focal-proposed/main) [2023112702~ubuntu0.20.04.1 => 2024071801~ubuntu0.20.04.1] (desktop-core, ubuntu-server)
[11:52] -queuebot:#ubuntu-release- Unapproved: dns-root-data (jammy-proposed/main) [2023112702~ubuntu0.22.04.1 => 2024071801~ubuntu0.22.04.1] (desktop-core, ubuntu-server)
[11:53] -queuebot:#ubuntu-release- Unapproved: dns-root-data (noble-proposed/main) [2023112702~willsync1 => 2024071801~ubuntu0.24.04.1] (desktop-core, ubuntu-server)
[11:53] -queuebot:#ubuntu-release- Unapproved: dns-root-data (oracular-proposed/main) [2024041801 => 2024071801~ubuntu0.24.10.1] (desktop-core, ubuntu-server)
=== cpaelzer_ is now known as cpaelzer
[12:05] <cpaelzer> mkukri: sorry for my unawareness of this area, but do the changes in https://code.launchpad.net/~mkukri/debian-cd/+git/ubuntu/+merge/476337 need to land somewhere before the old image packages can be removed?
[12:05] <cpaelzer> The comments suggest releasing the new grub is enough and https://launchpad.net/ubuntu/+source/grub2/2.12-5ubuntu7 is fully in plucky
[12:06] <mkukri> it was already deployed on cdimage build machines and apparently the latest plucky images are built without cd-boot-images now
[12:06] <cpaelzer> maybe I need to educate myself about these cd-boot-image-* and debian-cd, pointers ewlcome
[12:06] <cpaelzer> oh I see mkukri, that is where it needs to land and it did
[12:06] <mkukri> and grub needed to land in the archive but both did
[12:06] <mkukri> latest images seem to work and mwhudson confirmed that they were built using the new debian-cd
[12:07] <cpaelzer> is there any place once can check to see that this landed in the cdimage build machines and a pointer to a log of their last build?
[12:07] <mkukri> i dont have info beyond a mattermost thread on the foundations channel, sorry
[12:08] <cpaelzer> reading FO203 spec to update myself on this topic ...
[12:08] <mkukri> it's a very small spec
[12:09] <cpaelzer> I've not found cd-boot-image nor debian-cd in recent foundations channel, I'd appreciate a link to have a look myself
[12:09] <mkukri> i dont think he's up at this time, but mwhudson can probably comment on this later
[12:10] <cpaelzer> spec is small but still enough to make it TIL for me :-)
[12:11] <mkukri> tbf i knew absolutely nothing about any of this before working on this change
[12:12] <mkukri> and kind of want to go back to that state :D
[12:12] <cpaelzer> understandably
[12:17] <cpaelzer> mkukri: that discussion and the spec helped already - I stated on the bug what I'd think we should demonstrate to remove them
[12:17] <cpaelzer> mkukri: anyone deeper into the matter can remove them earlier, but otherwise it is still ok as we likely only have to wait until mwhudson is around again
[12:23] <mkukri> that sounds good to me. none of this is very urgent just wanted to put it out there
[14:33] -queuebot:#ubuntu-release- Unapproved: cockpit (jammy-backports/universe) [324-1~bpo22.04.1 => 329-1~bpo22.04.1] (no packageset)
[14:33] -queuebot:#ubuntu-release- Unapproved: cockpit (oracular-backports/universe) [324-1 => 329-1~bpo24.10.1] (no packageset)
[14:33] -queuebot:#ubuntu-release- Unapproved: cockpit (noble-backports/universe) [327-1~bpo24.04.1 => 329-1~bpo24.04.1] (no packageset)
[14:33] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (jammy-backports/universe) [94-1~bpo22.04.1 => 99-1~bpo22.04.1] (no packageset)
[14:34] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (jammy-backports/universe) [319-1~bpo22.04.1 => 324-1~bpo22.04.1] (no packageset)
[14:34] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (noble-backports/universe) [98-1~bpo24.04.1 => 99-1~bpo24.04.1] (no packageset)
[14:34] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (oracular-backports/universe) [94-1 => 99-1~bpo24.10.1] (no packageset)
[14:34] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (noble-backports/universe) [323-1~bpo24.04.1 => 324-1~bpo24.04.1] (no packageset)
[14:34] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (oracular-backports/universe) [319-1 => 324-1~bpo24.10.1] (no packageset)
[15:04] <mkukri> anyone doing sru shift today, can pillow sru be released?
[15:04] <mkukri> (i also have plenty of grub srus to approve)
[15:26] -queuebot:#ubuntu-release- New source: mofed-modules-24.10 (oracular-proposed/primary) [24.10.0.7.0.0+ds1-0ubuntu1~24.10.1]
=== dbungert1 is now known as dbungert
=== woky_ is now known as woky__
=== woky__ is now known as woky_
[16:33] -queuebot:#ubuntu-release- New: rejected amazon-ec2-net-utils [source] (focal-proposed) [2.3.0-2~ubuntu0.20.04]
[16:50] -queuebot:#ubuntu-release- Unapproved: accepted adsys [source] (noble-proposed) [0.14.3~24.04]
[16:51] -queuebot:#ubuntu-release- Unapproved: accepted adsys [source] (jammy-proposed) [0.14.3~22.04]
[17:00] <liushuyu> ubuntu-sru: Hi, can any SRU team member take a look at https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/2076309 and see if there's something problematic? Because it seems like this SRU bug was not picked up
[17:00] -ubottu:#ubuntu-release- Launchpad bug 2076309 in xfsprogs (Ubuntu) "[SRU] xfsprogs missing frame pointer" [Undecided, Confirmed]
[17:05] <ahasenack> liushuyu: for noble? I don't see it in unapproved, nor in proposed
[17:06] <ahasenack> https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=xfsprogs <-- noble unapproved
[17:06] <ahasenack> $ rmadison -asource xfsprogs|grep noble
[17:06] <ahasenack>  xfsprogs | 6.6.0-1ubuntu2      | noble             | source
[17:06] <ahasenack> so there is nothing for the sru team to do
[17:07] <halves> ubuntu-sru hi! apologies for putting yet another bug on the pile, bug 2081611 seems to have been picked up (and in -proposed) for Noble, but not for Jammy (still in the upload queue). could I request some eyes on this, please?
[17:07] -ubottu:#ubuntu-release- Bug 2081611 in dmidecode (Ubuntu Jammy) "Add processor support from SMBIOS 3.6.0 in Jammy and Noble" [Medium, In Progress] https://launchpad.net/bugs/2081611
[17:07] <ahasenack> mfo: are you on shift today?
[17:09] <ahasenack> liushuyu: it was rejected on November 14th: https://launchpad.net/ubuntu/noble/+queue?queue_state=4&queue_text=xfsprogs
[17:09] <ahasenack> "Two uploads fixing different bugs (lp #2081163 and #2076309); please coordinate a single upload fixing both."
[17:09] -ubottu:#ubuntu-release- Launchpad bug 2081163 in xfsprogs (Ubuntu Noble) "fix fsck.xfs run by different shells when fsck.mode=force is set" [Medium, Incomplete] https://launchpad.net/bugs/2081163
[17:09] -ubottu:#ubuntu-release- Launchpad bug 2076309 in xfsprogs (Ubuntu) "[SRU] xfsprogs missing frame pointer" [Undecided, Confirmed] https://launchpad.net/bugs/2076309
[17:11] <liushuyu> Huh? It was very clear the upload was only fixing LP: #2076309 not #2076309
[17:11] -ubottu:#ubuntu-release- Launchpad bug 2076309 in xfsprogs (Ubuntu) "[SRU] xfsprogs missing frame pointer" [Undecided, Confirmed] https://launchpad.net/bugs/2076309
[17:12] <liushuyu> Oh, the complaint was the upload _should_ fixing both
[17:13] <ahasenack> I think there was another one in unapproved
[17:13] <ahasenack> that was also rejected, for the same reason
[17:14] <liushuyu> ahasenack: Okay, I will coordinate with that other upload to merge the two uploads into one
[17:14] <liushuyu> * uploader
[17:15] <ahasenack> ok
[17:32] <liushuyu> ahasenack: I have proposed https://code.launchpad.net/~liushuyu-011/ubuntu/+source/xfsprogs/+git/xfsprogs/+merge/477153 for the combined upload. I am unsure if this is the correct way for fixing the upload conflicts
[17:33] <ahasenack> liushuyu: if you merged the other fix, sounds ok. I would ask for a review from that other fix's author, though
[17:33] <liushuyu> ahasenack: Sounds reasonable, I have now added them as a reviewer on that MP
[17:35] <liushuyu> Although they are in the UTC+8 timezone, which means we will need to at least wait for 10 hours
[18:02] <mfo> mkukri, ack on pillow
[18:02] <mfo> halves, ack on 2081611
[18:03] <mfo> ahasenack, yup, I started later on today's shihft.
[18:04] <mfo> liushuyu, I see you also already reached out/started working on the combined SRU for xfsprogs internally. Thanks!
[19:20] <falcojr> question about https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/VersionStrings.md#version-merging-from-upstream . It says "Represent that there are Ubuntu changes via `ubuntu1`". What exactly does "changes" mean there? If this an upload to devel and there are no Ubuntu changes from upstream (except for packaging), is it correct to
[19:20] <falcojr> use `ubuntu1` or `ubuntu0`?
[19:22] <jbicha> falcojr: ubuntu1 because the suffix numbering starts from 1
[19:22] <RikMills> falcojr: ubuntu refers to our packaging delta, so yes ubuntu1
[19:23] <falcojr> thanks!
[19:29] <holmanb> Followup question about: https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/VersionStrings.md#version-backport-from-upstream . It says "Signal that it was not yet packaged before in this Ubuntu release before via ubuntu0". However, following this advice would cause a stable release version based on a devel upload to be ordered earlier than a devel release version for an SRU of the same upstream release
[19:29] <holmanb> version. When (if ever) might it make sense to use ubuntu0?
[19:31] <liushuyu> I think if you are packaging something from upstream that Debian does not yet even started packaging that version
[19:31] <liushuyu> ... then you can use ubuntu0 to avoid the version number conflicts
[19:33] <falcojr> wouldn't the number before 'ubuntu' represent that though? I.e., 0ubuntu1?
[19:36] <liushuyu> falcojr: I think they are referring to part of the documentation that deals with backport from upstream to an older LTS release...
[19:36] <liushuyu> ... in order to avoid version number sorting higher than a newer Ubuntu release, we use the ubuntu0 trick
[19:37] <liushuyu> ... so that when the user is upgrading to a newer Ubuntu release, a newer package from that new Ubuntu release will be installed, instead of keeping the old one
[19:39] <falcojr> gotcha, thanks
[19:39] <liushuyu> You're welcome!
[19:51] -queuebot:#ubuntu-release- New binary: cloud-init [amd64] (plucky-proposed/main) [24.4-0ubuntu1] (core)
=== ebarretto_ is now known as ebarretto
[20:19] <juliank> falcojr: I think this is awkward, it should say 0ubuntu1 maybe
[20:19] <juliank> falcojr: i.e. if we package version 2.0 ahead of debian (2.0-1) ours would e 2.0-0ubuntu1
[20:19] <juliank> 0ubuntu0<something> are SRUs
[20:26] <mfo> mkukri, re: pillow, i posted an update/request about the verification, since this seemed to warrant more details, IMHO.
[21:42] <mkukri> mfo ill update it tomorrow
[21:54] -queuebot:#ubuntu-release- Unapproved: accepted dmidecode [source] (jammy-proposed) [3.3-3ubuntu0.2]
[22:00] <mfo> halves, dmidecode/jammy-proposed done!
[23:28] -queuebot:#ubuntu-release- New binary: fwupd [amd64] (plucky-proposed/main) [2.0.2-1] (core)
[23:29] -queuebot:#ubuntu-release- New binary: fwupd [armhf] (plucky-proposed/main) [2.0.2-1] (core)
[23:29] -queuebot:#ubuntu-release- New binary: fwupd [s390x] (plucky-proposed/main) [2.0.2-1] (core)
[23:30] -queuebot:#ubuntu-release- New binary: pythonmagick [s390x] (plucky-proposed/none) [0.9.19-11] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: fwupd [arm64] (plucky-proposed/main) [2.0.2-1] (core)
[23:31] -queuebot:#ubuntu-release- New binary: python-barcode [amd64] (plucky-proposed/none) [0.15.1-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: fwupd [ppc64el] (plucky-proposed/main) [2.0.2-1] (core)
[23:31] -queuebot:#ubuntu-release- New binary: pythonmagick [armhf] (plucky-proposed/none) [0.9.19-11] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: pythonmagick [arm64] (plucky-proposed/none) [0.9.19-11] (no packageset)
[23:35] -queuebot:#ubuntu-release- New binary: pythonmagick [ppc64el] (plucky-proposed/none) [0.9.19-11] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: pyobjcryst [amd64] (plucky-proposed/none) [2024.2.1-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: pythonmagick [amd64] (plucky-proposed/none) [0.9.19-11] (no packageset)