[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] 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] 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] 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] oops [02:46] that wasn't intended for the distro [02:57] mwhudson: I don't know if there's anyone around just yet who can reject things [02:58] 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] 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] mostly launchpad [04:11] like for the other distros, there are some other servers that do some assembly of the pieces later [04:12] and then everything shows up for you on cdimage.ubuntu.com (or release.ubuntu.com when it will be released) [04:12] 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] Its for a project, not really for helping out with QA / RelEng (this semester, anyway). I mostly just admire at a distance... [04:36] ok [04:38] 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] 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] awesome! I knew it had something to do with it [04:40] what kind of project? [04:46] 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] ok [04:47] well, the scripts in ubuntu-cdimage are kind of complicated [04:48] 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] 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] 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] cyphermox: thank you for the help! [05:00] 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] 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] 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] release team, do you know anything about the Cosmic mascot? [06:45] I've seen no emails and it seems rather late [06:46] 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] hello [07:21] 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] anyone ? [07:45] johnyfire, when its ready [07:45] join #ubuntu-release-party [07:46] 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] ubuntu release party is exactly the right place for that sort of thing [07:47] thank you both and sorry for asking [07:47] 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] johnyfire: why don't you just try the daily installer.. it'll hardly change if at all before the release [07:48] ^ 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] tjaalton: so I will use the daily installer and it wont need wipe to get the final release ? [07:50] no [07:51] or wait 12h, but I know it is an hard thing to do when ubuntu is getting released :) [07:52] 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] damn, java is broken :/ [07:57] nice way to break cosmic [07:58] (wsimport tool has disappeared, sigh) [08:58] why did we switch to openjdk11 one week before release, breaking stuff? [08:58] can we get the gnome-software uploads from the queue in as 0 day SRU? [09:01] 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] because 10 won't be supported anymore [09:05] doko, and breaking a ton of packages one week ahead is supported? [09:05] vbox is no way buildable [09:05] and lots of more java tools [09:05] I'm already in touch with oracle, not sure if they will give some help or have hints [09:06] the idea was to package corba and other tools separately, and *after* switch to 11 [09:06] I don't even see an FFE for it :/ [09:06] there is, see the ubuntu-release ML [09:20] 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:20] bug 1798554 in ubiquity (Ubuntu) "OEM setup: user language selection not taken into account" [Undecided,New] https://launchpad.net/bugs/1798554 [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] I don't see virtualbox on the list of the "affected packages", so probably who did craft the list did a mistake? [09:29] (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] didrocks: Please do point out in the bug if it's not a regression from bionic. [09:31] didrocks: Also, was that bionic.1 or bionic.0 you tested? [09:31] infinity: currently updating it once launchpad doesn't timeout for me [09:31] infinity: .1 [09:32] hum, someone modified the title… [09:32] didrocks: A bionic.0 (without network, so nothing upgrades under you) might be an interesting data point too. [09:32] infinity: ah, good idea, could try [09:33] 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] infinity: interesting behavior, indeed :p [09:48] ooooh cyphermox new upload is nice, my laptop got mok for the first time ever. [10:02] infinity: confirmed, .0 without network -> still the same (unsure it even worked one day TBH) [10:04] sil2100, Laney bug 1798562 [10:04] bug 1798562 in ubiquity (Ubuntu) "After a side by side installation, resized filesystem is corrupted" [Undecided,New] https://launchpad.net/bugs/1798562 [10:04] o m g [10:07] infinity, ^ [10:10] 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] & Oct 18 05:43:20 u systemd-fsck[475]: /dev/sda4: clean, 260/5857280 files, 644812/23400762 blocks [10:32] eek [10:56] 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) [10:56] Launchpad bug 1798236 in gnome-software (Ubuntu Cosmic) "gnome-software crashes with assertion failure Gs:ERROR:../lib/gs-plugin-loader.c:1698:gs_plugin_loader_pending_apps_add: assertion failed: (gs_app_list_length (list) > 0)" [High,Fix committed] https://launchpad.net/bugs/1798236 [11:09] -queuebot:#ubuntu-release- Unapproved: figtree (cosmic-proposed/universe) [1.4.3+dfsg-5 => 1.4.3+dfsg-6ubuntu1] (no packageset) [11:33] Confirmed LP: #1798562 at least in virtualbox [11:33] Launchpad bug 1798562 in ubiquity (Ubuntu) "After a side by side installation, resized filesystem is corrupted" [High,Confirmed] https://launchpad.net/bugs/1798562 [11:34] -queuebot:#ubuntu-release- Unapproved: freeipa (cosmic-proposed/universe) [4.7.1-1 => 4.7.1-2ubuntu1] (no packageset) [11:41] grrrr [11:53] Laney: is that an offline resize? [11:53] apw: the install alongside option from the installer [11:53] so... yes, I assume so [11:53] so then and e2resize bug? [11:54] with newer roots? [11:54] I tried with e2fsprogs from bionic and it still happened [11:54] in both the first & second installs [11:54] that's a valid test right? [11:54] is there any obvious options differences for root? [11:55] xnox is giving me a cosmic with bionic kernel [11:55] soon™ [11:55] not if the bug is a newer ext4 feature in cosmic not supported by e2resize [11:56] we could do with like a superblock dump from a root from a bionic install and from a cosmic install [11:56] to see if anything new is on [11:57] like dumpe2fs? [12:01] Laney: yes that sort of thing [12:02] Laney: particularly the Filsystem features [12:04] but it would be good to confirm 100% is offline, as that narrows search to tools [12:04] apw: think jibel's got that available [12:07] ⌛ [12:09] apw, how do you confirm it's ofline? [12:09] offline [12:10] jibel: not mounted [12:11] k [12:11] jibel, oh i am saying that someone who knows how casper does it confirm its an offline resize [12:13] caper/ubiquity/thign that does it [12:23] apw: it looks like ext4 does not support online shrinking so it would have to be offline [12:24] sforshee, then that is something [12:24] 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] 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] 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] 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] thanks! [14:20] ahasenack: no problem, those are easy! [14:20] bdmurray: can I keep the same version/release numbers? [14:22] apw, yes sorry bionic http://paste.ubuntu.com/p/4G5GpwzbBy/ cosmic http://paste.ubuntu.com/p/zSCz23Y4n3/ [14:23] ahasenack: yes, as they didn't make it into -proposed [14:24] thanks [15:23] xnox, do we have logs for the bionic kernel in cosmic kernel test ? [15:24] ... in cosmic userspace ... [15:35] apw, hey [15:35] 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] ext4 failures on the kernel [15:35] ack [15:39] 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] cascardo, apw - no i don't have those logs =/ should have booted qemu with dumping kernel/console to a log file [15:40] vorlon: I think there is [15:42] vorlon: I'm not finding it though [15:42] 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:42] Launchpad bug 1795024 in ubuntu-release-upgrader (Ubuntu) "release-upgrades Prompt to anything other than normal prevents beta upgrades" [Undecided,New] https://launchpad.net/bugs/1795024 [15:43] 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] xnox, ok [15:48] cyphermox: we're trying to find a reliable reproducer, also trying to figure out what could be causing this [15:48] But we're not getting reliable results [15:49] bdmurray: LP: #1798618 filed [15:49] Launchpad bug 1798618 in ubuntu-release-upgrader (Ubuntu) "confusing error message with 'do-release-upgrade -d' and Prompt=lts" [Medium,New] https://launchpad.net/bugs/1798618 [15:51] sil2100: ok, we'll I'll do a setup here [15:51] sil2100: where is your core18 build running? I don't have any indication of its status? [15:51] 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] didrocks: I knew it sounded familiar! [15:52] cyphermox: https://code.launchpad.net/~mvo/+snap/core18/+build/356205 <- here's the snap building, it's ekhm, waiting for now ;/ [15:52] oh, ok [15:53] crap, I had forgotten to replug the laptop :/ [15:54] bdmurray: glad to not be the only one who finded that weird, it's not only my French ;) [16:01] hmmm. queuebot died [16:01] Kubuntu marked as ready :) [16:03] didrocks: ok well, the message is incorrect and confusing, so bug filed :) [16:08] sil2100: cyphermox could Bug #1783757 or Bug #1796788 be related to the ext shrink corruption? [16:08] bug 1783757 in e2fsprogs (Ubuntu) "shrinking previous file systems makes them corrupted " [Undecided,New] https://launchpad.net/bugs/1783757 [16:08] bug 1796788 in e2fsprogs (Ubuntu) "resize2fs: Illegal indirect block found while trying to resize" [Undecided,Confirmed] https://launchpad.net/bugs/1796788 [16:08] Laney: 🦒 [16:09] xAAAAAAAAAHHHHHHHHHHHHHHH [16:10] Who knows where to find stgraber? [16:10] I think queuebot is MIA. [16:10] It's too quiet. :P [16:11] sil2100: also, with some interesting debug/reproducer methods from only FS metadata courtesy of Ted Tso: Bug #1778140 [16:11] bug 1778140 in e2fsprogs (Ubuntu) "resize2fs hoses a filesystem on lvm after resizing" [Undecided,Confirmed] https://launchpad.net/bugs/1778140 [16:11] Laney: 🦒 ❤ [16:12] 😱 [17:40] 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] by apw [17:40] methinks I should just accept it [17:43] 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] congrats all [17:43] infinity: Just saw the announcement, you called it an LTS. === infinity changed the topic of #ubuntu-release to: Released: Bionic 18.04.1, Cosmic 18.10 | Archive: Closed | Cosmic Release Coordination | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melius malum quod cognoscis. [17:43] Eickmeyer: Erm. Where? [17:44] infinity: Very beginning of the email. [17:44] Eickmeyer: Hah. Oops. Well, that's just the copy on ubuntu-release, I'll re-do it. :P [17:44] infinity: :D [17:48] Right, let's try that again. [18:22] infinity: do you want me to indicate the typo you did on ubuntu-announce too? [18:23] 'cause 18.04 LTS is indicated in the 18.10 announce message that went there too [18:23] just saying. [18:32] infinity, Oh, so you were the one who has always written the announcement mail! [18:32] I've always wondered who he was :) [19:05] cjwatson: do you happen to know if LP: #1798656 is a regression? [19:05] Launchpad bug 1798656 in debconf (Ubuntu) "gnome frontend gives no widget for answering a boolean prompt" [Critical,New] https://launchpad.net/bugs/1798656 [19:44] teward: Son of a. And three of us read that paragraph too. Well, can't take back the email now. [20:06] infinity: Speaking of broken things, RIP queuebot. stgraber seems to have disappeared, wat do? [20:10] snap refresh --channel=stable stgraber [20:10] * tsimonq2 throws a tomato at vorlon [20:10] ;) [20:16] tsimonq2: "2018-10-15 15:52:20 stgraber free: yeah, off Wed, Thu and Fri this week, then in SLC next week" [20:18] ack [20:37] vorlon: certainly could be, since I rewrote that frontend a fair bit. would it be possible to get an isolated reproducer? [20:37] sure [20:39] thought I'd tested all the question types but maybe I missed something [20:41] 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] 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] congrats all [20:48] vorlon: /proc/N/maps of the debconf process might reveal whether it thinks it's gtk2 or gtk3 [20:49] 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] yeah, have to reproduce it again first [20:50] the window did look like the gtk3 experience as I last recall it [20:50] 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] 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] cat /dev/null > teward [21:01] 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] teward: doesn't caffeine start leaking from your pores onto the keyboard with ~50 cups in? [21:13] valorie: he can't type, the shakes make it too hard [21:13] :-) [21:41] even I draw the line somewhere south of 50 ... [21:42] ^ [21:43] very small cups [21:44] (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] I could probably line up like 50 shot glasses of coffee and be fine enough with that :) [21:45] uh dude [21:45] that's like 2.5 pints at minimum [21:45] (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] pfft yeah that's doable [21:47] I mean maybe over like four hours [21:48] Yeah. [21:48] 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] when I can feel the caffeine in my teeth, I know it's time to stop [21:56] because my teeth def. do not need any revving up [21:57] i used to take pro-plus (caffeine tablets) it was fun, but eventually one does crash. [21:59] I stay away from the caffeine tablets, but I guess ymmv :) === lyorian is now known as lynorian [22:25] -queuebot:#ubuntu-release- Unapproved: parted (bionic-proposed/main) [3.2-20 => 3.2-20ubuntu0.1] (core) [23:39] vorlon, infinity - can i start uploading things into dd-series unapproved queue? or no?