[00:22] -queuebot:#ubuntu-release- New binary: golang-1.10 [i386] (trusty-proposed/universe) [1.10.4-2ubuntu1~14.04.1] (no packageset)
[00:35] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Cosmic Final] has been marked as ready
[00:59] -queuebot:#ubuntu-release- New: accepted golang-1.10 [amd64] (trusty-proposed) [1.10.4-2ubuntu1~14.04.1]
[00:59] -queuebot:#ubuntu-release- New: accepted golang-1.10 [armhf] (trusty-proposed) [1.10.4-2ubuntu1~14.04.1]
[00:59] -queuebot:#ubuntu-release- New: accepted golang-1.10 [ppc64el] (trusty-proposed) [1.10.4-2ubuntu1~14.04.1]
[00:59] -queuebot:#ubuntu-release- New: accepted golang-1.10 [arm64] (trusty-proposed) [1.10.4-2ubuntu1~14.04.1]
[01:00] -queuebot:#ubuntu-release- New: accepted golang-1.10 [i386] (trusty-proposed) [1.10.4-2ubuntu1~14.04.1]
[01:13] <jbicha> every 30 minutes, I'm getting an email telling me that brotli xenial-security 0.3.0+dfsg-2ubuntu1 is being rejected because it is older than 1.0.3-1ubuntu1~16.04.1
[01:13] <jbicha> maybe the part about the 1.0.3 version being in main and the security update being in universe is part of the problem?
[01:14] <jbicha> I think we will ultimately need 1.0.3 in -security too so maybe I should ask security to rebuild it there; maybe it will fix this
[01:38] -queuebot:#ubuntu-release- Unapproved: brotli (xenial-security/main) [1.0.3-1ubuntu1~16.04.1 => 0.3.0+dfsg-2ubuntu1] (no packageset) (sync)
[01:44] -queuebot:#ubuntu-release- Unapproved: rejected brotli [sync] (xenial-security) [0.3.0+dfsg-2ubuntu1]
[02:42] -queuebot:#ubuntu-release- Unapproved: cargo (cosmic-proposed/universe) [0.29.0-1ubuntu1 => 0.30.0-1~exp1ubuntu1] (no packageset)
[02:42] -queuebot:#ubuntu-release- Unapproved: rustc (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu2 => 1.29.2+dfsg1+llvm-0ubuntu1] (no packageset)
[02:42] -queuebot:#ubuntu-release- Unapproved: accepted cargo [source] (cosmic-proposed) [0.30.0-1~exp1ubuntu1]
[02:42] -queuebot:#ubuntu-release- Unapproved: accepted rustc [source] (cosmic-proposed) [1.29.2+dfsg1+llvm-0ubuntu1]
[02:45] -queuebot:#ubuntu-release- Unapproved: rustc (bionic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu1 => 1.29.2+dfsg1+llvm-0ubuntu1~18.04.1] (no packageset)
[02:46] <mwhudson> oops
[02:46] <mwhudson> that wasn't intended for the distro
[02:57] <cyphermox> mwhudson: I don't know if there's anyone around just yet who can reject things
[02:58] <mwhudson> well the changelog doesn't mention a bug etc so i'm sure it will get rejected anyway :)
[02:58]  * mwhudson off to collect kiddo, back online later
[04:03] <erasurecode> odd question. What servers are involved in building Ubuntu ISOs? fedora has koji and atomic-reactor, arch has archiso, coreos-assembler for coreos, catalyst for gentoo... I hear it's somehow a cron job or within launchpad itself?
[04:10] <cyphermox> mostly launchpad
[04:11] <cyphermox> like for the other distros, there are some other servers that do some assembly of the pieces later
[04:12] <cyphermox> and then everything shows up for you on cdimage.ubuntu.com (or release.ubuntu.com when it will be released)
[04:12] <cyphermox> erasurecode: right now I suggest you help testing the images (see iso.qa.ubuntu.com)
[04:14] -queuebot:#ubuntu-release- New binary: rustc [s390x] (cosmic-proposed/universe) [1.29.2+dfsg1+llvm-0ubuntu1] (no packageset)
[04:31] <erasurecode> Its for a project, not really for helping out with QA / RelEng (this semester, anyway). I mostly just admire at a distance...
[04:36] <cyphermox> ok
[04:38] <cyphermox> well, the short answer is that launchpad does most of the heavy lifting, and you have this: https://wiki.ubuntu.com/ReleaseTeam/CDImageSetup
[04:39] <cyphermox> it should get you some more idea how the servers are set up to do the rest of the assembly and publishing process.
[04:40] <erasurecode> awesome! I knew it had something to do with it
[04:40] <cyphermox> what kind of project?
[04:46] <erasurecode> remastersys / ansible / drone-ci / distro releng - I could do it the relinux/remastersys way, but I figured it would be nice to know how all the distros build ISOs officially.
[04:47] <cyphermox> ok
[04:47] <cyphermox> well, the scripts in ubuntu-cdimage are kind of complicated
[04:48] <cyphermox> it's not rocket surgery, but if you can avoid it... essentially it's a lot of different cases for various flavours, and what needs to be put on the image where.
[04:49] <erasurecode> I figured all of it would be. I still need to check on how smaller distros build their stuff, but for the most part, I hope this works in all cases to just adapt the major releng pipelines.
[04:51] <erasurecode> I think the problem is mostly about creating an ISO with software they were supposed to agree to a TOS for, like google-chrome or wifi drivers, or a non-free firefox extension. But, if the machine is running a build from scratch, I can have finer-grained control over ensuring no TOS-required software is allowed on a public image, and if they want Chrome pre-installed on an ISO, only they have access to it.
[04:54] <erasurecode> cyphermox: thank you for the help!
[05:00] <cyphermox> I recall once seeing some software project that was making all this easy for you to build images very close to what we build, but I don't remember the name
[05:02] <erasurecode> I'll research into it again in a month or two, after trying it a bit more in depth. Good luck on Cosmic! ttyl
[05:15] <Eickmeyer> Hey everyone! I'm zsyncing the latest Studio image, but alas, it's late, I'm tired, and a certain little boy has to be at the bus stop tomorrow morning, so I'll start running some test cases and ticking some checkboxes soon after I wake up and the coffee kicks-in. I should be awake around 7am US Pacific, and conscious sometime after that.
[06:45] <valorie> release team, do you know anything about the Cosmic mascot?
[06:45] <valorie> I've seen no emails and it seems rather late
[06:46] <valorie> acheronuk said that it's usually in the ubuntu slideshow but missing from there as well?
[06:47] -queuebot:#ubuntu-release- Unapproved: eclipselink (cosmic-proposed/universe) [2.6.5-3 => 2.6.5-4] (no packageset) (sync)
[06:47] -queuebot:#ubuntu-release- Unapproved: openjpa (cosmic-proposed/universe) [2.4.2-5 => 2.4.2-6] (no packageset) (sync)
[06:47] -queuebot:#ubuntu-release- Unapproved: libjdo-api-java (cosmic-proposed/universe) [3.1-2 => 3.1-3] (no packageset) (sync)
[06:47] -queuebot:#ubuntu-release- Unapproved: libquartz-java (cosmic-proposed/universe) [1:1.8.6-5 => 1:1.8.6-6] (no packageset) (sync)
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted eclipselink [sync] (cosmic-proposed) [2.6.5-4]
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted libquartz-java [sync] (cosmic-proposed) [1:1.8.6-6]
[06:48] -queuebot:#ubuntu-release- Unapproved: jaxrs-api (cosmic-proposed/universe) [2.1.2-1 => 2.1.2-2] (no packageset) (sync)
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted libjdo-api-java [sync] (cosmic-proposed) [3.1-3]
[06:48] -queuebot:#ubuntu-release- Unapproved: sitemesh (cosmic-proposed/universe) [2.4.1+dfsg-6 => 2.4.1+dfsg-7] (no packageset) (sync)
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted openjpa [sync] (cosmic-proposed) [2.4.2-6]
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted jaxrs-api [sync] (cosmic-proposed) [2.1.2-2]
[06:48] -queuebot:#ubuntu-release- Unapproved: accepted sitemesh [sync] (cosmic-proposed) [2.4.1+dfsg-7]
[07:07] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Cosmic Final] has been marked as ready
[07:20] <johnyfire> hello
[07:21] <johnyfire> got a question, what time UTC does 18.10 come online?
[07:29] -queuebot:#ubuntu-release- Unapproved: vcr.py (cosmic-proposed/universe) [2.0.1-1ubuntu2 => 2.0.1-2] (no packageset) (sync)
[07:30] -queuebot:#ubuntu-release- Unapproved: accepted vcr.py [sync] (cosmic-proposed) [2.0.1-2]
[07:44] <johnyfire> anyone ?
[07:45] <LocutusOfBorg> johnyfire, when its ready
[07:45] <LocutusOfBorg> join #ubuntu-release-party
[07:46] <johnyfire> thanks was just asking, because i got a Ryzen laptop and for the last month I can't use it at all , a friend of mine told me that only latest ubuntu will work with it, so iI just sit there and watch it powered off
[07:47] <mwhudson> ubuntu release party is exactly the right place for that sort of thing
[07:47] <johnyfire> thank you both and sorry for asking
[07:47] <mwhudson> np
[07:48] -queuebot:#ubuntu-release- Unapproved: dogtag-pki (cosmic-proposed/universe) [10.6.6-2 => 10.6.7-1] (no packageset) (sync)
[07:48] -queuebot:#ubuntu-release- Unapproved: elfutils (cosmic-proposed/main) [0.170-0.5 => 0.170-0.5ubuntu1] (core)
[07:48] <tjaalton> johnyfire: why don't you just try the daily installer.. it'll hardly change if at all before the release
[07:48] <mwhudson> ^ that elfutils upload might be better as an early SRU but well it's there
[07:49] -queuebot:#ubuntu-release- Unapproved: accepted dogtag-pki [sync] (cosmic-proposed) [10.6.7-1]
[07:49] <johnyfire> tjaalton: so I will use the daily installer and it wont need wipe to get the final release ?
[07:50] <tjaalton> no
[07:51] <LocutusOfBorg> or wait 12h, but I know it is an hard thing to do when ubuntu is getting released :)
[07:52] <johnyfire> I will wait then, it'll take some time to remove the dust for the laptop, either way. Hope it will work... thanks again you are very kind people
[07:56] <LocutusOfBorg> damn, java is broken :/
[07:57] <LocutusOfBorg> nice way to break cosmic
[07:58] <LocutusOfBorg> (wsimport tool has disappeared, sigh)
[08:58] <LocutusOfBorg> why did we switch to openjdk11 one week before release, breaking stuff?
[08:58] <seb128> can we get the gnome-software uploads from the queue in as 0 day SRU?
[09:01] <seb128> the one in the release pocket is screwed on i386, that has low number of users nowadays but would still be nice to have fixed in a SRU this week
[09:03] <doko> because 10 won't be supported anymore
[09:05] <LocutusOfBorg> doko, and breaking a ton of packages one week ahead is supported?
[09:05] <LocutusOfBorg> vbox is no way buildable
[09:05] <LocutusOfBorg> and lots of more java tools
[09:05] <LocutusOfBorg> I'm already in touch with oracle, not sure if they will give some help or have hints
[09:06] <LocutusOfBorg> the idea was to package corba and other tools separately, and *after* switch to 11
[09:06] <LocutusOfBorg> I don't even see an FFE for it :/
[09:06] <doko> there is, see the ubuntu-release ML
[09:20] <didrocks> going to try bug #1798554 on bionic if I can reproduce. I still marked the test as passing as cosmic isn't a big OEM target and OEM don't really use ubiquity step 2 but their own tool for creating users
[09:22] -queuebot:#ubuntu-release- Unapproved: guice (cosmic-proposed/universe) [4.2-3 => 4.2.1-1] (no packageset) (sync)
[09:23] -queuebot:#ubuntu-release- Unapproved: jcodings (cosmic-proposed/universe) [1.0.40-3 => 1.0.41-1] (no packageset) (sync)
[09:23] -queuebot:#ubuntu-release- Unapproved: jgit (cosmic-proposed/universe) [3.7.1-5 => 3.7.1-6] (no packageset) (sync)
[09:26] <LocutusOfBorg> I don't see virtualbox on the list of the "affected packages", so probably who did craft the list did a mistake?
[09:29] <didrocks> (reproduced the OEM issue on bionic as well)
[09:29] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (cosmic-proposed) [3.30.2-0ubuntu6]
[09:29] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (cosmic-proposed) [3.30.2-0ubuntu7]
[09:31] <infinity> didrocks: Please do point out in the bug if it's not a regression from bionic.
[09:31] <infinity> didrocks: Also, was that bionic.1 or bionic.0 you tested?
[09:31] <didrocks> infinity: currently updating it once launchpad doesn't timeout for me
[09:31] <didrocks> infinity: .1
[09:32] <didrocks> hum, someone modified the title…
[09:32] <infinity> didrocks: A bionic.0 (without network, so nothing upgrades under you) might be an interesting data point too.
[09:32] <didrocks> infinity: ah, good idea, could try
[09:33] <infinity> didrocks: Literally that user's only action in launchpad ever is to change your bug title to the single word "german".  WHAT DOES IT MEAN.
[09:33] <didrocks> infinity: interesting behavior, indeed :p
[09:48] <xnox> ooooh cyphermox new upload is nice, my laptop got mok for the first time ever.
[10:02] <didrocks> infinity: confirmed, .0 without network -> still the same (unsure it even worked one day TBH)
[10:04] <jibel> sil2100, Laney bug 1798562
[10:04] <Laney> o m g
[10:07] <jibel> infinity, ^
[10:10] <Laney> Oct 18 05:43:29 u kernel: EXT4-fs error (device sda4): ext4_find_extent:909: inode #27: comm Xorg: pblk 9727 bad header/extent: extent tree corrupted - magic f30a, entries 34, max 340(340), depth 0(0)
[10:11] <Laney> & Oct 18 05:43:20 u systemd-fsck[475]: /dev/sda4: clean, 260/5857280 files, 644812/23400762 blocks
[10:32] <acheronuk> eek
[10:56] <guiverc> Laney, lp #1798236 - leafpad, gedit, xscorch installed all worked, but it didn't return me to prompt as expected  (running from term; i eventually ^C to get prompt)
[11:09] -queuebot:#ubuntu-release- Unapproved: figtree (cosmic-proposed/universe) [1.4.3+dfsg-5 => 1.4.3+dfsg-6ubuntu1] (no packageset)
[11:33] <acheronuk> Confirmed LP: #1798562 at least in virtualbox
[11:34] -queuebot:#ubuntu-release- Unapproved: freeipa (cosmic-proposed/universe) [4.7.1-1 => 4.7.1-2ubuntu1] (no packageset)
[11:41] <sil2100> grrrr
[11:53] <apw> Laney: is that an offline resize?
[11:53] <Laney> apw: the install alongside option from the installer
[11:53] <Laney> so... yes, I assume so
[11:53] <apw> so then and e2resize bug?
[11:54] <apw> with newer roots?
[11:54] <Laney> I tried with e2fsprogs from bionic and it still happened
[11:54] <Laney> in both the first & second installs
[11:54] <Laney> that's a valid test right?
[11:54] <apw> is there any obvious options differences for root?
[11:55] <Laney> xnox is giving me a cosmic with bionic kernel
[11:55] <Laney> soon™
[11:55] <apw> not if the bug is a newer ext4 feature in cosmic not supported by e2resize
[11:56] <apw> we could do with like a superblock dump from a root from a bionic install and from a cosmic install
[11:56] <apw> to see if anything new is on
[11:57] <Laney> like dumpe2fs?
[12:01] <apw> Laney: yes that sort of thing
[12:02] <apw> Laney: particularly the Filsystem features
[12:04] <apw> but it would be good to confirm 100% is offline, as that narrows search to tools
[12:04] <Laney> apw: think jibel's got that available
[12:07] <Laney> ⌛
[12:09] <jibel> apw, how do you confirm it's ofline?
[12:09] <jibel> offline
[12:10] <TJ-> jibel: not mounted
[12:11] <jibel> k
[12:11] <apw> jibel, oh i am saying that someone who knows how casper does it confirm its an offline resize
[12:13] <apw> caper/ubiquity/thign that does it
[12:23] <sforshee> apw: it looks like ext4 does not support online shrinking so it would have to be offline
[12:24] <apw> sforshee, then that is something
[12:24] <apw> sforshee, i see we have a lot of work on detecting corruption post v4.15
[12:28]  * apw muses whether checksums are enabled
[12:39] -queuebot:#ubuntu-release- Unapproved: backuppc (xenial-proposed/main) [3.3.1-2ubuntu3.3 => 3.3.1-2ubuntu3.4] (core)
[12:49] <juliank> um, Does any file system support online shrinking?
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted figtree [source] (cosmic-proposed) [1.4.3+dfsg-6ubuntu1]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted guice [sync] (cosmic-proposed) [4.2.1-1]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted jgit [sync] (cosmic-proposed) [3.7.1-6]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (cosmic-proposed) [4.7.1-2ubuntu1]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted jcodings [sync] (cosmic-proposed) [1.0.41-1]
[12:50] -queuebot:#ubuntu-release- Unapproved: rejected elfutils [source] (cosmic-proposed) [0.170-0.5ubuntu1]
[12:51] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (cosmic-proposed) [1.29.2+dfsg1+llvm-0ubuntu1]
[13:03] <ahasenack> hi, can someone please reject my backuppc upload to xenial-proposed? I want to enhance the dep8 test a bit, make it more resilient
[13:08] <apw> jibel, i think you were getting the filesystem info dumps from the filesystems ?
[14:05] -queuebot:#ubuntu-release- Unapproved: rejected backuppc [source] (xenial-proposed) [3.3.1-2ubuntu3.4]
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Cosmic Final] has been marked as ready
[14:19] <ahasenack> thanks!
[14:20] <bdmurray> ahasenack: no problem, those are easy!
[14:20] <ahasenack> bdmurray: can I keep the same version/release numbers?
[14:22] <jibel> apw, yes sorry bionic http://paste.ubuntu.com/p/4G5GpwzbBy/  cosmic http://paste.ubuntu.com/p/zSCz23Y4n3/
[14:23] <bdmurray> ahasenack: yes, as they didn't make it into -proposed
[14:24] <ahasenack> thanks
[15:23] <apw> xnox, do we have logs for the bionic kernel in cosmic kernel test ?
[15:24] <apw> ... in cosmic userspace ...
[15:35] <xnox> apw, hey
[15:35] <xnox> apw, i have something.... do you want installer logs or runtime/boot stuff?
[15:35]  * xnox ponders what's the old bug number
[15:35] <cascardo> ext4 failures on the kernel
[15:35] <xnox> ack
[15:39] <vorlon> bdmurray: do you know if there's a bug open about the u-r-u message being confusing when you are in Prompt=lts mode and you run do-release-upgrade -d? ("Upgrades to the development release are only available from the latest supported release")
[15:40] <xnox> cascardo, apw - no i don't have those logs =/ should have booted qemu with dumping kernel/console to a log file
[15:40] <bdmurray> vorlon: I think there is
[15:42] <bdmurray> vorlon: I'm not finding it though
[15:42] <vorlon> bdmurray: I see LP: #1795024, but that's complaining about the effect of the prompt, whereas I'm just complaining about the inaccurate message
[15:43] <cyphermox> sil2100: jibel: apw: need help with the fs corruption bug?
[15:46] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Cosmic Final] has been marked as ready
[15:47] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Cosmic Final] has been marked as ready
[15:47] -queuebot:#ubuntu-release- Builds: Netboot i386 [Cosmic Final] has been marked as ready
[15:47] <apw> xnox, ok
[15:48] <sil2100> cyphermox: we're trying to find a reliable reproducer, also trying to figure out what could be causing this
[15:48] <sil2100> But we're not getting reliable results
[15:49] <vorlon> bdmurray: LP: #1798618 filed
[15:51] <cyphermox> sil2100: ok, we'll I'll do a setup here
[15:51] <cyphermox> sil2100: where is your core18 build running? I don't have any indication of its status?
[15:51] <didrocks> vorlon: I think bdmurray is confusing this with the exact same conversation we had ~1 month ago (I was puzzled as well by the error message). I don't think there was a plan to change it though and so, didn't open a bug IIRC
[15:52] <bdmurray> didrocks: I knew it sounded familiar!
[15:52] <sil2100> cyphermox: https://code.launchpad.net/~mvo/+snap/core18/+build/356205 <- here's the snap building, it's ekhm, waiting for now ;/
[15:52] <cyphermox> oh, ok
[15:53] <cyphermox> crap, I had forgotten to replug the laptop :/
[15:54] <didrocks> bdmurray: glad to not be the only one who finded that weird, it's not only my French ;)
[16:01] <acheronuk> hmmm. queuebot died
[16:01] <acheronuk> Kubuntu marked as ready :)
[16:03] <vorlon> didrocks: ok well, the message is incorrect and confusing, so bug filed :)
[16:08] <TJ-> sil2100: cyphermox could Bug #1783757 or Bug #1796788 be related to the ext shrink corruption?
[16:08] <sil2100> Laney: 🦒
[16:09] <Laney> xAAAAAAAAAHHHHHHHHHHHHHHH
[16:10] <tsimonq2> Who knows where to find stgraber?
[16:10] <tsimonq2> I think queuebot is MIA.
[16:10] <tsimonq2> It's too quiet. :P
[16:11] <TJ-> sil2100: also, with some interesting debug/reproducer methods from only FS metadata courtesy of Ted Tso: Bug #1778140
[16:11] <tsimonq2> Laney: 🦒 ❤
[16:12] <Laney> 😱
[17:40] <vorlon> infinity, sil2100: did you have eyes on the linux-oem in cosmic unapproved? bionic-updates currently has a higher version number than cosmic release, looks like this is a sync to get it up-to-date
[17:40] <vorlon> by apw
[17:40] <vorlon> methinks I should just accept it
[17:43] <infinity> vorlon: apw said he'd be handling it post-release and was just parking it in the queue so he didn't forget.
[17:43] <willcooke> congrats all
[17:43] <Eickmeyer> infinity: Just saw the announcement, you called it an LTS.
[17:43] <infinity> Eickmeyer: Erm.  Where?
[17:44] <Eickmeyer> infinity: Very beginning of the email.
[17:44] <infinity> Eickmeyer: Hah.  Oops.  Well, that's just the copy on ubuntu-release, I'll re-do it. :P
[17:44] <Eickmeyer> infinity: :D
[17:48] <infinity> Right, let's try that again.
[18:22] <teward> infinity: do you want me to indicate the typo you did on ubuntu-announce too?
[18:23] <teward> 'cause 18.04 LTS is indicated in the 18.10 announce message that went there too
[18:23] <teward> just saying.
[18:32] <wordless> infinity, Oh, so you were the one who has always written the announcement mail!
[18:32] <wordless> I've always wondered who he was :)
[19:05] <vorlon> cjwatson: do you happen to know if LP: #1798656 is a regression?
[19:44] <infinity> teward: Son of a.  And three of us read that paragraph too.  Well, can't take back the email now.
[20:06] <tsimonq2> infinity: Speaking of broken things, RIP queuebot. stgraber seems to have disappeared, wat do?
[20:10] <vorlon> snap refresh --channel=stable stgraber
[20:10]  * tsimonq2 throws a tomato at vorlon 
[20:10] <tsimonq2> ;)
[20:16] <TJ-> tsimonq2: "2018-10-15 15:52:20     stgraber        free: yeah, off Wed, Thu and Fri this week, then in SLC next week"
[20:18] <tsimonq2> ack
[20:37] <cjwatson> vorlon: certainly could be, since I rewrote that frontend a fair bit.  would it be possible to get an isolated reproducer?
[20:37] <vorlon> sure
[20:39] <cjwatson> thought I'd tested all the question types but maybe I missed something
[20:41] <vorlon> cjwatson: https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests/+packages noisy-fake-driver has a boolean and it does not show the bug.  DEBIAN_FRONTEND=Gnome dpkg-reconfigure docker.io also does not reproduce the original bug.  So... hmm.
[20:42] <vorlon> could be the bug was only present in the bionic versions of the packages and not in cosmic?  or it could be that a debconf frontend that has been started mid-upgrade was broken?
[20:44] <mwhudson> congrats all
[20:48] <cjwatson> vorlon: /proc/N/maps of the debconf process might reveal whether it thinks it's gtk2 or gtk3
[20:49] <cjwatson> if the bindings weren't there then surely it wouldn't be able to display a window at all ... so probably more subtle than that
[20:50] <vorlon> yeah, have to reproduce it again first
[20:50] <vorlon> the window did look like the gtk3 experience as I last recall it
[20:50] <teward> infinity: just going to say, I have about 50 cups of caffeine in me, it helps me spot stuff.  That, and the 'This is no longer offtopic" announcement on Ask Ubuntu helped me catch it too :P
[20:50] <teward> since attentionToDetail() is a thing :P
[20:56] -queuebot:#ubuntu-release- Unapproved: accepted nodejs [source] (bionic-proposed) [8.10.0~dfsg-2ubuntu0.4]
[20:56] -queuebot:#ubuntu-release- Unapproved: breeze-gtk (bionic-proposed/universe) [5.12.4-0ubuntu1 => 5.12.7-0ubuntu0.1] (kubuntu)
[21:00] <tsimonq2> cat /dev/null > teward
[21:01] <tsimonq2> dd if=/dev/null of=/dev/teward
[21:01] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (bionic-proposed) [1:3.26.4-0~ubuntu18.04.2]
[21:02] <valorie> teward: doesn't caffeine start leaking from your pores onto the keyboard with ~50 cups in?
[21:13] <cyphermox> valorie: he can't type, the shakes make it too hard
[21:13] <valorie> :-)
[21:41] <cjwatson> even I draw the line somewhere south of 50 ...
[21:42] <tsimonq2> ^
[21:43] <vorlon> very small cups
[21:44] <cjwatson> (turns out that when you drink coffee at more or less line rate from a pint mug your heart starts thumping really hard)
[21:44] <tsimonq2> I could probably line up like 50 shot glasses of coffee and be fine enough with that :)
[21:45] <cjwatson> uh dude
[21:45] <cjwatson> that's like 2.5 pints at minimum
[21:45] <cjwatson> (stupid units.  sorry.)
[21:45] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1024.29]
[21:45]  * tsimonq2 converts to American
[21:46] <tsimonq2> pfft yeah that's doable
[21:47] <cjwatson> I mean maybe over like four hours
[21:48] <tsimonq2> Yeah.
[21:48] <tsimonq2> I said it was doable, I didn't say it was *sane* ;)
[21:54] -queuebot:#ubuntu-release- Unapproved: parted (cosmic-proposed/main) [3.2-21ubuntu1 => 3.2-21ubuntu2] (core)
[21:56] <valorie> when I can feel the caffeine in my teeth, I know it's time to stop
[21:56] <valorie> because my teeth def. do not need any revving up
[21:57] <xnox> i used to take pro-plus (caffeine tablets) it was fun, but eventually one does crash.
[21:59] <tsimonq2> I stay away from the caffeine tablets, but I guess ymmv :)
[22:25] -queuebot:#ubuntu-release- Unapproved: parted (bionic-proposed/main) [3.2-20 => 3.2-20ubuntu0.1] (core)
[23:39] <xnox> vorlon, infinity - can i start uploading things into dd-series unapproved queue? or no?