[01:34] <smoser> bdmurray: sorry to pester you always. blackboxsw and I just uploaded another cloud-init to xenial and zesty.
[01:35] <smoser>  cloud-init 17.1-18-gd4f70470-0ubuntu1~16.04.2 and cloud-init 17.1-18-gd4f70470-0ubuntu1~17.04.2
[01:35] <smoser> if you could take a look in your sru time tomorrow we'd appreciate it.  its just one *very* tiny code change compared to what was already in -proposed.
[01:36] <smoser> bug 1724354
[06:40] <mitya57> xnox: ack
[06:41] <mitya57> tsimonq2: so let's plan Qt 5.9.3 and OpenSSL 1.0 for now
[06:52] <cpaelzer> hey, if a former proposed upload failed (due to gcc7 now making it an FTBFS) is that one of the cases to buildpackage with -v <version before last> ?
[06:53] <cpaelzer> to pick up in the changes file all effective changes that will hit the archive?
[06:57] <cpaelzer> I'm rather sure it is corrct for this case, so uploading like that for now
[06:58] <cpaelzer> but feel free to let me know if you tihnk otherwise would be better (and why)
[08:38] <infinity> cpaelzer: Yep.
[08:53] <test2222> hi all, could someone have a look at this Steam issue and give me a hint where I should raise another issue please? Not sure how to help the Valve guys: https://github.com/ValveSoftware/steam-for-linux/issues/3301#issuecomment-337832330
[13:32] <Laney> :-)
[13:42] <sladen> +1
[13:42] <sladen> "next please"
[13:44]  * xnox is betting on Brisk Bustard
[13:46] <infinity> xnox: What sort of animal is a Bustard?
[13:47] <xnox> infinity, a bird
[13:47] <xnox> https://www.google.co.uk/search?q=bustard&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwjm_bPs6PzWAhXLJMAKHXUyCLEQiR4IrwE&biw=1920&bih=990
[13:47] <xnox> infinity, looks like a heron to me
[13:48]  * mitya57 hopes 18.04 won't look like 8.04 because of that
[13:48] <xnox> but i'm not into birds
[14:32] <jbicha> breezier badger
[14:32] <jbicha> edgier eft
[14:33] <jbicha> too bad it doesn't well work for dapperer
[14:34]  * Laney is going to lobby for Dabbing
[14:34] <jbicha> the first 2 LTS were birds, I was thinking it was going to be a pattern, but nope
[14:42] <Faux> Laney: <3
[14:45] <xnox> Boring Bull?
[14:55] <roadmr> hello, it looks like the mirrors serving 17.10 images don't support zsync :( https://pastebin.canonical.com/201018/
[14:56] <cjwatson> I don't think we've ever pushed the zsync files to cloudfront
[14:56] <cjwatson> it's probably a bug on the IS side that they're redirecting .iso.zsync as well as .iso
[14:57] <roadmr> cjwatson: ugh - should I report this somewhere?
[14:58] <cjwatson> roadmr: either IS on IRC or RT, I guess
[14:58] <roadmr> cjwatson: will do, thanks!
[14:58] <cjwatson> roadmr: I mean it'll be a short-lived problem, but maybe a process bug somewhere
[14:58] <roadmr> yep, I guess once the thundering herd dies down things will point where they should
[15:17] <cjwatson> (for completeness: I totally misread the pastebin, this is probably unfixable at our end)
[16:41] <Sicnus> Who updates this file?  http://changelogs.ubuntu.com/meta-release  Also,d oes Dean H. (Beret) hang out here anymore?
[16:45] <nacc> Sicnus: it will get updated
[16:45] <nacc> Beret --^
[16:45] <nacc> Sicnus: feels like you could just look at who is in the channel
[16:46] <Sicnus> Beret: oheya Dean ;)   (Trae)
[17:08] <acheronuk> now updated
[17:09] <Sicnus> yeah thanks,  ;)  Just noticed.
[17:18] <nacc> slangasek: would it be appropriate for me to SRU a MRE for php7.1 to artful, and not fix it in BB, given an intention to update to php7.2 in BB? That is, I could wait for BB to open, and do the fix there, then SRU, but I'm going to be replacing php7.1 with php7.2 in BB evenually anyways
[17:23] <slangasek> nacc: what do you mean, "and not fix it in BB"?
[17:24] <slangasek> nacc: if this is just about SRUing before BB is open, it's fine to start an SRU now and have us copy forward to BB when it opens
[17:24] <nacc> slangasek: well, yeah I guess I meant that -- as in do I need to wait for BB to open
[17:24] <nacc> slangasek: as my first plan of action for BB is to sync 7.2 and drop 7.1 anyways
[17:30] <jbicha> nacc: y'all are targeting postgresql-10 for BB, right?
[17:30] <nacc> jbicha: yeah, i believe so
[17:31] <nacc> jbicha: it should line up well
[17:31] <jbicha> Debian completed the transition so hopefully it'll be fairly smooth in BB too
[17:32] <nacc> jbicha: yep
[17:37] <nacc> slangasek: general development question; is 'devel' a valid changelog distribution only in ubuntu?
[17:39] <slangasek> nacc: yes
[17:39] <nacc> slangasek: thanks
[18:07] <bdmurray> jbicha: In addition to commenting on bug 1721626, tagging it v-failed would have been helpful.
[18:10] <jbicha> ok, not clear whether there is a regression there or not, but probably would have been better to tag it like that until it can be investigated
[18:30] <bdmurray> jbicha: Yes, because the report shows that SRU as releasable.
[20:06] <infinity> bdmurray: The bug isn't in console-setup anyway, I'm sure.
[20:07] <infinity> bdmurray: Pretty sure that's another manifestation of "sometimes plymouth --ping doesn't return".
[20:11] <bdmurray> infinity: right, I was commeting on the process
[20:13] <infinity> bdmurray: Oh yes, indeed.  I was going to v-fail it after I sorted out it was to blame.  And it clearly wasn't to blame, from a cursory view of the diff.  So, the real process failure was not removing the regression tags from the other bug.
[20:13] <infinity> bdmurray: (That said, shouldn't a regression-proposed bug be scraped by sru-report and flagged up?)
[20:16] <bdmurray> infinity: There is a bot that looks for bugs about packages from -proposed but that filters on ones reported by apport.
[20:23] <infinity> bdmurray: Ahh, well.  Yay tools.  Another argument to push for britney-driven SRU migrations this cycle.  That block-proposed tag would have actually been useful. :P
[20:43] <slangasek> infinity: yeah, was discussed at the SRU team meeting in NYC, I think we're ready to push on that this cycle
[21:10] <tsimonq2> Excuse my ignorance but will all the uploads that have been 0-day SRU'ed into Artful be automatically copied to Bubonic Baboon once it opens or will developers have to do this on a case-by-case basis?
[21:15] <LocutusOfBorg> I think the former
[21:15] <LocutusOfBorg> otherwise we will end up with big b00bs being with lower versions than artful-updates
[21:19] <tsimonq2> True, I just didn't know if Bubonic Baboon when created would copy including -updates and -security.
[21:19] <tsimonq2> (And what about -proposed?)
[21:45] <sarnold> I'd expect all but -proposed
[21:49] <tsimonq2> sarnold: But why not -proposed? Those have the potential to land and might be greater than the one in Big Bat...
[21:49] <sarnold> tsimonq2: because they might not land.. presumably there's few enough of them for real trouble
[21:51] <tsimonq2> sarnold: I guess my point is is that once they *do* land, the version will be greater than Big Bat...
[21:52] <hallyn> note on the artful desktop installer - run from inside a VM, the display always seems wrong, such that the 'continue' button for choosing a keyboard layout is off the screen, so you can't click it, have to tab over to it and guess that it is highlighted.
[22:55] <nacc> hrm, i'm getting a Hash Sum mismatch on xenial-updates from archive.ubuntu.com in a LXD container
[22:55] <sarnold> any chance ss or netstat still tells you which IP was used?
[22:55] <nacc> anyone else seeing that (i'm seing it in autopkgtest)
[22:56] <nacc> sarnold: let me see if it goes away if i refresh my local build env
[22:56] <nacc> sarnold: autopkgtest-build-lxd didn't complain, so it must be something in my autopkgtest-lxd env
[22:57] <sarnold> nacc: apt-cacher-ng? squid-deb-proxy?
[22:57] <sarnold> everyone's reported one of them corrupts files and the other one works fine..
[22:57] <nacc> yeah i think it must be acng
[23:01] <nacc> sarnold: yep, that was it
[23:02] <nacc> sorry for the noise, and thanks sarnold!
[23:02] <sarnold> nacc: did you notice if it happened to serve up a different file than the one expected? i gave up on it when I saw that once..
[23:03] <nacc> sarnold: I did not. Once i reran autopkgtest-build-lxd and used that image, it worked correctly
[23:03] <sarnold> nacc: well, at least you're moving again :)
[23:03] <nacc> sarnold: yeah :)