User1: Hi everyone! Still need someone from the SRU team to take a look at a fix that we'd like to SRU for raring: https://bugs.launchpad.net/unity/+bug/1043627
User2: Launchpad bug 1043627 in nux (Ubuntu Raring) "[SRU] Add XIM Support to Nux" [Undecided,Confirmed]
User1: It seems to be somewhat important
User3: Can I ask for PowerPC builds be rescored of packages listed in Levels 1-3, excluding (boost-mpi-source1.53, ogre, ogre-1.8) for the boost1.54 transition http://people.canonical.com/~ubuntu-archive/transitions/boost1.54.html ?
User4: User3 doing
User3: thanks.
User4: User3 frogatto librcsb-core-wrapper mkvtoolnix pentobi rdkit btag enblend-enfuse gringo lightspark mira source-highlight vera++ laserboy -> 4000
User3: User4 thanks, all good.
User5: User4 User9 could i know when trusty server images will start appearing in cdimages?
User4: was planning to poke at that tomorrow; so tomorrow or Friday
User4: I uploaded the d-i components today that need to be touched for the new release name
User5: User4 ack, thanks
User6: Hi, I continue getting pinged about bug 943195 â can somebody accept the SRU please?
User2: Launchpad bug 943195 in xpdf (Ubuntu Raring) "xpdf.real crashed with SIGSEGV in GooHashbd6c:f4c4:4f6:c742:59d8:35db:68f6:4d5fhash()" [High,Triaged] https://launchpad.net/bugs/943195
User6: (It's a bug affecting 116 people with ugly but working fix)
User7: User4 hey-- you asked me to upload apparmor for perl 5.18, so I did, but it seems to be blocked by perl now
User4: User7 Yes, that's expected
User4: User7 Should be done with that transition in a day or two
User7: User4 ok, cool, thanks
User4: If you desperately need to upload something you can stack it on top as long as you're sure it isn't going to fail to build somewhere, or you can wait
User7: User4 no, we aren't blocked-- I just noticed it and thought I;d ask
User4: User7 If you want to speed it along you could help figure out any of the libdr-tarantool, gdal, or libmongodb-perl build failures :)
User8: howdy! i uploaded maas to saucy-proposed a few days ago (beforr trusty was open). can someone please accept it into -propsed for sru verification and copy it into trusty?
User9: User8 I'll look at it after I get the last of this perl transition licked.
User8: User9 perfect! thank you!
User9: User4 FWIW, I'm fixing the gdal FTBFS, if you were planning on that.
User9: User4 I think stgraber is looking at libdr-tarantool-perl, though possibly with some confusion.
User10: is anyone planning to let some of the saucy SRUs in this week?
User9: User4 So, that leaves ibmongodb-perl
User10: or should I consider direct pings to get mines in? ;-)
User9: l*
User4: User9 Oh, good, I'd got part-way into the gdal FTBFS but was interrupted by dinner.  Be m yguest.
User9: User10 I'm going to look at the SRU queues once this perl transition looks to be under control.  Don't want to keep trusty-proposed in this state too long.
User11: User9 I'm fighting with airlines at the moment but will get back to figuring out why the test segfaults after that
User10: infinity, User14 do you plan do SRUs this week or next ? ;-)
User9: User10 Red 8 minutes back in backscroll.
User10: User9 sorry, missed that ... thanks ;-)
 * seb128 blames that web client (behind a connection blocking IRC ports atm)
User9: User10 Ew.
User12: User9 how much longer do you think it's going to take to get perl through?  The maas SRU is AIUI a time-sensitive one, so maybe I should look at it
User9: User12 Oh, if it's time-sensitive (the maas one?), I can look.  I already had a bit of context.
User11: User12 down to 3 packages
User9: My gdal FTBFS fix worked, and then failed on the next g++ call, so I clearly have a bit of work to do there. :P
User13: User14 hey, any news on bug 1232363 ?
User2: Launchpad bug 1232363 in update-manager (Ubuntu) "Update Manager Restart button fails on xubuntu" [Medium,Triaged] https://launchpad.net/bugs/1232363
User12: User9 oh, actually, maas was not mentioned as one of the packages affected by what I'm thinking of
User12: User9 so don't let it disrupt your flow
User12: I was thinking of walinuxagent+cloud-init, which I think was just precise and already done
User9: Ahh.
User11: yeah, I dealt with the cloud-init + walinuxagent uploads (so far precise + raring I believe)
User12: User15 is there still a quantal SRU coming of cloud-init + walinuxagent?
User14: User13 I'm working on it
User13: User14 thanks, still curious if my patch works, well it's no magic anyway, copy and paste mostly :)
User4: Wonder if I can figure out libmongodb-perl
User4: Not my field, to put it mildly, but
User4: Ha.  https://github.com/mongodb/mongo-perl-driver/commit/dc4db9bf3807627828859bb630ff4e852d8d261b
User12: destroy all software... or at least its tests
User4: IOW "the javascript engine reports errors in too many random ways so let's give up for the moment"
User4: works for me for now ...
User9: User4 Oh dear.
User9: TMTOWTDI, I guess.
User9: Though, that seems the wrong way. :P
User4: It does, but I'll go with upstream terribleness over home-grown terribleness for software I don't know
 * infinity nods.
