[00:00] <vorlon> doko: I haven't been able to convince myself that this python3-defaults update in bionic-proposed is obviously safe; it's a wholesale update of a lot of things that look entirely unrelated to making python3-stdlib-extensions installable, and the only SRU bug linked doesn't even mention the python3-defaults package, let alone a test case for it
[00:48] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1025.30] (kernel)
[05:27] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [4.15.0-1024.25]
[05:27] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1025.30]
[05:27] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1004.4]
[06:30] -queuebot:#ubuntu-release- Unapproved: virtualbox (cosmic-proposed/multiverse) [5.2.20-dfsg-1 => 5.2.20-dfsg-3] (ubuntu-cloud) (sync)
[06:39] <LocutusOfBorg> please accept vbox and vbox-hwe, you can keep it in proposed for DD, I care about it being built :)
[06:42] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-139.165] (core, kernel)
[07:02] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-139.165]
[08:09] <acheronuk> sil2100: could you perhaps let the remaining plasma 5.12.7 as discussed last night? if KDE want to revert the changes made by an l10n maintainer, they will have to do a new plasma release
[08:09] <acheronuk> I would like to put out a call for testing of LP: #1794494 as a whole on our website
[08:10] <acheronuk> *plasma 5.12.7 in bionic queue
[08:10] <sil2100> acheronuk: ok
[08:11]  * sil2100 checks backlog
[08:11]  * Laney eyes the bionic livefs builds
[08:14] <sil2100> acheronuk: ok, so the 'id' translations getting reverted to English is expected, right?
[08:15] <sil2100> acheronuk: in the .desktop files of systemsettings?
[08:16] <Laney> I guess we need the python3-defaults in the SRU queue for that?
[08:16] <Laney> comes down to:
[08:16] <Laney> The following packages have unmet dependencies:
[08:16] <Laney>  python3-distutils : Depends: python3 (>= 3.6.6-1~) but 3.6.5-3ubuntu1 is to be installed
[08:16] <Laney>                      Depends: python3-lib2to3 (>= 3.6.4) but it is not going to be installed
[08:16] <Laney> E: Unable to correct problems, you have held broken packages.
[08:17] <sil2100> Laney: let me take a look at that one in the queue
[08:19] <Laney> ta
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted systemsettings [source] (bionic-proposed) [4:5.12.7-0ubuntu0.1]
[08:23] <sil2100> Laney: (ignore the just failed ubuntu-core builds, those failed for a now-known reason)
[08:23]  * Laney was just 🤔 at those
[08:27] <acheronuk> sil2100: it from upstream. not a mispacked tar. I am querying, but as said if they want to change that now they will need to do a new release
[08:37] <Laney> sil2100: just saw a msg from vorlon above about that pkg btw
[08:38] <sil2100> Laney: I think doko needs to re-upload it since the changelog bug is wrong, but I guess I could do that too
[08:38] <sil2100> Laney: what did Steve say about it?
[08:38]  * sil2100 has no backlog
[08:38] <Laney> 25/10 01:00:21 <vorlon> doko: I haven't been able to convince myself that this python3-defaults update in bionic-proposed is obviously safe; it's a wholesale update of a lot of things that look entirely unrelated to making
[08:38] <Laney>                         python3-stdlib-extensions installable, and the only SRU bug linked doesn't even mention the python3-defaults package, let alone a test case for it
[08:47] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (cosmic-proposed/main) [4.18.0-1003.4] (kernel)
[08:48] <sil2100> Yeah, he linked the wrong bug for that
[08:49] <sil2100> I'll re-upload it myself if he won't pop up soon
[09:24] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (xenial-proposed/main) [1.361.1 => 1.361.2] (core)
[09:41] <xnox> infinity, vorlon - http://paste.ubuntu.com/p/ynT6xbYN8t/ i think when we were seeding ubuntu-advantage-tools into precise, something like this also happened (inclusion of xorg-lts) and we chose to not take those updates.
[09:41] <xnox> I guess for this trusty update, i should too, only take the ubuntu-advantage-tools change, right?
[09:42] <xnox> (and specify bug #1686183 in the right changelog line)
[09:50] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.35.5+18.04]
[09:51] -queuebot:#ubuntu-release- Unapproved: accepted user-manager [source] (bionic-proposed) [4:5.12.7-0ubuntu0.1]
[09:51] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.35.5]
[09:52] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.35.5~14.04]
[09:53] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal-kde [source] (bionic-proposed) [5.12.7-0ubuntu0.1]
[09:54] <sil2100> acheronuk: ok, I think those are all - I see that Chris rejected the plasma-desktop package because of some cruft in it
[09:54] <sil2100> acheronuk: I guess you'd want to re-upload that?
[09:55] <acheronuk> he did? what cruft?
[09:56] <acheronuk> gotta go. back later
[09:56] <sil2100> Seeing his rejection comment:
[09:56] <sil2100> "An upload of plasma-desktop to bionic-proposed has been rejected from the upload queue for the following reason: "Package appears to have some binary cruft (eg /tmp/tmpixkYbi/UwMNumLrtq/plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/wc.db )"."
[09:59] <sil2100> acheronuk: ^ once you're back
[11:13] -queuebot:#ubuntu-release- Unapproved: python3-defaults (bionic-proposed/main) [3.6.5-3ubuntu1 => 3.6.7-1~18.04] (core)
[11:14] -queuebot:#ubuntu-release- Unapproved: rejected python3-defaults [source] (bionic-proposed) [3.6.7-1~18.04]
[11:15] -queuebot:#ubuntu-release- Unapproved: python3-defaults (cosmic-proposed/main) [3.6.6-1 => 3.6.7-1~18.10] (core)
[11:15] -queuebot:#ubuntu-release- Unapproved: rejected python3-defaults [source] (cosmic-proposed) [3.6.7-1~18.10]
[11:30] -queuebot:#ubuntu-release- Unapproved: upower (cosmic-proposed/main) [0.99.8-2 => 0.99.8-2ubuntu0.1] (kubuntu, ubuntu-desktop)
[11:30] -queuebot:#ubuntu-release- Unapproved: rejected upower [source] (cosmic-proposed) [0.99.8-2ubuntu0.1]
[11:31] -queuebot:#ubuntu-release- Unapproved: upower (cosmic-proposed/main) [0.99.8-2 => 0.99.8-2ubuntu0.1] (kubuntu, ubuntu-desktop)
[11:31] -queuebot:#ubuntu-release- Unapproved: rejected upower [source] (cosmic-proposed) [0.99.8-2ubuntu0.1]
[11:32] <seb128> (sorry, screwed up that upower upload and rejected, the most recent one is good now/in the queue)
[11:33] -queuebot:#ubuntu-release- Unapproved: upower (cosmic-proposed/main) [0.99.8-2 => 0.99.8-2ubuntu0.1] (kubuntu, ubuntu-desktop)
[11:34] <infinity> xnox: Indeed, adding the hwe xorg to desktop is problematic, as it breaks switching back and forth.
[11:34] -queuebot:#ubuntu-release- Unapproved: accepted python3-defaults [source] (bionic-proposed) [3.6.7-1~18.04]
[11:42] -queuebot:#ubuntu-release- Unapproved: xkeyboard-config (cosmic-proposed/main) [2.23.1-1ubuntu1 => 2.23.1-1ubuntu1.18.10.1] (core)
[11:43] -queuebot:#ubuntu-release- Unapproved: xkeyboard-config (bionic-proposed/main) [2.23.1-1ubuntu1 => 2.23.1-1ubuntu1.18.04.1] (core)
[11:44] <xnox> infinity, and about debootstrap.... do you care for it to know how to debootstrap with -updates|-security from the initial set of debs downloaded and unpacked, or not?
[11:44] <acheronuk> sil2100: those 'binary' file exist in the 5.12.4 and 5.12.6 tarballs in the archive at the very least. so not sure what you expect me to do
[11:45] <xnox> cause it should be possible to extend "components" to support pockets too
[11:45] <infinity> xnox: It's a long-standing feature request that might be neat.  I don't care today, no.
[11:46] <xnox> infinity, right, so it's not that crazy, and to be fair only has a limited usage. And really is not needed to hack ubuntu-meta by hand to include non-release-pocket-package
[11:47] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (trusty-proposed/main) [1.325 => 1.325.1] (core)
[11:48] <infinity> xnox: Are you going to do xenial as well, instead of waiting 2 years to revisit the same bug all over? :P
[11:48] <xnox> infinity, i did xenial already thank you very much ;-)
[11:48] <xnox> it's in unapproved
[11:48] <xnox> or at least, i'm under such impression
[11:49] <xnox> infinity, and yes, i'm actioning the acient distro column card from the backlog
[11:49]  * xnox is trying to do all the SRUs until we get a new codename
[11:49] <xnox> yeap, it is there https://bugs.launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=ubuntu-meta
[11:49] <acheronuk> slashd: in fact, tars back to plasma-desktop 5.10.0 have them
[11:49] <acheronuk> sil2100 I mean ^^^
[11:50] <infinity> xnox: Oh, shiny.  Thanks.
[11:51] <infinity> Speaking of all the SRUs, making all of py3 uninstallable in xenial for hours sure caused a lot of vomit in my inbox.
[11:51] <infinity> Err, bionic.
[11:52] <xnox> hahahahhahhahahaha
[11:52] <xnox> infinity, he did mention in the morning standup that he is bored without a new codename. I guess that is his subconscious way of not being bored =)
[12:04] -queuebot:#ubuntu-release- Unapproved: accepted python3-defaults [source] (cosmic-proposed) [3.6.7-1~18.10]
[12:04] -queuebot:#ubuntu-release- Unapproved: plasma-desktop (bionic-proposed/universe) [4:5.12.6-0ubuntu0.1 => 4:5.12.7-0ubuntu0.1] (kubuntu)
[12:06] <acheronuk> sil2100: ^^^ please accept. I can maybe poke KDE about what they are doing with their tarball generation script, but since it's been like that for many releases I can't see why need to mess with it right now
[12:45] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-39.42~16.04.1] (kernel)
[12:50] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-39.42~16.04.1] (kernel)
[14:18] <acheronuk> sil2100: FYI https://bugs.kde.org/show_bug.cgi?id=400292
[14:23] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-39.42~16.04.1]
[14:23] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-39.42~16.04.1]
[14:25] <sil2100> acheronuk: ok, thanks! I'll pick up the old upload from Rejected then
[14:25] <sil2100> Ah, you reuploaded
[14:25] <sil2100> Good
[14:25] <sil2100> Thanks o/
[14:30] <sil2100> acheronuk: that's not a blocker and probably not a problem, but I see in the CMakeLists.txt you bumped the version of AppStreamQt but the libappstreamqt-dev dep is unversioned
[14:31] <sil2100> Anyway, it's otherwise good, accepting
[14:32] -queuebot:#ubuntu-release- Unapproved: accepted plasma-desktop [source] (bionic-proposed) [4:5.12.7-0ubuntu0.1]
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (bionic-proposed) [3:13.0.1-0ubuntu3]
[14:46] <acheronuk> sil2100: thanks :)
[15:04] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (xenial-proposed) [1.361.2]
[15:04] <vorlon> sil2100, doko: what to do about python3-defaults> IMHO we should fix the versioned deps in python3-stdlib-extensions and reupload that instead
[15:05] <doko> vorlon: I disagree. we should have the autopkg tests run this time. didn't do that for 3.6.6. now already running
[15:05] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (trusty-proposed) [1.325.1]
[15:06] <vorlon> doko: what do autopkgtests have to do with python3-defaults being forklifted in with a bunch of unrelated changes just to satisfy a version constraint?
[15:07] <doko> what do you mean by unrelated changes? the Policy update? There is nothing more
[15:07] <vorlon> doko: the policy update and the pile of other changes to versioned dependencies
[15:09] <xnox> vorlon, maybe join the meeting, eh?!
[15:09] <vorlon> nope
[15:09] <doko> the versioned dependencies are part of the update, yes
[15:09] <xnox> vorlon, then stop distracting doko from the meeting =))))))))
[15:09]  * vorlon checks who has been sending whom PMs during the meeting
[15:15] <sil2100> I thought that the python3-defaults version bumps were part of the overall 3.6.7 update, part of the usual process for new minor releases
[15:16] <doko> they are
[15:24] -queuebot:#ubuntu-release- Unapproved: shim-signed (trusty-proposed/main) [1.33.1~14.04.2 => 1.33.1~14.04.3] (core)
[15:28] -queuebot:#ubuntu-release- Unapproved: totem (cosmic-proposed/main) [3.26.2-1ubuntu1 => 3.26.2-1ubuntu2] (ubuntu-desktop)
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (trusty-proposed) [1.33.1~14.04.3]
[15:51] <bdmurray> Where did the lubuntu-core package go?
[16:42] <xnox> vorlon, would it help reviewing ubuntu-keyring if I dput upload it, rather than sync it?
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.2-7034-g2f5deb8b8-0ubuntu1 => 2.5.0~beta4-7354-g3de074967-0ubuntu1~18.04.1] (ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.2-7034-g2f5deb8b8-0ubuntu1 => 2.5.0~beta4-7358-g703416782-0ubuntu1~18.04.1] (ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (cosmic-proposed/main) [2.5.0~beta2-7291-gd0345ced5-0ubuntu1 => 2.5.0~beta4-7355-g629adfda8-0ubuntu1~18.10.1] (ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.2-7034-g2f5deb8b8-0ubuntu1 => 2.5.0~beta4-7355-g629adfda8-0ubuntu1~18.04.1] (ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (cosmic-proposed/main) [2.5.0~beta2-7291-gd0345ced5-0ubuntu1 => 2.5.0~beta4-7358-g703416782-0ubuntu1~18.10.1] (ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: maas (cosmic-proposed/main) [2.5.0~beta2-7291-gd0345ced5-0ubuntu1 => 2.5.0~beta4-7354-g3de074967-0ubuntu1~18.10.1] (ubuntu-server)
[20:38] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.2-7034-g2f5deb8b8-0ubuntu1 => 2.5.0~beta4-7359-g1f94845ac-0ubuntu1~18.04.1] (ubuntu-server)
[20:38] -queuebot:#ubuntu-release- Unapproved: maas (cosmic-proposed/main) [2.5.0~beta2-7291-gd0345ced5-0ubuntu1 => 2.5.0~beta4-7359-g1f94845ac-0ubuntu1~18.10.1] (ubuntu-server)
[21:48] <vorlon> xnox: it would help reviewing ubuntu-keyring if the internal documentation about key rotation had any relation at all to what you're doing
[21:48] <vorlon> xnox: that's what's slowing it down
[21:49] <vorlon> xnox: (and I also don't mean just going and changing the wiki page, I mean getting sign-off from both juliank and cjwatson that the changes to the documentation are correct)
[22:11] <xnox> vorlon, i'm not sure which pages you are refering to.
[22:11] <xnox> vorlon, last time the key rotation was done wrong; and i had to finish up incomplete rotations for upgrade tarballs; cd signing; etc.
[22:12] <xnox> vorlon, also the format of keys was changed, and locations of where they are stored on disk.
[22:12] <xnox> vorlon, also the remote update of trusted keys was disabled long time ago, because it is CVE buggy.
[22:12] <xnox> vorlon, and the new one that juliank and I drafted was never implemented.
[22:13] <xnox> vorlon, as in to have a signed gpg blob that is validated and piped into a /etc/apt/trusted.gpg.d/remote-updated-key.gpg
[22:13] <xnox> vorlon, and i have no idea where the idea of signing the new signing key with master key came, from, because as far as i can tell previous keys were not signed like that, and it's fine, cause gpg web of trust is not used.
[22:14] <xnox> vorlon, what i'm proposing is trivial.... start trusting new key in addition to the old key, which is obviously correct thing to do, and is the same thing that was done with the previous key migration to the 2012 key.
[22:15] <xnox> vorlon, i'm currious which documentation you are reviewing. Also note that cjwatson did +1 the launchpad signing cod merge proposal.
[22:15] -queuebot:#ubuntu-release- Unapproved: accepted sendmail [source] (cosmic-proposed) [8.15.2-11ubuntu1]
[22:15] <xnox> vorlon, see https://code.launchpad.net/~xnox/ubuntu-archive-publishing/dual-sign-2018/+merge/356919
[23:13] <vorlon> xnox: https://wiki.canonical.com/UbuntuArchiveKeyDisasterRecovery is the documented key rotation process
[23:15] <vorlon> xnox: for that particular branch, not merged yet because I haven't put the key in place