[01:36] <infinity> Logan: Bootstrapping.
[04:54] <slangasek> pitti: hi, so we're seeing some test failures on the amd64 and i386 autopkgtest runners for glibc revdeps where gtk is failing consistently; it's not a problem on other archs, I can't reproduce it locally, and the error points to a problem related to selecting a mir backend instead of an X backend.  Have there been any testbed config changes recently that could be to blame?
[05:02] <stgraber> could be a side effect of the pocket pinning logic in adt
[05:03] <stgraber> which would explain why a plain adt-run using the whole proposed pocket would succeed but the autopkgtest.ubuntu.com wouldn't as it's only pulling some packages from proposed
[05:36] <slangasek> stgraber: I didn't do an adt-run using the whole proposed pocket.
[07:33] <infinity> Logan: Well, sbcl bootstrap attempted, anyway.  It failed.
[07:36]  * infinity tries it on a newer kernel.
[18:26] <Unit193> infinity: bitlbee had a new release, not entirely bugfix (https://www.bitlbee.org/main.php/changelog.html) but mainly.  It's had a good amount of testing I'm told, I take it an FFe is still needed?
[18:27] <infinity> Unit193: Assuming the release is somewhat featureful, yeah.
[18:27] <Unit193> Bummer.  Thanks.
[18:31] <infinity> Unit193: Oh, but it's not seeded anywhere, so meh.
[18:31] <infinity> Unit193: JFDI, IMO.
[18:31] <infinity> Unit193: Here's your verbal FFe.
[18:32] <Unit193> Woohoo!  If you feel specifically like uploading: https://launchpad.net/~unit193/+archive/ubuntu/staging/+files/bitlbee_3.4.2-0ubuntu1.dsc, otherwise I'll go find someone.
[18:33] <infinity> Unit193: It is just a straight uupdate with a new orig, basically?
[18:33]  * infinity looks.
[18:34] <Unit193> It needs more updating, but on Debian's side.
[18:35] <infinity> Looks like a uupdate job to me.  No changes in debian/ except for the changelog.
[18:35] <Unit193> Mhmm.
[18:36] <infinity> Kay.  Source tarball looks sane, etc.
[18:36] <infinity> Want a slightly more verbose changelog? :P
[18:37]  * infinity shrugs and uploads.
[18:37] <Unit193> Oh dear, I'm too concise again. :3
[18:37] <infinity> Unit193: Too late, it's uploaded.
[18:38] <Unit193> Yey!  Thank you very much, infinity!
[18:38] <Unit193> I'll pass it along to who poked me.
[18:42] <dx> ♥
[20:20] <slangasek> doko: why did libnih need a rebuild for the new libc?  the versioned dep seems to have been resolved some time ago
[20:31] <cjwatson> pitti: Could we generate a stronger key for ddebs.u.c?
[20:32] <infinity> slangasek: It doesn't, I assume he was just working from an old list.
[20:33] <cjwatson> pitti: Also needs --digest-algo SHA384 or similar, but probably not much point until we have something better than 1024-bit DSA
[21:42] <slangasek> doko: do you know anything about valgrind compatibility with glibc 2.23? http://autopkgtest.ubuntu.com/packages/c/colord/xenial/amd64/ (or is this a toolchain regression somehow?)
[21:44] <mwhudson> infinity: did i ask you to look at https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1555856 at all yet?
[21:44] <mwhudson> (i asked stgraber to look at it and he asked if you'd seen it...)
[22:52] <doko> slangasek, just looked at the debian transition issue. the armhf build issue is not caused by the libc update. also seen in the test rebuilds
[23:25] <nacc> slangasek: will update my automated file, as i was using apt-cache redepends, which includes breaks and others, while reverse-depends does not. will provide an updated list first thing tmrw


[00:53] <daker> hi cjwatson, does LP builders do support pulling git submodules when building snaps ?
[00:53] <daker> https://github.com/canonical-websites/build.snapcraft.io/issues/813
[14:56] <m_hampl> There currently are lots of spam messages in the Inkscape answer section. Can someone please deal with them. Thanks in advance.
[15:02] <Mc> there are just ~150 of them
[16:18] <smoser> cjwatson, https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/324625 if re-submit the proposal, will it still hit bug https://bugs.launchpad.net/launchpad/+bug/1693543 ?
[16:18] <smoser> or is there any way i can get a diff on that mp ?
[17:00] <cjwatson> smoser: don't have enough brain right now to work out whether it will hit it again, but you can try rescanning the repository using the API: https://launchpad.net/+apidoc/devel.html#git_repository-rescan
[17:01] <smoser> thanks!
[17:04] <cjwatson> m_hampl: thanks, slaughtering
[17:18] <cjwatson> I think that's the latest run cleared
[18:08] <m_hampl> unfortunately the spam attack ist still ongoing, 50 additional messages in the past 15 minutes
[18:49] <cjwatson> m_hampl: I'll do my best, but I won't be able to keep up manually in my evening.  It'll mostly need to wait for wgrant to come back and bring the automation back online.
[19:09] <m_hampl> cjwatson: I fully understand that it is not your main task to fight spam. My main aim of this message was to make you aware of the current attack. I hope that there will be a chance to clean up the mess in the coming days. Thank you for your work done.
[19:37] <smoser> i suspect this is k nown...
[19:37] <smoser> http://paste.ubuntu.com/24718116/
[19:37] <smoser> json decode error with python3 and launchpadlib
[19:37] <smoser> worked with python2
[19:53] <cjwatson> fixed in launchpadlib or lazr.restfulclient trunk iirc.  need to get round to doing releases.


[05:52] <Researcher-> :)
[05:52] <Kilos> hellooooooo africa
[05:53] <Researcher-> waka waka africa
[05:53] <Researcher-> :D
[05:53] <Kilos> they all sleep late i think
[05:53] <Researcher-> yeah
[05:53] <Researcher-> guess so
[05:53] <Kilos> only za peeps wake early
[14:24] <Kilos> helloooo africa
[14:55] <Na3iL> Hello Kilos Hello Africa
[14:55] <Na3iL> Hows your day?
[14:56] <Kilos> very busy outside getting lands ready for planting oats for winter feed Na3iL
[14:56] <Kilos> how was yours
[14:56] <Na3iL> ah that's cool :D
[14:56] <Na3iL> me as usual, work work work xD
[14:56] <Kilos> lol
[14:57] <Na3iL> :D
[14:57] <Kilos> if you dont work you dont eat
[14:57] <Kilos> life can be tough
[14:58] <Na3iL> haha indeed
[15:17] <Kilos> hi josuebrunel
[15:17] <Kilos> and ongolaBoy
[15:17] <Kilos> and loganaden
[15:18] <Kilos> when are you guys bringing more recruits here?


[00:40] <penguin42> hurrah it finally went - with a BadAccess and I have a core
[00:42] <penguin42> oh that was possibly from IcedTea and well, that's flaky as hell
[00:44] <BUGabundo> fta: yeah gwibber is just burping a lot :(
[02:42] <[reed]> fta: ping
[02:42] <fta> yes?
[02:43] <[reed]> fta: to make shaver happy, can you do a build with the patches from mozilla bug 463605 backed out and see if it works?
[02:43] <[reed]> as in, backout http://hg.mozilla.org/mozilla-central/rev/0bd17bd1cbaf and http://hg.mozilla.org/mozilla-central/rev/5baf439a991a
[02:43] <[reed]> and try a build
[02:47] <fta> [reed], i sure can, but i don't see what is opaque in my build logs
[02:48] <[reed]> fta: I agree, but please do it
[02:48] <[reed]> it'll appease shaver
[02:49] <[reed]> fta: https://bugzilla.mozilla.org/show_bug.cgi?id=513067#c12
[02:49] <[reed]> also that
[02:51] <fta> [reed], the reason it fails is really simple, there's an absolute path somewhere. this is a make install DESTDIR=debian/tmp: http://paste.ubuntu.com/261696/
[02:52] <[reed]> can you say that in the bug?
[02:52] <fta> [reed], so line 67+ are all wrong
[02:52] <[reed]> explain exactly
[03:02] <fta> [reed], done. it's a misery to revert the patches, more patches have been applied on top already
[03:12] <fta> hm, it's also wrong in dist/
[03:16] <fta> [reed], commented, twice. it's 4am, i'm off now
[03:16] <[reed]> thanks
[07:50] <rugby471> hi guys
[07:51] <rugby471> trying to create a patch for a bug in firefox
[07:51] <rugby471> however I can't seem to get quilt to work for me
[07:51] <rugby471> I have done apt-get source firefox-3.5
[07:51] <rugby471> gone into that directory and extracted the archive as mozilla/
[07:51] <rugby471> however when I try to do 'quilt push -a'
[07:52] <rugby471> it says No file to patch.  Skipping patch. for all the patches
[07:52] <rugby471> any help?
[08:29] <rugby471> don't worry I managed to write the quilt patch manually
[12:17] <BUGabundo> hey
[16:39] <fta> BUGabundo, your redent lost the \ ?
[16:40] <BUGabundo> darn xmpp bug :(
[21:07] <fta> ripps, http://bazaar.launchpad.net/~fta/+junk/ppa-scripts/revision/119
[21:09] <micahg> fta: can there be only one package that provides the meta package xulrunner-dev?
[21:09] <fta> no
[21:09] <micahg> ok, I'm trying to verify stuff for the karmic transistion
[21:10] <micahg> and xulrunner-dev is still provided by xul1.9 in the .head branch
[21:10] <micahg> is this ok?
[21:10] <fta> yes, the version is lower than 3.5 so it's fine
[21:10] <micahg> ok
[21:10] <fta> i meant 1.9.1
[21:10] <micahg> so, as long as xul1.9.1 provides it, we're ok?
[21:11] <fta> i think so
[21:11] <micahg> ok
[21:28] <fta> well well well, my bot is starting to look good, may be time to package it
[23:00] <fta> [reed], 4th day red
[23:02] <BUGabundo> oooooh
[23:02] <[reed]> fta: he respondede
[23:02] <[reed]> -e
[23:02] <[reed]> you could respond
[23:03] <fta> [reed], to say what? he admitted he made the change causing the regression, now what?
[23:04] <[reed]> well, let's see what he has to say