[00:03] <infinity> bluesabre: Why are pepole adding zsys for zfs installer support?
[00:04] <infinity> (note that it's not there for Ubuntu desktop, cause it's in universe)
[00:04] <infinity> Oh, Didied filed an MIR a month ago.  Whee.
[00:05] <bluesabre> infinity: Suggestion by Wimpress for better support in 20.04, I believe.
[00:05] <infinity> To be clear, I intent to have a long talk with the desktop team in the morning about their implementation here.
[00:05] <infinity> No other filesystem/storagelayer requires tools be in the desktop seeds.
[00:05] <infinity> This is not how we do this. :P
[00:06] <bluesabre> :)
[00:06] <infinity> But yes, we'll pick up your meta changes if I lose that argument or give up yelling.
[00:06] <bluesabre> I’m just following the pack, happy to make adjustments as you see fit.
[00:08] <infinity> bdmurray: Removing the click hook feels more like an upstream change, not something to do in an Ubuntu revision, surely?
[00:08] <infinity> (I realise we're also upstream, but it's not packaged natively)
[00:09] <infinity> Oh, gross.  It *is* packaged natively, but not *versioned* natively.
[00:09] <infinity> Ick, ick.
[00:32] <rharper> hi, cloud-init has an upload to eoan to fix  a bug that can prevent cloud-init from running in lxd/kvm cloud images,  https://bugs.launchpad.net/cloud-init/+bug/1846511 ; would be good to get this in so eoan cloud-images don't have a busted config in the image
[00:41] <infinity> rharper: Icky.  And accepted.
[00:41] <rharper> infinity: indeed; thanks!
[00:41] <infinity> rharper: I assume that same bug will need all the SRUs too?
[00:41] <rharper> no, it only affected eoan
[00:42] <infinity> Oh, lucky.
[00:42] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (eoan-proposed) [19.2-36-g059d049c-0ubuntu3]
[00:42] <rharper> very
[00:42] <rharper> not looking for another critical sru for cloud-init any time soon
[00:42] <rharper> this was too close for comfort
[00:42] <infinity> I did appreciate the accidental recursion, though.
[00:42] <rharper> hehe
[00:43] <infinity> https://accidentallyquadratic.tumblr.com/
[00:43] <infinity> Doesn't quite belong, but certainly in the spirit of it.
[00:43] <rharper> lol
[00:54] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (eoan-proposed) [2.20.11-0ubuntu8]
[01:58] -queuebot:#ubuntu-release- Unapproved: partman-auto (eoan-proposed/main) [134ubuntu10 => 134ubuntu11] (core, i386-excludes)
[02:07] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.17 => 19.10.18] (core)
[02:08] <xnox> updated description of https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1845571 most of the code for "installer media detection" fails on el-torito hybrid images and partman/parted is very confused about it, thus the strict /cdrom grep is the only thing that is preventing to autopartition the cdrom media one is booted from. And the grep needs expanding, now that we properly mount an el-torito
[02:08] <xnox> partition of the cdrom.
[02:09] <xnox> Laney:  infinity: ^
[02:10] <xnox> maybe vorlon too
[02:10]  * xnox sleeps
[02:11] <xnox> happy RC day
[02:24] <tsimonq2> infinity: Oh yeah, so there's another Calamares.
[02:25] <tsimonq2> infinity: Someone forgot to mention that we have an Apport hook that has that path hardcoded. Bleh.
[02:25] <tsimonq2> infinity: Anyway, kc2bez handled it, so that Should be the last Cala for this cycle.
[02:27] <tsimonq2> infinity: Ah, well, the bot that's in here must have derped, because it seems it was accepted. :P
[03:50] <tjaalton> pretty please, intel-* from the queue finish my plate on migration to llvm9 (intel-comput-runtime needed a new version, which needed new -gmmlib, which forced rebuilds of intel-media-*)
[05:12] -queuebot:#ubuntu-release- New: accepted backport-iwlwifi-dkms [source] (eoan-proposed) [7906-0ubuntu1]
[05:14] -queuebot:#ubuntu-release- New binary: backport-iwlwifi-dkms [amd64] (eoan-proposed/universe) [7906-0ubuntu1] (no packageset)
[05:15] <vorlon> tjaalton: it seems libigdgmm9 is seeded on pretty much all of the desktop flavors except for Ubuntu itself, so that's a risky transition to be handling at this point in the cycle; what's the impact if we don't migrate to llvm9 until FF opens?
[05:15] <vorlon> infinity: ^^ and I'll defer to you on actually deciding what to do about these intel packages
[05:17] -queuebot:#ubuntu-release- New: accepted backport-iwlwifi-dkms [amd64] (eoan-proposed) [7906-0ubuntu1]
[06:01] <tjaalton> vorlon: really? the only rdepends for it are intel-media-va-driver* and intel-opencl-icd.. so the other images have the va-driver included?
[06:02] -queuebot:#ubuntu-release- Unapproved: dmraid (eoan-proposed/main) [1.0.0.rc16-8ubuntu1 => 1.0.0.rc16-8ubuntu2] (core)
[06:05] -queuebot:#ubuntu-release- Unapproved: mesa (eoan-proposed/main) [19.2.0-1ubuntu2 => 19.2.1-1ubuntu1] (core, xorg)
[06:05] <tjaalton> mesa ^ is a bugfix release
[06:10] <tjaalton> as for the impact on intel-compute-runtime still on llvm8 while spirv-llvm-translator and opencl-clang moved on to llvm9, I'm not sure
[06:11] -queuebot:#ubuntu-release- Unapproved: accepted partman-auto [source] (eoan-proposed) [134ubuntu11]
[06:11] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (eoan-proposed) [19.10.18]
[06:13] <tjaalton> libigc1 et al pulls in llvm9
[06:13] <tjaalton> libllvm9
[06:14] <tjaalton> I don't see compute-runtime (intel-opencl-icd) to use it directly, so could be fine as is
[06:15] <infinity> tjaalton: I've decided to let it in anyway, please give it some abuse from whatever angles you can think of, though.
[06:15] <infinity> tjaalton: It seems to be on flavour media due to weird twisty dependencies of things like libavcodec. :P
[06:15] -queuebot:#ubuntu-release- Unapproved: accepted intel-compute-runtime [source] (eoan-proposed) [19.39.14278-0ubuntu1]
[06:15] -queuebot:#ubuntu-release- Unapproved: accepted intel-media-driver-non-free [source] (eoan-proposed) [19.2.1+ds1-2ubuntu1]
[06:15] -queuebot:#ubuntu-release- Unapproved: accepted intel-gmmlib [source] (eoan-proposed) [19.3.2+ds1-0ubuntu1]
[06:15] -queuebot:#ubuntu-release- Unapproved: accepted intel-media-driver [source] (eoan-proposed) [19.2.1+dfsg1-2ubuntu1]
[06:16] <tjaalton> ah, via libva2
[06:16] <tjaalton> and va-driver-all
[06:16]  * infinity nods.
[06:17] -queuebot:#ubuntu-release- Unapproved: accepted dmraid [source] (eoan-proposed) [1.0.0.rc16-8ubuntu2]
[06:17] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (eoan-proposed) [19.2.1-1ubuntu1]
[06:18] -queuebot:#ubuntu-release- New binary: intel-gmmlib [amd64] (eoan-proposed/universe) [19.3.2+ds1-0ubuntu1] (kubuntu)
[06:18] <tjaalton> thanks, I'll figure out a better test-case for opencl than darktable :)
[06:19] -queuebot:#ubuntu-release- Unapproved: firefox (eoan-proposed/main) [69.0.2+build1-0ubuntu2 => 69.0.3+build1-0ubuntu1] (mozilla, ubuntu-desktop)
[06:25] <infinity> tjaalton: intel-gmmlib FTBFS on i386.
[06:25] <infinity> tjaalton: And this one might be in the class of things we actually want working.
[06:26] <tjaalton> bah
[06:26] <tjaalton> I'll check
[06:26] <infinity> [ RUN      ] CTestAuxTable.TestAuxTableContent
[06:26] <infinity> /<<BUILDDIR>>/intel-gmmlib-19.3.2+ds1/Source/GmmLib/ULT/GmmAuxTableULT.cpp:244: Failure
[06:26] <infinity> Value of: val
[06:26] <infinity>   Actual: 281474827812864
[06:26] <infinity> Expected: expected
[06:26] <infinity> Which is: 18446744073560653824
[06:26] <infinity> [  FAILED  ] CTestAuxTable.TestAuxTableContent (0 ms)
[06:26] <infinity> Truncation of 64-bit type to 32-bit?
[06:27] <infinity> Except 281474827812864 is a lot bigger than 32-bits, so no.
[06:30] <tjaalton> this one got added in 19.3.2, nice
[06:34] <infinity> tjaalton: Testing new code, or just new test exposing a bug that was already there?
[06:34] <infinity> (or potentially new test that is, itself, buggy_
[06:34] <infinity> )
[06:35] <tjaalton> new test
[06:35] <tjaalton> and code
[06:35] <tjaalton> a09c68fd3244eee Add Pagetable manager  and auxtable  support.
[06:38] <tjaalton> could just skip tests on i386 for now
[06:38] <tjaalton> filed it upstream
[06:38] <tjaalton> though they're kinda actively dropping support for 32bit
[06:39] <tjaalton> the opencl runtime is amd64 only, for instance
[06:39] <infinity> I don't mind dropping i386 if you can make sure the revdeps all get handled sanely.
[06:39] <infinity> And by tomorrow. :P
[06:40] <tjaalton> yeah I'm looking at it
[06:40] <tjaalton> actually, I don't think the tests were run previously, since they need certain cpu features from the builder
[06:40] <tjaalton> and the check was buggy in the past
[06:41] <tjaalton> hmm no, this test is new and is just buggy
[06:41] <infinity> I'd certainly prefer "fix buggy test/code", if the bug's jumping out at you.
[06:43] <infinity> I'm going to go see if I can catch some sleep so I can catch EU before their EOD in the morning.
[06:43] <infinity> tjaalton: If you find a fix, pass it by someone you trust for review, but feel free to self-accept a fixed upload after triple-checking the debdiff isn't bonkers.
[06:43] <tjaalton> I'll poke them to provide a fix or I'll just skip tests for now. amd64 is proben to pass them now :)
[06:43] <tjaalton> *proven
[06:44] <tjaalton> got it
[06:44] <infinity> tjaalton: Ditto for binary NEW.  It looks fine to me, but not accepting because of the arch skew.
[06:45]  * infinity wanders off.
[08:00] -queuebot:#ubuntu-release- Unapproved: python3.8 (eoan-proposed/universe) [3.8.0~rc1-1 => 3.8.0~rc1-3] (no packageset) (sync)
[08:10] <apw> tjaalton, i am about if you have something to review
[08:17] <tjaalton> apw: not yet
[08:18] <tjaalton> but yes, i'll ping you once I do
[08:43] -queuebot:#ubuntu-release- Unapproved: accepted python3.8 [sync] (eoan-proposed) [3.8.0~rc1-3]
[09:11] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (eoan-proposed/main) [1:19.10.13 => 1:19.10.14] (core)
[09:22] <doko> xnox, ginggs: I see you had some successful give backs for http://autopkgtest.ubuntu.com/packages/p/python-sparse/eoan/i386. any idea?
[09:30] -queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (xenial-proposed) [2.27.1-6ubuntu3.9]
[09:33] -queuebot:#ubuntu-release- Unapproved: apt (trusty-proposed/main) [1.0.1ubuntu2.23 => 1.0.1ubuntu2.24] (core)
[09:35] <sil2100> apw: hello o/ Would you have a moment to take a look at ubuntu-release-upgrader? The diff is quite big, but it's due to demotion/translation changes, the actual diff is 3 lines
[09:35] <sil2100> (in eoan of course)
[09:37] <apw> sil2100, sure
[09:39] -queuebot:#ubuntu-release- Unapproved: gnome-nibbles (eoan-proposed/universe) [1:3.34.0-1 => 1:3.34.1-1] (desktop-extra) (sync)
[09:40] -queuebot:#ubuntu-release- Unapproved: quadrapassel (eoan-proposed/universe) [1:3.34.0-1 => 1:3.34.1-1] (desktop-extra) (sync)
[09:41] <ginggs> doko: six seems to be a common trigger in those that passed.  i've just triggered itself to try to see if it has regressed in release
[09:42] <ginggs> maybe six needs another rebuild?  see https://launchpad.net/ubuntu/+source/six/1.12.0-1build1
[09:43] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (eoan-proposed) [1:19.10.14]
[09:43] <sil2100> apw: thanks!
[09:44] -queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu10 => 2.04-1ubuntu11] (core)
[09:45] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-ubuntu-dock (eoan-proposed/main) [66ubuntu19.10.2 => 67ubuntu19.10.1] (ubuntu-desktop) (sync)
[09:46] -queuebot:#ubuntu-release- Unapproved: gcc-9 (eoan-proposed/main) [9.2.1-9ubuntu1 => 9.2.1-9ubuntu2] (core)
[09:46] -queuebot:#ubuntu-release- Unapproved: grub2-signed (eoan-proposed/main) [1.126 => 1.127] (core)
[09:46] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-desktop-icons (eoan-proposed/main) [19.01.4-1 => 19.10.2-1] (ubuntu-desktop)
[09:47] <doko> ginggs: do you know why that rebuild was necessary? LocutusOfBorg?
[09:48] <ginggs> doko: no idea, I just happened to see it in the changelog
[09:53] <LocutusOfBorg> doko, actually it wasn't, at least to the test log... http://autopkgtest.ubuntu.com/packages/p/python-sparse/eoan/i386
[09:54] -queuebot:#ubuntu-release- Unapproved: iproute2 (eoan-proposed/main) [5.2.0-1ubuntu1 => 5.2.0-1ubuntu2] (core)
[09:54] <LocutusOfBorg> the fix has been in 1.12.0-2 with "Mark autopkgtests as superficial."
[09:54] -queuebot:#ubuntu-release- Unapproved: gnome-maps (eoan-proposed/universe) [3.34.0-1 => 3.34.1-1] (desktop-extra, ubuntu-budgie, ubuntugnome) (sync)
[09:56] <didrocks> Laney: here is the grub2 update fixing the signed kernel filtering we discussed ^ (grub2, grub2-signed and ofc grubzfs-testsuite which was updated for autopkgtests to pass)
[09:56] -queuebot:#ubuntu-release- Unapproved: grubzfs-testsuite (eoan-proposed/universe) [0.4.3 => 0.4.4] (no packageset)
[09:56] <apw> didrocks, did that 'optimisation' patch that was causing non-initialisation of the display get sorted in grub2
[09:57] <apw> (i was expecting it to get dropped i think)
[09:57] <didrocks> apw: hum, I'm unsure about which patch you are talking about, I'm a little bit out of context, was that something we discussed?
[09:57] <apw> didrocks, hmmm, maybe, or maybe it was cyphermox ...
[09:58] <didrocks> apw: that's the second time you are doing that to me on grub2-related things! :) we speak the same language, but with a different accent :p
[09:58] <seb128> apw, is that one that has to do with flickerfree boot? do you have a lp reference?
[09:58] <didrocks> (but more seriously, I think it was with him, because nor a patch not this discussion rings a bell to me)
[09:59] <apw> seb128, right something to do with reducing flicker
[09:59] <seb128> apw, reverting would add the flicker back ... is there a proper report explaining the issue?
[09:59] <Laney> juliank: seems a bit late for that packagekit change ...
[10:00] <juliank> Laney: packagekit?
[10:00] <Laney> HEH
[10:00] <Laney> forget it, I'm looking at disco
[10:00] <juliank> oh that one
[10:01] <apw> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1827203
[10:01] <Laney> scared about it there too, but not my call thankfully :>
[10:01] <seb128> apw, thx
[10:02] <ginggs> doko, LocutusOfBorg: the passing test on 2019-07-30 12:35:34 UTC was with a rebuilt six, and so was 2019-09-02 08:43:44 UTC (0.2.0-2 was obviously built after 0.2.0-1)
[10:02] <juliank> Laney: the change + aptdaemon followup to make that use it is planned to go back all the way to xenial; but need to come up with a better test case I guess
[10:02] <apw> seb128, ok that patch is still in there ... for me i was able to downgrade to the version before that was added and got normal updates
[10:03] <juliank> the current test case stats to check the socket is used and stuff still works correctly
[10:03] <seb128> apw, you pinned your grub? or got it updated again to newer version and didn't see the issue again?
[10:03] <juliank> but it does not actually state to like use a frontend and then close it while stuff is being installed
[10:05] <apw> seb128, i repeatedly pushed it back to an older version which i have in my home
[10:05] <apw> so manually pinned
[10:05] <apw> seb128, let me upgrade now and con
[10:05] <apw> confirm it is still sad
[10:05] <seb128> k, we should investigate the issue then
[10:05] <seb128> but it sounds a bit late to revert, especially that nobody else noticed/complained and cyphermox asked for debug details
[10:06] <seb128> for what we know it could be an hardware issue specific to your machine
[10:06] <apw> seb128, we talked about it at the time, and i had gotten the impression it was a somewhat dodgy change not yet accepted upstream; and it iwas going
[10:06] <apw> seb128, i am sure it is h/w specific in some sense, though this is a common Dell
[10:07] <apw> seb128, the bigger issue to my mind is mostly don't notice it if you don't have the menu turned on and your machine isn't broken
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (eoan-proposed) [1.127]
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted grubzfs-testsuite [source] (eoan-proposed) [0.4.4]
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (eoan-proposed) [2.04-1ubuntu11]
[10:08] <didrocks> thx!
[10:09] <ginggs> python-sparse/i386 passed in release https://autopkgtest.ubuntu.com/packages/python-sparse/eoan/i386
[10:09] <seb128> apw, right, we should fix it. Reverting would be a bit sad since it would mean that we loose flickerfree boot
[10:10] <apw> seb128, a bit less flicker boot, as we are still doing a panel reset to change the tiling
[10:10] <apw> i guess an option to say, i am poo please don't use it would be fine
[10:11] <seb128> well, that patch is supposed to avoid the mode change in the case the menu isn't displayed
[10:11] <seb128> so it sounds like it's buggy
[10:13] <seb128> also what panel reset is that that? I'm not expert on that stack but my understanding from the upstream work is that it was supposed to be fully flicker free on recent intel cards where i915.fastboot is default now
[10:13] <apw> seb128, isn't the efi framebuffer defined as non-tiled and we want to be tiled by the time we get to X
[10:14] <apw> seb128, but also, i am not keeping up, so take everything i say with a grain of salt
[10:14] <apw> seb128, anyhow will update, reboot, and report back
[10:14] -queuebot:#ubuntu-release- Unapproved: binutils-mingw-w64 (eoan-proposed/universe) [8.3ubuntu2 => 8.3ubuntu3] (no packageset)
[10:14] <seb128> could be, as said I'm not familiar with those details
[10:14] <seb128> apw, thx!
[10:19] -queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu11 => 2.04-1ubuntu11] (core)
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [source] (eoan-proposed) [10.5-0ubuntu7]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (eoan-proposed) [1.25.8-0ubuntu1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted firefox [source] (eoan-proposed) [69.0.3+build1-0ubuntu1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted quadrapassel [sync] (eoan-proposed) [1:3.34.1-1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (eoan-proposed) [0.197]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (eoan-proposed) [1.25.10-0ubuntu1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted gnome-nibbles [sync] (eoan-proposed) [1:3.34.1-1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-meta [source] (eoan-proposed) [2.230]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (eoan-proposed) [1.25.9-0ubuntu1]
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-budgie-meta [source] (eoan-proposed) [0.54]
[10:32] -queuebot:#ubuntu-release- Unapproved: intel-gmmlib (eoan-proposed/universe) [19.3.2+ds1-0ubuntu1 => 19.3.2+ds1-0ubuntu2] (kubuntu)
[10:32] <tjaalton> apw: ^ gmmlib skips all tests now
[10:34] <apw> tjaalton, we couldn't just skip them on i386 ?
[10:36] -queuebot:#ubuntu-release- Unapproved: python2.7 (eoan-proposed/universe) [2.7.16-4 => 2.7.17~rc1-1] (kubuntu)
[10:37] <tjaalton> apw: the tests passed fine on amd64, and this is likely the last upload for eoan, so.. :)
[10:39] <tjaalton> let me test (ha) something
[10:40] -queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu11 => 2.04-1ubuntu11] (core)
[10:46] -queuebot:#ubuntu-release- Unapproved: six (eoan-proposed/main) [1.12.0-2 => 1.12.0-2build1] (core)
[10:49] -queuebot:#ubuntu-release- Unapproved: accepted python2.7 [source] (eoan-proposed) [2.7.17~rc1-1]
[10:49] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-dashtodock (eoan-proposed/universe) [66-1 => 67-1] (no packageset) (sync)
[10:49] -queuebot:#ubuntu-release- Unapproved: accepted six [source] (eoan-proposed) [1.12.0-2build1]
[10:49] -queuebot:#ubuntu-release- Unapproved: accepted binutils-mingw-w64 [source] (eoan-proposed) [8.3ubuntu3]
[10:50] <doko> ginggs: ^^^ ok, one more no-change upload, the autopkg testers are idle, so it doesn't hurt
[10:51] <tjaalton> apw: ok, I have another version to upload
[10:51] <apw> tjaalton, go for it
[10:52] <apw> seb128, ok confirmed it is the same with the latest version, i am pretty sure i do not have fastboot=1
[10:52] <apw> (i see a bios 'hit return' thing which is what suppresses that right?)
[10:52] -queuebot:#ubuntu-release- Unapproved: intel-gmmlib (eoan-proposed/universe) [19.3.2+ds1-0ubuntu1 => 19.3.2+ds1-0ubuntu2] (kubuntu)
[10:53] -queuebot:#ubuntu-release- Unapproved: gcc-mingw-w64 (eoan-proposed/universe) [22~exp1ubuntu1 => 22~exp1ubuntu2] (no packageset)
[10:54] -queuebot:#ubuntu-release- Unapproved: rejected intel-gmmlib [source] (eoan-proposed) [19.3.2+ds1-0ubuntu2]
[10:54] -queuebot:#ubuntu-release- Unapproved: cups-filters (eoan-proposed/main) [1.25.10-0ubuntu1 => 1.25.11-0ubuntu1] (desktop-core, ubuntu-server)
[10:55] -queuebot:#ubuntu-release- Unapproved: accepted intel-gmmlib [source] (eoan-proposed) [19.3.2+ds1-0ubuntu2]
[10:55] <apw> tjaalton, ^
[10:56] <tjaalton> apw: thanks!
[10:56] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (eoan-proposed) [2.04-1ubuntu11]
[10:56] -queuebot:#ubuntu-release- Unapproved: flash-kernel (eoan-proposed/main) [3.98ubuntu3 => 3.98ubuntu4] (core)
[10:56] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (eoan-proposed) [2.04-1ubuntu11]
[10:57] -queuebot:#ubuntu-release- Unapproved: rejected flash-kernel [source] (eoan-proposed) [3.98ubuntu4]
[10:57] <apw> doko, i assume this was not irony: "No-change rebuild. For what reason?"
[10:57] -queuebot:#ubuntu-release- Unapproved: flash-kernel (eoan-proposed/main) [3.98ubuntu3 => 3.98ubuntu4] (core)
[10:58] -queuebot:#ubuntu-release- New binary: intel-gmmlib [amd64] (eoan-proposed/universe) [19.3.2+ds1-0ubuntu2] (kubuntu)
[11:00] -queuebot:#ubuntu-release- New binary: intel-gmmlib [i386] (eoan-proposed/universe) [19.3.2+ds1-0ubuntu2] (kubuntu)
[11:01] <LocutusOfBorg> apw, no irony, it worked in the past but we don't know why
[11:01] <LocutusOfBorg> so, if the test automagically works, we can debug it further
[11:01] <LocutusOfBorg> and I plan to do it
[11:03] -queuebot:#ubuntu-release- New: rejected intel-gmmlib [amd64] (eoan-proposed) [19.3.2+ds1-0ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted intel-gmmlib [amd64] (eoan-proposed) [19.3.2+ds1-0ubuntu2]
[11:04] -queuebot:#ubuntu-release- New: accepted intel-gmmlib [i386] (eoan-proposed) [19.3.2+ds1-0ubuntu2]
[11:05] -queuebot:#ubuntu-release- Unapproved: swift (eoan-proposed/main) [2.22.0-0ubuntu1 => 2.22.0-0ubuntu2] (openstack)
[11:06] <doko> apw: no. see above: " ^^^ ok, one more no-change upload, the autopkg testers are idle, so it doesn't hurt"
[11:16] -queuebot:#ubuntu-release- Unapproved: python-stdlib-extensions (eoan-proposed/universe) [2.7.16-2 => 2.7.17~rc1-1] (kubuntu)
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (eoan-proposed) [1.25.11-0ubuntu1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9 [source] (eoan-proposed) [9.2.1-9ubuntu2]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-dashtodock [sync] (eoan-proposed) [67-1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted python-stdlib-extensions [source] (eoan-proposed) [2.7.17~rc1-1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (eoan-proposed) [3.98ubuntu4]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted iproute2 [source] (eoan-proposed) [5.2.0-1ubuntu2]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted gnome-maps [sync] (eoan-proposed) [3.34.1-1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted swift [source] (eoan-proposed) [2.22.0-0ubuntu2]
[11:51] -queuebot:#ubuntu-release- Unapproved: accepted gcc-mingw-w64 [source] (eoan-proposed) [22~exp1ubuntu2]
[11:56] <doko> rbasak: https://tracker.debian.org/pkg/python-trio  not in Debian, wondering why we need to ship that in Ubuntu?
[11:59] -queuebot:#ubuntu-release- Unapproved: python-msrest (eoan-proposed/universe) [0.6.1-1 => 0.6.1-1ubuntu1] (no packageset)
[12:00] -queuebot:#ubuntu-release- Unapproved: rejected python-msrest [source] (eoan-proposed) [0.6.1-1ubuntu1]
[12:03] <rbasak> doko: what would you prefer to do for Ubuntu? It's fine for a non-LTS I think.
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-aws (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-meta-aws (eoan-proposed/main) [5.3.0.1002.2 => 5.3.0.1003.3] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-meta (eoan-proposed/main) [5.3.0.17.19 => 5.3.0.18.20] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux (eoan-proposed/main) [5.3.0-17.18 => 5.3.0-18.19] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-gcp (eoan-proposed/main) [5.3.0-1003.3 => 5.3.0-1004.4] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules (eoan-proposed/restricted) [5.3.0-17.18 => 5.3.0-18.19] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-meta-gcp (eoan-proposed/main) [5.3.0.1003.3 => 5.3.0.1004.4] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: python-msrest (eoan-proposed/universe) [0.6.1-1 => 0.6.1-1ubuntu1] (no packageset)
[12:06] <doko> rbasak: I'm currently looking at the python-msrestazure autopkg test failures, and python-trio is in the way, that's why I'm asking
[12:06] -queuebot:#ubuntu-release- New sync: linux-restricted-modules-aws (eoan-proposed/primary) [5.3.0-1003.3]
[12:06] -queuebot:#ubuntu-release- New sync: linux-restricted-modules-gcp (eoan-proposed/primary) [5.3.0-1004.4]
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-kvm (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (eoan-proposed/main) [5.3.0-1003.3 => 5.3.0-1004.4] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-meta-kvm (eoan-proposed/main) [5.3.0.1002.2 => 5.3.0.1003.3] (core, kernel) (sync)
[12:06] -queuebot:#ubuntu-release- Unapproved: linux-signed (eoan-proposed/main) [5.3.0-17.18 => 5.3.0-18.19+1] (core, kernel) (sync)
[12:07] -queuebot:#ubuntu-release- Unapproved: accepted python-msrest [source] (eoan-proposed) [0.6.1-1ubuntu1]
[12:08] <Laney> wtf
[12:08] <rbasak> doko: looking
[12:09] <Laney> doko: can you please stop accepting your own stuff :(
[12:09] <Laney> I was going to reject that, you typoed override
[12:09] <doko> ouch, ok
[12:10] <Laney> also you didn't make it respect nocheck in DEB_BUILD_OPTIONS which you should really do when overriding dh_auto_test
[12:10] <Laney> bonus also: that might have been accepted by auto-accept but someone has made a syntax error so that bot isn't functioning atm
[12:10] <Laney> /o\
[12:11] <doko> Laney: so, no, then please just override the python-msrestazure autopkg test. fails in the release too
[12:11] <Laney> no you won't fix it?
[12:11] <rbasak> doko: I'm not sure I understand yet. Do you mean the python-msrestazure autopkgtest failures in Ubuntu? How is it being blocked by python-trio?
[12:13] <doko> Laney: no, it's a regression in release? and apparently not in debian
[12:13] <doko> rbasak: I don't care to look. it's blocked in debian because -trio is blocked apparenty?
[12:13] <Laney> this seems like a strange response to me pointing out a typo in your upload
[12:13] <doko> Laney: I'll remove it in -proposed
[12:13] <rbasak> doko: https://tracker.debian.org/pkg/python%2Dmsrestazure says it's in testing? I don't see anything blocked.
[12:14] <apw> Laney, that explains why the autobot has been so quiet
[12:15] <doko> rbasak: no, migration is stalled: https://tracker.debian.org/pkg/python-msrest
[12:15] <rbasak> Ah that's a different source package
[12:15]  * rbasak looks again
[12:16] <Laney> I've just fixed the auto-accept bot, so any future upload will probably just sail in
[12:16] <doko> rbasak: and python-msrestazure 0.6 apparently needs the new msrest
[12:16] <xnox> doko:  although ~ubuntu-archive have powers to accept, process wise ~ubuntu-release should be processing the queue right now.
[12:16] <xnox> doko:  and you are not ~ubuntu-release
[12:17] <xnox> Laney:  yeah, i have noticed some things that was expected to auto-accept and weren't. But i thought maybe it needs manual review.
[12:17] <Laney> xnox: apw: SyntaxError: invalid syntax
[12:17] <Laney>   File "/home/ubuntu-archive/auto-accept", line 12
[12:17] <Laney>     PACKAGESET_WHITELIST = {"ubuntugnome", "edubuntu", "i386-eoan-excludes", "i386-excludes"]
[12:17] <Laney> /o\\\\\\\\\\\\\\\
[12:17] <doko> xnox, I didn't accept my toolchain uploads
[12:17] <xnox> doko:  ok. thanks.
[12:18] <rbasak> doko: OK I think I understand what you're pointing out and why you pinged me now.
[12:18] <rbasak> doko: are you expecting to take any action or asking me to take any action about python-trio?
[12:19] <doko> rbasak: I asked Laney now to ignore the autopkg test failures as a stop gap. I see that we have inconsistant versions, and I don't want to spend time investing these universe packages
[12:20] <Laney> I dunno what's going on to be honest
[12:20] <Laney> I pointed out a typo, and then I got in response what seems like a very strange refusal to re-upload a fixed version
[12:20] <rbasak> I think it's OK to kick out of the release pocket in Ubuntu anything that is being caught up by this, but I don't think it's necessary for python-trio itself.
[12:21] <doko> sure, so that's why I'm asking to ignore the autopkg test for now
[12:24] <rbasak> I would just kick python-msrest out of the release pocket
[12:25] <rbasak> (which might need kicking out python-msrestazure too)
[12:27] <rbasak> Or, consider the current version of 0.5.5-1 in the release pocket good, as it is in Debian
[12:27] <rbasak> And that /0.6.1-1(ubuntu1)?/ is correct in not migrating
[12:27] <rbasak> Since AFAICT the test is revealing a real problem here?
[12:28] <doko> rbasak: it's already broken in the release: http://autopkgtest.ubuntu.com/packages/p/python-msrestazure/eoan/amd64
[12:30] <rbasak> I've not looked in detail to confirm, but it seems to me that the autopkgtest failure in the release pocket is a different root cause
[12:31] <rbasak> IMHO, either some MOTU volunteers to fix this (I'm suggesting that it's not the job of any Canonical employee to fix everything in universe) or we should kick out what we know to be broken in the release pocket.
[12:31] <rbasak> Which might be just python-msrestazure then.
[12:33] -queuebot:#ubuntu-release- Unapproved: flash-kernel (eoan-proposed/main) [3.98ubuntu4 => 3.98ubuntu5] (core)
[12:33] <doko> ... + python-azure, python-azure-storage, python-django-storages, ...
[12:39] <rbasak> Laney: are you available to badtest hint the two reds for mysql-8.0 please? Or would you prefer one or two MPs?
[12:39] <rbasak> Neither are caused by the mysql update
[12:39] <rbasak> (as evidenced by recent failures in tests not triggered by mysql-8.0)
[12:49] -queuebot:#ubuntu-release- Unapproved: python-defaults (eoan-proposed/universe) [2.7.16-1 => 2.7.17-1] (kubuntu)
[12:51] <rbasak> ^ https://code.launchpad.net/~racb/britney/mysql-8.0-migration/+merge/373960
[13:01] <didrocks> sil2100: are the ubuntu-images autopkgtests known to be flaky? The "mount" tests fails on both amd64 and s390x and the grub change we have is unrelated to it
[13:01] <didrocks> (in the history, the tests seemed to be reliable)
[13:16] -queuebot:#ubuntu-release- Unapproved: shoogle (eoan-proposed/universe) [0.1.4-7 => 0.1.4-8] (no packageset) (sync)
[13:16] -queuebot:#ubuntu-release- Unapproved: accepted shoogle [sync] (eoan-proposed) [0.1.4-8]
[13:17] <doko> RikMills: why is python2 (python-defaults) still in the kubuntu set?
[13:21] <RikMills> doko: I have no clue. it is not seeded or 'supported'
[13:33] <sil2100> didrocks: hmm, so I'd have to look at it again, but I feel like there has been some flakyness in mount in the past - can't remember for which arches, let me take a look in a moment
[13:34] <didrocks> sil2100: sure! as long as tomorrow's image has the new grub, it's good :)
[13:34] -queuebot:#ubuntu-release- Unapproved: gnome-session (eoan-proposed/main) [3.34.1-1ubuntu1 => 3.34.1-1ubuntu2] (ubuntu-desktop)
[13:40] <cjwatson> python> https://people.canonical.com/~ubuntu-archive/germinate-output/kubuntu.eoan/rdepends/python-defaults/python near the end shows it: kubuntu-desktop Recommends: konversation Depends: konversation-data Recommends: python
[13:40] <cjwatson> RikMills: ^-
[13:43] -queuebot:#ubuntu-release- Unapproved: thunderbird (eoan-proposed/main) [1:68.1.1+build1-0ubuntu1 => 1:68.1.2+build1-0ubuntu1] (mozilla, ubuntu-desktop)
[13:46] <RikMills> cjwatson: ah. want that fixed
[13:46] <didrocks> sil2100: ok, they were flaky
[13:48] <sil2100> \o/
[13:48] <sil2100> ;p
[13:48] <sil2100> I mean, I shouldn't be happy about that
[13:49] <didrocks> sil2100: heh, don't show it at least ;)
[13:55] <doko> RikMills: fix uploaded, waiting in the queue
[13:55] -queuebot:#ubuntu-release- Unapproved: konversation (eoan-proposed/universe) [1.7.5-1ubuntu2 => 1.7.5-1ubuntu3] (kubuntu)
[13:56] <RikMills> doko: did you fix the current FTBFS in proposed?
[13:57] <doko> RikMills: oops, no. do you want to take the diff for your next upload?
[13:57] <RikMills> needed: https://cgit.kde.org/konversation.git/commit/?h=1.7&id=4d0036617becc26a76fd021138c98aceec4c7b53
[13:57] <doko> RikMills: do you want me to upload?
[13:57] <RikMills> doko: Qt 5.13 in that is a fib ^^ it is another reason
[13:58] <RikMills> doko: if you like, I am doing other things right now
[13:58] <doko> ok, doing
[14:07] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (disco-proposed) [0.131ubuntu19.2]
[14:08] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.9]
[14:08] -queuebot:#ubuntu-release- Unapproved: konversation (eoan-proposed/universe) [1.7.5-1ubuntu2 => 1.7.5-1ubuntu3] (kubuntu)
[14:08] -queuebot:#ubuntu-release- Unapproved: rejected konversation [source] (eoan-proposed) [1.7.5-1ubuntu3]
[14:09] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.16]
[14:17] -queuebot:#ubuntu-release- Unapproved: openjdk-14 (eoan-proposed/universe) [14~14-2 => 14~18-1] (no packageset)
[14:19] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-14 [source] (eoan-proposed) [14~18-1]
[14:33] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (eoan-proposed) [3.98ubuntu5]
[14:33] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (eoan-proposed) [1:68.1.2+build1-0ubuntu1]
[14:33] <Laney> rbasak: I'll have a look (was out at lunch)
[14:33] -queuebot:#ubuntu-release- Unapproved: accepted gnome-session [source] (eoan-proposed) [3.34.1-1ubuntu2]
[14:33] <Laney> & getting stabbed in the arm with a needle
[14:33] <Laney> looks like apw did it
[14:48] -queuebot:#ubuntu-release- New: accepted linux-restricted-modules-aws [sync] (eoan-proposed) [5.3.0-1002.2+1]
[14:48] -queuebot:#ubuntu-release- New: accepted linux-restricted-modules-oracle [sync] (eoan-proposed) [5.3.0-1001.1]
[14:48] -queuebot:#ubuntu-release- New: accepted linux-restricted-modules-azure [sync] (eoan-proposed) [5.3.0-1002.2]
[14:51] -queuebot:#ubuntu-release- New: accepted linux-restricted-modules-gcp [sync] (eoan-proposed) [5.3.0-1003.3]
[15:02] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (eoan-proposed/main) [149 => 150] (ubuntu-desktop)
[15:12] <apw> infinity, i am assuming you will review the kernels in Unapproved; i have reviewed the corresponding lrms in New and you are free to accept them in sycn
[15:13] <apw> (as i assume you are expecting them)
[15:14] <rbasak> Laney, apw: thank you for poking at MySQL for me. It looks like it's all landed and done now.
[15:25] <Laney> nice one
[15:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-430 (eoan-proposed/restricted) [430.50-0ubuntu1 => 430.50-0ubuntu2] (ubuntu-desktop)
[15:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-435 (eoan-proposed/restricted) [435.21-0ubuntu1 => 435.21-0ubuntu2] (no packageset)
[15:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-340 (eoan-proposed/restricted) [340.107-0ubuntu6 => 340.107-0ubuntu7] (ubuntu-desktop)
[15:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-390 (eoan-proposed/restricted) [390.129-0ubuntu1 => 390.129-0ubuntu2] (core)
[15:42] <tseliot> apw, Laney: hey, I know it's not ideal (given the date), but I think it would be worth having the two fixes for nvidia in, unless we want to break dist-upgrades from Disco, or we want suspend to be broken on some systems (see the changelog)
[15:43] <tseliot> these nvidia ^^
[15:43] <tseliot> help would be very welcome
[16:02] -queuebot:#ubuntu-release- Unapproved: accepted python-defaults [source] (eoan-proposed) [2.7.17-1]
[16:08] <doko> ginggs, LocutusOfBorg, apw: so yes, python-sparse/i386 succeeded with the "no-change" six upload
[16:08] <LocutusOfBorg> meh, will look
[16:11] <LocutusOfBorg> doko, no
[16:11] <LocutusOfBorg> 0.2.0-1	python3-defaults/3.7.5-1	2019-10-10 12:32:55 UTC	0h 03m 09s	doko	fail	log   artifacts  
[16:11] <LocutusOfBorg> this run was bad, but with latest sparse
[16:12] <LocutusOfBorg> 0.2.0-1	python3-defaults/3.7.5-1	2019-10-10 14:33:35 UTC	0h 03m 29s	doko	pass	log   artifacts  
[16:12] <LocutusOfBorg> this one is good with same packages
[16:12] <doko> 0.2.0-1	python3-defaults/3.7.5-1	2019-10-10 14:33:35 UTC	0h 03m 29s	doko	pass
[16:13] <LocutusOfBorg> yes, and the very same run with the very same installed packages failed two hours before
[16:13] <LocutusOfBorg> I would say more flaky test rather than rebuild neede4d
[16:18] <doko> vorlon: django-compat/unknown still needs on override
[16:25] <Laney> tseliot: eek
[16:27] <tseliot> Laney, I wouldn't ask if it weren't really urgent, especially LP: #1830961 . Sorry
[16:27] <Laney> no worries
[16:27] <Laney> but someone other than me might know better about the compiler flags stuff
[16:27] <Laney> apw: got a chance to check them maybe?
[16:28] <apw> sforshee, ^ i think you are our -fcf-protection guru
[16:29] <Laney> delegation in action
[16:30] <tseliot> apw, Laney: those flags are set by the kernel in Eoan, but they are not in Disco, which is a problem when dist-upgrading. sforshee commented here, but I don't know if the fix was backported to 19.04 https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/comments/36
[16:35] <ginggs> doko: i have no idea how!  i diffoscope'd the binaries and they were essentially identical
[16:35] <sforshee> Laney, tseliot: I did send those for sru to b/d, but seems they haven't been released yet
[16:35] <ricotz> hello, vala is currently stuck in -proposed due to some unrelated automake-1.16 test failure, I hoping it is possible to force a transition to get it into the release -- https://launchpad.net/ubuntu/+source/vala/0.44.9-0ubuntu1
[16:35] <sforshee> yes, looks like they are in the -proposed kernels
[16:46] <apw> sforshee, the ones expected to release the monday after release; correct ?
[16:47] <sforshee> apw: yes, unfortunately. When I sent them I thought they would be out before the release, either I was off or there was a delay in the cycle
[16:50] <apw> sforshee, likley the extension of cycle-1 to 4 weeks has skewed things
[16:50] <sforshee> yeah, wasn't paying close enough attention to that I guess
[16:51] <bittin_> RC of 19.10 in 10 minutes
[16:51] <apw> upgrades are triggered by our meta-data updates arn't they? so we might be able to wait on them
[16:53] <tseliot> apw, sforshee: my patch in the nvidia drivers check if the flags are available in the default compiler, and disables that. This should work regardless of whether users have the updated kernel
[16:54] <sforshee> tseliot: but other dkms modules are also affected
[16:54] <sforshee> so unless we can make dkms do likewise ...
[16:54] <apw> sforshee, so one of those "if the dkms upgrades first we are ok, otherwise not" situations
[16:55] <sforshee> apw: well there's no such patch to dkms yet, but yes I suppose then we'd have that situation
[16:55] <infinity> apw: We could delay the meta-release upgrade stuff, but we almost never do for more than a few days for non-LTS.
[16:56] <apw> infinity, right, that, well the kernels for disco would release the monday after rellease
[16:56] <infinity> apw: But if these are scheduled to go out on the Monday post-release, releasing them Wed/Thurs would only be a few business days early.  Maybe we can get testing all done by then?
[16:56] <apw> infinity, would we need to do anyhing more than disco for this ?
[16:57] <infinity> apw: Nope.
[16:57] <apw> sforshee, ok so we need to go back to stable and tell them they need to expedite disco out early
[16:57] <apw> slightly early
[16:57] <infinity> apw: bionic needs to be fixed before disco EOLs (cause then the non-LTS upgrade path from bionic will be to eoan), but right now, bionic upgrades go through disco, so disco is the only place the fix must exist by eoan release.
[16:58] <tseliot> sforshee, oh, right
[16:59] <apw> infinity, i beleive all the kernls are fixed on that cycle, so monday right sforshee ?
[16:59] <sforshee> correct
[17:01] <infinity> apw: Sure, I gathered that, my point is that only disco needs to be expedited, cause the bionic fix isn't (yet) urgent.
[17:01] <apw> infinity, ack, best to be utterly clear
[17:09] <vorlon> infinity: there are some seeded nvidias coming in per tseliot's comments regarding criticality
[17:10] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-435 [source] (eoan-proposed) [435.21-0ubuntu2]
[17:11] <vorlon> there are linked bugs so if these need to be diverted to -updates they can be
[17:12] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-430 [source] (eoan-proposed) [430.50-0ubuntu2]
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-390 [source] (eoan-proposed) [390.129-0ubuntu2]
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-340 [source] (eoan-proposed) [340.107-0ubuntu7]
[17:13] -queuebot:#ubuntu-release- Unapproved: firewalld (eoan-proposed/universe) [0.7.1-1ubuntu9 => 0.7.2-1] (no packageset) (sync)
[17:14] -queuebot:#ubuntu-release- Unapproved: accepted firewalld [sync] (eoan-proposed) [0.7.2-1]
[17:15] <tomreyn> the 19.10 RC bittin_ announced, would that go to http://cdimage.ubuntu.com/releases/19.10/ ?
[17:16] -queuebot:#ubuntu-release- Unapproved: hedgewars (eoan-proposed/universe) [0.9.25-5build3 => 1.0.0-2] (no packageset) (sync)
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted hedgewars [sync] (eoan-proposed) [1.0.0-2]
[17:20] <infinity> tomreyn: I don't know who or what a bittin_ is, and no, RCs are just the dailies leading up to final release, there's no formal publishing for them.
[17:21] <tomreyn> thanks infinity - i was referring to this above: <bittin_> RC of 19.10 in 10 minutes
[17:21] <RikMills> what?
[17:22] <infinity> Indeed, what? :)
[17:22] <infinity> tomreyn: Let me reiterate the "I don't know who or what a bittin_ is", in the sense that he doesn't speak for the Ubuntu release team. :)
[17:22] <RikMills> oh, in #ubuntu+1
[17:22] <tomreyn> also here
[17:23] <tomreyn> at :51
[17:23] <infinity> So he did.  Right in the middle of a conversation I was in too.
[17:23] <infinity> Mentally filtered it right out. :P
[17:23] <tomreyn> thanks for clarifying, guess i got bittin_ rolled.
[17:24] <infinity> tomreyn: We all get bittin_ sometimes.
[17:25] <infinity> tomreyn: Anyhow, if you're curious about RCs because you want to help test a flavour or two, I expect based on the current state of things that are in flight that the first set will be posted to the ISO tracker sometime late tonight (US Pacificish time).
[17:25] <infinity> Though that depends on how quickly sil2100 can shove langpack updates in.
[17:26] <infinity> And some other bits and bobs.
[17:26] <infinity> Not uncommon for me to spin the first RCs on Saturday from an airport, but I think we'll be earlier than that this cycle.  Maybe.
[17:27] <RikMills> :)
[17:28] <tomreyn> :) good luck there. i'll watch.
[17:29] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (bionic-proposed/main) [5.0.0-1021.21~18.04.1] (kernel)
[17:30] <RikMills> don't watch. help test. ;)
[17:32] <tomreyn> oh i most likely will (if maybe not the QA way). thanks for the invitation.
[17:39] <sil2100> cwayne, plars, bdmurray: the pi respins have finished building: http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20191010.1/
[17:40] <sil2100> infinity: I'll try to be as fast as possible!
[17:40] <cwayne> sil2100: ack thanks, should get pulled automatically for pi2/3, and plars can take care of 4
[17:41]  * sil2100 whips language-pack-exporter
[17:41] <sil2100> cwayne: thanks! Hopefully those should work on the pi4 fine - but that being said, I didn't check the manifests
[17:41] <sil2100> Anyway, those are test images for now
[17:49] -queuebot:#ubuntu-release- Unapproved: systemd (xenial-proposed/main) [229-4ubuntu21.22 => 229-4ubuntu21.23] (core)
[17:50] -queuebot:#ubuntu-release- Unapproved: dbus (xenial-proposed/main) [1.10.6-1ubuntu3.4 => 1.10.6-1ubuntu3.5] (core)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-azure (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-meta-oracle (eoan-proposed/main) [5.3.0.1001.1 => 5.3.0.1002.2] (core, kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-oracle (eoan-proposed/main) [5.3.0-1001.1 => 5.3.0-1002.2] (core, kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules-azure (eoan-proposed/restricted) [5.3.0-1002.2 => 5.3.0-1003.3] (kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-meta-azure (eoan-proposed/main) [5.3.0.1002.19 => 5.3.0.1003.20] (core, kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-raspi2 (eoan-proposed/universe) [5.3.0-1006.7 => 5.3.0-1007.8] (kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-meta-raspi2 (eoan-proposed/universe) [5.3.0.1006.2 => 5.3.0.1007.3] (kernel) (sync)
[18:01] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules-oracle (eoan-proposed/restricted) [5.3.0-1001.1 => 5.3.0-1002.2] (kernel) (sync)
[18:02] -queuebot:#ubuntu-release- Unapproved: linux-signed-azure (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[18:02] -queuebot:#ubuntu-release- Unapproved: linux-signed-oracle (eoan-proposed/main) [5.3.0-1001.1 => 5.3.0-1002.2] (core, kernel) (sync)
[19:25] <sil2100> Uploading language-packs, will approve them from the queue once they're all there
[19:29] <cyphermox> seb128: vorlon: is ubiquity ready for upload?
[19:30] <cyphermox> well, it doesn't matter really, I guess we'll definitely get a bugfix in to land the translation changes
[20:07] <sil2100> infinity: packages being accepted right now
[20:07] -queuebot:#ubuntu-release- Unapproved: linux-kvm (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[20:07] -queuebot:#ubuntu-release- Unapproved: linux-meta-kvm (eoan-proposed/main) [5.3.0.1002.2 => 5.3.0.1003.3] (core, kernel) (sync)
[20:07] -queuebot:#ubuntu-release- Unapproved: linux-signed (eoan-proposed/main) [5.3.0-17.18 => 5.3.0-18.19+1] (core, kernel) (sync)
[20:07] -queuebot:#ubuntu-release- Unapproved: linux-meta-gcp (eoan-proposed/main) [5.3.0.1003.3 => 5.3.0.1004.4] (core, kernel) (sync)
[20:07] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (eoan-proposed/main) [5.3.0-1003.3 => 5.3.0-1004.4] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux-aws (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux-meta-aws (eoan-proposed/main) [5.3.0.1002.2 => 5.3.0.1003.3] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules (eoan-proposed/restricted) [5.3.0-17.18 => 5.3.0-18.19] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux-gcp (eoan-proposed/main) [5.3.0-1003.3 => 5.3.0-1004.4] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux (eoan-proposed/main) [5.3.0-17.18 => 5.3.0-18.19] (core, kernel) (sync)
[20:09] -queuebot:#ubuntu-release- Unapproved: linux-meta (eoan-proposed/main) [5.3.0.17.19 => 5.3.0.18.20] (core, kernel) (sync)
[20:10] -queuebot:#ubuntu-release- Unapproved: konversation (eoan-proposed/universe) [1.7.5-1ubuntu2 => 1.7.5-1ubuntu3] (kubuntu)
[20:10] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (eoan-proposed/main) [5.3.0-1003.3 => 5.3.0-1004.4] (core, kernel) (sync)
[20:10] -queuebot:#ubuntu-release- Unapproved: linux-azure (eoan-proposed/main) [5.3.0-1002.2 => 5.3.0-1003.3] (core, kernel) (sync)
[20:10] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (eoan-proposed/main) [149 => 150] (ubuntu-desktop)
[20:13] <plars> sil2100: waveform: just to confirm - the pi2/3/4/cm3 all use the same raspi3 image now, correct? any plan to get rid of the raspi2 image there which seems to have a different checksum?
[20:28] <sil2100> plars: ah, good catch! So actually we no longer build any raspi2 images, but apparently cdimage 'copies over' the old images everytime a new build is happening
[20:28] <sil2100> So those images are actually from June
[20:28] <sil2100> (the raspi2 ones)
[20:28] <sil2100> Need to remove those, forgot about this cdimage functionality, just disabling the arch is not enough!
[20:29] <infinity> sil2100: \o/
[20:29] <rbalint> sil2100, could you please merge this for systemd? https://code.launchpad.net/~rbalint/britney/autopkgtest-eoan-hints/+merge/373987
[20:30] <rbalint> sil2100, infinity also could systemd please go in to eoan release?
[20:31] <plars> sil2100: waveform: I have some fixups to somehow do to make some tests work with eoan so things may not show up on the image testing board for now.  But I'm at least booting and checking dmesg, apt-get, etc for now. So far most things are looking ok, but rpi3ap doesn't seem to boot in the lab. I'll try it at home too, but it only gets as far as "Starting kernel ..." then nothing
[20:34] <ginggs> LocutusOfBorg: check in the log of the  	2019-10-10 14:33:35 UTC python-sparse/i386 test to see the actual version of python3-six that was installed
[20:52] <LocutusOfBorg> ginggs, I melded them... no differences in apt
[20:53] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [5.0.0-1021.21~18.04.1]
[20:59] -queuebot:#ubuntu-release- Unapproved: libpcap (eoan-proposed/main) [1.9.0-2build1 => 1.9.1-2] (core) (sync)
[21:02] <vorlon> cyphermox: from seb's commit message I figured the .pot file might also need regenerating in the source branch; I hadn't looked that far yet, can you carry it across the finish line for upload?
[21:06] <cyphermox> sure; I was questioning whether to wait for any last-minute fixes for something else
[21:06] <cyphermox> otoh if we want any translations for it; there might be a chance to get some the sooner it's in rather than later
[21:07] <cyphermox> OTOH, I think I see something odd there; there's already a translatable "Skip" string; looks like this was meant to be composited previously.... but it's also not going to work with shortcuts
[21:09] <seb128>  cyphermox, "Skip" is another string even if technically it's the same word, the translation for that string exists in other templates (e.g nautilus) so it should be easy to just revalidate for translators
[21:45] <cyphermox> seb128: what I mean is that I think this was meant to be composited in; but it never worked
[21:45] <cyphermox> it's irrelevant anyway, we just need to remember how to update the templates.pot file now ;)
[21:45] <cyphermox> I think I figured it out, just trying to get it right
[21:45] <cyphermox> (templates.pot gets updated in one command, but the update is a bit wonky)
[21:48] <cyphermox> heh, I just had the wrong command
[21:48] <cyphermox> seb128: anyway; you okay with me uploading this now?
[21:48] <seb128> cyphermox, well if there is no other change don't bother, I just did an upload of the template to launchpad manually
[21:48] <seb128> so no need of a source upload
[21:50] <cyphermox> ah, cool
[21:50] <cyphermox> you mean debian/real-po/templates.pot manually edited to add _Skip ?
[21:52] <seb128> cyphermox, I downloaded the current one from https://translations.launchpad.net/ubuntu/eoan/+source/ubiquity/+pots/ubiquity-debconf/+export , edited to add the string and uploaded on https://translations.launchpad.net/ubuntu/eoan/+source/ubiquity/+pots/ubiquity-debconf/+upload
[21:52] <seb128> cyphermox, which worked, string is there, https://translations.launchpad.net/ubuntu/eoan/+source/ubiquity/+pots/ubiquity-debconf/fr/30/+translate
[21:55] <cyphermox> cool
[21:56] <seb128> cyphermox, we should use debconf-updatepo to update the tempalte/translations still before the next upload though otherwise my change will be overwriten by the import
[21:56] <cyphermox> fwiw; updating debian/real-po/templates.pot from the debian/ubiquity.templates is as simple as running debconf-updatepo
[21:56] <cyphermox> yup
[21:56] <seb128> so if you want to do that and commit that would be useful
[21:56] <seb128> thx
[21:56] <cyphermox> (I'm applying that)
[21:56] <seb128> great
[21:56] <seb128> thx
[22:15] -queuebot:#ubuntu-release- Unapproved: atk1.0 (eoan-proposed/main) [2.34.0-1 => 2.34.1-1] (core) (sync)
[22:16] -queuebot:#ubuntu-release- Unapproved: at-spi2-core (eoan-proposed/main) [2.34.0-2 => 2.34.0-3] (core) (sync)
[22:16] -queuebot:#ubuntu-release- Unapproved: rejected at-spi2-core [sync] (eoan-proposed) [2.34.0-3]
[22:16] -queuebot:#ubuntu-release- Unapproved: rejected atk1.0 [sync] (eoan-proposed) [2.34.1-1]
[22:17] -queuebot:#ubuntu-release- Unapproved: gnome-calendar (eoan-proposed/main) [3.34.1-1 => 3.34.2-1] (desktop-extra, ubuntu-desktop) (sync)
[22:18] -queuebot:#ubuntu-release- Unapproved: network-manager (eoan-proposed/main) [1.20.4-2ubuntu1 => 1.20.4-2ubuntu2] (desktop-core)
[22:27] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (eoan-proposed/main) [19.10.2 => 19.10.3] (ubuntu-desktop)
[22:47] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (trusty-proposed) [1.0.1ubuntu2.24]
[22:51] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.0.0-32.34~18.04.2] (kernel)
[22:51] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [5.0.0-32.34~18.04.2] (kernel)
[22:51] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (disco-proposed/main) [5.0.0-1005.9] (core, kernel)
[22:51] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [arm64] (bionic-proposed/main) [5.0.0-32.34~18.04.2] (kernel)
[22:51] -queuebot:#ubuntu-release- New binary: linux-signed-oem-osp1 [amd64] (bionic-proposed/universe) [5.0.0-1025.28] (no packageset)
[22:51] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (disco-proposed) [5.0.0-1005.9]
[22:52] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [5.0.0-32.34~18.04.2]
[22:52] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [5.0.0-32.34~18.04.2]
[22:52] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [arm64] (bionic-proposed) [5.0.0-32.34~18.04.2]
[22:52] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1025.28]
[22:58] -queuebot:#ubuntu-release- New binary: linux-signed-gke-5.0 [amd64] (bionic-proposed/universe) [5.0.0-1022.22~18.04.3] (kernel)
[23:01] -queuebot:#ubuntu-release- New: accepted linux-signed-gke-5.0 [amd64] (bionic-proposed) [5.0.0-1022.22~18.04.3]
[23:20] -queuebot:#ubuntu-release- Unapproved: gnome-2048 (eoan-proposed/universe) [3.34.0-1 => 3.34.1-1] (ubuntu-budgie) (sync)
[23:21] -queuebot:#ubuntu-release- Unapproved: gnome-tetravex (eoan-proposed/universe) [1:3.34.0-1 => 1:3.34.1-1] (desktop-extra) (sync)
[23:26] -queuebot:#ubuntu-release- Unapproved: gjs (eoan-proposed/main) [1.58.0-1 => 1.58.1-1] (desktop-core, desktop-extra, mozilla) (sync)
[23:30] -queuebot:#ubuntu-release- Unapproved: gpaste (eoan-proposed/universe) [3.34.0-1 => 3.34.1-1] (no packageset) (sync)
[23:30] -queuebot:#ubuntu-release- Unapproved: accepted gpaste [sync] (eoan-proposed) [3.34.1-1]
[23:35] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-workspaces-to-dock (eoan-proposed/universe) [51-1 => 52-1] (no packageset) (sync)
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-workspaces-to-dock [sync] (eoan-proposed) [52-1]
[23:47] -queuebot:#ubuntu-release- Unapproved: ruby-gnome (eoan-proposed/universe) [3.3.8-2 => 3.4.0-1] (no packageset) (sync)
[23:47] -queuebot:#ubuntu-release- Unapproved: accepted ruby-gnome [sync] (eoan-proposed) [3.4.0-1]