/srv/irclogs.ubuntu.com/2016/04/22/#ubuntu-release.txt

wxlwe going to wait until we got a name for y cycle before turning dailies on, i'm assuming00:08
wxl?00:08
slangasekyes00:09
wxlko thx00:09
bjfslangasek: we have a name and it is yakkity yak00:24
bjf*yakkety yak*00:24
slangasekmy money was on yippee yappee yahooey00:24
dokoyou lost your money, it always was tuples not triples00:32
infinityslangasek: 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
infinitydoko: ^00:38
infinityAlso, hahahahahahaha.  Yakkity (though misspelled?) yak won!00:38
slangasekare we sure he really meant it? :)00:39
wxlwait00:39
infinityHard to say.00:39
wxlyakkity yak, really?00:39
wxloh please say it's true!00:39
slangasekhttp://www.markshuttleworth.com/archives/149600:40
wxloh.00:40
wxlyakkety.00:40
wxlsorry, what he says, goes. :)00:40
wxlwe're going to get REAAAAALY sick of typing yakkety.00:41
tewardwxl: i haven't typed it yet, and I am *already* sick of it >.<00:41
wxlhahahahhaah00:41
wxlwell time to turn dailies on then XD00:41
bjfinfinity, which spelling are you going with?00:41
infinitybjf: 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:42
wxlwell, maybe that's the point00:43
wxlit's wartier XD00:43
* tsimonq2 agrees with wxl, it's gonna be annoying after a while to type XD00:55
wxlhttps://wiki.ubuntu.com/YakketyYak00:56
Kamilion?00:57
* tsimonq2 creates00:57
Kamilionshouldn't that be yakkity?00:57
wxlhahahah00:57
tsimonq2I did Xenial so it's my turn again XD00:57
tsimonq2(seriously, look at the XenialXerus page)00:58
wxlnot according to sabdfl00:58
KamilionWow, we even get not invented here syndrome from release names now? <300:58
tsimonq2no I mean the wiki page00:58
tsimonq2XenialXerus (last edited 2015-10-22 17:55:18 by tsimonq2)00:58
DalekSecKamilion: http://www.markshuttleworth.com/archives/149600:58
tsimonq2infinity: look good? https://wiki.ubuntu.com/YakketyYak01:00
wxltsimonq2: don't forget https://wiki.ubuntu.com/ReleaseSchedule01:00
* tsimonq2 gets that done01:01
wxlaw someone should fix up https://wiki.ubuntu.com/ReleaseSchedule/LTStoLTS for into the future01:01
KamilionDalekSec: https://en.wikipedia.org/wiki/Yakkity_Yak01:01
DalekSecGood for it?01:01
Kamilionunless it's referring to the song? https://en.wikipedia.org/wiki/Yakety_Yak01:01
wxlhe said yakkety01:01
wxlit is what it is :)01:02
Kamilioneither way, it's ke or i01:02
Kamilionerr01:02
Kamilionki or e01:02
Kamilionnot ke01:02
wxleither way it SHOULD be01:02
wxlbut mark IS the dictator for life XD01:02
Kamilionhence the "not invented here syndrome" joke01:02
wxloh i got it01:02
Kamilioncan't use wayland, gotta write mir01:02
KamilionETC01:02
infinityConfirmed with sabdfl that it's yakkety, as spelled in the blog post.01:02
wxlhahahahhaah01:02
infinityhttps://launchpad.net/ubuntu/yakkety01:02
Kamilionubuntu has a history of reinvention of the wheel, sort of01:02
wxlhahahah01:02
* Kamilion points fingers at upstart01:02
Kamilion<joke> it can't even launch apache! </joke>01:03
wxlum, there's no wheel. that's unix, man. :)01:03
* Kamilion lmfao01:03
Kamilionnext you'll be telling me /usr is more than an RK-05 disk pack's worth of bytes01:03
wxlXD01:03
KamilionIn my day, we hand assembled binaries uphill in the snow both ways!01:04
Kamilionwith a needle and a very steady hand01:04
KamilionAlright, i'm done with the comedian act; back to seriousness01:04
wxlsomeone needs to add the point release schedule to https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule at some point01:04
tsimonq2infinity: mind acking https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule as well>01:05
wxlwe should expect the first around july, hm?01:05
infinitytsimonq2: Those dates all need to be Thursdays.01:06
infinitywxl: First point release is scheduled in LP for the 21st of July, I'll add it to the schedule soon.01:06
wxlthx infinity01:06
tsimonq2infinity: ok adjusting01:07
* tsimonq2 copied from Wily's01:07
infinitytsimonq2: wily's should be a good base indeed, just needs minor shuffling.01:07
tsimonq2infinity: also ack https://wiki.ubuntu.com/ReleaseSchedule while you are at it if you could :)01:07
infinityslangasek: Do we have UOS dates?01:07
tsimonq2May 3-5 I thought...?01:08
infinityAhh, indeed, summit.ubuntu.com has the dates.01:08
slangasekyah01:08
infinityI must have missed the usual email thread about it.01:08
tsimonq2infinity: FWIW we have an extra week in June subtracted from July...same amount of weeks but I'd thought I would mention it01:10
infinitytsimonq2: 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:11
tsimonq2yep, covered :)01:12
tsimonq2that also means first week in October gets bumped up to September01:13
infinityYep, s'all good.01:13
infinityCalendars suck.01:13
infinityThanks for doing the draft.01:13
tsimonq2np01:14
tsimonq2https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule look good?01:14
tsimonq2as a suggestion, maybe put Ubuntu 16.04 somewhere by April 21, 201601:14
tsimonq2oh lol I forgot, it's all 2015, fixing01:15
tsimonq2there fixed01:15
infinityHeh.  You didn't fix the suffixes. ;)01:16
infinity23th, 22th, etc. ;)01:16
tsimonq2I didn't?01:16
* tsimonq2 looks01:16
infinityAnd Alpha1 should move to Jun30.01:16
tsimonq2oh jeez01:16
tsimonq2alright01:16
infinitySemptember 1rd is my favourite.01:16
infinity1rd, yo.01:16
tsimonq2hahahahahahahah01:17
infinityAnd UOS is Tue-Thu, not Mon-Thu.01:18
infinityOtherwise, looks good.01:18
tsimonq2fixed?01:18
tsimonq2and do you think it's relevant to put the release of 16.04 by April 21?01:18
infinityNah.01:19
infinityI think it's generally taken as a given that a release happened before the release schedule. :P01:19
tsimonq2hey, the first time I read the release scedule, I was checking the dates going, "OK, what?!? who screwed up the schedule?!?" XD01:19
tsimonq2*schedule01:19
tsimonq2*shrug* but if you don't think it's needed I won't put it XD01:20
infinityCurrent state looks good to me.  Thanks.01:20
infinityJust 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:20
tsimonq2hahahahahah01:21
tsimonq2need me to do that?01:21
infinityNein.01:21
tsimonq2alright01:21
* tsimonq2 assumes that's no01:22
infinityIt is. :)01:22
tsimonq2:)01:22
tsimonq2 /o\ long day, it's _finally_ over01:22
tsimonq2but still, Yakkety?! /me wonders what it's referring to...01:23
infinityYaks, of course.01:24
tsimonq2hahahahahahahahah01:24
tsimonq2and I thought Xenial Xerus would be hard to spell/remember01:24
tsimonq2:P01:24
infinityYou might be too young to really appreciate the yakety yak, yakety sax, yakkity yak references.01:25
infinityBut it's making some of us giggle. :)01:25
tsimonq2yeah I have no idea what those are... :P01:25
DalekSecinfinity: Don't talk back!01:26
tsimonq2?01:34
tsimonq2¯\_(ツ)_/¯01:34
infinitytsimonq2: https://www.youtube.com/watch?v=PtTC3pGBjs4 -- educate yoself.01:36
tsimonq2hahahahah01:43
=== Wulf4 is now known as Wulf
tsimonq2infinity: has lsb_release been updated yet?01:55
* tsimonq2 uses the devel alias01:55
infinitytsimonq2: The archive doesn't exist yet, so no.  Patience.01:56
infinityThis is not actually an instant process.01:56
tsimonq2ohhh gotcha sorry :)01:56
LocutusOfBorghi, can I sync libpng*?06:14
infinityLocutusOfBorg: Maybe.06:19
LocutusOfBorgit will end up in unapproved... and in new because of the soname change06:22
LocutusOfBorgso, lets sync and leave the decision to release team06:22
LocutusOfBorgoops unapproved, because somebody sync'd it before already06:23
LocutusOfBorgwell, I opened LP: #1573415 for the old libpng-dev removal06:38
ubot5`Launchpad bug 1573415 in libpng (Ubuntu) "please merge libpng from debian" [Undecided,New] https://launchpad.net/bugs/157341506:38
* LocutusOfBorg thinks about a transition tracker06:39
* flocculant lols at yakketyyak06:40
infinityHrm.  Might have to walk to the office to update chroot tarballs.06:42
infinitySeems like everyone in this hotel woke up at once and started surfing porn.06:42
=== smb` is now known as smb
* infinity grabs a quick shower before heading in to finish opening.06:43
LocutusOfBorgLOL06:45
flocculantmorning infinity - now the madness is over - thanks to you all :)06:45
infinityflocculant: 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:52
flocculantinfinity: :)06:54
flocculantstill laughing at yakkety yak :D06:55
* infinity -> Bluefin.06:59
infinitydoko: Did you have any pre-opening toolchain bits for 16.10, or shall we just roll into it once the checklist is done?08:10
ogra_infinity, seems 15.04 is gone from http://releases.ubuntu.com/ .... there were snappy images in there that are still valid08:32
davmor2ogra_: 15.04 was dropped 3 months into 15.10 this isn't a new thing ;)08:35
ogra_ha ha08:35
davmor2ogra_: no I'm serious08:35
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_*images08:36
=== Loopeth is now known as Loopeth_upgradin
infinityogra_: I can copy the snappy ones back, gimme time.  I'm multitasking a bit.08:46
ogra_no hurry08:46
xnoxi'm gonna have so many laughs about10:25
xnoxyakkety security10:25
xnoxand yakkety backports10:25
xnoxand yakkety updates10:25
Laneyyakports10:25
infinityxnox: Oh joy, a new boost.10:29
infinityxnox: Do we want that built before we open?10:29
infinityxnox: (ie: is there a defaults bump too?)10:29
xnoxinfinity, default bump in progress10:32
xnoxinfinity, i also believe this boost1.60 will fail to migrate on s390x, but we shall see.10:33
infinityxnox: Well, that's not ideal.10:33
infinityxnox: Don't really want autosync all backed up on boost.10:33
xnoxinfinity, well i'm trying to sort out if britney is lying in debian, or there really is something fishy about s390x in debian/rules10:34
xnoxinfinity, in any case i will be fixing this in debian and uploading there and syncing over, e.g. today.10:35
xnoxcause yeah i do want to open with new boost.10:35
infinityxnox: Kay.10:37
infinityxnox: I'll accept it then, and you'd better fix it ASAFP if you break anything.10:37
xnoxack.10:37
clivejoxnox: when do the +1 archives usually get created?10:42
infinityclivejo: A few hours ago.10:42
clivejooh that was fast10:43
dokowhy do you accept new boost before we change the toolchain defaults?10:44
infinitydoko: I can kill the builds.  Do you have a new toolchain prepped?10:45
dokosure, however yesterday I was told I shouldn't expect opening today ...10:46
infinitydoko: Boost builds killed.10:46
cjwatsonYesterday we didn't have a name and you know what expectations are like there.10:46
infinitydoko: I asked earlier this morning if you had toolchain bits, I guess you slept in (like most of us should have done).10:46
infinitydoko: So, waiting on you before I build anything else.10:46
dokota10:47
Laneyinfinity: https://paste.debian.net/440208/10:51
infinityLaney: Ta.10:52
xnoxthat boost will have dropped binaries, there are mistakes in debian/control that smr did10:54
infinityxnox: Well, it's cancelled anyway, so fix it. :P10:57
infinitydoko: Patch gcc-linaro.diff does not apply (enforce with -f)11:06
dokoyep11:06
=== rvba` is now known as rvba
xnoxnew 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:09
infinityYep.11:10
infinityI'll delete the current one so no one's tempted to retry it.11:10
xnoxand test building debian build now, so off to buy neoprene sand socks in the mean time.11:10
xnoxinfinity, sounds good.11:10
infinityDone.11:10
dokoxnox, is this boost ready for GCC 6?11:11
Laneyxnox: https://www.youtube.com/watch?v=A6hNXUwOHKQ these guys aren't wearing socks11:12
dokoxnox, also please consider building icu from experimental before doing the new boost11:12
Laneyur doin it rong11:12
ginggsxnox, are you want to drop context/coroutine from arm64, i understood it was available there from boost1.5911:17
ginggsare you sure*11:17
infinitypitti: When can we have Yodeling Yam autopkgtests?11:52
* apw shouts at network-manager ... this new version is utter pants12:04
pittiinfinity: I like yodelling a lot better than yakkety!12:08
infinitypitti: Too late.12:08
pittiinfinity: queues exist now, so britney can issue test requests12:15
pittithey aren't served yet, still need to build containers and yakkety cloud images12:15
infinitypitti: May have to reissue the batch that vim caused?12:15
pittiwill do that in a bit, need to run out for some errands12:15
infinityNot sure where they went...12:15
infinityIf anywhere. :)12:15
pittiinto the void12:16
pittiyes, I'll retry all the bits on excuses.html12:16
infinitypitti: I assume "yakkety cloud images" are a xenial custom hack job, not you blocking on CPC, right?12:16
pittiinfinity: correct12:16
infinityCheck.12:16
dokocoq-float succeeded to build? strange12:22
infinityYeah.  Probably means we should have done one last give-back a week before release.  Oh well.12:22
dokoI did12:23
infinityTwo days before release? :)12:23
infinityPretty sure that changing the strings in os-release didn't fix it.12:23
infinityI would hope...12:23
maprerithere was this idea of importing libpng before everything, to avoid doing hundreds of rebuilds later, is that going to happen? :)12:24
infinitymapreri: After the toolchain, but before the world, yes.12:24
apwit is in the queue12:24
maprericool12:24
xnoxginggs, available empty package is not useful at all.12:28
ginggsxnox: 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 packaging12:35
Odd_Blokepitti: You do _eventually_ use our images though, right?12:36
Odd_Blokepitti: (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
infinityOdd_Bloke: Well, he's using your images even in the hacked case. :P12:37
infinityOdd_Bloke: Also, slaaaacker!  I'll have Ubuntu (and flavour) ISOs building in a few minutes.12:37
infinity*cough*12:37
Odd_Blokeinfinity: ^_^12:38
Odd_BlokeI 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
infinityOdd_Bloke: Yes, that.12:39
infinityOdd_Bloke: yakkety is a fully-functional distro.12:39
infinityOdd_Bloke: I'm running it.12:39
xnoxhm12:39
xnoxginggs, maybe.12:39
xnoxi shall try that.12:40
Odd_Blokeinfinity: So hipster.12:40
infinityOdd_Bloke: So hip I can't see over my own pelvis.12:40
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 it12:46
LocutusOfBorg:( no libpng accepted makes me sad12:47
* LocutusOfBorg read about the archive opening on irclogs.u.c12:47
Odd_BlokeThough I feel like I've normally seen in on s390x, now I think about it.12:49
mapreriLocutusOfBorg: it's not open yet?12:49
infinityLocutusOfBorg: Still building the initial toolchain.12:52
Odd_Blokeinfinity: Any ideas about https://launchpadlibrarian.net/255173456/buildlog_ubuntu_yakkety_amd64_cpc-development_BUILDING.txt.gz ?12:53
Odd_Blokeinfinity: ("Try waiting" is an acceptable answer :)12:54
infinityOdd_Bloke: You need the debootstrap in proposed.12:54
infinityOdd_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:54
infinityOh, a bit more than a tiny bit, since its migration to the release pocket is blocked on pitti's autopkgtests.12:55
infinitySo, you'd be best off copying it.12:55
LocutusOfBorginfinity, not a problem, but the issue is: I would like to have something more than just a libpng imported12:56
infinityLocutusOfBorg: Well, you didn't ask for anything else. :P12:57
LocutusOfBorgoh well, gcc-5 failed to upload12:57
LocutusOfBorghttps://launchpadlibrarian.net/255171857/upload_9610916_log.txt12:57
LocutusOfBorginfinity, give me one sec12:57
LocutusOfBorghttps://bugs.launchpad.net/ubuntu/+source/libpng/+bug/152432812:58
ubot5`Launchpad bug 1524328 in libpng (Ubuntu) "libpng 1.6 transition" [High,Confirmed]12:58
infinitydoko: gcc-5 still builds gcc-6 binaries?12:58
LocutusOfBorgmessage #1212:58
infinity(libgcc, etc)12:58
dokofixed12:58
xnoxOdd_Bloke, i'd love to spin up yakkety cloud-images in my ppa =)13:00
infinityLocutusOfBorg: Seems the only absolute necessity there are both the libpng sources happening before the world opens.13:00
LocutusOfBorginfinity, and gdk-pixbuf rebuilds maybe13:00
LocutusOfBorgbut yes, we can retry it until it builds13:00
LocutusOfBorgthe problem is gdk-pixbuf embedding somewhere a libpng broken pkgconfig, so the other tools will fail in configure13:01
Odd_Blokexnox: Hm?13:02
* apw will sort out debootstrap in the stables ...13:03
pittiOdd_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->xenial13:04
xnoxOdd_Bloke, because i can give experimental yakkety images to try out to others =)13:05
pittiinfinity: open> do you want a debhelper merge? that's traditionally on my list, can do after dealing with the yak images13:05
Odd_Blokexnox: Well, we can do that too... :p13:06
infinitypitti: If you're in the mood.13:07
LocutusOfBorgthanks for fixing boost1.60 delta <313:10
LocutusOfBorgaka thanks for archive reorg13:10
LocutusOfBorg:D13:10
Odd_Blokeinfinity: Am I missing an easy way to copy archive/-proposed packages in to a PPA?  Should I just backportpackage it?13:11
cjwatsoncopy-package13:11
cjwatson--from ubuntu --from-suite whatever --to ppa:OWNER/ubuntu/NAME --to-suite whatever ...13:12
infinityOdd_Bloke: copy-package --from=ubuntu --from-suite=yakkety-proposed --to=ppa:username/ubuntu/ppaname --to-suite=yakkety -b debootstrap13:12
pitticloudy autopkgtest (i386, amd64, ppc64el) are now yakified13:27
pittibuilding lxc containers failed during debootstrap (armhf, s390x)13:28
willcookeinfinity, Should the vagrant images have a xenial options too?  http://cloud-images.ubuntu.com/vagrant/13:39
Odd_Blokewillcooke: Nope, those have moved in alongside the other image files.13:40
infinityogra_: Your 15.04 snappy images should be back.  Sorry about that.13:41
Odd_Blokewillcooke: e.g. http://cloud-images.ubuntu.com/xenial/20160420.3/xenial-server-cloudimg-amd64-vagrant.box13: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
infinityogra_: Well, tell whomever cares that they're resurrected. :P13:41
ogra_yep, doing so13:41
willcookeOdd_Bloke, thanks.  I've been told that they're "not working" - are you happy everything is as it should be?13:41
Odd_Blokewillcooke: 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.0413:42
willcookeOdd_Bloke, ta13:42
ogra_(sync mirro still running ? )13:42
infinityogra_: They were never on releases, were they?  I thought they were on cdimage.13:43
infinityogra_: Or am I mistaken?13:43
ogra_they were on http://releases.ubuntu.com/15.04/13:44
infinityogra_: Oh, huh.  Someone had put them on releases.13:44
infinityogra_: Moving again. :P13:44
ogra_http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz was the amd64 one13:44
ogra_yeah, crazy :)13:44
ogra_i would prefer to kleep them in cdimage.u.c/ubuntu-snappy/ for the future13:44
ogra_we'll see if i'll have success with that once we have actual 16.04 releases :)13:45
infinityogra_: http://releases.ubuntu.com/15.04/13:46
ogra_perfetto !13:47
willcookeOdd_Bloke, I think this is it:  https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/157305813:47
ubot5`Launchpad bug 1573058 in livecd-rootfs (Ubuntu) "Ubuntu 16.04 current not booting in Vagrant (gurumeditation)" [Undecided,Confirmed]13:47
willcookeOdd_Bloke, and this is who my source is:  https://twitter.com/therealmarv/status/723485477328850944 ;)13:48
Odd_Blokewillcooke: OK, in a meeting ATM so will dig in a few minutes. :)13:49
willcookeOdd_Bloke, nw, thanks13:49
Odd_BlokeStep 1) Actually manage to download something from our DC13:52
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:53
infinityogra_: They're not, those are symlinks from the wrong names to the right ones. :P13:54
ogra_lol13:54
ogra_k13:54
ogra_i only noticed they are duplicated in the MD5SUM too13:54
infinityYeah, checksum-directory will sum anything with a file extension it likes.13:54
infinityI has to be dumb and follow links or the linking to ../pool magic would break.13:55
infinitys/I has/It has/13:55
didrocksthanks infinity, ogra_ :)13:56
didrockscustomers care about 15.04 btw :p13:56
infinitydidrocks: Anything else I can delete for you while I'm here? :P13:56
ogra_didrocks, which is awful !13:56
LocutusOfBorgcan we have a libpng16 transition tracking page?13:57
infinityLocutusOfBorg: Sure.13:57
LocutusOfBorg<313:57
LocutusOfBorgthanks13:57
didrocksinfinity: please do delete everything, I would be relieved! :-)14:03
didrocksogra_: if there was a finale ubuntu core 16.04, I would agree fully :)14:04
ogra_didrocks, just a few months :)14:04
* ogra_ wouldnt care so much about final ... but feature-functional would be good14:05
didrockslike having config? :p14:06
ogra_config ... a classic shell so you can actually build snaps ... (sicne we dont support cross building)14:07
Odd_BlokeLocutusOfBorg: 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:07
ogra_these are the two pressing items imho ... once  they are back we should really push everyone to use 16.0414:08
LocutusOfBorgOdd_Bloke, yes14:08
LocutusOfBorga serious one14:08
LocutusOfBorghttps://launchpadlibrarian.net/254650006/virtualbox_5.0.18-dfsg-2_5.0.18-dfsg-2build1.diff.gz14:08
LocutusOfBorglook at the diff14:08
LocutusOfBorg+Description: fix https://www.virtualbox.org/ticket/1531714:09
LocutusOfBorgupstream asked me to cherry-pick the patch14:09
infinityOdd_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. :P14:09
Odd_Blokeinfinity: Yep. ^_^14:10
infinityOdd_Bloke: Shame his followers won't see that.14:10
Odd_Blokeinfinity: 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
infinitywillcooke: ^14:10
LocutusOfBorgI got a lot of bug reports about 5.0.18 without the patch and 5.0.1614:10
LocutusOfBorgand *none* yet about the version landed in xenial14:11
Odd_BlokeLocutusOfBorg: Yeah, I saw it when testing the Vagrant box pre-release.14:11
infinityLocutusOfBorg: Find a large tree to knock on.14:11
Odd_BlokeBut upgraded and it went away.14:11
LocutusOfBorginfinity, I didn't get it :)14:11
willcookethanks infinity14:11
LocutusOfBorgthanks Odd_Bloke for confirming the fix14:11
Odd_BlokeI did enjoy a moment of sheer panic though, when I _did_ think it was an issue with our vagrant boxes. ;)14:12
pittiinfinity: ^ prerequisite for merged debhelper14:14
dokopitti: done14:15
pittidoko, infinity: ^14:22
pittiinfinity: yakkety autopkgtests should be fully running; next britney run will re-issue the lost test requests14:22
infinitypitti: Huzzah.14:22
dokopitti, done14:24
Odd_Blokeinfinity: Luckily, he only posted about it in replies, so only people who follow the people he was replying to will see it. :)14:26
LocutusOfBorgOdd_Bloke, link?14:28
Odd_BlokeLocutusOfBorg: https://twitter.com/therealmarv/with_replies <-- a couple of tweets in there; I replied to one already :)14:29
LocutusOfBorgso at the end we should thanks infinity for accepting the last minute virtualbox fix :D14:31
Odd_BlokeIndeed. :)14:37
pittiinfinity: fun, the pbuilder regression looks pretty much like the failure to deboostrap a yakkety container that I experienced earlier14:44
infinitypitti: All I see is 404s...14:45
infinityOh, I guess the log links work.14:45
pitti404s?14:45
pittioh, I see what you mean (I didn't try looking at the debci page)14:46
infinityhttp://autopkgtest.ubuntu.com/packages/p/pbuilder/yakkety/amd6414:46
* pitti will fix that14:46
infinitypitti: Ugh.  I think it's Steve's sysvinit.14:53
pittiinfinity: I wonder why that SRU was released already14:53
pittigiven that it had a regression14:53
infinitypitti: It wasn't, it was copied from xenial-proposed to yakkety-proposed.14:53
pittioh, *phew*14:53
pittiright, only the floating task is closed14:54
pittiso, similar to bug 1573240 I figure (no debootstrap.log in the output)14:54
ubot5bug 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/157324014:54
infinitypitti: Seems he subtly perturbed dependencies just enough to get util-linux configuring before systemd, which it seems to be not fond of.14:54
infinityslangasek: ^14:55
pittihttp://autopkgtest.ubuntu.com/packages/p/pbuilder/ (and others) are yaky now (some might still be missing, html generation isn't done yet)14:55
* pitti adds Launchpad apport retracer configs for yak14:57
slangasekinfinity: right, I didn't count on it being copied forward to yakkety so soon; do you want to revert that in yakkety?15:10
infinityslangasek: Yeah.  Want to revert properly with a higher version?15:13
slangasekinfinity: sorry, I was suggesting you go ahead and do the revert, as it'll be about 3 hours before I can get to it15:13
infinityOh.  Kay.15:13
infinityslangasek: Done.15:16
balloonscan juju-core be accepted?15:40
=== nodoubleg is now known as nodoubleg-lunch
jderoseanyone 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.0416:28
tewardjderose: i know the 'standard' way for 14.04 to 16.04 without -d is not available until .116:29
jderoseteward: okay, thanks. this is a new scenario, isn't it? i don't think i've ever encountered this before16:29
tewardI dunno, I've never went from LTS -> LTS until at least .116:30
teward:P16:30
hggdhjderose: it is not new16:47
jderosehggdh: 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 :P16:48
hggdhjderose: 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.0416:49
jderosehggdh: okay, maybe it started happening with 14.04 then16:49
hggdhi think it did, though...16:49
hggdhreasoning 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 months16:51
hggdh(I mean on production servers)16:51
cjwatson-d should work though.16:51
hggdhyes16:51
cjwatsonboth http://changelogs.ubuntu.com/meta-release-development and http://changelogs.ubuntu.com/meta-release-lts-development list xenial16:52
wxlum, yakkety dailies are all set up on the tracker but it seems like the cronjobs might not have been turned back on17:02
=== nodoubleg-lunch is now known as nodoubleg
LaneyIt's the first day, the archive isn't properly open - be patient. :)17:12
wxlpatience?! i have isos that need updated!!!!! they're probably at least 0.0000001% different by now!17:13
wxl;)17:13
wxljust making sure things get done, seriously. i know it's easy to forget things after release week phew17:13
cjwatsonplease don't, we have a checklist17:13
cjwatsonasking about nearly the last thing on it isn't helpful :)17:13
* wxl hangs his head in shame17:14
jderosecjwatson: 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:18
* apw installs a 14.04 install to confirm/deny that17:22
jderoseapw: thank you very much! maybe it's just an issue with me, mirrors i'm using, etc17:23
dokopitti, are the s390x autopkg testers running?17:23
dokoxnox, do you want to do the boost transition before opening the archive for general uploads?17:30
infinitydoko: 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
infinitydoko: 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:40
dokoinfinity, ok. but xnox didn't answer my question if boost1.60 is ready for GCC 6, and if we need another boost transition this cycle17:41
infinitydoko: Sure, if he gives you crap answers, don't wait on him. :P17:41
* doko looks at icu ...17:41
apwjderose, 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.0417:52
jderoseapw: 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 test17:53
apwjderose, yes the -d is needed to let it see the update before .117:54
jderoseapw: okay, thanks! i'll try `update-manager -d` again shortly17:54
apwjderose, if it says you have updates to the local version it won't consider an upgrade between them17:55
jderoseapw: hmm, strange. did you have any such local updates that you think should have triggered this behavior?17:57
apwjderose, 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 releases17:58
jderosehmm, i did do an `apt-get update && apt-get dist-upgrade` first17:59
slangasekinfinity: are you happy taking a command-not-found SRU without a bug + verification (since it's a flat db update)?18:25
dokoslangasek, he's on a plane18:29
infinityNot yet.  Sleeping currently.18:30
infinityIn theory.18:30
infinityslangasek: Would pay big money for it to be done in the same locale as the previous update.18:31
infinityTo avoid sorting diffs like:18:31
infinity-i386|main|qemu-system-ppc|qemu-system-ppcemb,qemu-system-ppc,qemu-system-ppc64le,qemu-system-ppc6418:31
infinity+i386|main|qemu-system-ppc|qemu-system-ppcemb,qemu-system-ppc64,qemu-system-ppc64le,qemu-system-ppc18:31
infinityMan, I was sure I saw mvo update this fairly recently too.  That's a lot of churn.18:33
jderoseinfinity: you should sleep in practice, i expect you've earned it :D18:45
slangasekinfinity: "in the same locale" wut18:52
slangasekso... I should set a German locale to run the update?18:52
slangasekinfinity: 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 fix18:53
=== tedg_ is now known as tedg
infinityslangasek: Oh, it's not mangled on your machine after fetch?  That's even weirder.18:59
infinityslangasek: 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. :P19:00
infinityslangasek: Looks like most of the updates were legit anyway, I only spotted the occasional sort inversion.19:01
infinityslangasek: 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:01
infinity(THough, perhaps c-n-f itself acts as a full linter...)19:02
slangasekinfinity: 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 happy19:04
infinityslangasek: 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
infinitys/seem/seems/19:09
jderoseapw: 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
infinityjderose: Yeah, it's not meant to without -d for another 3 months, so that sounds all correct.19:10
jderoseinfinity: okay, gotcha. guess i just never noticed this before :)19:11
infinityjderose: 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. :P19:12
infinityI know I don't.19:12
* infinity decides to wander off and get some sleep after the last 36h stretch.19:13
* jderose suggests infinity get some sleep :)19:14
infinityThat's the plan.19:14
infinitySome sleep and then a plane.19:14
infinityI'll catch everyone when I'm back in Canadia.19:14
infinityslangasek: 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
infinityslangasek: Cause keeping it updated through an LTS might not be stupid either.19:17
slangasekinfinity: I agree and will try to not let that fall off my stack19:18
DalekSecI'd think so for geoip-databases too. :319:18
infinityYeah, 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:19
infinityAs 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:20
slangasekwe 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 year19:22
ogra_what if they dropped DST completely ?19:24
slangasekogra_: as long as they did this with 6 months notice, all fine!19:24
ogra_heh19:24
slangasekinstead 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_lol19:25
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:27
infinityslangasek: 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:32
mdeslaurhehe19:35
apwinfinity, 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-progress19:56
apwinfinity, so sysvinit ain't going anywhere19:56
apwoh _now_ you refresh and it dissapears ... pththth19:57
pittidoko: 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 yakkety20:19
pittibut that's for Monday morning20:19
xnoxdoko, infinity - general uploads i don't care, before we start syncing from debian... probably yes.20:34
xnoxsorry that i was out playing beach volleyball, in british down-pour rain, in a wet suit, in a sand pit =)20:34
tumbleweedsounds like xnox's life20:34
xnoxhehe20:35
dokoxnox, icu uploaded, will wait with any boost1.60 accept until that is built20:35
dokodo you know if 1.60 is ready for GCC 6?20:35
xnoxdoko, nice one.20:35
xnoxdoko, it should be yes.20:35
xnoxdoko, are you default for gcc 6 already?20:36
xnoxsyncpackage: Error: Debian version 1.60.0+dfsg-4 has not been picked up by LP yet. Please try again later.20:36
xnoxi can't sync the right boost yet20:36
xnoxslangasek, doko, infinity - $ syncpackage -r yakkety boost1.60 -V 1.60.0+dfsg-420:38
xnoxwhen you need it.20:38
dokota20:38
dokoxnox, please add a transition tracker20:44
xnoxwgrant, could I please have equivalent of primary-xenial-s390x-release.html for yakkety on http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/ ?20:47
xnoxi still think i have quite a few things that I could fix.20:47
xnox¯\_(ツ)_/¯20:52
maprerixnox: can you also sync gdk-pixbuf while the archive is still closed?21:52
xnoxmapreri, no, cannot sync cause it's missing my bug fix =)21:53
xnoxneeds a merge =)21:53
mapreri(message relayed.  /me feels like a homing pigeon)21:56
dokomapreri, gdk-pixbuf really needs that unfulfillable dependency fixed: = on a arch any and an arch all package21:58
mapreridoko: sorry, not sure about what are you referring to.  i was only aware of debian #81977922:00
ubot5Debian bug 819779 in libgdk-pixbuf2.0-dev "gdk-pixbuf: libgdk-pixbuf2.0-dev depends on libpng-dev but gdk-pixbuf2.0.pc requires libpng12-dev" [Serious,Fixed] http://bugs.debian.org/81977922:00
slangaseksounds like he's describing non-binnmu-safe dependencies; which are only an issue for Debian, not Ubuntu22:01
doko$ apt-cache show libgdk-pixbuf2.0-0|grep Depends22:01
dokoDepends: libgdk-pixbuf2.0-common (= 2.34.0-1)22:01
slangaseksure22:02
slangaseknot a problem in Ubuntu :)22:02
mapreriah, yes, not a problem here.22:03
maprerithough, there is not even a bug report in debian22:03
dokofiling one22:04
maprerita22:05
xnoxthat looks odd22:42
xnoxdoko, what are you doing?22:42
xnoxah icu, ok22:43
LocutusOfBorgI'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/157383922:59
ubot5Ubuntu bug 1573839 in gdk-pixbuf (Ubuntu) "please merge gdk-pixbuf from debian" [Undecided,New]22:59
LocutusOfBorgI 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 fixed23:00
* LocutusOfBorg goes to sleep23:00
=== jgrimm is now known as jgrimm-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!