[00:02] -queuebot:#ubuntu-release- Unapproved: zfs-linux (jammy-proposed/main) [2.1.2-1ubuntu3 => 2.1.4-0ubuntu0.1] (core, kernel-dkms)
[00:04] <xnox> kryten: once kenetic is open for development the upgrade paths will be fixed up too as well. It is one of the items that release team do, to update all of these things.
[00:04] <xnox> apw:  the zfs-linux above fixes fallocate, and compat with current oem & future hwe kernels.
[00:04] <xnox> it passed regression, stress, zsys testing.
[07:56] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (focal-proposed) [1:3.36.5-0ubuntu4]
[07:58] <apw> xnox, ack
[10:27] -queuebot:#ubuntu-release- Packageset: 7931 entries have been added or removed
[12:02] <jbicha> could we get a bookworm series added to https://launchpad.net/debian/+series ?
[12:09] <cjwatson> jbicha: Yeah I meant to do that.  Will organize it on the LP side
[12:09] <cjwatson> (it's a bit more fiddly than it looks, but not too impossible.  Also mostly not very important)
[12:13]  * cjwatson starts with https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/420554 which shouldn't need to exist but currently does
[12:14] <juliank> note taht apt-key reaches it's EOL in kinetic after archive opening
[12:14] <juliank> at least for third party consumers
[12:15] <juliank> I'm moving it to /usr/lib/apt, not sure I have the time to remove the script entirely and call gpg directly from apt
[12:15] <juliank> I sure hope
[12:16] <juliank> apt-key currently assembles all keyrings into one combined one, sets up a gpg  homedir and stuff
[12:16] <juliank> the gpg setup stuff is not needed anymore, but assembling the keys and dearmoering them is; but that's much nicer to do in C++ than in a shell script anyway, though I lost my code
[12:27] <cjwatson> juliank: We still need to fix launchpad-buildd for that, so if you move apt-key first it'll break kinetic builds
[12:27] <cjwatson> I'll try to get that done ...
[12:27] <juliank> oh? ok
[12:28] <juliank> it has warned about that since aug 2020
[12:28] <juliank> :(
[12:28] <xnox> not sure if things are healthy or expected
[12:28] <xnox> i see https://launchpad.net/ubuntu/+source/linux-riscv/5.15.0-1008.8 has duplicate kinetic-proposed and kinetic-proposed again entries
[12:28] <cjwatson> We have a pretty constant churn of stuff to keep up with, because software, so sometimes things get missed
[12:28] <juliank> "Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))."
[12:28] <cjwatson> xnox: *shrug*
[12:28] <juliank> it's hard to break CI and not break it at the same time
[12:29] <cjwatson> I think that happens sometimes
[12:29] <xnox> if that's harmless that's fine; i just didn't see that before i don't think.
[12:29] <cjwatson> The dominator will probably sort it out once the publisher starts running properly
[12:30] <juliank> So we add warnings, nobody notices them, then remove stuff/make them errors and people "suddenly" break despite having had two release cycles (at least one LTS cycle) to fix stuff
[12:30] <cjwatson> I'm going to fix it, I could do without the complaints about how terrible we are at the same time though
[12:31] <juliank> cjwatson: it's not a complaint about you, but rather that we lack a way to signal deprecations to users in a more sensible way
[12:31] <cjwatson> I'm just saying that if we do this out of order then it will be quite difficult for Ubuntu to do anything else :)
[12:31] <juliank> yeah
[12:31] <juliank> I always wonder if I should make stuff errors and provide opt-outs instead of having warnings
[12:32] <cjwatson> I think I've reached the opinion that there's just no good way to do deprecations.  Every approach sucks in one way or another for somebody
[12:36] <cjwatson> Hm, how far back does the /etc/apt/trusted.gpg.d/*.asc approach work?
[12:49] <xnox> cjwatson:  i think trusted.gpg.d/*.gpg (binary) works for longer. i thought maybe xenial was cutoff, or trusty?
[12:49] <xnox> and failing to figure it out from source code
[12:52] -queuebot:#ubuntu-release- Unapproved: budgie-control-center (jammy-proposed/universe) [1.0.1-2 => 1.0.1-2ubuntu1] (ubuntu-budgie)
[12:52] <cjwatson> launchpad-buildd needs to do things in a way that works for all Ubuntu releases it currently builds for, which probably means back to precise
[13:00] <juliank> cjwatson: apt 1.4
[13:00] <juliank> that's xenial?
[13:00] <juliank> bionic
[13:00] <cjwatson> juliank: Oh dear.  How far back does *.gpg go?
[13:01] <juliank> cjwatson: longer than I can remember
[13:01] <cjwatson> Longer than precise?
[13:02] <juliank> certainly before 2010 :)
[13:02] <juliank> was it around like hoary?
[13:03] <juliank> ah ok it was in 10.10 really
[13:03] <juliank> anyhow all Ubuntu releases still supported :)
[13:03] <cjwatson> To be fair the last precise build we dispatched was in September
[13:04] <juliank> I think precise ESM is a bit of a zombie
[13:04] <juliank> Or like schrödinger's cat
[13:05] <cjwatson> Hm, can I convert from armored format to binary easily, I wonder
[13:06] <cjwatson> gpg --dearmor I suppose
[13:06] <juliank> cjwatson: yes, let me give you the awk
[13:06] <juliank> cjwatson: https://paste.ubuntu.com/p/JdBcVJMGqx/
[13:07] <juliank> cjwatson: This is the awk | base64 -d apt-key uses to dearmor
[13:07] <wgrant> gpg --dearmor does indeed work. I wonder how far back that goes.
[13:07] <wgrant> At least precise.
[13:07] <cjwatson> Just checking if precise has it
[13:07] <juliank> You can do that if you have gpg installed
[13:07] <juliank> Arguably it would be nice to avoid having gpg installed
[13:08] <cjwatson> launchpad-buildd can always depend on gpg and do that outside the chroot
[13:08] <juliank> that works too, but then be careful with setting up home dirs and agents and whatever
[13:08] <cjwatson> I don't think gpg --dearmor requires that.  But obviously will check
[13:08] <juliank> I think the new gpg binary is agent-free, but the gnupg binary spawns all sorts of agents :)
[13:09] <cjwatson> (this would be on focal)
[13:09] <juliank> which is why apt-key is so complex
[13:09] <juliank> it mktemps directories, kills gpg agents, and removes temp directory
[13:10] <juliank> the goal is to drop the script eventually, call gpgv directly and avoid all that mess
[13:10] <cjwatson> On precise gpg --dearmor doesn't even create a .gnupg
[13:10] <juliank> like who likes shell scripts in their trust path
[13:12] <juliank> (and then gpg changed their keyring format, that was hilarious too, as trusted.gpg broke because people were using it with --keyring and it got converted :D)
[13:49] -queuebot:#ubuntu-release- Unapproved: openjdk-lts (kinetic-proposed/main) [11.0.14.1+1-0ubuntu1 => 11.0.15+10-0ubuntu0.22.04.1] (core, i386-whitelist) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: openjdk-17 (kinetic-proposed/universe) [17.0.2+8-1 => 17.0.3+7-0ubuntu0.22.04.1] (i386-whitelist) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-17 [sync] (kinetic-proposed) [17.0.3+7-0ubuntu0.22.04.1]
[13:57] <icey> any chance for a review of https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964802 ? it's been in proposed for nearly two weeks, and verified for about a week at this point
[14:36] <bdmurray> icey: I only see one of the two bugs as being verified
[14:37] <bdmurray> icey: so that's surely why it has been waiting
[14:37] <icey> bdmurray: gah, knew there must be something :-/
[15:54] -queuebot:#ubuntu-release- Unapproved: base-files (kinetic-proposed/main) [12ubuntu4.1 => 12ubuntu5] (core, i386-whitelist)
[16:02] -queuebot:#ubuntu-release- Unapproved: debootstrap (kinetic-proposed/main) [1.0.126+nmu1 => 1.0.126+nmu1ubuntu1] (desktop-core)
[16:16] <paride> I updated https://wiki.ubuntu.com/Releases with the new codename and dates
[16:18] <sil2100> bdmurray: ^ can you take a look at base-files? Thanks! :)
[16:24] <vorlon> I can look
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (kinetic-proposed) [12ubuntu5]
[16:29] <vorlon> sil2100, bdmurray: base-files accepted
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (kinetic-proposed) [1.0.126+nmu1ubuntu1]
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-lts [sync] (kinetic-proposed) [11.0.15+10-0ubuntu0.22.04.1]
[16:51] <paride> The distro-info-data SRU bug (LP: #1970227) has tasks for trusty and xenial, but those were not updated with the latest releases
[16:51] <paride> Xenial stops at Impish, Trusty stops at Focal
[16:54] <paride> Can I set those tasks as wontfix? Or do we want to update distro-info-data in past-EoSS releases for some reason?
[16:57] <bdmurray> paride: Did you check the ESM archive / PPA?
[17:02] -queuebot:#ubuntu-release- Unapproved: debootstrap (jammy-proposed/main) [1.0.126+nmu1 => 1.0.126+nmu1ubuntu0.1] (desktop-core)
[17:07] <paride> bdmurray, right, I didn't
[17:07] -queuebot:#ubuntu-release- Unapproved: debootstrap (impish-proposed/main) [1.0.124ubuntu0.1 => 1.0.124ubuntu0.2] (desktop-core)
[17:10] -queuebot:#ubuntu-release- Unapproved: debootstrap (focal-proposed/main) [1.0.118ubuntu1.6 => 1.0.118ubuntu1.7] (core)
[17:12] -queuebot:#ubuntu-release- Unapproved: distro-info-data (kinetic-proposed/main) [0.52 => 0.52ubuntu1] (core, i386-whitelist)
[17:14] -queuebot:#ubuntu-release- Unapproved: debootstrap (bionic-proposed/main) [1.0.95ubuntu0.10 => 1.0.95ubuntu0.11] (core)
[17:30] -queuebot:#ubuntu-release- Unapproved: distro-info-data (focal-proposed/main) [0.43ubuntu1.9 => 0.43ubuntu1.10] (core, i386-whitelist)
[17:30] -queuebot:#ubuntu-release- Unapproved: distro-info-data (jammy-proposed/main) [0.52 => 0.52ubuntu0.1] (core, i386-whitelist)
[17:30] -queuebot:#ubuntu-release- Unapproved: distro-info-data (impish-proposed/main) [0.51ubuntu1.1 => 0.51ubuntu1.2] (core, i386-whitelist)
[17:30] -queuebot:#ubuntu-release- Unapproved: distro-info-data (bionic-proposed/main) [0.37ubuntu0.13 => 0.37ubuntu0.14] (core)
[17:48] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (jammy-proposed) [0.52ubuntu0.1]
[17:49] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (impish-proposed) [0.51ubuntu1.2]
[17:51] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (kinetic-proposed/main) [1.481 => 1.482] (core)
[17:52] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (focal-proposed) [0.43ubuntu1.10]
[17:54] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (bionic-proposed) [0.37ubuntu0.14]
[17:55] <Eickmeyer> Hey! I had SRU bug 1969798 for Carla. Do I need to reupload for kinetic now?
[18:03] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (jammy-proposed) [1.0.126+nmu1ubuntu0.1]
[18:05] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (impish-proposed) [1.0.124ubuntu0.2]
[18:06] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (focal-proposed) [1.0.118ubuntu1.7]
[18:08] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (bionic-proposed) [1.0.95ubuntu0.11]
[18:12] -queuebot:#ubuntu-release- Unapproved: pam (kinetic-proposed/main) [1.4.0-11ubuntu2 => 1.4.0-13ubuntu1] (core, i386-whitelist)
[18:36] <ahasenack> I know the archive is still closed, but if I sync a package now, will it annoy you guys, or get in the way of reopening the archive?
[18:36] <ahasenack> it's bacula, the new debian upload fixes the ftbfs that prompted its removal before
[19:43] <vorlon> ahasenack: it doesn't get in the way
[19:43] <ahasenack> thx
[19:44] <ogra> ahasenack, oh, nice, there is a semi-angry discussion on the ubuntu users ML about it (people taking backups they cant play back after upgrading to jammy)
[19:44] <vorlon> well, that doesn't reintroduce it to jammy, only to kinetic
[19:44] <ahasenack> well, this won't bring it back to jammy I'm afraid, not directly at least
[19:45] -queuebot:#ubuntu-release- Unapproved: bacula (kinetic-proposed/universe) [9.6.7-3build1 => 9.6.7-4] (no packageset) (sync)
[19:45] <ogra> but has the possibility of an SRU in it ...
[19:45] <ahasenack> I suppose
[19:45] -queuebot:#ubuntu-release- Unapproved: accepted bacula [sync] (kinetic-proposed) [9.6.7-4]
[19:45] -queuebot:#ubuntu-release- Unapproved: xubuntu-meta (kinetic-proposed/universe) [2.241 => 2.242] (xubuntu)
[19:49] -queuebot:#ubuntu-release- Unapproved: gnome-calendar (kinetic-proposed/main) [41.2-3 => 42.0-1] (desktop-extra, ubuntu-desktop) (sync)
[19:52] -queuebot:#ubuntu-release- New binary: bacula [s390x] (kinetic-proposed/universe) [9.6.7-4] (no packageset)
[19:53] -queuebot:#ubuntu-release- New binary: bacula [amd64] (kinetic-proposed/universe) [9.6.7-4] (no packageset)
[19:53] -queuebot:#ubuntu-release- New binary: bacula [ppc64el] (kinetic-proposed/universe) [9.6.7-4] (no packageset)
[19:54] <vorlon> uh why is the robot still running
[19:54] <vorlon> sil2100, bdmurray: ^^
[19:54] <vorlon> turning it off now
[19:55] -queuebot:#ubuntu-release- Unapproved: rejected apt [source] (impish-proposed) [2.3.9ubuntu0.1]
[19:55] <ahasenack> at least it built :)
[19:55] <ahasenack> (bacula)
[19:55] <bdmurray> vorlon: turning it off how?
[19:55] <vorlon> sil2100, bdmurray: should the bot have been disabled as part of the release checklist somewhere?
[19:55] <vorlon> bdmurray: commenting it out in the cronjob
[19:56] <vorlon> (crontab)
[19:57] -queuebot:#ubuntu-release- New: accepted bacula [amd64] (kinetic-proposed) [9.6.7-4]
[19:57] -queuebot:#ubuntu-release- New: accepted bacula [s390x] (kinetic-proposed) [9.6.7-4]
[19:57] -queuebot:#ubuntu-release- New: accepted bacula [ppc64el] (kinetic-proposed) [9.6.7-4]
[19:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-meta (kinetic-proposed/universe) [0.92 => 0.93] (no packageset)
[20:00] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-manager [source] (jammy-proposed) [0.3.0-0ubuntu2]
[20:03] <vorlon> RikMills: could I persuade you to move the kubuntu seeds from bzr to git?
[20:07] -queuebot:#ubuntu-release- Unapproved: kubuntu-meta (kinetic-proposed/universe) [1.418 => 1.419] (kubuntu)
[20:14] -queuebot:#ubuntu-release- Unapproved: lubuntu-meta (kinetic-proposed/universe) [22.04.3 => 22.10.1] (lubuntu)
[20:22] <bdmurray> ahasenack, ogra: should the bacula removal be release noted for Jammy?
[20:23] <ahasenack> I didn't see the discussions, but I would guess yes
[20:23] -queuebot:#ubuntu-release- Unapproved: rejected apt [source] (impish-proposed) [2.3.9ubuntu0.1]
[20:23] <ahasenack> the package belongs to the security team, odd
[20:25] <ahasenack> hm, maybe not
[20:25] <ogra> bdmurray, do we usually notify about universe removals ?
[20:26] <vorlon> ogra: "notify"?
[20:26] <ogra> "release note" it
[20:26] <vorlon> no
[20:26] <ogra> right
[20:26] <ogra> bdmurray, so i guess not ...
[20:27] <vorlon> there are lots of packages that get removed over a cycle, especially over a two-year cycle.  What would the release note say that update-manager doesn't already tell you on upgrade?
[20:27] <RikMills[m]> vorlon:  I have no objection to the kubuntu seed moving
[20:28] <ogra> well, it was not intentionally removed eiter i suppose, it simply FTBFS for a while
[20:28] <ogra> *either
[20:28] <vorlon> all removals are "intentional" :)
[20:28] <ahasenack> the update-manager list of removals is correct, but too fine grained
[20:28] <ahasenack> it's easy to miss something
[20:28] <ahasenack> and does it say bacula (for example) would be removed?
[20:28] <ahasenack> or would it keep the old version installed
[20:29] <ahasenack> depends on the dependencies I guess?
[20:30] <vorlon> update-manager will tell you about all obsolete packages not present in the series you're upgrading to, and offer to remove them
[20:31] -queuebot:#ubuntu-release- Unapproved: ubuntu-budgie-meta (kinetic-proposed/universe) [0.94 => 0.95] (personal-fossfreedom, ubuntu-budgie)
[20:37] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (kinetic-proposed/universe) [1.282 => 1.283] (ubuntu-mate)
[20:46] <bdmurray> vorlon: I forget do we need to run the failing tests here w/ a new distro-info-data https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#debootstrap
[20:50] <bdmurray> looking at impish probably not
[21:40] <vorlon> bdmurray: pbuilder certainly seems to be failing due to out-of-date distro-info-data
[21:41] <vorlon> though migration-reference seems to be doing its thing just fine
[21:42] <bdmurray> I think distro-info-data needs to be released and then the tests rerun but ICBW
[21:42] <bdmurray> either way I've verified bug 1970227 if you want to release it
[21:43] <vorlon> if you want the tests to pass, you need new distro-info-data.  But as they are currently regressed in -updates, britney will DT"R"T
[21:44] <Eickmeyer> I know everyone is busy, but what is happening to SRUs that were submitted prior to Kinetic's creation?
[21:46] <bdmurray> I'll looked at some of them and will continue to look at them.
[21:47] <vorlon> bdmurray: distro-info-data releasing now
[21:47] <bdmurray> And part of the archive opening process includes copying packages from -proposed so you don't need to do anything
[21:50] <Eickmeyer> bdmurray: That's the problem: one in particular (Carla) wasn't accepted prior to Kinetic's creation.
[21:51] <bdmurray> Eickmeyer: I'm trying to tell you its not a problem
[21:51] <Eickmeyer> Ok, fair.
[21:52] <bdmurray> We aren't at step 35 yet https://wiki.ubuntu.com/NewReleaseCycleProcess
[21:55] -queuebot:#ubuntu-release- Unapproved: accepted carla [source] (jammy-proposed) [2.4.2-0ubuntu3]
[21:59] -queuebot:#ubuntu-release- Unapproved: ubuntu-unity-meta (kinetic-proposed/universe) [0.4 => 0.5] (no packageset)
[22:20] -queuebot:#ubuntu-release- Unapproved: accepted gnome-music [source] (jammy-proposed) [41.1-0ubuntu1]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted gnome-text-editor [source] (jammy-proposed) [42.1-0ubuntu1]
[22:31] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-meta (kinetic-proposed/universe) [0.46 => 0.47] (ubuntukylin)
[22:36] -queuebot:#ubuntu-release- Unapproved: accepted budgie-control-center [source] (jammy-proposed) [1.0.1-2ubuntu1]
[22:54] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-meta (kinetic-proposed/universe) [0.266 => 0.267] (ubuntustudio)
[23:03] <Eickmeyer> bdmurray: Of course, it FTBFS. It'll probably have to be the second scenario as described in the SRU bug report. It can wait until Kinetic opens. Thanks anyhow. :)