User9: gdal seems licked, just waiting for it's enormously slow test build to finish.
User9: its...
User9: Damn you, internet.
User9: Phew.  gdal fixed.
User9: So, that just leaves us whatever-tarantool-thingee.
User9: And any arch lag...
User9: I think I caught all the lagging PPC perl builds, but I'll do another sweep.
User4: Also poking proposed-migration/autopkgtest until it stops being confused about a few things
User4: User9 Anything that was lagging and that mattered would show up in the transition tracker, I expect
User9: User4 There were plenty of PPC builds showing as blanks in the tracker, I think I got them all.
User4: Blanks don't matter for migration
User9: They should, since you can't migrate with half-built sources.
User4: If it's a blank then it probably wasn't built before ...
User4: If it was built before I'd expect an x, since it would've been against perlapi-5.14.blah
User9: Oh, I guess outdate doesn't matter for new sources?
 * infinity shrugs.
User4: It's not outdate if it hasn't been built :)
User9: Anyhow, I picked them all off anyway.
User9: I think.
User4: I have about three different views of this.  Going round and checking them all.
User9: I'll stop fixing arm64 perl FTBFSes for a few cycles, so we can let the dust settle without me revving source versions again.
User9: ... and score that gdal through the roof so it happens this century.
User4: I already scored it high enough
User9: Oh, it's already building.  Yay.
User9: Heh.
 * cjwatson reruns the sbuild autopkgtest now that schroot is in sync
User9: It disturbs me that I knew more about GCC floating point options in April than I do in November.
User4: samba4 similarly
User9: My fixes to teem seem entirely like voodoo to me now.
User9: s/November/October/
User11: User4 ah, I just finished running the samba4 one locally and pushed an hint to ignore the failure, but a re-run works too :)
User4: I prefer making them pass than overriding them
User9: User11 Any hope on the tarantool segv thing?
User11: User4 how can I trigger a re-run?
User4: User11 you need an account on the private jenkins, then there's a "build now" operation at the top level of a test
User11: User9 poking at this slowly (while on hold, still fighting with airlines...)
User4: There we go, samba4 and sbuild autopkgtests back to green.  I wonder if p-m will notice
User11: User4 who do I poke to get one of those accounts?
User4: User11 I think I poked jibel
User11: ok
User15: slangasek, quantal is difficult...
 * cjwatson sighs and goes to kick auto-package-testing inna head
User15: and not terribly high priority to anyone
User15: other than to the upgrade path from p -> q
User11: User9 I'm done being a travel agency and back to poking at that tarantool thing
User4: hm, it's running, maybe I'll leave it
User4: ah, looks like it picked up the rerun, good
User4: grr, and of course the perl transition gets britney into one of its unhappy "I'm going to take ages because when I try individual packages the world becomes uninstallable" moods
User4: (which was why I blocked it when it was hopelessly incomplete)
User4: "AIEEE: counter overflow"  yes yes I know
User9: Heh.
User12: User15 ok; no skin off my nose if q isn't a priority for you
User15: slangasek, ok. thank you. the backport is harder there.
 * slangasek puts some paper towels down on the counter
User8: q/win 13
User11: User4 infinity suggested you may be faster at solving the libdr-tarantool-perl failure than us ;)
User11: User4 http://paste.ubuntu.com/6291627/ is the stacktrace
User11: User4 the function that's failing didn't change between saucy and trusty but the rest of the code changed quite a bit
User9: I'm fine with demoting or reverting that, if it ends up being our only blocker, but fixed would be nicer if the bug jumps brobinson@example.org.
User11: User4 and the fun being that this only fails on i386, amd64 works fine
User4: I used to be an XS expert but it's been a while
User11: User9 I'm testing a rebuild of saucy's version on trusty now to confirm that's an option
User4: Let me grab some coffee and take a look
User11: User9 not an option, segfaults too
User9: Oh, lawlz.
User9: So maybe it's in something it links to?
User4: Looks to me like a changed packet format or something
User4: But I'll see if I can just debug it directly ...
User9: Though, no.  Not link, per se.
User11: (saucy-i386-sbuild)root@castiana:~/libdr-tarantool-perl-0.42# ldd ./blib/arch/auto/DR/Tarantool/Tarantool.so
User11: linux-gate.so.1 =>  (0xf7788000)
User11: libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75c3000)
User11: /lib/ld-linux.so.2 (0xf7789000)
User9: User11 Yeah, more likely sometihng it's calling out to (ie: tarantool)
User9: Not that tarantool is segfaulting but, as Colin says, maybe some format has changed.
 * cjwatson also eyes an earlier fix https://github.com/dr-co/dr-tarantool/commit/dc33e60713dfd996dcef936b26e6ce5acc67c855 to nearby code
