[00:08] <wxl> we going to wait until we got a name for y cycle before turning dailies on, i'm assuming
[00:08] <wxl> ?
[00:09] <slangasek> yes
[00:09] <wxl> ko thx
[00:24] <bjf> slangasek: we have a name and it is yakkity yak
[00:24] <bjf> *yakkety yak*
[00:24] <slangasek> my money was on yippee yappee yahooey
[00:32] <doko> you lost your money, it always was tuples not triples
[00:38] <infinity> slangasek: I've got targets in LP for 14.04.5 and 16.04.1, will mirror same to the release schedule(s) tomorrow.
[00:38] <infinity> doko: ^
[00:38] <infinity> Also, hahahahahahaha.  Yakkity (though misspelled?) yak won!
[00:39] <slangasek> are we sure he really meant it? :)
[00:39] <wxl> wait
[00:39] <infinity> Hard to say.
[00:39] <wxl> yakkity yak, really?
[00:39] <wxl> oh please say it's true!
[00:40] <slangasek> http://www.markshuttleworth.com/archives/1496
[00:40] <wxl> oh.
[00:40] <wxl> yakkety.
[00:40] <wxl> sorry, what he says, goes. :)
[00:41] <wxl> we're going to get REAAAAALY sick of typing yakkety.
[00:41] <teward> wxl: i haven't typed it yet, and I am *already* sick of it >.<
[00:41] <wxl> hahahahhaah
[00:41] <wxl> well time to turn dailies on then XD
[00:41] <bjf> infinity, which spelling are you going with?
[00:42] <infinity> bjf: Well, it's either "Yakety" if the reference is "Yakety Sax" (the song), or "Yakkity" if the reference is "Yakkity Yak" (the TV show), but yakkety is wrong. ;)
[00:43] <wxl> well, maybe that's the point
[00:43] <wxl> it's wartier XD
[00:55]  * tsimonq2 agrees with wxl, it's gonna be annoying after a while to type XD
[00:56] <wxl> https://wiki.ubuntu.com/YakketyYak
[00:57] <Kamilion> ?
[00:57]  * tsimonq2 creates
[00:57] <Kamilion> shouldn't that be yakkity?
[00:57] <wxl> hahahah
[00:57] <tsimonq2> I did Xenial so it's my turn again XD
[00:58] <tsimonq2> (seriously, look at the XenialXerus page)
[00:58] <wxl> not according to sabdfl
[00:58] <Kamilion> Wow, we even get not invented here syndrome from release names now? <3
[00:58] <tsimonq2> no I mean the wiki page
[00:58] <tsimonq2> XenialXerus (last edited 2015-10-22 17:55:18 by tsimonq2)
[00:58] <DalekSec> Kamilion: http://www.markshuttleworth.com/archives/1496
[01:00] <tsimonq2> infinity: look good? https://wiki.ubuntu.com/YakketyYak
[01:00] <wxl> tsimonq2: don't forget https://wiki.ubuntu.com/ReleaseSchedule
[01:01]  * tsimonq2 gets that done
[01:01] <wxl> aw someone should fix up https://wiki.ubuntu.com/ReleaseSchedule/LTStoLTS for into the future
[01:01] <Kamilion> DalekSec: https://en.wikipedia.org/wiki/Yakkity_Yak
[01:01] <DalekSec> Good for it?
[01:01] <Kamilion> unless it's referring to the song? https://en.wikipedia.org/wiki/Yakety_Yak
[01:01] <wxl> he said yakkety
[01:02] <wxl> it is what it is :)
[01:02] <Kamilion> either way, it's ke or i
[01:02] <Kamilion> err
[01:02] <Kamilion> ki or e
[01:02] <Kamilion> not ke
[01:02] <wxl> either way it SHOULD be
[01:02] <wxl> but mark IS the dictator for life XD
[01:02] <Kamilion> hence the "not invented here syndrome" joke
[01:02] <wxl> oh i got it
[01:02] <Kamilion> can't use wayland, gotta write mir
[01:02] <Kamilion> ETC
[01:02] <infinity> Confirmed with sabdfl that it's yakkety, as spelled in the blog post.
[01:02] <wxl> hahahahhaah
[01:02] <infinity> https://launchpad.net/ubuntu/yakkety
[01:02] <Kamilion> ubuntu has a history of reinvention of the wheel, sort of
[01:02] <wxl> hahahah
[01:02]  * Kamilion points fingers at upstart
 it can't even launch apache! </joke>
