[04:22] <chiluk> what would be the correct way to version mythtv if I'm goign to upload a fix for x-a?
[04:24] <chiluk> z=0.28.0+fixes.20170206.03f4403-0ubuntu3.1 and a=0.28.0+fixes.20170206.03f4403-0ubuntu5 ... but what for x and y?
[04:26] <hloeung> chiluk: guess that worked! Thanks for reporting this
[04:26] <chiluk> x = 0.28.0+fixes.20160413.15cf421-0ubuntu2-16.04.0 ? y=0.28.0+fixes.20160413.15cf421-0ubuntu2-16.10.0?  I can't use ~ here because it will version below what's currently there..
[04:26] <hloeung> err that was meant to be a PM
[04:26] <chiluk> hloeung: still trying to figure out what's correct for x and y..
[04:31] <chiluk> cyphermox_: ^^ when you wake up want to give me a little mentorship on the above?
[05:02] <chiluk> arges may like to educate me as well. ^^  ..
[05:03] <chiluk> and one last question.. when uploading should my changelog point at the <release>-proposed pocket or to the <release> pocket?
[05:23] <cjwatson> chiluk: Either is fine - they're mapped to the same thing.  I normally go for just <release>
[05:26] <cjwatson> chiluk: xenial should be 2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.04.1, yakkety 2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.10.1
[05:26] <cjwatson> chiluk: (per the security team's practices - there are various possibilities but this will do)
[05:27] <cjwatson> chiluk: you mustn't use a "-" to separate the last bit - that has surprising effects on how the version is parsed that you don't want
[09:21] <cpaelzer> hi, it seems all LP build recipes for artful fail since over the weekend  - I see some apt complains about not signed Release files
[09:21] <cpaelzer> https://launchpadlibrarian.net/326582597/buildlog.txt.gz
[09:22] <cpaelzer> anybody seen similar recently?
[09:23] <Unit193> Scollback here has some info on it, specifically from julian k and cj watson.
[09:23] <cpaelzer> thanks Unit193 - will read back on this then
[09:23] <Unit193> Basically, apt did it, "whoops"
[09:26] <cpaelzer> That is => https://bugs.launchpad.net/launchpad-buildd/+bug/1701826 then
[09:26] <cpaelzer> thanks
[09:28] <jamespage> o/
[09:28] <jamespage> morning all
[09:28] <jamespage> doko: hey - I'm blocked on a ceph upload for artful on https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1702044
[09:28] <jamespage> arm64 only afaict - would you have time to take a look?
[09:41] <jibel> could someone help with bug 1700557 ?
[09:41] <jibel> xnox, ^ maybe ?
[09:42] <juliank> cpaelzer: sorry
[09:42] <juliank> Who imagined that apt migrated that fast?
[09:43] <cpaelzer> migrations are only slow when you need/want them fast :-)
[09:45] <juliank> cpaelzer: Oh, I wanted it fast for testing, but forgot to think about the LP implications
[09:45] <cpaelzer> hehe
[09:45] <juliank> or maybe I even only noticed them after the upload
[09:46] <cpaelzer> you probably hit the best week you could to affect few people with the 4th of july ahead
[09:51] <juliank> cpaelzer: I'm pretty sure that's a fairly US-centric point of view
[10:01] <Unit193> mwhudson: Even given https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jacobsa-crypto.git/commit/?h=debian&id=f78d4a91ed54ec4ac3c70a8cd921858964f7ed71, not sure why armhf failed..
[10:02] <mwhudson> Unit193: unaligned access? he says without actually thinking about anything at all, i just saw armhf in there
[10:03] <Unit193> Interesting that s390x "moved" though.
[10:04] <mwhudson> yeah that seems a bit fishy
[10:04] <mwhudson> golang doesn't really support s390x on debian though
[10:04] <mwhudson> (debian supports super old isas)
[10:05] <Unit193> Maybe a mistake when he was correcting the 'le' → 'el' typo?
[10:06] <mwhudson> um
[10:06] <mwhudson> the golang arch is ppc64le
[10:06] <mwhudson> so that's definitely a mistake :)
[10:07] <Unit193> Meh, I don't know golang at all. \o/
[10:07] <Unit193> So yes, no idea where the regression was for the one at least.
[10:08] <mwhudson> Unit193: where did armhf fail?
[10:09] <mwhudson> oh autopkgtest?
[10:10] <mwhudson> oh build failed
[10:10] <mwhudson> not unaligned access then
[10:10] <mwhudson> i'm sure there should be something about _why_ the build failed in the log ...
[10:11] <mwhudson> Unit193: uh that patch adds too many commas by far, i think
[10:12] <mwhudson> it should just be // +build 386 arm  mips mipsel s390x
[10:12] <Unit193> Seems very vague to me, but s390x failed tests during build.
[10:12] <mwhudson> (well probably not x390x)
[10:13]  * mwhudson is not here btw
[10:13] <Unit193> OK, you do a very good ghost.
[10:14] <xnox> jibel, =/ not me, i'm not at all sure what's happening there.
[13:58] <chiluk> thanks cjwatson.. I had a feeling I was missing something there.
[14:27] <cjwatson> slangasek: could you merge debconf, or do you want me to?  I'd like to get something based on 1.62 into artful so I can proceed with the next stage of splitting out python{,3}-debconf
[14:27] <cjwatson> 1.5.62 that is
[14:28] <cjwatson> slangasek: (also not having at least 1.5.61 is going to be very bad as soon as the next perl transition lands)
[14:32] <seb128> speaking about debconf and perl is anyone working on replacing libgtk2-perl by something more modern?
[14:33] <cjwatson> I'd be very happy to take a patch to convert it to GI but I don't think anyone's working on it at the moment
[14:34] <cjwatson> (unless I missed a patch somewhere)
[14:35] <seb128> ok, thanks
[14:35] <seb128> everybody is busy so I doubt we have anyone at the moment to help on that
[14:35] <seb128> but let's see if we can make space for it, I would really like to get gtk2 out of the iso this cycle or next
[15:00] <sil2100> !dmb-ping
[15:33] <doko> jamespage: is it expected that ceph doesn't used parallel builds for it's subdirs?
[15:56] <jamespage> doko: hmm
[15:57] <jamespage> doko: that might be possible but I would expect a level of paralleism to some level
[15:57] <jamespage> doko: on the lp builders, we quite often hit memory limits so the max parallel gets limited
[17:30] <leitao> apw: I am currently installing 16.04.3 beta (http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed/main/installer-ppc64el/current/images/hwe-netboot/ubuntu-installer/ppc64el) but it does not find kernel 4.10-27.
[17:30] <leitao> it seems that kernel -27 is at proposed at this moment.
[17:31] <leitao> I understand I should enable -proposed during the installation.
[17:31] <leitao> I understand that the right way to do so is using "apt-setup/proposed=true".
[17:31] <leitao> but I am not able to install this beta version.
[17:31] <leitao> any recomendations?
[18:54] <chiluk> can i have someone reject my upload of mythtv in the yakkety queue... apparently the original sources were never rebuilt for yakkety and it ftbfs's even without my changes... I'll upload a fix for all that shortly.
[19:01] <juliank> infinity: in case you missed it: You can start removing apt-transport-https from the artful chroots :)
[22:24] <chiluk> infinity: ... I'm not sure how you feel about the intel-microcode update,  but I put it on the x and y upload queues for your SRU perusal