User11: FWIW I confirmed the crash on saucy happens on the exact same line of the tp_next function
User4: Also FWIW the counts seem random
User11: build works when downgrading tarantool to saucy's version
User4: https://launchpadlibrarian.net/154728856/buildlog_ubuntu-trusty-i386.libdr-tarantool-perl_0.42-1_FAILEDTOBUILD.txt.gz got through two rounds of the loop before failing; my local build got through 14
User4: 1, 13, 16 ... definitely racy
User11: hmm, looks like I was lucky, even with saucy's version I can get it to segfault
User4: So something like an adapted version of that earlier commit seems like a decent potential candidate
User9: Oh, if this is racy, I can give it back 37 times. :P
User4: And indeed it does sometimes succeed
User4: Nah, would rather attempt a fix
User9: Yeah, that was sarcasm.
 * infinity goes back to seeing if birch is salvageable.
User4: my $body = join '', map { chr int rand 256 } 1 .. (300 + int rand 300);
User4: wonder if it depends on the length of that
User4: ... not obviously
User9: User4 When we thing the perl transition is ready, we might want to pause the publisher, so that massive block of copies and deletes from britney happens atomically.
User9: s/thing/think/
User4: I was thinking that too
User4: There's still a fair amount of stuff in output
User4: It might be over-autohinting, or more likely it's stuff that doesn't show up in the tracker :-/
User4: Or could be under-autohinting.  gammaray's installable in trusty-proposed-amd64.
User4: Ah, graphviz mini-transition too
 * cjwatson crafts another tracker
User4: Also libbuffy-bindings FTBFS; not sure why that didn't show up on the tracker, since it was there at one point
User4: Sigh, this is going to be painful - we should've done the new graphviz after the perl transition was done
User4: I didn't realise it was going to involve sourceful changes to dependent packages of its own
User4: Though at least not all of them ...
User4: This mess absolutely vindicates the decision to defer the new graphviz from saucy to trusty, though
User11: 2/9 worked with a rebuild, we've seen better, thankfully there aren't that many of those
User9: poppler can be much worse, when it happens.
User9: Thankfully, though they break ABI every eight days, they seem to only violently break API once a year or so. :P
User16: cjwatson, sorry, forgot about the graphviz one
User4: Hmm.  Maybe this is just me not understanding something, but the reply from tarantool in the segfaulting case looks like total nonsense
User4: Sensible-ish header but then the tuple lengths are off in la-la land
User11: User4 there'll apparently be a new Debian upload of tarantool real soon (changelog entry was pushed to git 14 hours ago), I wonder if this may help
User4: Oh, actually it's not tarantool at all
User4: The packet I'm looking at is entirely generated by the test code
User4: So it is utterly dumb luck whether it happens to cause it to overflow into space
User4: Not too sure why it ever worked, though it clearly does sometimes and I can't be bothered to sort out why.
User11: so are you close to figuring it out how to fix the test or should we just turn that one off (or click rebuild a couple of times and see it magically pass)?
User4: I'm close
User4: But there's no rush now since we have at least graphviz to do before perl can land
User9: The number of times I've run into people actually attempting to update config.{sub,guess} but landing it in the wrong directory is quite funny.
User17: Also lots of people use autoreconf to do it
User17: But then their setup is sufficiently strange, or they just don't use automake, so it doesn't actually work.
User9: I'm pretty much madly in love with dh_autotools_dev's spray of bullets approach to the problem.
User9: Seems to DTRT every time, so far.
User17: Yep
User9: Finished 1 minute ago (took 13 minutes, 47.2 seconds)
User9: Finished 1 minute ago (took 13 minutes, 46.6 seconds)
User9: birch and sulfur fight to the death at the finish line...
User9: I obviously need some breakfast if I'm sitting here comparing build times.
User3: Can I ask for PowerPC builds be rescored to 4000 of packages listed in Levels 6 which did succeed on "adm64 i386 armhf" at http://people.canonical.com/~ubuntu-archive/transitions/boost1.54.html ?
ubuntu-release
Ubuntu IRC