[00:08] we going to wait until we got a name for y cycle before turning dailies on, i'm assuming [00:08] ? [00:09] yes [00:09] ko thx [00:24] slangasek: we have a name and it is yakkity yak [00:24] *yakkety yak* [00:24] my money was on yippee yappee yahooey [00:32] you lost your money, it always was tuples not triples [00:38] 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] doko: ^ [00:38] Also, hahahahahahaha. Yakkity (though misspelled?) yak won! [00:39] are we sure he really meant it? :) [00:39] wait [00:39] Hard to say. [00:39] yakkity yak, really? [00:39] oh please say it's true! [00:40] http://www.markshuttleworth.com/archives/1496 [00:40] oh. [00:40] yakkety. [00:40] sorry, what he says, goes. :) [00:41] we're going to get REAAAAALY sick of typing yakkety. [00:41] wxl: i haven't typed it yet, and I am *already* sick of it >.< [00:41] hahahahhaah [00:41] well time to turn dailies on then XD [00:41] infinity, which spelling are you going with? [00:42] 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] well, maybe that's the point [00:43] it's wartier XD [00:55] * tsimonq2 agrees with wxl, it's gonna be annoying after a while to type XD [00:56] https://wiki.ubuntu.com/YakketyYak [00:57] ? [00:57] * tsimonq2 creates [00:57] shouldn't that be yakkity? [00:57] hahahah [00:57] I did Xenial so it's my turn again XD [00:58] (seriously, look at the XenialXerus page) [00:58] not according to sabdfl [00:58] Wow, we even get not invented here syndrome from release names now? <3 [00:58] no I mean the wiki page [00:58] XenialXerus (last edited 2015-10-22 17:55:18 by tsimonq2) [00:58] Kamilion: http://www.markshuttleworth.com/archives/1496 [01:00] infinity: look good? https://wiki.ubuntu.com/YakketyYak [01:00] tsimonq2: don't forget https://wiki.ubuntu.com/ReleaseSchedule [01:01] * tsimonq2 gets that done [01:01] aw someone should fix up https://wiki.ubuntu.com/ReleaseSchedule/LTStoLTS for into the future [01:01] DalekSec: https://en.wikipedia.org/wiki/Yakkity_Yak [01:01] Good for it? [01:01] unless it's referring to the song? https://en.wikipedia.org/wiki/Yakety_Yak [01:01] he said yakkety [01:02] it is what it is :) [01:02] either way, it's ke or i [01:02] err [01:02] ki or e [01:02] not ke [01:02] either way it SHOULD be [01:02] but mark IS the dictator for life XD [01:02] hence the "not invented here syndrome" joke [01:02] oh i got it [01:02] can't use wayland, gotta write mir [01:02] ETC [01:02] Confirmed with sabdfl that it's yakkety, as spelled in the blog post. [01:02] hahahahhaah [01:02] https://launchpad.net/ubuntu/yakkety [01:02] ubuntu has a history of reinvention of the wheel, sort of [01:02] hahahah [01:02] * Kamilion points fingers at upstart [01:03] it can't even launch apache! [01:03] um, there's no wheel. that's unix, man. :) [01:03] * Kamilion lmfao [01:03] next you'll be telling me /usr is more than an RK-05 disk pack's worth of bytes [01:03] XD [01:04] In my day, we hand assembled binaries uphill in the snow both ways! [01:04] with a needle and a very steady hand [01:04] Alright, i'm done with the comedian act; back to seriousness [01:04] someone needs to add the point release schedule to https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule at some point [01:05] infinity: mind acking https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule as well> [01:05] we should expect the first around july, hm? [01:06] tsimonq2: Those dates all need to be Thursdays. [01:06] wxl: First point release is scheduled in LP for the 21st of July, I'll add it to the schedule soon. [01:06] thx infinity [01:07] infinity: ok adjusting [01:07] * tsimonq2 copied from Wily's [01:07] tsimonq2: wily's should be a good base indeed, just needs minor shuffling. [01:07] infinity: also ack https://wiki.ubuntu.com/ReleaseSchedule while you are at it if you could :) [01:07] slangasek: Do we have UOS dates? [01:08] May 3-5 I thought...? [01:08] Ahh, indeed, summit.ubuntu.com has the dates. [01:08] yah [01:08] I must have missed the usual email thread about it. [01:10] 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] tsimonq2: Yup, just shuffle the alpha up a week to keep it at the end of the month. [01:11] (And fix the colours) [01:11] *sigh* thank god nothing is September 1... [01:12] yep, covered :) [01:13] that also means first week in October gets bumped up to September [01:13] Yep, s'all good. [01:13] Calendars suck. [01:13] Thanks for doing the draft. [01:14] np [01:14] https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule look good? [01:14] as a suggestion, maybe put Ubuntu 16.04 somewhere by April 21, 2016 [01:15] oh lol I forgot, it's all 2015, fixing [01:15] there fixed [01:16] Heh. You didn't fix the suffixes. ;) [01:16] 23th, 22th, etc. ;) [01:16] I didn't? [01:16] * tsimonq2 looks [01:16] And Alpha1 should move to Jun30. [01:16] oh jeez [01:16] alright [01:16] Semptember 1rd is my favourite. [01:16] 1rd, yo. [01:17] hahahahahahahah [01:18] And UOS is Tue-Thu, not Mon-Thu. [01:18] Otherwise, looks good. [01:18] fixed? [01:18] and do you think it's relevant to put the release of 16.04 by April 21? [01:19] Nah. [01:19] I think it's generally taken as a given that a release happened before the release schedule. :P [01:19] 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] *schedule [01:20] *shrug* but if you don't think it's needed I won't put it XD [01:20] Current state looks good to me. Thanks. [01:20] 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] hahahahahah [01:21] need me to do that? [01:21] Nein. [01:21] alright [01:22] * tsimonq2 assumes that's no [01:22] It is. :) [01:22] :) [01:22] /o\ long day, it's _finally_ over [01:23] but still, Yakkety?! /me wonders what it's referring to... [01:24] Yaks, of course. [01:24] hahahahahahahahah [01:24] and I thought Xenial Xerus would be hard to spell/remember [01:24] :P [01:25] You might be too young to really appreciate the yakety yak, yakety sax, yakkity yak references. [01:25] But it's making some of us giggle. :) [01:25] yeah I have no idea what those are... :P [01:26] infinity: Don't talk back! [01:34] ? [01:34] ¯\_(ツ)_/¯ [01:36] tsimonq2: https://www.youtube.com/watch?v=PtTC3pGBjs4 -- educate yoself. [01:43] hahahahah === Wulf4 is now known as Wulf [01:55] infinity: has lsb_release been updated yet? [01:55] * tsimonq2 uses the devel alias [01:56] tsimonq2: The archive doesn't exist yet, so no. Patience. [01:56] This is not actually an instant process. [01:56] ohhh gotcha sorry :) [06:14] hi, can I sync libpng*? [06:19] LocutusOfBorg: Maybe. [06:22] it will end up in unapproved... and in new because of the soname change [06:22] so, lets sync and leave the decision to release team [06:23] oops unapproved, because somebody sync'd it before already [06:38] well, I opened LP: #1573415 for the old libpng-dev removal [06:38] 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] Hrm. Might have to walk to the office to update chroot tarballs. [06:42] Seems like everyone in this hotel woke up at once and started surfing porn. === smb` is now known as smb [06:43] * infinity grabs a quick shower before heading in to finish opening. [06:45] LOL [06:45] morning infinity - now the madness is over - thanks to you all :) [06:52] 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] infinity: :) [06:55] still laughing at yakkety yak :D [06:59] * infinity -> Bluefin. [08:10] 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] infinity, seems 15.04 is gone from http://releases.ubuntu.com/ .... there were snappy images in there that are still valid [08:35] ogra_: 15.04 was dropped 3 months into 15.10 this isn't a new thing ;) [08:35] ha ha [08:35] ogra_: no I'm serious [08:36] 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] *images === Loopeth is now known as Loopeth_upgradin [08:46] ogra_: I can copy the snappy ones back, gimme time. I'm multitasking a bit. [08:46] no hurry [10:25] i'm gonna have so many laughs about [10:25] yakkety security [10:25] and yakkety backports [10:25] and yakkety updates [10:25] yakports [10:29] xnox: Oh joy, a new boost. [10:29] xnox: Do we want that built before we open? [10:29] xnox: (ie: is there a defaults bump too?) [10:32] infinity, default bump in progress [10:33] infinity, i also believe this boost1.60 will fail to migrate on s390x, but we shall see. [10:33] xnox: Well, that's not ideal. [10:33] xnox: Don't really want autosync all backed up on boost. [10:34] 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] infinity, in any case i will be fixing this in debian and uploading there and syncing over, e.g. today. [10:35] cause yeah i do want to open with new boost. [10:37] xnox: Kay. [10:37] xnox: I'll accept it then, and you'd better fix it ASAFP if you break anything. [10:37] ack. [10:42] xnox: when do the +1 archives usually get created? [10:42] clivejo: A few hours ago. [10:43] oh that was fast [10:44] why do you accept new boost before we change the toolchain defaults? [10:45] doko: I can kill the builds. Do you have a new toolchain prepped? [10:46] sure, however yesterday I was told I shouldn't expect opening today ... [10:46] doko: Boost builds killed. [10:46] Yesterday we didn't have a name and you know what expectations are like there. [10:46] 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] doko: So, waiting on you before I build anything else. [10:47] ta [10:51] infinity: https://paste.debian.net/440208/ [10:52] Laney: Ta. [10:54] that boost will have dropped binaries, there are mistakes in debian/control that smr did [10:57] xnox: Well, it's cancelled anyway, so fix it. :P [11:06] doko: Patch gcc-linaro.diff does not apply (enforce with -f) [11:06] yep === rvba` is now known as rvba [11:09] 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] Yep. [11:10] I'll delete the current one so no one's tempted to retry it. [11:10] and test building debian build now, so off to buy neoprene sand socks in the mean time. [11:10] infinity, sounds good. [11:10] Done. [11:11] xnox, is this boost ready for GCC 6? [11:12] xnox: https://www.youtube.com/watch?v=A6hNXUwOHKQ these guys aren't wearing socks [11:12] xnox, also please consider building icu from experimental before doing the new boost [11:12] ur doin it rong [11:17] xnox, are you want to drop context/coroutine from arm64, i understood it was available there from boost1.59 [11:17] are you sure* [11:52] pitti: When can we have Yodeling Yam autopkgtests? [12:04] * apw shouts at network-manager ... this new version is utter pants [12:08] infinity: I like yodelling a lot better than yakkety! [12:08] pitti: Too late. [12:15] infinity: queues exist now, so britney can issue test requests [12:15] they aren't served yet, still need to build containers and yakkety cloud images [12:15] pitti: May have to reissue the batch that vim caused? [12:15] will do that in a bit, need to run out for some errands [12:15] Not sure where they went... [12:15] If anywhere. :) [12:16] into the void [12:16] yes, I'll retry all the bits on excuses.html [12:16] pitti: I assume "yakkety cloud images" are a xenial custom hack job, not you blocking on CPC, right? [12:16] infinity: correct [12:16] Check. [12:22] coq-float succeeded to build? strange [12:22] Yeah. Probably means we should have done one last give-back a week before release. Oh well. [12:23] I did [12:23] Two days before release? :) [12:23] Pretty sure that changing the strings in os-release didn't fix it. [12:23] I would hope... [12:24] there was this idea of importing libpng before everything, to avoid doing hundreds of rebuilds later, is that going to happen? :) [12:24] mapreri: After the toolchain, but before the world, yes. [12:24] it is in the queue [12:24] cool [12:28] ginggs, available empty package is not useful at all. [12:35] 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] pitti: You do _eventually_ use our images though, right? [12:37] 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] Odd_Bloke: Well, he's using your images even in the hacked case. :P [12:37] Odd_Bloke: Also, slaaaacker! I'll have Ubuntu (and flavour) ISOs building in a few minutes. [12:37] *cough* [12:38] infinity: ^_^ [12:39] 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] Odd_Bloke: Yes, that. [12:39] Odd_Bloke: yakkety is a fully-functional distro. [12:39] Odd_Bloke: I'm running it. [12:39] hm [12:39] ginggs, maybe. [12:40] i shall try that. [12:40] infinity: So hipster. [12:40] Odd_Bloke: So hip I can't see over my own pelvis. [12:46] "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] :( no libpng accepted makes me sad [12:47] * LocutusOfBorg read about the archive opening on irclogs.u.c [12:49] Though I feel like I've normally seen in on s390x, now I think about it. [12:49] LocutusOfBorg: it's not open yet? [12:52] LocutusOfBorg: Still building the initial toolchain. [12:53] infinity: Any ideas about https://launchpadlibrarian.net/255173456/buildlog_ubuntu_yakkety_amd64_cpc-development_BUILDING.txt.gz ? [12:54] infinity: ("Try waiting" is an acceptable answer :) [12:54] Odd_Bloke: You need the debootstrap in proposed. [12:54] 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] Oh, a bit more than a tiny bit, since its migration to the release pocket is blocked on pitti's autopkgtests. [12:55] So, you'd be best off copying it. [12:56] infinity, not a problem, but the issue is: I would like to have something more than just a libpng imported [12:57] LocutusOfBorg: Well, you didn't ask for anything else. :P [12:57] oh well, gcc-5 failed to upload [12:57] https://launchpadlibrarian.net/255171857/upload_9610916_log.txt [12:57] infinity, give me one sec [12:58] https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1524328 [12:58] Launchpad bug 1524328 in libpng (Ubuntu) "libpng 1.6 transition" [High,Confirmed] [12:58] doko: gcc-5 still builds gcc-6 binaries? [12:58] message #12 [12:58] (libgcc, etc) [12:58] fixed [13:00] Odd_Bloke, i'd love to spin up yakkety cloud-images in my ppa =) [13:00] LocutusOfBorg: Seems the only absolute necessity there are both the libpng sources happening before the world opens. [13:00] infinity, and gdk-pixbuf rebuilds maybe [13:00] but yes, we can retry it until it builds [13:01] the problem is gdk-pixbuf embedding somewhere a libpng broken pkgconfig, so the other tools will fail in configure [13:02] xnox: Hm? [13:03] * apw will sort out debootstrap in the stables ... [13:04] 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] Odd_Bloke, because i can give experimental yakkety images to try out to others =) [13:05] infinity: open> do you want a debhelper merge? that's traditionally on my list, can do after dealing with the yak images [13:06] xnox: Well, we can do that too... :p [13:07] pitti: If you're in the mood. [13:10] thanks for fixing boost1.60 delta <3 [13:10] aka thanks for archive reorg [13:10] :D [13:11] infinity: Am I missing an easy way to copy archive/-proposed packages in to a PPA? Should I just backportpackage it? [13:11] copy-package [13:12] --from ubuntu --from-suite whatever --to ppa:OWNER/ubuntu/NAME --to-suite whatever ... [13:12] Odd_Bloke: copy-package --from=ubuntu --from-suite=yakkety-proposed --to=ppa:username/ubuntu/ppaname --to-suite=yakkety -b debootstrap [13:27] cloudy autopkgtest (i386, amd64, ppc64el) are now yakified [13:28] building lxc containers failed during debootstrap (armhf, s390x) [13:39] infinity, Should the vagrant images have a xenial options too? http://cloud-images.ubuntu.com/vagrant/ [13:40] willcooke: Nope, those have moved in alongside the other image files. [13:41] ogra_: Your 15.04 snappy images should be back. Sorry about that. [13:41] willcooke: e.g. http://cloud-images.ubuntu.com/xenial/20160420.3/xenial-server-cloudimg-amd64-vagrant.box [13:41] 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] ogra_: Well, tell whomever cares that they're resurrected. :P [13:41] yep, doing so [13:41] Odd_Bloke, thanks. I've been told that they're "not working" - are you happy everything is as it should be? [13:42] 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] infinity, hmm, are we talking about http://releases.ubuntu.com/ ? i dont see 15.04 [13:42] Odd_Bloke, ta [13:42] (sync mirro still running ? ) [13:43] ogra_: They were never on releases, were they? I thought they were on cdimage. [13:43] ogra_: Or am I mistaken? [13:44] they were on http://releases.ubuntu.com/15.04/ [13:44] ogra_: Oh, huh. Someone had put them on releases. [13:44] ogra_: Moving again. :P [13:44] http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz was the amd64 one [13:44] yeah, crazy :) [13:44] i would prefer to kleep them in cdimage.u.c/ubuntu-snappy/ for the future [13:45] we'll see if i'll have success with that once we have actual 16.04 releases :) [13:46] ogra_: http://releases.ubuntu.com/15.04/ [13:47] perfetto ! [13:47] Odd_Bloke, I think this is it: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1573058 [13:47] Launchpad bug 1573058 in livecd-rootfs (Ubuntu) "Ubuntu 16.04 current not booting in Vagrant (gurumeditation)" [Undecided,Confirmed] [13:48] Odd_Bloke, and this is who my source is: https://twitter.com/therealmarv/status/723485477328850944 ;) [13:49] willcooke: OK, in a meeting ATM so will dig in a few minutes. :) [13:49] Odd_Bloke, nw, thanks [13:52] Step 1) Actually manage to download something from our DC [13:53] 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] ogra_: They're not, those are symlinks from the wrong names to the right ones. :P [13:54] lol [13:54] k [13:54] i only noticed they are duplicated in the MD5SUM too [13:54] Yeah, checksum-directory will sum anything with a file extension it likes. [13:55] I has to be dumb and follow links or the linking to ../pool magic would break. [13:55] s/I has/It has/ [13:56] thanks infinity, ogra_ :) [13:56] customers care about 15.04 btw :p [13:56] didrocks: Anything else I can delete for you while I'm here? :P [13:56] didrocks, which is awful ! [13:57] can we have a libpng16 transition tracking page? [13:57] LocutusOfBorg: Sure. [13:57] <3 [13:57] thanks [14:03] infinity: please do delete everything, I would be relieved! :-) [14:04] ogra_: if there was a finale ubuntu core 16.04, I would agree fully :) [14:04] didrocks, just a few months :) [14:05] * ogra_ wouldnt care so much about final ... but feature-functional would be good [14:06] like having config? :p [14:07] config ... a classic shell so you can actually build snaps ... (sicne we dont support cross building) [14:07] 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] these are the two pressing items imho ... once they are back we should really push everyone to use 16.04 [14:08] Odd_Bloke, yes [14:08] a serious one [14:08] https://launchpadlibrarian.net/254650006/virtualbox_5.0.18-dfsg-2_5.0.18-dfsg-2build1.diff.gz [14:08] look at the diff [14:09] +Description: fix https://www.virtualbox.org/ticket/15317 [14:09] upstream asked me to cherry-pick the patch [14:09] 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] infinity: Yep. ^_^ [14:10] Odd_Bloke: Shame his followers won't see that. [14:10] infinity: If only he were running Ubuntu, he would never have had this problem. [14:10] (And seems unlikely he'll mention it) [14:10] willcooke: ^ [14:10] I got a lot of bug reports about 5.0.18 without the patch and 5.0.16 [14:11] and *none* yet about the version landed in xenial [14:11] LocutusOfBorg: Yeah, I saw it when testing the Vagrant box pre-release. [14:11] LocutusOfBorg: Find a large tree to knock on. [14:11] But upgraded and it went away. [14:11] infinity, I didn't get it :) [14:11] thanks infinity [14:11] thanks Odd_Bloke for confirming the fix [14:12] I did enjoy a moment of sheer panic though, when I _did_ think it was an issue with our vagrant boxes. ;) [14:14] infinity: ^ prerequisite for merged debhelper [14:15] pitti: done [14:22] doko, infinity: ^ [14:22] infinity: yakkety autopkgtests should be fully running; next britney run will re-issue the lost test requests [14:22] pitti: Huzzah. [14:24] pitti, done [14:26] 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] Odd_Bloke, link? [14:29] LocutusOfBorg: https://twitter.com/therealmarv/with_replies <-- a couple of tweets in there; I replied to one already :) [14:31] so at the end we should thanks infinity for accepting the last minute virtualbox fix :D [14:37] Indeed. :) [14:44] infinity: fun, the pbuilder regression looks pretty much like the failure to deboostrap a yakkety container that I experienced earlier [14:45] pitti: All I see is 404s... [14:45] Oh, I guess the log links work. [14:45] 404s? [14:46] oh, I see what you mean (I didn't try looking at the debci page) [14:46] http://autopkgtest.ubuntu.com/packages/p/pbuilder/yakkety/amd64 [14:46] * pitti will fix that [14:53] pitti: Ugh. I think it's Steve's sysvinit. [14:53] infinity: I wonder why that SRU was released already [14:53] given that it had a regression [14:53] pitti: It wasn't, it was copied from xenial-proposed to yakkety-proposed. [14:53] oh, *phew* [14:54] right, only the floating task is closed [14:54] so, similar to bug 1573240 I figure (no debootstrap.log in the output) [14:54] bug 1573240 in sysvinit (Ubuntu) "package initscripts 2.88dsf-59.2ubuntu2.1 failed to install/upgrade: pre-dependency problem - not installing initscripts" [Critical,New] https://launchpad.net/bugs/1573240 [14:54] 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] slangasek: ^ [14:55] 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] 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] slangasek: Yeah. Want to revert properly with a higher version? [15:13] 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] Oh. Kay. [15:16] slangasek: Done. [15:40]