[01:03] <wxl> um, there's no wheel. that's unix, man. :)
[01:03]  * Kamilion lmfao
[01:03] <Kamilion> next you'll be telling me /usr is more than an RK-05 disk pack's worth of bytes
[01:03] <wxl> XD
[01:04] <Kamilion> In my day, we hand assembled binaries uphill in the snow both ways!
[01:04] <Kamilion> with a needle and a very steady hand
[01:04] <Kamilion> Alright, i'm done with the comedian act; back to seriousness
[01:04] <wxl> someone needs to add the point release schedule to https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule at some point
[01:05] <tsimonq2> infinity: mind acking https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule as well>
[01:05] <wxl> we should expect the first around july, hm?
[01:06] <infinity> tsimonq2: Those dates all need to be Thursdays.
[01:06] <infinity> wxl: First point release is scheduled in LP for the 21st of July, I'll add it to the schedule soon.
[01:06] <wxl> thx infinity
[01:07] <tsimonq2> infinity: ok adjusting
[01:07]  * tsimonq2 copied from Wily's
[01:07] <infinity> tsimonq2: wily's should be a good base indeed, just needs minor shuffling.
[01:07] <tsimonq2> infinity: also ack https://wiki.ubuntu.com/ReleaseSchedule while you are at it if you could :)
[01:07] <infinity> slangasek: Do we have UOS dates?
[01:08] <tsimonq2> May 3-5 I thought...?
[01:08] <infinity> Ahh, indeed, summit.ubuntu.com has the dates.
[01:08] <slangasek> yah
[01:08] <infinity> I must have missed the usual email thread about it.
[01:10] <tsimonq2> infinity: FWIW we have an extra week in June subtracted from July...same amount of weeks but I'd thought I would mention it
[01:11] <infinity> tsimonq2: Yup, just shuffle the alpha up a week to keep it at the end of the month.
[01:11] <infinity> (And fix the colours)
[01:11] <tsimonq2> *sigh* thank god nothing is September 1...
[01:12] <tsimonq2> yep, covered :)
[01:13] <tsimonq2> that also means first week in October gets bumped up to September
[01:13] <infinity> Yep, s'all good.
[01:13] <infinity> Calendars suck.
[01:13] <infinity> Thanks for doing the draft.
[01:14] <tsimonq2> np
[01:14] <tsimonq2> https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule look good?
[01:14] <tsimonq2> as a suggestion, maybe put Ubuntu 16.04 somewhere by April 21, 2016
[01:15] <tsimonq2> oh lol I forgot, it's all 2015, fixing
[01:15] <tsimonq2> there fixed
[01:16] <infinity> Heh.  You didn't fix the suffixes. ;)
[01:16] <infinity> 23th, 22th, etc. ;)
[01:16] <tsimonq2> I didn't?
[01:16]  * tsimonq2 looks
[01:16] <infinity> And Alpha1 should move to Jun30.
[01:16] <tsimonq2> oh jeez
[01:16] <tsimonq2> alright
[01:16] <infinity> Semptember 1rd is my favourite.
[01:16] <infinity> 1rd, yo.
[01:17] <tsimonq2> hahahahahahahah
[01:18] <infinity> And UOS is Tue-Thu, not Mon-Thu.
[01:18] <infinity> Otherwise, looks good.
[01:18] <tsimonq2> fixed?
[01:18] <tsimonq2> and do you think it's relevant to put the release of 16.04 by April 21?
[01:19] <infinity> Nah.
[01:19] <infinity> I think it's generally taken as a given that a release happened before the release schedule. :P
[01:19] <tsimonq2> hey, the first time I read the release scedule, I was checking the dates going, "OK, what?!? who screwed up the schedule?!?" XD
[01:19] <tsimonq2> *schedule
[01:20] <tsimonq2> *shrug* but if you don't think it's needed I won't put it XD
[01:20] <infinity> Current state looks good to me.  Thanks.
[01:20] <infinity> Just need to add a big "DRAFT, DO NOT RELY ON THIS YET" to the top so we can send it out for comment and reject^Wconsider people's complaints.
[01:21] <tsimonq2> hahahahahah
[01:21] <tsimonq2> need me to do that?
[01:21] <infinity> Nein.
[01:21] <tsimonq2> alright
[01:22]  * tsimonq2 assumes that's no
[01:22] <infinity> It is. :)
[01:22] <tsimonq2> :)
[01:22] <tsimonq2>  /o\ long day, it's _finally_ over
[01:23] <tsimonq2> but still, Yakkety?! /me wonders what it's referring to...
[01:24] <infinity> Yaks, of course.
[01:24] <tsimonq2> hahahahahahahahah
[01:24] <tsimonq2> and I thought Xenial Xerus would be hard to spell/remember
[01:24] <tsimonq2> :P
[01:25] <infinity> You might be too young to really appreciate the yakety yak, yakety sax, yakkity yak references.
[01:25] <infinity> But it's making some of us giggle. :)
[01:25] <tsimonq2> yeah I have no idea what those are... :P
[01:26] <DalekSec> infinity: Don't talk back!
[01:34] <tsimonq2> ?
[01:34] <tsimonq2> ¯\_(ツ)_/¯
[01:36] <infinity> tsimonq2: https://www.youtube.com/watch?v=PtTC3pGBjs4 -- educate yoself.
[01:43] <tsimonq2> hahahahah
[01:55] <tsimonq2> infinity: has lsb_release been updated yet?
[01:55]  * tsimonq2 uses the devel alias
[01:56] <infinity> tsimonq2: The archive doesn't exist yet, so no.  Patience.
[01:56] <infinity> This is not actually an instant process.
[01:56] <tsimonq2> ohhh gotcha sorry :)
[06:14] <LocutusOfBorg> hi, can I sync libpng*?
[06:19] <infinity> LocutusOfBorg: Maybe.
[06:22] <LocutusOfBorg> it will end up in unapproved... and in new because of the soname change
[06:22] <LocutusOfBorg> so, lets sync and leave the decision to release team
[06:23] <LocutusOfBorg> oops unapproved, because somebody sync'd it before already
[06:38] <LocutusOfBorg> well, I opened LP: #1573415 for the old libpng-dev removal
[06:38] <ubot5`> Launchpad bug 1573415 in libpng (Ubuntu) "please merge libpng from debian" [Undecided,New] https://launchpad.net/bugs/1573415
[06:39]  * LocutusOfBorg thinks about a transition tracker
[06:40]  * flocculant lols at yakketyyak
[06:42] <infinity> Hrm.  Might have to walk to the office to update chroot tarballs.
[06:42] <infinity> Seems like everyone in this hotel woke up at once and started surfing porn.
[06:43]  * infinity grabs a quick shower before heading in to finish opening.
[06:45] <LocutusOfBorg> LOL
[06:45] <flocculant> morning infinity - now the madness is over - thanks to you all :)
[06:52] <infinity> flocculant: It's never really over.  Now I get to open yakkety, and people get to fix all the bugs we found in the release so we can have a better point release, and and and...
[06:54] <flocculant> infinity: :)
[06:55] <flocculant> still laughing at yakkety yak :D
[06:59]  * infinity -> Bluefin.
[08:10] <infinity> doko: Did you have any pre-opening toolchain bits for 16.10, or shall we just roll into it once the checklist is done?
[08:32] <ogra_> infinity, seems 15.04 is gone from http://releases.ubuntu.com/ .... there were snappy images in there that are still valid
[08:35] <davmor2> ogra_: 15.04 was dropped 3 months into 15.10 this isn't a new thing ;)
[08:35] <ogra_> ha ha
[08:35] <davmor2> ogra_: no I'm serious
[08:36] <ogra_> i think there are pages linking to them, the 15.04 snappy image are supported until the 16.04 snappy release ... which is some time in summer (june/july)
[08:36] <ogra_> *images
[08:46] <infinity> ogra_: I can copy the snappy ones back, gimme time.  I'm multitasking a bit.
[08:46] <ogra_> no hurry
[10:25] <xnox> i'm gonna have so many laughs about
[10:25] <xnox> yakkety security
[10:25] <xnox> and yakkety backports
[10:25] <xnox> and yakkety updates
[10:25] <Laney> yakports
[10:29] <infinity> xnox: Oh joy, a new boost.
[10:29] <infinity> xnox: Do we want that built before we open?
[10:29] <infinity> xnox: (ie: is there a defaults bump too?)
[10:32] <xnox> infinity, default bump in progress
[10:33] <xnox> infinity, i also believe this boost1.60 will fail to migrate on s390x, but we shall see.
[10:33] <infinity> xnox: Well, that's not ideal.
[10:33] <infinity> xnox: Don't really want autosync all backed up on boost.
[10:34] <xnox> infinity, well i'm trying to sort out if britney is lying in debian, or there really is something fishy about s390x in debian/rules
[10:35] <xnox> infinity, in any case i will be fixing this in debian and uploading there and syncing over, e.g. today.
[10:35] <xnox> cause yeah i do want to open with new boost.
[10:37] <infinity> xnox: Kay.
[10:37] <infinity> xnox: I'll accept it then, and you'd better fix it ASAFP if you break anything.
[10:37] <xnox> ack.
[10:42] <clivejo> xnox: when do the +1 archives usually get created?
[10:42] <infinity> clivejo: A few hours ago.
[10:43] <clivejo> oh that was fast
[10:44] <doko> why do you accept new boost before we change the toolchain defaults?
[10:45] <infinity> doko: I can kill the builds.  Do you have a new toolchain prepped?
[10:46] <doko> sure, however yesterday I was told I shouldn't expect opening today ...
[10:46] <infinity> doko: Boost builds killed.
[10:46] <cjwatson> Yesterday we didn't have a name and you know what expectations are like there.
[10:46] <infinity> doko: I asked earlier this morning if you had toolchain bits, I guess you slept in (like most of us should have done).
[10:46] <infinity> doko: So, waiting on you before I build anything else.
[10:47] <doko> ta
[10:51] <Laney> infinity: https://paste.debian.net/440208/
[10:52] <infinity> Laney: Ta.
[10:54] <xnox> that boost will have dropped binaries, there are mistakes in debian/control that smr did
[10:57] <infinity> xnox: Well, it's cancelled anyway, so fix it. :P
[11:06] <infinity> doko: Patch gcc-linaro.diff does not apply (enforce with -f)
[11:06] <doko> yep
[11:09] <xnox> new boost will be upload into debian, and then i guess we will want to wait for armhf to finish building gcc, before you accept that one.
[11:10] <infinity> Yep.
[11:10] <infinity> I'll delete the current one so no one's tempted to retry it.
[11:10] <xnox> and test building debian build now, so off to buy neoprene sand socks in the mean time.
[11:10] <xnox> infinity, sounds good.
[11:10] <infinity> Done.
[11:11] <doko> xnox, is this boost ready for GCC 6?
[11:12] <Laney> xnox: https://www.youtube.com/watch?v=A6hNXUwOHKQ these guys aren't wearing socks
[11:12] <doko> xnox, also please consider building icu from experimental before doing the new boost
[11:12] <Laney> ur doin it rong
[11:17] <ginggs> xnox, are you want to drop context/coroutine from arm64, i understood it was available there from boost1.59
[11:17] <ginggs> are you sure*
[11:52] <infinity> pitti: When can we have Yodeling Yam autopkgtests?
[12:04]  * apw shouts at network-manager ... this new version is utter pants
[12:08] <pitti> infinity: I like yodelling a lot better than yakkety!
[12:08] <infinity> pitti: Too late.
[12:15] <pitti> infinity: queues exist now, so britney can issue test requests
[12:15] <pitti> they aren't served yet, still need to build containers and yakkety cloud images
[12:15] <infinity> pitti: May have to reissue the batch that vim caused?
[12:15] <pitti> will do that in a bit, need to run out for some errands
[12:15] <infinity> Not sure where they went...
[12:15] <infinity> If anywhere. :)
[12:16] <pitti> into the void
[12:16] <pitti> yes, I'll retry all the bits on excuses.html
[12:16] <infinity> pitti: I assume "yakkety cloud images" are a xenial custom hack job, not you blocking on CPC, right?
[12:16] <pitti> infinity: correct
[12:16] <infinity> Check.
[12:22] <doko> coq-float succeeded to build? strange
[12:22] <infinity> Yeah.  Probably means we should have done one last give-back a week before release.  Oh well.
[12:23] <doko> I did
[12:23] <infinity> Two days before release? :)
[12:23] <infinity> Pretty sure that changing the strings in os-release didn't fix it.
[12:23] <infinity> I would hope...
[12:24] <mapreri> there was this idea of importing libpng before everything, to avoid doing hundreds of rebuilds later, is that going to happen? :)
[12:24] <infinity> mapreri: After the toolchain, but before the world, yes.
[12:24] <apw> it is in the queue
[12:24] <mapreri> cool
[12:28] <xnox> ginggs, available empty package is not useful at all.
[12:35] <ginggs> xnox: thanks for checking. yeah, empty package worse is than no package. i think they can be built for arm64, but maybe there's still a problem with the packaging
[12:36] <Odd_Bloke> pitti: You do _eventually_ use our images though, right?
[12:37] <Odd_Bloke> pitti: (I'm all for you not blocking on us for now, it'll be a few days before we have the infrastructure for yakkety in place :)
[12:37] <infinity> Odd_Bloke: Well, he's using your images even in the hacked case. :P
[12:37] <infinity> Odd_Bloke: Also, slaaaacker!  I'll have Ubuntu (and flavour) ISOs building in a few minutes.
[12:37] <infinity> *cough*
[12:38] <Odd_Bloke> infinity: ^_^
[12:39] <Odd_Bloke> I didn't think we had packages in yakkety yet?  Or do we copy the xenial packages over and then all the toolchain things land etc.?
[12:39] <infinity> Odd_Bloke: Yes, that.
[12:39] <infinity> Odd_Bloke: yakkety is a fully-functional distro.
[12:39] <infinity> Odd_Bloke: I'm running it.
[12:39] <xnox> hm
[12:39] <xnox> ginggs, maybe.
[12:40] <xnox> i shall try that.
[12:40] <Odd_Bloke> infinity: So hipster.
[12:40] <infinity> Odd_Bloke: So hip I can't see over my own pelvis.
[12:46] <Odd_Bloke> "chroot: failed to run command '/usr/bin/env': No such file or directory" <-- that's a livefs build error I've seen before, but I can't remember what causes it
[12:47] <LocutusOfBorg> :( no libpng accepted makes me sad
[12:47]  * LocutusOfBorg read about the archive opening on irclogs.u.c
[12:49] <Odd_Bloke> Though I feel like I've normally seen in on s390x, now I think about it.
[12:49] <mapreri> LocutusOfBorg: it's not open yet?
[12:52] <infinity> LocutusOfBorg: Still building the initial toolchain.
[12:53] <Odd_Bloke> infinity: Any ideas about https://launchpadlibrarian.net/255173456/buildlog_ubuntu_yakkety_amd64_cpc-development_BUILDING.txt.gz ?
[12:54] <Odd_Bloke> infinity: ("Try waiting" is an acceptable answer :)
[12:54] <infinity> Odd_Bloke: You need the debootstrap in proposed.
[12:54] <infinity> Odd_Bloke: If you have a PPA you use with your builds, just copy it over.  Or build with PROPOSED=1.  Or wait a tiny bit.
[12:55] <infinity> Oh, a bit more than a tiny bit, since its migration to the release pocket is blocked on pitti's autopkgtests.
[12:55] <infinity> So, you'd be best off copying it.
[12:56] <LocutusOfBorg> infinity, not a problem, but the issue is: I would like to have something more than just a libpng imported
[12:57] <infinity> LocutusOfBorg: Well, you didn't ask for anything else. :P
[12:57] <LocutusOfBorg> oh well, gcc-5 failed to upload
[12:57] <LocutusOfBorg> https://launchpadlibrarian.net/255171857/upload_9610916_log.txt
[12:57] <LocutusOfBorg> infinity, give me one sec
[12:58] <LocutusOfBorg> https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1524328
[12:58] <ubot5`> Launchpad bug 1524328 in libpng (Ubuntu) "libpng 1.6 transition" [High,Confirmed]
[12:58] <infinity> doko: gcc-5 still builds gcc-6 binaries?
[12:58] <LocutusOfBorg> message #12
[12:58] <infinity> (libgcc, etc)
[12:58] <doko> fixed
[13:00] <xnox> Odd_Bloke, i'd love to spin up yakkety cloud-images in my ppa =)
[13:00] <infinity> LocutusOfBorg: Seems the only absolute necessity there are both the libpng sources happening before the world opens.
[13:00] <LocutusOfBorg> infinity, and gdk-pixbuf rebuilds maybe
[13:00] <LocutusOfBorg> but yes, we can retry it until it builds
[13:01] <LocutusOfBorg> the problem is gdk-pixbuf embedding somewhere a libpng broken pkgconfig, so the other tools will fail in configure
[13:02] <Odd_Bloke> xnox: Hm?
[13:03]  * apw will sort out debootstrap in the stables ...
[13:04] <pitti> Odd_Bloke: yes, as soon as there are daily yakkety images, I'll build the adt images from them instead of from a dist-upgraded xenial one; same appraoch as for wily->xenial
[13:05] <xnox> Odd_Bloke, because i can give experimental yakkety images to try out to others =)
[13:05] <pitti> infinity: open> do you want a debhelper merge? that's traditionally on my list, can do after dealing with the yak images
[13:06] <Odd_Bloke> xnox: Well, we can do that too... :p
[13:07] <infinity> pitti: If you're in the mood.
[13:10] <LocutusOfBorg> thanks for fixing boost1.60 delta <3
[13:10] <LocutusOfBorg> aka thanks for archive reorg
[13:10] <LocutusOfBorg> :D
[13:11] <Odd_Bloke> infinity: Am I missing an easy way to copy archive/-proposed packages in to a PPA?  Should I just backportpackage it?
[13:11] <cjwatson> copy-package
[13:12] <cjwatson> --from ubuntu --from-suite whatever --to ppa:OWNER/ubuntu/NAME --to-suite whatever ...
[13:12] <infinity> Odd_Bloke: copy-package --from=ubuntu --from-suite=yakkety-proposed --to=ppa:username/ubuntu/ppaname --to-suite=yakkety -b debootstrap
[13:27] <pitti> cloudy autopkgtest (i386, amd64, ppc64el) are now yakified
[13:28] <pitti> building lxc containers failed during debootstrap (armhf, s390x)
[13:39] <willcooke> infinity, Should the vagrant images have a xenial options too?  http://cloud-images.ubuntu.com/vagrant/
[13:40] <Odd_Bloke> willcooke: Nope, those have moved in alongside the other image files.
[13:41] <infinity> ogra_: Your 15.04 snappy images should be back.  Sorry about that.
[13:41] <Odd_Bloke> willcooke: e.g. http://cloud-images.ubuntu.com/xenial/20160420.3/xenial-server-cloudimg-amd64-vagrant.box
[13:41] <ogra_> infinity, i must admit i dont care about them at all ... thibaut and didrocks do though :)
[13:41]  * ogra_ is all 16.04 :)
[13:41] <infinity> ogra_: Well, tell whomever cares that they're resurrected. :P
[13:41] <ogra_> yep, doing so
[13:41] <willcooke> Odd_Bloke, thanks.  I've been told that they're "not working" - are you happy everything is as it should be?
[13:42] <Odd_Bloke> willcooke: I did a test yesterday that seemed fine, so if you could ask your source to file a bug at https://bugs.launchpad.net/cloud-images/+filebug ? :)
[13:42] <ogra_> infinity, hmm, are we talking about http://releases.ubuntu.com/ ? i dont see 15.04
[13:42] <willcooke> Odd_Bloke, ta
[13:42] <ogra_> (sync mirro still running ? )
[13:43] <infinity> ogra_: They were never on releases, were they?  I thought they were on cdimage.
[13:43] <infinity> ogra_: Or am I mistaken?
[13:44] <ogra_> they were on http://releases.ubuntu.com/15.04/
[13:44] <infinity> ogra_: Oh, huh.  Someone had put them on releases.
[13:44] <infinity> ogra_: Moving again. :P
[13:44] <ogra_> http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz was the amd64 one
[13:44] <ogra_> yeah, crazy :)
[13:44] <ogra_> i would prefer to kleep them in cdimage.u.c/ubuntu-snappy/ for the future
[13:45] <ogra_> we'll see if i'll have success with that once we have actual 16.04 releases :)
[13:46] <infinity> ogra_: http://releases.ubuntu.com/15.04/
[13:47] <ogra_> perfetto !
[13:47] <willcooke> Odd_Bloke, I think this is it:  https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1573058
[13:47] <ubot5`> Launchpad bug 1573058 in livecd-rootfs (Ubuntu) "Ubuntu 16.04 current not booting in Vagrant (gurumeditation)" [Undecided,Confirmed]
[13:48] <willcooke> Odd_Bloke, and this is who my source is:  https://twitter.com/therealmarv/status/723485477328850944 ;)
[13:49] <Odd_Bloke> willcooke: OK, in a meeting ATM so will dig in a few minutes. :)
[13:49] <willcooke> Odd_Bloke, nw, thanks
[13:52] <Odd_Bloke> Step 1) Actually manage to download something from our DC
[13:53] <ogra_> infinity, hmm, if you want to save diskspace you might want to check why all images are duplicated on http://releases.ubuntu.com/15.04/
[13:54] <infinity> ogra_: They're not, those are symlinks from the wrong names to the right ones. :P
[13:54] <ogra_> lol
[13:54] <ogra_> k
[13:54] <ogra_> i only noticed they are duplicated in the MD5SUM too
[13:54] <infinity> Yeah, checksum-directory will sum anything with a file extension it likes.
[13:55] <infinity> I has to be dumb and follow links or the linking to ../pool magic would break.
[13:55] <infinity> s/I has/It has/
[13:56] <didrocks> thanks infinity, ogra_ :)
[13:56] <didrocks> customers care about 15.04 btw :p
[13:56] <infinity> didrocks: Anything else I can delete for you while I'm here? :P
[13:56] <ogra_> didrocks, which is awful !
[13:57] <LocutusOfBorg> can we have a libpng16 transition tracking page?
[13:57] <infinity> LocutusOfBorg: Sure.
[13:57] <LocutusOfBorg> <3
[13:57] <LocutusOfBorg> thanks
[14:03] <didrocks> infinity: please do delete everything, I would be relieved! :-)
[14:04] <didrocks> ogra_: if there was a finale ubuntu core 16.04, I would agree fully :)
[14:04] <ogra_> didrocks, just a few months :)
[14:05]  * ogra_ wouldnt care so much about final ... but feature-functional would be good
[14:06] <didrocks> like having config? :p
[14:07] <ogra_> config ... a classic shell so you can actually build snaps ... (sicne we dont support cross building)
[14:07] <Odd_Bloke> LocutusOfBorg: Hey, was https://launchpad.net/ubuntu/+source/virtualbox/5.0.18-dfsg-2build1 fixing an upstream issue (that users of Virtualbox 5.0.18 on other platforms might see)?
[14:08] <ogra_> these are the two pressing items imho ... once  they are back we should really push everyone to use 16.04
[14:08] <LocutusOfBorg> Odd_Bloke, yes
[14:08] <LocutusOfBorg> a serious one
[14:08] <LocutusOfBorg> https://launchpadlibrarian.net/254650006/virtualbox_5.0.18-dfsg-2_5.0.18-dfsg-2build1.diff.gz
[14:08] <LocutusOfBorg> look at the diff
[14:09] <LocutusOfBorg> +Description: fix https://www.virtualbox.org/ticket/15317
[14:09] <LocutusOfBorg> upstream asked me to cherry-pick the patch
[14:09] <infinity> Odd_Bloke: So, sounds like the self-important bug submitter who felt the need to call us out on twitter is just running a buggy version of VirtualBox. :P
[14:10] <Odd_Bloke> infinity: Yep. ^_^
[14:10] <infinity> Odd_Bloke: Shame his followers won't see that.
[14:10] <Odd_Bloke> infinity: If only he were running Ubuntu, he would never have had this problem.
[14:10] <infinity> (And seems unlikely he'll mention it)
[14:10] <infinity> willcooke: ^
[14:10] <LocutusOfBorg> I got a lot of bug reports about 5.0.18 without the patch and 5.0.16
[14:11] <LocutusOfBorg> and *none* yet about the version landed in xenial
[14:11] <Odd_Bloke> LocutusOfBorg: Yeah, I saw it when testing the Vagrant box pre-release.
[14:11] <infinity> LocutusOfBorg: Find a large tree to knock on.
[14:11] <Odd_Bloke> But upgraded and it went away.
[14:11] <LocutusOfBorg> infinity, I didn't get it :)
[14:11] <willcooke> thanks infinity
[14:11] <LocutusOfBorg> thanks Odd_Bloke for confirming the fix
[14:12] <Odd_Bloke> I did enjoy a moment of sheer panic though, when I _did_ think it was an issue with our vagrant boxes. ;)
[14:14] <pitti> infinity: ^ prerequisite for merged debhelper
[14:15] <doko> pitti: done
[14:22] <pitti> doko, infinity: ^
[14:22] <pitti> infinity: yakkety autopkgtests should be fully running; next britney run will re-issue the lost test requests
[14:22] <infinity> pitti: Huzzah.
[14:24] <doko> pitti, done
[14:26] <Odd_Bloke> infinity: Luckily, he only posted about it in replies, so only people who follow the people he was replying to will see it. :)
[14:28] <LocutusOfBorg> Odd_Bloke, link?
[14:29] <Odd_Bloke> LocutusOfBorg: https://twitter.com/therealmarv/with_replies <-- a couple of tweets in there; I replied to one already :)
[14:31] <LocutusOfBorg> so at the end we should thanks infinity for accepting the last minute virtualbox fix :D
[14:37] <Odd_Bloke> Indeed. :)
[14:44] <pitti> infinity: fun, the pbuilder regression looks pretty much like the failure to deboostrap a yakkety container that I experienced earlier
[14:45] <infinity> pitti: All I see is 404s...
[14:45] <infinity> Oh, I guess the log links work.
[14:45] <pitti> 404s?
[14:46] <pitti> oh, I see what you mean (I didn't try looking at the debci page)
[14:46] <infinity> http://autopkgtest.ubuntu.com/packages/p/pbuilder/yakkety/amd64
[14:46]  * pitti will fix that
[14:53] <infinity> pitti: Ugh.  I think it's Steve's sysvinit.
[14:53] <pitti> infinity: I wonder why that SRU was released already
[14:53] <pitti> given that it had a regression
[14:53] <infinity> pitti: It wasn't, it was copied from xenial-proposed to yakkety-proposed.
[14:53] <pitti> oh, *phew*
[14:54] <pitti> right, only the floating task is closed
[14:54] <pitti> so, similar to bug 1573240 I figure (no debootstrap.log in the output)
[14:54] <infinity> pitti: Seems he subtly perturbed dependencies just enough to get util-linux configuring before systemd, which it seems to be not fond of.
[14:55] <infinity> slangasek: ^
[14:55] <pitti> http://autopkgtest.ubuntu.com/packages/p/pbuilder/ (and others) are yaky now (some might still be missing, html generation isn't done yet)
[14:57]  * pitti adds Launchpad apport retracer configs for yak
[15:10] <slangasek> infinity: right, I didn't count on it being copied forward to yakkety so soon; do you want to revert that in yakkety?
[15:13] <infinity> slangasek: Yeah.  Want to revert properly with a higher version?
[15:13] <slangasek> infinity: sorry, I was suggesting you go ahead and do the revert, as it'll be about 3 hours before I can get to it
[15:13] <infinity> Oh.  Kay.
[15:16] <infinity> slangasek: Done.
[15:40] <balloons> can juju-core be accepted?
[16:28] <jderose> anyone know why `update-manger` isn't offering the upgrade to 16.04 for 14.04 users? on 14.04 systems, even `update-manager -d` seems to no longer offer the upgrade to 16.04
[16:29] <teward> jderose: i know the 'standard' way for 14.04 to 16.04 without -d is not available until .1
[16:29] <jderose> teward: okay, thanks. this is a new scenario, isn't it? i don't think i've ever encountered this before
[16:30] <teward> I dunno, I've never went from LTS -> LTS until at least .1
[16:30] <teward> :P
[16:47] <hggdh> jderose: it is not new
[16:48] <jderose> hggdh: do you know when this started happening? in the grand schema of things, it is new, because there was a time when Ubuntu didn't do LTS point releases :P
[16:49] <hggdh> jderose: I do not remember from the top of my head; it already happened on 14.04, but I am unsure if it also happened on 12.04
[16:49] <jderose> hggdh: okay, maybe it started happening with 14.04 then
[16:49] <hggdh> i think it did, though...
[16:51] <hggdh> reasoning is this allows for major issues to be found before production upgrades are started (I, for one, never upgraded to a new version of a distro (or OS) before at *least* a few months
[16:51] <hggdh> (I mean on production servers)
[16:51] <cjwatson> -d should work though.
[16:51] <hggdh> yes
[16:52] <cjwatson> both http://changelogs.ubuntu.com/meta-release-development and http://changelogs.ubuntu.com/meta-release-lts-development list xenial
[17:02] <wxl> um, yakkety dailies are all set up on the tracker but it seems like the cronjobs might not have been turned back on
[17:12] <Laney> It's the first day, the archive isn't properly open - be patient. :)
[17:13] <wxl> patience?! i have isos that need updated!!!!! they're probably at least 0.0000001% different by now!
[17:13] <wxl> ;)
[17:13] <wxl> just making sure things get done, seriously. i know it's easy to forget things after release week phew
[17:13] <cjwatson> please don't, we have a checklist
[17:13] <cjwatson> asking about nearly the last thing on it isn't helpful :)
[17:14]  * wxl hangs his head in shame
[17:18] <jderose> cjwatson: perhaps it's issues with my internet, but today `update-manager -d` isn't working for me for 14.04 to 16.04 upgrades. which is fine, just a bit unexpected :)
[17:22]  * apw installs a 14.04 install to confirm/deny that
[17:23] <jderose> apw: thank you very much! maybe it's just an issue with me, mirrors i'm using, etc
[17:23] <doko> pitti, are the s390x autopkg testers running?
[17:30] <doko> xnox, do you want to do the boost transition before opening the archive for general uploads?
[17:40] <infinity> doko: I think the intention was to get boost1.60 (and defaults) in as well as libpng16 (and the libpng12 that disables the -dev), and then open the flood gates to do both transitions.
[17:40] <infinity> doko: Also, I'm going to be sleeping and then on a plane, so I trust you, cjwatson, pitti, etc have this all in hand and we'll be ready to release when I get home. :)
[17:41] <doko> infinity, ok. but xnox didn't answer my question if boost1.60 is ready for GCC 6, and if we need another boost transition this cycle
[17:41] <infinity> doko: Sure, if he gives you crap answers, don't wait on him. :P
[17:41]  * doko looks at icu ...
[17:52] <apw> jderose, ok mine insisted i updated my 14.04, but once it was shiney and updated "update-manager -d" is offering me an update to 16.04
[17:53] <jderose> apw: so it did take `update-manager -d`, not just running the update manager normally? i'll try again shortly, currently i'm doing a 15.10-->16.04 test
[17:54] <apw> jderose, yes the -d is needed to let it see the update before .1
[17:54] <jderose> apw: okay, thanks! i'll try `update-manager -d` again shortly
[17:55] <apw> jderose, if it says you have updates to the local version it won't consider an upgrade between them
[17:57] <jderose> apw: hmm, strange. did you have any such local updates that you think should have triggered this behavior?
[17:58] <apw> jderose, no just if you have any kinds of update it will always only consider applying those, once the system at its current version is up-to-date, then and only then it will offer you updates to new releases
[17:59] <jderose> hmm, i did do an `apt-get update && apt-get dist-upgrade` first
[18:25] <slangasek> infinity: are you happy taking a command-not-found SRU without a bug + verification (since it's a flat db update)?
[18:29] <doko> slangasek, he's on a plane
[18:30] <infinity> Not yet.  Sleeping currently.
[18:30] <infinity> In theory.
[18:31] <infinity> slangasek: Would pay big money for it to be done in the same locale as the previous update.
[18:31] <infinity> To avoid sorting diffs like:
[18:31] <infinity> -i386|main|qemu-system-ppc|qemu-system-ppcemb,qemu-system-ppc,qemu-system-ppc64le,qemu-system-ppc64
[18:31] <infinity> +i386|main|qemu-system-ppc|qemu-system-ppcemb,qemu-system-ppc64,qemu-system-ppc64le,qemu-system-ppc
[18:33] <infinity> Man, I was sure I saw mvo update this fairly recently too.  That's a lot of churn.
[18:45] <jderose> infinity: you should sleep in practice, i expect you've earned it :D
[18:52] <slangasek> infinity: "in the same locale" wut
[18:52] <slangasek> so... I should set a German locale to run the update?
[18:53] <slangasek> infinity: oh.  for that matter, the source of the new data is an scp from mvo's homedir, so... kinda not something changing my local locale will fix
[18:59] <infinity> slangasek: Oh, it's not mangled on your machine after fetch?  That's even weirder.
[19:00] <infinity> slangasek: Cause those flips (ppc for ppc64, _ for -) are classic locale sort mismatches.  Oh well.  I'll tell him to fix his crap to be consistent another time. :P
[19:01] <infinity> slangasek: Looks like most of the updates were legit anyway, I only spotted the occasional sort inversion.
[19:01] <infinity> slangasek: So, to answer your question, I don't think it needs a bug, but it does need either a human to read it, or a linter that can tell me it's at least not broken.
[19:02] <infinity> (THough, perhaps c-n-f itself acts as a full linter...)
[19:04] <slangasek> infinity: it spits out a diff as part of the updater script, which I reviewed and give my blessing to.  There were various last-minute removals which looked sane, a few new commands which is what was driving me to look at this update, and a whole bunch of main->universe demotions that make everyone happy
[19:09] <infinity> slangasek: Check.  If the way c-n-f loads/parses the DB effectively also acts as a reasonable runtime check against mechanical breakage (and I suspect that's true), that all seem kosher to me.
[19:09] <infinity> s/seem/seems/
[19:10] <jderose> apw: i just tried a 14.04 to 16.04 upgrade again... Ubuntu Software Updater normally isn't prompted for the upgrade to 16.04, but `update-manager -d` is again working for me. it didn't work earlier for me, but that could have been an issue with my internet, isp caching, etc.
[19:10] <infinity> jderose: Yeah, it's not meant to without -d for another 3 months, so that sounds all correct.
[19:11] <jderose> infinity: okay, gotcha. guess i just never noticed this before :)
[19:12] <infinity> jderose: Well, it's only LTS->LTS upgrades that we delay for the extra polish (partially for the UI/UX "polish", mostly because unwinding all the weird upgrade bugs for a 2yr span can take some SRUs to get right), so maybe you just don't do that often. :P
[19:12] <infinity> I know I don't.
[19:13]  * infinity decides to wander off and get some sleep after the last 36h stretch.
[19:14]  * jderose suggests infinity get some sleep :)
[19:14] <infinity> That's the plan.
[19:14] <infinity> Some sleep and then a plane.
[19:14] <infinity> I'll catch everyone when I'm back in Canadia.
[19:17] <infinity> slangasek: FWIW (yes, really, I'm leaving), I would suggest that c-n-f probably belongs in https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases alongside tzdata, as long as we can document a "this is how you check that it's not completely busted" paragraph.
[19:17] <infinity> slangasek: Cause keeping it updated through an LTS might not be stupid either.
[19:18] <slangasek> infinity: I agree and will try to not let that fall off my stack
[19:18] <DalekSec> I'd think so for geoip-databases too. :3
[19:19] <infinity> Yeah, I manually reviewed the last geoipdb update, that wasn't fun.  Again, if there's a way to lint it, I think it belongs there too.
[19:20] <infinity> As does wireless-regdb (which has the added bonus of actually putting you in a position of potentially breaking some local laws if you *don't* keep it updated)
[19:22] <slangasek> we should tie the wireless-regdb updates to the tzdata updates, and only accept regdb updates for countries that haven't jerked us around on DST settings for the past year
[19:24] <ogra_> what if they dropped DST completely ?
[19:24] <slangasek> ogra_: as long as they did this with 6 months notice, all fine!
[19:24] <ogra_> heh
[19:25] <slangasek> instead of "oh we know DST starts next month but we decided to let the states vote on whether or not they're going to follow it this year, I hear their state assemblies are meeting in two weeks in order to vote on it"
[19:25] <ogra_> lol
[19:27] <slangasek> (for A completely hypothetical example that in no way Resembles a real thinG that Ever happeNed in a real counTry causINg us to hAve to do an emergency tzdata update)
[19:32] <infinity> slangasek: whilE i aGree that slow democratic process sucks, You may find that military dictators who just change their timezone on a whim and exPect all the computers in their country to magically fix Themselves overnight are even more annoying.
[19:32] <slangasek> :-)
[19:35] <mdeslaur> hehe
[19:56] <apw> infinity, looks like there is something wrong with adt testing on s390x, there appear to be no adt tests in progress, but s390x is still listed in-progress
[19:56] <apw> infinity, so sysvinit ain't going anywhere
[19:57] <apw> oh _now_ you refresh and it dissapears ... pththth
[20:19] <pitti> doko: running in principle yes, but they all segfault like https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/s390x/f/floodlight/20160422_142808@/log.gz in yakkety
[20:19] <pitti> but that's for Monday morning
[20:34] <xnox> doko, infinity - general uploads i don't care, before we start syncing from debian... probably yes.
[20:34] <xnox> sorry that i was out playing beach volleyball, in british down-pour rain, in a wet suit, in a sand pit =)
[20:34] <tumbleweed> sounds like xnox's life
[20:35] <xnox> hehe
[20:35] <doko> xnox, icu uploaded, will wait with any boost1.60 accept until that is built
[20:35] <doko> do you know if 1.60 is ready for GCC 6?
[20:35] <xnox> doko, nice one.
[20:35] <xnox> doko, it should be yes.
[20:36] <xnox> doko, are you default for gcc 6 already?
[20:36] <xnox> syncpackage: Error: Debian version 1.60.0+dfsg-4 has not been picked up by LP yet. Please try again later.
[20:36] <xnox> i can't sync the right boost yet
[20:38] <xnox> slangasek, doko, infinity - $ syncpackage -r yakkety boost1.60 -V 1.60.0+dfsg-4
[20:38] <xnox> when you need it.
[20:38] <doko> ta
[20:44] <doko> xnox, please add a transition tracker
[20:47] <xnox> wgrant, could I please have equivalent of primary-xenial-s390x-release.html for yakkety on http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/ ?
[20:47] <xnox> i still think i have quite a few things that I could fix.
[20:52] <xnox> ¯\_(ツ)_/¯
[21:52] <mapreri> xnox: can you also sync gdk-pixbuf while the archive is still closed?
[21:53] <xnox> mapreri, no, cannot sync cause it's missing my bug fix =)
[21:53] <xnox> needs a merge =)
[21:56] <mapreri> (message relayed.  /me feels like a homing pigeon)
[21:58] <doko> mapreri, gdk-pixbuf really needs that unfulfillable dependency fixed: = on a arch any and an arch all package
[22:00] <mapreri> doko: sorry, not sure about what are you referring to.  i was only aware of debian #819779
[22:01] <slangasek> sounds like he's describing non-binnmu-safe dependencies; which are only an issue for Debian, not Ubuntu
[22:01] <doko> $ apt-cache show libgdk-pixbuf2.0-0|grep Depends
[22:01] <doko> Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)
[22:02] <slangasek> sure
[22:02] <slangasek> not a problem in Ubuntu :)
[22:03] <mapreri> ah, yes, not a problem here.
[22:03] <mapreri> though, there is not even a bug report in debian
[22:04] <doko> filing one
[22:05] <mapreri> ta
[22:42] <xnox> that looks odd
[22:42] <xnox> doko, what are you doing?
[22:43] <xnox> ah icu, ok
[22:59] <LocutusOfBorg> I'm not sure how we are left, but first thanks for the libpng1.6 accept, and second, pretty please --> https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1573839
[23:00] <LocutusOfBorg> I already prepared around ~20 packages to upload, when the archive will be open (they are ubuntu specific packages), and I hope the auto import will do most of the job with gdk fixed
[23:00]  * LocutusOfBorg goes to sleep