[00:28] <slangasek> bregma: so I see there's a libgrip package in the raring-proposed queue that's been synced from https://launchpad.net/~ubuntu-unity/+archive/sru-staging ... our SRU process is not equipped to handle such things.  Do you have someone who can do a sourceful upload instead of a sync?
[01:05] <bregma> slangasek, I can take care of that
[01:05] <bregma> that change must have been languishing for the last 4 months, i never noticed
=== jbicha is now known as Guest92324
=== ikonia_ is now known as ikonia
=== freeflying_away is now known as freeflying
[12:29] <sergiusens> slangasek: xnox with a move to cross compilation, that means we are most likely going to move dh_auto_test unit tests to autopackage tests?
=== freeflying is now known as freeflying_away
[15:32] <smartboyhw> Laney, you don't mind me updating Rhythmbox to 3.0?
[15:32]  * smartboyhw will file a FFe for this;)
[15:40] <jbicha> smartboyhw: see bug 1220972 and https://bugzilla.gnome.org/707527
[15:40] <ubottu> Gnome bug 707527 in Plugins (other) "zeitgeist: More python3 porting" [Normal,Unconfirmed]
[15:40] <ubottu> bug 1220972 in rhythmbox (Ubuntu) "Upgrade rhythmbox to 3.0" [Wishlist,Confirmed] https://launchpad.net/bugs/1220972
[15:40] <smartboyhw> ubottu, ooh:)
[15:40] <smartboyhw> jbicha, ooh
[15:42] <smartboyhw> jbicha, so, it's impossible to touch on it since it wouldn't work?
[15:45] <jbicha> I wouldn't say that but it needs work to make sure all the python plugins work; that needs to be done eventually anyway
[15:46] <smartboyhw> jbicha, OK
[15:46] <jbicha> otherwise backporting fixes from 3.0 to saucy would be helpful
[15:47] <smartboyhw> jbicha, that will be quite a lot of backporting-.-
[16:26] <infinity> RAOF: "axserver-xorg-video-ati", you say? :)
[16:26] <infinity> RAOF: (From the changelog for xserver-xorg-video-ati)
[16:27] <infinity> RAOF: http://launchpadlibrarian.net/149219505/xserver-xorg-video-ati_1%3A7.2.0-0ubuntu5_1%3A7.2.0-0ubuntu6.diff.gz <-- Looks like you lost an argument with vi. ;)
[17:28] <Laney> jbicha: did you notice that your blender sync ftbfsed?
[17:28] <Laney> also owncloud-client but I'm looking into that one
[17:31] <jbicha> Laney: thanks for looking at owncloud-client since it looked a bit tricky to fix
[17:32] <Laney> I think it's just arch/indep fail
[17:32] <jbicha> yes but I wasn't sure the correct way to fix that
[17:32] <jbicha> for blender, see http://irclogs.ubuntu.com/2013/08/25/%23ubuntu-motu.html and continuing to 08/26
[17:33] <Laney> mmm
[17:43] <cjwatson> sergiusens: There's no reason to *move* them, since they're useful for native builds.  You might wish to run them from autopkgtest *as well*
[17:43] <jbicha> I'm not going to be able to fix blender as I have too much else going on right now
[17:43] <cjwatson> sergiusens: It'll be a long time before official package builds stop being natively-built, if ever
[17:44] <cjwatson> sergiusens: As far as I'm aware, current work on cross-building is mainly with the aim of making developer-system iteration easier and quicker
[19:09] <sergiusens> cjwatson: ack with the debian package building... what about click and CI. Should we aim for xcompile or native?
=== Nisstyre-laptop is now known as nisstyre
[20:20] <cjwatson> sergiusens: well, native comes out in the wash no matter what generally, but we need to aim for making cross-compile work too
[20:25] <jtaylor> can (ppa) packages depend on backports?  (e.g. via versioned depends)
[21:00] <cjwatson> That's a lot of chromiums building in parallel.
[21:01] <cjwatson> Glad I removed the restriction on PPAs :)
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying