[00:19] <slangasek> eep, python-support trying to sneak back in
[00:24] <infinity> slangasek: Can't we just rid Debian of it and not fight this fight every 3 weeks? :/
[00:24] <slangasek> infinity: I'm surprised we're having to fight it again
[00:24] <slangasek> er, especially since this is an Ubuntu-specific change
[00:25] <xnox> some pythons cannot change their spots....
[00:25] <infinity> Oh, the issue is that something started depending on libffdao?
[00:25] <slangasek> infinity: no, the issue is that libffado now depends on python-support in Ubuntu where it doesn't in Debian
[00:26] <slangasek> AIUI
[00:26] <slangasek> one sec, still sharpening my pitchfork
[00:26] <infinity> slangasek: Oh, apt-get source got me an old version from Q...
[00:26] <infinity> doko just messed up the merge, s'all.
[00:27] <infinity> Oh, no.  Not even that.
[00:27] <infinity> Current source is fine (except for the FTBFS).
[00:28] <slangasek> hmm, so there's a britney bug here?
[00:28] <slangasek> libffado source was updated in raring, all binaries are out of date
[00:28] <infinity> slangasek: The "issue" is that someone did the silly "sync, then merge" thing, and component-mismatches is reporting on the synced one.
[00:29] <slangasek> hmm
[00:29] <infinity> Since the synced one made it through.
[00:29] <slangasek> furthermore, they synced to raring
[00:29] <infinity> Or that.
[00:29] <infinity> doko: Update your copy of ubuntu-dev-tools.
[00:30] <infinity> doko: To one that syncs to -proposed by default, since you're an AA and bypass the reject.
[00:30] <slangasek> doko: unless you want us to consider main open for python-support dependencies ;)
[00:30] <infinity> slangasek: Oh, same thing to you, if you haven't already, you had a direct sync or two on -changes as well. :P
[00:30]  * infinity goes to eat.
[00:30] <slangasek> infinity: ack, pulling now
[00:33] <jbicha> infinity: can you sponsor http://paste.ubuntu.com/1344064/ for me?
[00:49] <xnox> jbicha: infinity: done.
[01:00] <jbicha> infinity: I've never seen that "hyphen at the end of a package to mark it for removal" feature
[01:04] <infinity> jbicha: You can also do the inverse, which is wildly confusing: "apt-get remove foo+"
[01:04] <infinity> jbicha: And yeahp, sponsoring away.
[01:05] <jbicha> infinity: xnox already sponsored it
[01:05] <infinity> jbicha: Oh, so he did.
[01:06] <infinity> slangasek: Any clue about the dh_python2 vomit in https://launchpadlibrarian.net/122410716/buildlog_ubuntu-raring-i386.libffado_2.0.99%2Bsvn2171-2ubuntu1_FAILEDTOBUILD.txt.gz ?
[01:09] <ScottK> infinity: ffado-mixer-qt4 isn't actually made of Python is it?
[01:09] <infinity> ScottK: Probably not.  But shouldn't dh_python2 -i DTRT?
[01:09] <infinity> Like any other dh_ thingee...
[01:09] <infinity> Though this would explain why it only fails on i386.
[01:09] <ScottK> At a glance it's a dh_python2 bug to not handle that gracefully, but -Xffado-mixer-qt4 should at least work around it.
[01:10] <infinity> ScottK: Check.  Let me give that a whirl.
[01:10] <ScottK> infinity: Please file a bug against python-defaults in Debian too.
[01:12] <infinity> Oh, wait, it's being called explicitle on -pffado-mixer-qt4
[01:12] <infinity> explicitly, too.
[01:12] <ScottK> Unless it's made of Python, just don't do that then.
[01:12] <ScottK> Bogus dh_python2 transitions FTL.
[01:12] <infinity> Well, doko was just doing s/dh_pysupport/dh_python2/
[01:13] <infinity> So, this may warrant a bit of looking at.
[01:14] <infinity> ScottK: Yeah, it's definitely python.
[01:15]  * ScottK looks.
[01:16] <infinity> Or, at least, support/mixer-qt4/ffado/ is full of python...
[01:16] <infinity> Yeah, and so is ./support/mixer-qt4/ffado-mixer.in
[01:17] <ScottK> Right.  And the whole thing is full of CDBS.
[01:17] <infinity> It sure is.
[01:17] <ScottK> The best thing about meeting Jonas at UDS was the chance to abuse him in person about CDBS.
[01:17] <infinity> That shouldn't matter at this point, though.
[01:18] <infinity> Since the build log clearly shows dh_install and friends happening before dh_python2, we should be out of potential CDBS hell by then.
[01:18] <xnox> infinity: ScottK: https://launchpadlibrarian.net/121157920/urwid_1.0.1-2_1.0.1-2ubuntu1.diff.gz
[01:18] <ScottK> I have this suspicion that somehow by the time we get there, the python versions is unset somehow.
[01:18] <infinity> xnox: Eww, for the "literary" reference.
[01:19] <infinity> xnox: But if you know what's broken, feel free to fix it. :P
[01:19] <infinity> Although, it's 1am there.
[01:19] <xnox> yeah!.....
[01:19] <infinity> Maybe this should be a python/cdbs learning experience for me.
[01:24] <jbicha> yay! cogl migrated
[01:25] <infinity> jbicha: Thanks for fixing -gst. :)
[01:26] <xnox> will upload the other half of boost1.49 tomorrow
[09:17]  * cjwatson tries to work around an LP timeout in kernel-overrides
[09:17] <cjwatson> (i.e. please don't process those kernel binaries in NEW as I have a nice test case right now)
[09:18] <infinity> Heh, I won't.
[09:19] <infinity> (Though, since kernels went all-main, I can't say I ever used fancy scripts)
[09:52] <cjwatson> infinity: also helps that I believe the default binary override bug has been fixed
[09:53] <cjwatson> ok, fallback now in kernel-overrides - at least it might help with kernels other than the mainline one
[10:21] <ScottK> xnox: Did you get libffado sorted?
[10:23] <xnox> ScottK: didn't even look at it.
[10:23] <ScottK> Oh.
[10:27] <doko> ScottK, infinity did upload
[10:27] <ScottK> doko: Thanks.
[10:28] <ScottK> infinity: Please file a bug against python-defaults since whatever was wrong in the package, dh_python2 should do something more friendly than a traceback.
[10:29] <doko> ScottK, it did work before, not sure what I did do wrong in the patch
[10:56] <seb128> cjwatson, do you know why boost1.49 is not moving to raring?
[10:56] <seb128> it's a simple patch upload (e.g no packaging, abi, shlib, etc change) and it built on all arches
[10:57] <cjwatson> looking
[10:57] <seb128> thanks
[10:59] <Laney> it seems entangled with swig2.0
[10:59] <cjwatson> seb128: boost-mpi-source1.49 produces binaries with exact-version dependencies on libboost1.49-dev
[10:59] <cjwatson> looks like that needs to be updated in sync
[11:00] <cjwatson> want me to take care of that or will you?
[11:00] <seb128> cjwatson, if you want to do it please feel free
[11:01] <seb128> I will have a look in a bit otherwise (just finishing something else first)
[11:01] <cjwatson> I'll sort it out
[11:01] <seb128> cjwatson, thanks
[11:02] <seb128> cjwatson, btw how did you find the issue? going through the binaries listed on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt?
[11:02] <cjwatson> I used chdist
[11:02] <cjwatson> 'chdist apt-get raring-proposed-i386 install dolfin-dev' as ubuntu-archive@lillypilly and then repeatedly added the binaries it was complaining about until apt gave me a useful error
[11:03] <cjwatson> same way I'd have debugged any uninstallability problem in the past
[11:03] <seb128> ok, thanks for the hint
[11:04] <cjwatson> now, Laney's correct that it's also tied up with swig2.0, so I'll have a look at that too in a bit if nobody else does
[11:04] <cjwatson> (you can find that part by starting with dolfin-bin)
[11:04] <cjwatson> that might not actually be a blocker for boost1.49 absent the boost-mpi-source1.49 problem
[11:05] <Laney> not sure if boost couldn't migrate on its own though
[11:05] <cjwatson> yeah, I think it probably could
[11:05] <cjwatson> easiest to fix mpi and then find out :)
[11:11] <xnox> cjwatson: me was thinking to do do boost1.49 today, or did you match it already?
[11:11] <cjwatson> boost-mpi-source1.49 you mean?  I'm working on it now
[11:12] <xnox> cjwatson: ok. go ahead.
[19:20] <plars>  #newark
[19:21] <plars> poo irc client
[19:21] <micahg>  #hades ?
[19:27] <ogra-cb>  #jfk
[19:31] <xnox>  #luton   <--- probably the most unfriendly airport I have ever been to.
[19:32] <ogra-cb> xnox, well, micahg's suggestion sounds even more unpleasant to fly to :)
[19:33] <xnox> ogra-cb: ha =) it's the weekend, and I don't know what to do =)
[19:34] <ogra-cb> oh you poor workaholic
[19:34]  * ogra-cb pets xnox 
[19:35] <xnox> ogra-cb: funny you should say that, I'm not sure when to take my holidays =)
[19:35] <ogra-cb> heh, same here
[19:35] <micahg> xnox: port the rest of main to python3? :)
[19:35] <ogra-cb> i guess the december will be silent this year
[19:36] <xnox> micahg: well, I want to setup a local mirror first. I guess I can do that now....
[19:37] <ogra-cb> that doesnt require much work though
[19:38] <ogra-cb> more of a test of our patiency and yous bandwith
[19:38] <ogra-cb> *your
[19:39]  * xnox has 100 MBps line....
[19:39]  * micahg guesses xnox is paying less for his 100Mbps than /me is paying for 25Mbps
[19:40] <ogra-cb> you are so spoiled
[19:40]  * ogra-cb still is on 2M SDSL
[20:13] <slangasek> ogra-cb: not ISDN? ;)
[20:13] <ogra-cb> haha, to expensive :)
[20:17]  * stgraber is on symetric 1000Mbps at the moment ;)
[20:17] <stgraber> and that's on my laptop, not some remote server :)
[20:22]  * iulian is on asymmetric rubbish Mbps.
[20:22] <iulian> That's what happens when one is miles away from the telephone exchange.
[20:22] <iulian> :(
[21:09]  * tumbleweed sees armel has gone. Britney will need to be told to stop caring about it
[21:10] <infinity> tumbleweed: We'll get there.
[21:11]  * tumbleweed waves goodbye to it, and goes to bed
[22:13] <xnox> thanks for accepting debtags python3, now I uploaded python3-pyasn1 ;-)
[22:15] <infinity> xnox: http://amzn.to/lC4jhe
[22:17] <xnox> infinity: coming from you, it is a bit ironic =)
[22:18] <infinity> xnox: Just because I'm illeterate doesn't give you the right to make fu-- oh, you mean because I don't sleep?  Right.
[22:18] <infinity> illiterate, even.  There's some irony...
[22:18] <infinity> xnox: But I'm "sleeping" right now.  I took a sick day and went back to bed, remember?
[22:20] <xnox> infinity: as in you don't always sleep on schedule. not making any fun of anybody =)
[22:22] <cjwatson> Do we need to wait for things like libreoffice/armel to finish before killing the DAS?
[22:22] <cjwatson> Oh, that's in quantal anyway
[22:22] <cjwatson> Running builds, in any case
[22:22] <cjwatson> Er, and echan
[22:22] <infinity> Yeah, probably.
[23:52] <xnox> DON'T PANIC
[23:52]  * xnox got an armel reject email ;-)