[03:30] <pitti> Good morning
[03:33] <larsu> pitti: good morning :) How are you?
[03:37] <pitti> hey larsu! prima, danke, und Dir?
[03:37] <pitti> larsu: are you still at Ryan's?
[03:37] <larsu> pitti: auch sehr gut! Hacking away on a balcony in Toronto :)
[03:38] <larsu> I'm in Toronto, but not at Ryan's place
[03:38] <pitti> sweet
[03:40] <larsu> ya, it's an awesome night here. And I have a very good view of the cn tower
[03:41] <larsu> it changes its lights in hypnotizing ways...
[03:42] <pitti> and you can still work on code with that? :-)
[03:43] <larsu> I admit that it distracts me for a couple of minutes every now and then :D
[03:57] <pitti> larsu: well, so do IRC, G+, youtube, etc. :)
[03:58] <larsu> hehe, true!
[04:28] <Mirv> hello
[06:00] <didrocks> good morning
[06:04] <didrocks> good morning Mirv ;)
[06:17] <Mirv> morning didrocks!
[06:17] <didrocks> Mirv: how are you?
[06:19] <Mirv> didrocks: sad that sdk still didn't build, there was a python script added yesterday to the trunk without python dependency.. otherwise fine :)
[06:19] <didrocks> Mirv: remind them to ask whenever they think there is a package change needed :)
[06:19] <didrocks> Mirv: should I retrigger the build now?
[06:21] <Mirv> didrocks: not yet
[06:22] <didrocks> Mirv: ok, keep me posted, I want to have next ready today :)
[06:22] <Mirv> ok, will do
[06:52] <jibel> good morning
[06:53] <Mirv> didrocks: can we start the Qt uploads now?
[06:54] <didrocks> salut jibel! Il y a enfin du soleil ici! et toi? :)
[06:54] <didrocks> Mirv: doing
[06:55] <jibel> didrocks, salut! oui enfin, c'est l'heure d'aller à la plage :)
[06:55] <didrocks> et de manger une glace! :)
[07:03] <Sweetsha1k> xnox: awesome thanks!
[07:03] <Sweetsha1k> Moin a tous btw!
[07:06] <didrocks> Mirv: fail :p
[07:06] <didrocks> Sweetshark: bonjour bonjour :)
[07:07] <Mirv> didrocks: :(
[07:07] <didrocks> Mirv: do you need a hand?
[07:07] <didrocks> Mirv: I didn't look at the content, just got email spam :)
[07:09] <Mirv> didrocks: I wonder if I haven't subscribed to something..
[07:09] <didrocks> Mirv: you should get the FTBFS from ~ubuntu-unity ppas?
[07:09] <didrocks> as you are part of the team
[07:13] <Mirv> didrocks: hmm, which fail you are talking about actually, apparently not related to Qt 5.0.2 packages?
[07:14] <Mirv> didrocks: ah, yes, ui-toolkit. I meant to ask about saucy Qt uploads :)
[07:14] <didrocks> Mirv: I'm getting <xxx> build of ubuntu-ui-toolkit <version> build failure emails
[07:14] <didrocks> Mirv: you do get those emails, right?
[07:14] <Mirv> I'm still looking at the ui-toolkit, there's more than just the dependency error
[07:14] <Mirv> didrocks: yes, I get those
[07:14] <didrocks> Mirv: ok, let's get that done, rebuild and then, moving to Qt, ok?
[07:15] <Mirv> didrocks: sure
[07:15] <didrocks> keep me posted or ask me if you have any question :)
[07:16] <Mirv> I'm just multi-tasking a bit while I've pbuilder runs going on
[07:16] <Mirv> ok
[07:57] <Laney> morning
[07:57] <didrocks> hey Laney!
[07:58] <Laney> didier!
[07:58] <seb128> hey desktopers
[07:58] <seb128> hey Laney didrocks
[07:58] <Laney> seb!
[07:58] <seb128> how are you?
[07:58] <didrocks> salut seb128!
[07:58] <didrocks> good good, yourself?
[07:58] <seb128> I'm good
[07:58] <seb128> in this rainy tuesday :p
[07:58] <didrocks> someone stole my sun!
[07:58] <didrocks> it was around this morning, I saw it
[07:58] <seb128> not me
[07:58] <didrocks> where is it now? :p
[07:59] <seb128> doh, it's already tuesday, it feels like the week just started ... I will miss the short work weeks and log weekends
[07:59] <didrocks> seb128: it's even thursday, not tuesday :p
[07:59] <seb128> the national holidays fun is mostly over for a while now
[07:59] <seb128> didrocks, double doh :p
[07:59] <Laney> nah, if you move to the UK you get one on Monday :P
[07:59] <didrocks> seb128: hem, we can create some :p
[08:00] <seb128> Laney, ;-)
[08:00] <didrocks> seb128: did you hear about the national rain day? :)
[08:00] <didrocks> I heard it's off :p
[08:00] <seb128> Laney, can I get non-rainy weather as well with it?
[08:00] <seb128> didrocks, seems like every day until end of the month?
[08:00] <seb128> ;-)
[08:00] <Laney> http://www.bbc.co.uk/weather/2641170 says no :(
[08:00] <didrocks> seb128: yeah, I read the same, should be true then!
[08:00]  * didrocks opens canonicaladmin
[08:00]  * seb128 shakes fist at the weather
[08:01] <didrocks> :)
[08:03] <didrocks> Mirv: sdk fix is found and merging? If so, we can maybe starts the Qt part together
[08:05] <Mirv> didrocks: it's merging yes now
[08:05] <Mirv> didrocks: yes we can
[08:06] <didrocks> Mirv: ok, so, I open https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=4
[08:07] <Mirv> first part would be from qtbase to qtdeclarative. I'm looking at qtscript a bit since it's in Debian NEW queue and apparently I can't fetch the orig tarball directly from there
[08:07] <didrocks> Mirv: do you mind giving me edit rights? that will enable me to copy/paste only the branch url :)
[08:07] <Mirv> and first part of the first part would be checking and uploading qtbase
[08:07] <didrocks> Mirv: ok :)
[08:08] <Mirv> didrocks: added
[08:08] <didrocks> Mirv: thanks :)
[08:08] <didrocks> Mirv: nice document btw, really helpfull
[08:08] <Mirv> thanks, it was really needed to keep things in order
[08:16] <didrocks> Mirv: ok, qt-default to be arch: any is a debian thing? they do want it?
[08:17] <didrocks> qt5-default*
[08:21] <Mirv> didrocks: yes, they now ship configuration files in multi-arch triplet dirs
[08:23] <didrocks> ok
[08:23] <didrocks> that's what I saw
[08:24] <didrocks> Mirv: just an advice: you should name upstream patch git_…
[08:24] <didrocks> Mirv: that's easier then to see if it doesn't apply that we should just remove it
[08:25] <didrocks> speaking of debian/patches/rename_qabs_function_for_timeval.patch
[08:25] <didrocks> and some others :)
[08:26] <Mirv> right, thanks.. I'll try to remember that
[08:26] <seb128> Mirv, btw, I just upgrade with the qt5-beta-proper/saucy ppa, things work fine and my menus are back in the panel as they should
[08:26] <seb128> just upgraded*
[08:26] <Mirv> seb128: thanks, I also tested, seems normal
[08:30] <ritz_> seb128 bonjour , https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1027086/comments/26
[08:30] <ubot2> Ubuntu bug 1027086 in vino (Ubuntu Precise) "incorrect schema setting used for authentication-methods in vino server" [Medium,In progress]
[08:30] <seb128> ritz_, hey
[08:30] <ritz_> hi :)
[08:31] <seb128> ritz_, I'm still not really happy with the hack there, did anyone confirm that it's the solution wanted?
[08:32] <ritz_> seb128 , as per upstream, this is the way to go.
[08:32] <ritz_> removing the choice listing form schema
[08:32] <seb128> ritz_, ok, fine enough, you should subscribe ubuntu-sponsors to the bug so it's in the sponsoring queue
[08:36] <didrocks> Mirv: my new saucy pbuilder just starting to build qtbase :)
[08:37] <sil2100> didrocks: hi! I have a question related to the generic AP jobs - where does the /tmp/autopilot.head.*.skip file come from?
[08:37] <sil2100> didrocks: when is it created and what triggers it?
[08:37] <Mirv> didrocks: ok!
[08:41] <didrocks> sil2100: it's created when there is no tests to run for that stack
[08:41] <didrocks> sil2100: that avoids UTAH to provision for nothing
[08:41] <didrocks> so the -prepare and -check jobs create it if needed
[08:42] <didrocks> sil2100: hum, did you rerun the HUD?
[08:43] <sil2100> didrocks: yes, just the tests
[08:43] <didrocks> sil2100: you didn't check "with whole ppa", did you?
[08:44] <sil2100> didrocks: so hm, why is the OIF stack creating that file even though there is one test to be run?
[08:44] <didrocks> sil2100: it won't take latest unity autopilot tests then
[08:44] <sil2100> didrocks: no, I just built with foo
[08:44] <sil2100> I just want to re-run
[08:44] <sil2100> To see if the 2 failures we have are reproducible
[08:44] <didrocks> sil2100: ok, so not with unity-autopilot changes you did, right?
[08:44] <sil2100> Since HUD seems to have a strange regression
[08:45] <sil2100> didrocks: those got merged yesterday, right?
[08:45] <sil2100> So they're in already
[08:45] <sil2100> And they have been used
[08:45] <didrocks> sil2100: "No new source uploaded to PPA and CHECK_WITH_WHOLE_PPA is not set.  Skipping check!
[08:45] <didrocks> "
[08:45] <didrocks> so no need to run tests
[08:45] <didrocks> for oif
[08:45] <didrocks> sil2100: hum, really?
[08:45] <didrocks> sil2100: ah, maybe unity is in next?
[08:46] <didrocks> sil2100: because normally, they shouldn't be installed or veebers has an issue in his script…
[08:46] <didrocks> sil2100: do you have the run that shows that latest unity is used, even built without --check-with-whole-ppa?
[08:46] <sil2100> didrocks: I'll double check, but the test results seem to show that my and Francis branch are in
[08:46] <sil2100> One moment
[08:47] <didrocks> sil2100: weird weird weird ;)
[08:52] <sil2100> didrocks: so, it's using 7.0.0daily13.05.22.1ubuntu.unity.next-0ubuntu1, which is based on revision 3338, so with our two fixes included already
[08:52] <sil2100> didrocks: that's the one from yesterday's re-build it seems, 16 hours ago?
[08:55] <didrocks> sil2100: ok, we need to ping veebers, seems the preseed regressed…
[08:57] <sil2100> didrocks: my understanding was that it is currently using the packages available in the daily-build-next PPA
[08:59] <didrocks> sil2100: yeah, and that's wrong, we should only use the set
[08:59] <didrocks> sil2100: I think his refactoring broke it
[09:00] <sil2100> didrocks: might be, as I remember he was doing some fixes there, so maybe the original idea got lost somewhere
[09:02] <didrocks> yeah
[09:02] <didrocks> sil2100: ok, let's try to get everything green today and in -next?
[09:02] <sil2100> attente: once you're up, give me a ping
[09:02] <didrocks> sil2100: I think we are really close :)
[09:03] <sil2100> didrocks: yea, let's do that - I think we are, I re-built all the packages that failed for unity, the problems being the one unit test in libunity that likes to time out (Paweł is trying to fix it now)
[09:03] <sil2100> didrocks: since the home scope and libunity failed for powerpc, home scope because of missing libunity
[09:04] <sil2100> didrocks: if this test won't get fixed quickly, I would recommend disabling it temporarily, as it's slowing down the release process due to it's flackyness
[09:05] <didrocks> sil2100: right, we need to give that to upstream as a TODO to get things fixed first
[09:08] <didrocks> sil2100: hud finished
[09:09] <sil2100> One failure, hm
[09:10] <sil2100> Yes, this one I think is an actual regression, as I noticed it sometimes as well
[09:10] <didrocks> Mirv: what do you mean by "(Synced but pkg transition)" ?
[09:10] <sil2100> i.e. no results returned
[09:10] <didrocks> sil2100: is there anyone in the HUD circles to be able to fix this?
[09:11] <sil2100> didrocks: I could ask Pete and maybe someone from the unity-frontend team to take a look
[09:11] <sil2100> Normally I would ask Ted, but he's on holiday this week
[09:12] <didrocks> sil2100: right, do you think we should manually publish for now?
[09:13] <sil2100> didrocks: let's do that, doesn't make sense to block on this issue
[09:14] <didrocks> sil2100: you will handle it?
[09:14] <didrocks> sil2100: maybe we can put the threshold to 1 as well for now?
[09:15] <sil2100> hmmm
[09:16] <sil2100> didrocks: ok, would make sense maybe, since anyway sometimes the fuzzy tests might fail because of invalid guessing
[09:16] <didrocks> jibel: (as we don't have write access, isn't it?) ^ head/hud, triggers 1/1 for failure, regressions please :)
[09:16] <sil2100> didrocks: it's always sad to have a threshold set, but still better than having to manually publish every time
[09:16] <didrocks> sil2100: right
[09:16] <didrocks> sil2100: please do a manual publishing meanwhile :)
[09:18] <sil2100> didrocks: should I check the 'force' checkbox ;p? I forgot what it was for ;p
[09:19] <didrocks> sil2100: not the first time
[09:19] <didrocks> sil2100: it's to force is upstream stacks failing but we know we want to publish
[09:19] <didrocks> sil2100: or if there are packaging changes and we ack them
[09:22] <didrocks> Mirv: qtbase sponsored
[09:22] <didrocks> Mirv: doing sync now
[09:22] <didrocks> Mirv: waiting for your answer on synced but pkg transitions :p
[09:25] <sil2100> didrocks: the publish is yellow, since QA has failed to publish - is that ok?
[09:26] <jibel> didrocks, I added ACLs for the desktop-team and you should have write access now. Coul dyou try?
[09:27] <didrocks> jibel: sure
[09:28] <didrocks> sil2100: well, you know that the QA stack can't interfere with runtime for the HUD
[09:28] <didrocks> sil2100: so you can force the publication :)
[09:28] <sil2100> Checking force \o/
[09:28] <didrocks> jibel: worked perfectly :)
[09:33] <Laney> where do I get unity-gtk-module from? daily-build-next?
[09:33] <didrocks> sil2100: ^
[09:34] <Laney> maybe I'll just build the package :P
[09:34] <sil2100> Laney: yes ;)
[09:35] <Laney> ty
[09:39] <seb128> Laney, do you need it for something or just trying it?
[09:40] <Laney> updating gnome-terminal and it had menus in the app, thought that might fix it
[09:41] <Mirv> didrocks: thanks, was on luch.. it means that "in sync with Debian in practice, but Ubuntu has additional package name transitions" (ie. replaces: etc)
[09:41] <didrocks> Mirv: ok
[09:41] <Laney> (it does not)
[09:42] <Mirv> didrocks: so those need to be still uploaded with Ubuntu specific changes, compared to those that can be actually synced directly like qtjsbackend, qtxmlpatterns, qtsvg
[09:43] <seb128> Laney, to test you need to uninstall UBUNTU_MENUPROXY and you need indicator-appmenu trunk
[09:43] <didrocks> Mirv: right :)
[09:43] <seb128> unset
[09:43] <seb128> or uninstall appmenu-gtk3
[09:43] <Laney> yeah it installs an Xsession.d file which does that
[09:43] <Laney> the UBUNTU_MENUPROXY thing
[09:43] <Laney> trunk> ok, getting
[09:46] <Laney> I wonder why the "alternate scrolling" patch never went upstream
[09:46] <Laney> seb128: do you know?
[09:46] <didrocks> Mirv: do you mind providing a diff with debian for all the stuff we only have diff with replaces, conflicts and so on?
[09:47] <didrocks> that will speed it up for me :)
[09:51] <xnox> Sweetsha1k: my source package is $ dget http://people.canonical.com/~xnox/repo/libreoffice_4.0.2-0ubuntu2.dsc
[09:51] <xnox> the original tarballs should be as in the archive atm.
[09:51] <didrocks> Mirv: some copyright are not good on qtpim :/
[09:52] <darkxst> seb128, hi
[09:52] <darkxst> did you ever get a change to look over my external panels for g-c-c patch?
[09:52] <xnox> Sweetsha1k: libhsqldb-java got bumped higher in saucy-proposed, yet there is build-conflicts on the higher version in the libreoffice package.
[09:53] <xnox> Sweetsha1k: when building just on "saucy" without "saucy-proposed" i get one test failure.
[09:53] <Laney> nope, still no menus even with trunk
[09:53] <Laney> maybe something for attente to look at ;-)
[09:53] <didrocks> Mirv: and no COPYING file in tarball, I think we need to fix that one with the exception
[09:54] <Laney> the styling is kind of weird too for me
[09:54] <Laney> like they don't get the orange background on hover
[09:56] <didrocks> Mirv: shouldn't we have separated qt5 and qtdeclarative packages for the qml part?
[09:56] <seb128> Laney, which scrolling patch?
[09:56] <seb128> darkxst, hey, no, I'm still trying to get the new gtk in first to unblock other things
[09:57] <Laney> seb128: 20_add_alt_screen_toggle_ui.patch
[09:57] <seb128> then I will look at the rdepends
[09:57] <Laney> "Author: ?" is amusing :P
[09:57] <seb128> Laney, where is that? gtk?
[09:57] <Laney> gnome-terminal
[09:57] <seb128> oh
[09:57] <seb128> no idea about that then
[09:57] <Laney> it's for letting you scroll with the mousewheel in the pager (like manpages)
[09:58] <Laney> I guess I can port it to the new gsettings stuff and forward it
[09:58] <seb128> right
[09:58] <seb128> but I wonder if that update is worth it
[09:58] <seb128> seems non trivial
[09:59] <seb128> but we need to get ride of gconf at some point
[09:59] <Laney> right
[10:00] <Laney> I don't think it'll be too hard to fix it up anyway
[10:00] <Laney> of course the other option is to either get rid of the patch or force the config to always be on ...
[10:01] <Mirv> didrocks: ok, I can provide the diff:s. looking at qtpim after that, it hasn't been in archives yet.
[10:03] <didrocks> Mirv: yeah, that's why I'm doing a full review
[10:03] <seb128> yeah, qt 5.0.2 in the archive
[10:03] <seb128> didrocks, Mirv: well done ;-)
[10:04] <sil2100> \o/
[10:04] <didrocks> sil2100: do you mind running the unity stack if all the FTBFS are fixed?
[10:05] <sil2100> didrocks: without rebuilding, yes? I think the FTBFS are all fixed in the PPA by now
[10:05] <didrocks> sil2100: yeah, so with "foo" :
[10:05] <didrocks> :)
[10:05] <didrocks> and qtsensors sponsored
[10:05] <sil2100> didrocks: just did that ;) Let's see how the check job goes *keeps his fingers crossed*
[10:06] <didrocks> :)
[10:09]  * didrocks starts building qtwebkit
[10:11] <Laney> didrocks: I pinged Riddell about that one the other day - perhaps check he's not looking at it too
[10:11] <Laney> (assuming you mean the sponsor request)
[10:11] <Laney> (it was because he had a version stuck in proposed)
[10:11] <didrocks> Laney: yeah, well, I started to build with qt 5.0.2, so we need to update for everything now, will ping him
[10:11] <Laney> sure
[10:11] <didrocks> Laney: in proposed?
[10:11] <Laney> https://launchpad.net/ubuntu/+source/qtwebkit-source/2.3.0-0ubuntu3
[10:11] <Laney> if you mean this source
[10:12] <didrocks> Laney: ah, I mean qtwebkit-opensource-src
[10:12] <didrocks> which is the Qt5 version :)
[10:12] <Laney> aha
[10:12] <Laney> carry on :P
[10:12] <didrocks> ;-)
[10:13] <didrocks> qtsvg synced
[10:14] <seb128> Laney, did you handle the clutter MRs yesterday through your sync? they are still in the sponsoring queue
[10:14] <didrocks> as well as qtimageformats, qttranslations was already in proposed
[10:14] <Laney> seb128: let's see ...
[10:14] <didrocks> Mirv: don't forget qtdeclarative for the diff at the top!
[10:17] <Mirv> didrocks: yes, just added after assuming you want that too :)
[10:17] <didrocks> Mirv: perfect! looking at those while qtwebkit is building
[10:17] <didrocks> Mirv: qtquick1 is fine, I'm just waiting to build the other to have all build-deps :)
[10:18] <darkxst> seb128, ok, yes we need gtk, just a little bit! ;)
[10:18] <Laney> not sure what to do with the MP for an uploaded SRU
[10:18] <Laney> darkxst: https://code.launchpad.net/~darkxst/ubuntu/raring/clutter-1.0/lp963925/+merge/164832 can you mark it merged maybe?
[10:19] <Laney> to get it off the sponsoring list as it's in the upload queue now
[10:19] <darkxst> Laney, done
[10:19] <Laney> ty
[10:20] <seb128> darkxst, do you know if anyone looked at the software-center issue?
[10:20] <didrocks> Mirv: hum, as 5.0.2-2 is not released
[10:20] <darkxst> seb128, the crash
[10:20] <seb128> yes
[10:20] <darkxst> ?
[10:20] <didrocks> Mirv: in debian, I won't call ours 5.0.2-2ubuntu1
[10:21] <darkxst> I have never been able to reproduce it
[10:21] <didrocks> Mirv: I'll remove the debian/changelog and add the cherry-pick as 5.0.2-1ubuntu1
[10:21] <seb128> darkxst, the last issue listed on https://blueprints.launchpad.net/ubuntu/+spec/desktop-gnome-3-8
[10:21] <seb128> it seems the only remaining blocker
[10:21] <seb128> or maybe we should just upload...
[10:22] <Laney> the screenshot/cheese thing is fixed?
[10:22] <seb128> screenshot is since 3.8.1
[10:22] <seb128> (just edited the whiteboard)
[10:22] <seb128> what is the cheese issue?
[10:22] <Mirv> didrocks: that's correct, thanks. there are some newer updates in Debian, though, but at the time of that sync the -2 was not yet uploaded
[10:22] <seb128> I don't use cheese
[10:22] <seb128> but I can test...
[10:22] <Laney> same thing
[10:22] <Laney> flashes the screen
[10:22] <seb128> ok, so yeah, it's fixed
[10:22] <didrocks> Mirv: let's use that one ;) (pushed for qtdeclarative)
[10:23] <Mirv> didrocks: thanks
[10:23] <Laney> right, good - none of the bugs or the BP have any indication of that
[10:23] <seb128> I've updated the BP
[10:23] <seb128> upstream ignored the bug mterry opened but fixed following an IRC ping
[10:24] <Laney> fair enough, probably can close that one then
[10:24] <seb128> yep
[10:24] <seb128> I don't have issues with s-c either
[10:24] <darkxst> seb128, I would say go ahead with the upload, there really hasnt been much noise about the software-center crash
[10:24] <seb128> does anyone is running gtk 3.8 and has?
[10:25] <Laney> we can do the trick of blocking it in proposed and watching jenkins for regressions too maybe
[10:25] <seb128> darkxst, well "noise", quite some users seem affected
[10:26] <seb128> Laney, let's do that, can you put the block?
[10:26] <Laney> yes
[10:26] <seb128> thanks
[10:26] <darkxst> seb128, there was a real crash earlier on
[10:26] <seb128> darkxst, ok, maybe it has been fixed ;-)
[10:27] <Laney> blocked
[10:28] <seb128> Laney, thanks, I'm doing a test build on current saucy to make sure everything is still alright (like if it builds with the new glib) and I will upload to saucy after lunch
[10:29] <Laney> excellent
[10:29] <Laney> I'm leaning to porting this gnome-terminal patch without the UI bits
[10:29] <Laney> defaulting to on
[10:29] <seb128> wfm
[10:29] <Laney> the text didn't make sense anyway
[10:29] <Laney> who knows what "alternate scrolling" is?!
[10:30] <seb128> seems like an old geeky option ;-)
[10:30] <Laney> it's some technical term from within vte
[10:30]  * Laney shrugs
[10:32] <Laney> mmm, gvim's gotten its menus back in the window too
[10:35] <darkxst> Laney, I think that gnome-terminal patch, breaks the scroll back when not using overlay scrollbars
[10:38] <Laney> yeah?
[10:38] <Laney> that would be weird
[10:38] <darkxst> Laney, well like when you scroll back to pause the output
[10:38] <darkxst> it doesnt work, with alternate scrolling enabled
[10:38] <darkxst> it will just keep scrolling
[10:38] <Laney> right, I can understand effects like that
[10:39] <Laney> but having an interaction with overlay scrollbars
[10:39] <darkxst> well I don't use the overlay scrollbars, but I am sure it did work with them and not without
[10:41] <Laney> ok, well I'll PPA it when done and we can see
[10:41] <darkxst> ok
[10:53] <didrocks> Mirv: ok, sponsored everything I can but qtwebkit that is still building, I let the rest on your hands :)
[10:53] <didrocks> Mirv: on the sdk side, is it ok to rerun the stack?
[10:53]  * didrocks wants to have everything published today
[10:54] <didrocks> Mirv: also, file a bug for the binary packages we need to remove
[10:54] <czajkowski> andrewebdev: ello :0
[10:54] <andrewebdev> hi
[10:55] <andrewebdev> morning all. Am in a spot of trouble here: http://askubuntu.com/questions/298881/13-04-unity-graphics-suddenly-broken-for-no-reason
[10:55] <Mirv> didrocks: qtpim updated with copyright info and license files which I also submitted to upstream
[10:55] <didrocks> ok, nice :)
[10:55] <didrocks> Mirv: did you see my question about separate packages?
[10:56] <Mirv> ok to run sdk stack
[10:56] <didrocks> doing
[10:56] <Mirv> didrocks: ok, going to file the bugs
[10:56] <Mirv> didrocks: right, what did you mean with the qt5 <-> qml separation again?
[10:56] <joetacos> how do i get pass the Ubuntu 13.04 installer it hangs after clicking 3rd party and download updates. and sometimes i get a black screen with text
[10:56] <andrewebdev> Since my /home/ folder is on a separate partition, I was wondering if some faulty unity setting is stored in my home folder. Is there anyway I can delete all unity settings safely?
[10:56] <czajkowski> didrocks: morning do you know best andrewebdev could ask for him with his question on AU ?
[10:56] <didrocks> Mirv: IIRC, the qmldir packages were separated in <something>-plugin package
[10:57] <didrocks> czajkowski: andrewebdev: I would say go on #ubuntu-unity and ask here, upstreams unity are there
[10:57] <andrewebdev> :)
[10:57] <andrewebdev> ok
[10:57] <didrocks> but seeing the corruptions, it can be as well something for mlankhorst ^
[10:58] <didrocks> and tjaalton :)
[10:58] <czajkowski> didrocks: thanks
[10:58] <didrocks> yw ;)
[10:58] <mlankhorst> we didn't touch raring in any way yet
[10:58] <mlankhorst> so I would guess kernel
[10:58] <didrocks> andrewebdev: #ubuntu-kernel then
[10:59] <Mirv> didrocks: ah, for qtpim, probably that yes still
[11:00] <didrocks> Mirv: ok :)
[11:00] <Mirv> didrocks: qttools resynced with Debian
[11:00] <mlankhorst> pitti: can autopkgtest descend subdirectories too?
[11:00] <didrocks> Mirv: ok, will have a look after running outside (finishing an upload first)
[11:01] <didrocks> Mirv: qtmultimedia-opensource-src FTBFS here
[11:01] <pitti> mlankhorst: how do you mean?
[11:01] <didrocks> Mirv: the symbols are not up to date
[11:01] <pitti> mlankhorst: oh, you mean tests in debian/tests/subdir? I'm not actually sure
[11:01] <pitti> mlankhorst: if you specify them that way in debian/tests/control it might work, but we never had such a case so far
[11:02] <Mirv> didrocks: right, Debian seems to have done the updates after uploads, collecting from builders or something like that
[11:02] <Mirv> (symbol updates)
[11:03] <mlankhorst> pitti: can I test the Tests-Directory to some system path? right now I'm installing a bunch of tests to /usr/lib/xorg-integration-tests/SUBDIR/testname, so if I could set the Tests-Directory: to /usr/lib/xorg-integration-tests I could just specify the tests to run directly :)
[11:03] <Mirv> but have not done that for qtmultimedia yet
[11:04] <didrocks> Mirv: ok, waiting for this one :)
[11:05] <Mirv> looking at the symbols after qtpim
[11:05] <mlankhorst> hm I guess not
[11:10] <mlankhorst> ah well, I'll write a script to invoke it for me then. :)
[11:10] <pitti> mlankhorst: no, you'll need symlinks for that; they must be in debian/tests/
[11:10] <pitti> or a wrapper script which iterates over them, right
[11:17] <pitti> hm, what the heck is wrong with gstreamer apps in saucy? totem and rhythmbox take like 30 seconds to start
[11:20] <seb128> pitti, wfm
[11:20] <seb128> pitti, but rb segfaults on track changes on g-i code
[11:21] <seb128> not sure if that's buggy code on the rb side or something wrong in the g-i stack though
[11:22] <seb128> ok, gtk 3.8 on its way to saucy-proposed, let's see how that goes
[11:23] <seb128> pitti, do you get any error during those 30s? can you get a gdb stacktrace to see where it's hanging?
[11:25] <pitti> seb128: hm, I'll try after lunch
[11:26] <pitti> seb128: no, when I start them from a terminal there is no output at all (nor an apport .crash)
[11:26] <seb128> weird
[11:26] <pitti> [pid  4734] poll([{fd=10, events=POLLIN}], 1, 25000
[11:26] <pitti> strace is just sitting there
[11:26] <seb128> what about gdb?
[11:27] <pitti> g_main_context_poll()
[11:27] <seb128> weird...
[11:27] <pitti> ah, further down is g_dbus_connection_send_message_with_reply_sync()
[11:27] <pitti> i. e. it's a temp main loop from gdbus sync (waiting for reply)
[11:28] <pitti> ooh, hang on
[11:28] <pitti> sorry, PEBCAK
[11:28] <pitti> it was talking to gvfs-udisks2-volume-monitor, which was in STOPped state
[11:28] <pitti> (fallout from me running udisks2 tests this morning)
[11:28]  * pitti grabs brown paperbag
[11:29] <seb128> pitti, k ;-)
[11:29] <seb128> still annoying that we have sync calls in there
[11:30] <seb128> the multimedia players shouldn't block on gvfs to start
[11:39] <mlankhorst> pitti: hm server/server        SKIP Test breaks testbed but testbed does not advertise revert-full-system
[11:40] <mlankhorst> is breaks-testbed needed if temporary virtual input devices will be added, that can mess up if you are using the system for something else at the moment?
[12:00] <Mirv> didrocks: qtpim updated again, same for qttools. interestingly qtmultimedia does not complain about symbols when I build it in pbuilder, only when I build it locally
[12:01] <Mirv> didrocks: oh, but, I'm using raring. creating a saucy pbuilder.
[12:02] <attente> sil2100, hey
[12:03] <attente> Laney, are your gnome-terminal menus still broken?
[12:03] <Laney> attente: this is with 3.8 that I'm preparing, and yes
[12:03] <sil2100> attente: hello! Again about u-g-m
[12:04] <sil2100> attente: I have been wondering... what would need to be done to be able to use unity-gtk3-module when appmenu-gtk3 is still installed? Will some patch have to be dropped from somewhere?
[12:06] <attente> Laney, it's just gnome-terminal? everything else is ok?
[12:07] <sil2100> attente: I'm asking because hm, I prepared the packaging changes for u-g-m to replace appmenu-gtk, but since u-g-m is part of the unity stack, it's installation would remove appmenu-gtk and even the unity tests would currently run on u-g-m
[12:07] <Laney> attente: gvim too
[12:07] <attente> sil2100, are you asking about having both installed and being able to switch on-demand?
[12:07] <sil2100> attente: yes, for instance
[12:08] <sil2100> attente: since currently, I think we would prefer to test unity in the standard environment (i.e. with appmenu-gtk), and only unity-gtk-module-autopilot tests with the unity-gtk-module instead
[12:08] <sil2100> Not all of them with u-g-m, at least not yet until we won't make the official switch
[12:09] <Laney> gvim gives some criticals: ** (gvim:1430): CRITICAL **: gtk_widget_shell_shows_menubar: assertion `G_IS_PARAM_SPEC (pspec)' failed
[12:10] <seb128> sil2100, we will do the change once you manage to land that package in saucy
[12:10] <attente> sil2100: the difficulty is that appmenu-gtk depends on the gtk patch and u-g-m depends on not having the patch
[12:10] <seb128> sil2100, it's easy enough, don't plan for the overlap period there
[12:10] <seb128> just land the thing so we can drop the gtk patches and everyone will be happy
[12:10] <sil2100> Ok then ;)
[12:15] <desrt> good morning, all
[12:15] <sil2100> Morning!
[12:17] <mlankhorst> g'day!
[12:19] <seb128> hey Canada ;-)
[12:20] <didrocks> urgh sun…
[12:20] <seb128> didrocks, time for exercice?
[12:21]  * didrocks went for running and enjoyed the only 30 minutes with rain of the day it seems…
[12:21] <didrocks> and not a small one
[12:21] <seb128> oh, you did already :/
[12:21]  * didrocks needs a shower
[12:21] <didrocks> yeah, wrong decision it seems!
[12:21] <seb128> didn't you just had one outside? :p
[12:21] <didrocks> seb128: tssss :p
[12:21] <seb128> ;-)
[12:21] <didrocks> seb128: when I was cycling, no issue
[12:21] <didrocks> just when I arrived at the park
[12:21] <didrocks> and for the full run in the park
[12:21] <seb128> k
[12:22] <seb128> you better take a warm shower now
[12:22] <seb128> or you will get a cold
[12:22] <didrocks> then, back on the bike, I had some time to just catch a cold :p
[12:22] <didrocks> seb128: yeah, I'm just starting some pbuilder
[12:22] <didrocks> and then, shower :)
[12:22] <mlankhorst> it's still bad here
[12:22] <mlankhorst> http://buienradar.nl/
[12:22] <didrocks> mlankhorst: almost blue sky, I really regret :p
[12:23] <seb128> we have some sun showing as well, weird
[12:23] <Laney> attente: you can grab gnome-terminal from http://people.canonical.com/~laney/package-junkyard/ if you want to try it out for yourself
[12:23] <Laney> I noticed that I don't get overlay scrollbars at all on it ...
[12:23] <didrocks> seb128: it's like "what's this?" :p
[12:23] <mlankhorst> it doesn't look like we get this thing called 'sun' today
[12:24] <seb128> didrocks, exactly ;-)
[12:34] <Mirv> didrocks: ok, updated qtmultimedia's libqgsttools symbols for saucy
[12:36] <didrocks> Mirv: thanks, continuing sponsoring the small components :)
[12:37] <Sweetsha1k> hmm, "28 affected users, bug heat 130" in one day for a package in a PPA --- is that a new record?
[12:38] <mlankhorst> is it about libreoffice?
[12:38] <Mirv> didrocks: btw sdk stack now would have published successfully, but qa stack has failed again so it did not
[12:38] <didrocks> Mirv: so manual publish?
[12:39] <Mirv> didrocks: yes, hmm
[12:39] <Mirv> -, hmm
[12:39] <Mirv> the ticket for access rights is still ongoing
[12:39] <didrocks> Mirv: yeah, you did receive an email when I opened it, right?
[12:41] <Mirv> didrocks: yes, and I was asked whether I want the access rights to the existing account (yes), waiting for next message
[12:41] <didrocks> ok :)
[12:41] <didrocks> Mirv: you can directly ping retoaded on IRC to speed things up
[12:41] <didrocks> (he's in the US time)
[12:41] <didrocks> Mirv: meanwhile, published for you
[12:42] <Mirv> didrocks: ok. thanks.
[12:42] <Sweetsha1k> mlankhorst: yes, bug 1182082
[12:42] <ubot2> Launchpad bug 1182082 in LibreOffice Productivity Suite "libreoffice menu not working" [Medium,Won't fix] https://launchpad.net/bugs/1182082
[12:42] <didrocks> yw :)
[13:08] <didrocks> Mirv: doc/src/snippets/legal/CatharonLicense.txt is mentionning Catharon Productions, Inc.
[13:08] <didrocks> in qtpim
[13:08] <Mirv> didrocks: it's mentioning it, but I didn't find a file that would be covered by it (it's the license itself)
[13:09] <Mirv> no files mention [C/c]atharon in any other way
[13:09] <didrocks> Mirv: you should open a bug upstream
[13:09] <didrocks> Mirv: otherwise, fine with me :)
[13:09] <Mirv> didrocks: yes, ok
[13:11] <didrocks> Mirv: for the -plugin package, do you know of anyone installing the pim package already?
[13:12] <didrocks> Mirv: as you didn't provide any Replaces: for the transition?
[13:12] <didrocks> Mirv: also, priority should be optional
[13:13] <didrocks> and also, the -plugin should maybe dep on there binary package which contains the .so files?
[13:14] <didrocks> Mirv: on Qttools, I have a FTBFS on symbols
[13:14] <Mirv> didrocks: no, AFAIK the QML modules have been actually broken before Renato's patch that is in the upstream codereview
[13:14] <Mirv> broken as in functionality
[13:14] <didrocks> Mirv: ok, so no need for replaces: if nobody installed the package
[13:15] <didrocks> Mirv: mind doing the other changes?
[13:15] <Mirv> didrocks: pushed the priority change
[13:15] <Mirv> didrocks: I'm working on qttools, just got the symbols complains in my saucy pbuilder as well
[13:15] <didrocks> Mirv: did you see my question on the dep to finish qtpim?
[13:16] <didrocks> qtdeclarative5-qtcontacts-plugin shold dep on libqt5contacts5?
[13:16] <didrocks> (and same for the other -plugin one)
[13:17] <Mirv> didrocks: oh, that I missed. pushed.
[13:17] <Mirv> opened also upstream QTBUG-31315 to ask for removal / doing something about the Catharon license
[13:17] <didrocks> Mirv: got it, sponsoring qtpim then :)
[13:17] <didrocks> perfect
[13:19] <didrocks> seb128: qtpim in source NEW (at next publish round), mind having a look? there is also qtgraphicaleffects-opensource-src in bin NEW.
[13:19] <seb128> didrocks, ok
[13:19] <didrocks> thanks :)
[13:19] <seb128> yw
[13:48] <didrocks> hey kenvandine, around?
[13:49] <kenvandine> didrocks, hey, what's up?
[13:50] <didrocks> kenvandine: I think you already saw that you have a lot of stack in manual publishing mode, can you handle them quickly so that we can have everything in next today? :)
[13:50] <didrocks> kenvandine: I rebuilt some for you due to UTAH
[13:50] <didrocks> you just need to review the manual publishing :)
[13:50] <didrocks> (media, settings, webapp, webcred)
[13:52] <kenvandine> sure, i was too excited about having gmail this morning... so i started customizing :)
[13:52]  * kenvandine does the happy dance
[13:52] <kenvandine> i'll go look over the stacks now
[13:53] <jbicha> seb128: does the gnome-icon-theme/-full split still make sense?
[13:54] <seb128> jbicha, I guess it does yes, no reason to waste disk space
[13:54] <didrocks> kenvandine: thanks :)
[13:56] <kenvandine> didrocks, so did webcred not publish because QA failed?
[13:56]  * didrocks looks
[13:56] <kenvandine> that's what it looks like to me
[13:56] <didrocks> kenvandine: right
[13:56] <kenvandine> ok
[13:57] <didrocks> kenvandine: I wonder if I shouldn't just declare QA as a safe stack to ignore the status
[13:57] <kenvandine> probably
[13:57] <didrocks> as if tests passed… :)
[13:57] <didrocks> the others deps shouldn't
[13:57] <didrocks> but QA…
[13:59] <kenvandine> media failed because of hud and qa
[13:59] <kenvandine> so maybe that one shouldn't get published
[14:00] <didrocks> kenvandine: ask cyphermox, but I think there is no issue with the HUD that is preventing us to publish
[14:00] <didrocks> or sil2100
[14:00] <didrocks> from what I know, the hud tests failing are false positives
[14:03] <kenvandine> cyphermox, sil2100: can you confirm ^^
[14:03] <kenvandine> didrocks, i checked webapp and webcred, both looked good and i published
[14:03] <kenvandine> settings view isn't setup yet
[14:03] <didrocks> kenvandine: great! :-)
[14:04] <kenvandine> i filed an rt ticket for that
[14:04] <didrocks> kenvandine: so hopefully, tomorrow, we won't have all that spam on the webapps* land :p
[14:04] <kenvandine> :-D
[14:04] <didrocks> kenvandine: http://10.97.0.1:8080/job/cu2d-settings-head-3.0publish/ for the publish
[14:04]  * kenvandine is glad webapps stack is robru's :)
[14:04] <didrocks> ahah :)
[14:04] <kenvandine> oh... so we can still find it :)
[14:04] <didrocks> right, in the head view
[14:04] <didrocks> click on all
[14:05] <didrocks> you will see all "heads" job
[14:05] <didrocks> then, clicking on it, you can see the workflow :)
[14:05] <kenvandine> ugh
[14:05] <kenvandine> http://10.97.0.1:8080/job/cu2d-settings-head-3.0publish/3/console
[14:06] <kenvandine> oh wait...
[14:06] <kenvandine> we didn't want to publish settings anyway :)
[14:06]  * kenvandine is glad it failed
[14:07] <didrocks> kenvandine: well, even if it succeeded, you put it to manual publishing :)
[14:07] <didrocks> kenvandine: see http://10.97.0.1:8080/job/cu2d-settings-head-3.0publish/lastSuccessfulBuild/artifact/publisher.xml
[14:07] <kenvandine> ah, so forcing publishing would still not publish right?
[14:07] <didrocks> kenvandine: ah it would :)
[14:07] <kenvandine> yeah... so glad my force didn't work :)
[14:07] <didrocks> oh, you rerun it :p
[14:07]  * kenvandine needs more coffee
[14:08] <didrocks> bzr: ERROR: exceptions.Exception: UserNotBranchReviewer
[14:08] <didrocks> what's this? :/
[14:08] <kenvandine> no idea!
[14:08] <kenvandine> oh... maybe we need to add one of the ps teams to it?
[14:08] <didrocks> kenvandine: well, it's just a lp-propose, it shouldn't need to be on the team…
[14:09] <didrocks> vila: any idea? ^
[14:09] <didrocks> vila: basically a bot is pushing a branch to a project (under his namespace), and then doing bzr lp-propose to trunk
[14:10] <didrocks> and we get: https://jenkins.qa.ubuntu.com/job/cu2d-settings-head-3.0publish/3/console
[14:10] <didrocks> kenvandine: the copy went through next though
[14:10] <didrocks> kenvandine: you need to remove it if you don't want the package
[14:10] <kenvandine> whoops :)
[14:10] <didrocks> ah, or maybe not, let me check the code :)
[14:11] <kenvandine> it would end up in NEW for saucy
[14:11] <vila> didrocks: out of the blue, I'd say it comes from the plugin implementing lp-propose, bzr itself has no idea what a branch reviewer is
[14:11] <didrocks> kenvandine: ah? it's not for next, right, so no worry, the xml wasn't generated :)
[14:11] <didrocks> vila: do you know who we should poke for lp-propose?
[14:11] <vila> didrocks: does that use to work or is it the first time you try to lp-propose from a bot ?
[14:11] <kenvandine> didrocks, right
[14:12] <vila> didrocks: abentley is the author IIRC
[14:12] <didrocks> vila: we used lp-propose thousands of times from a bot, but this is a new project
[14:12] <didrocks> vila: so I would bet for a configuration issue on the project
[14:12] <vila> didrocks: ha, then may be the teams aren't set up properly ?
[14:12]  * vila nods
[14:12] <didrocks> yeah :)
[14:12] <didrocks> thanks vila, I'll hunt for him :)
[14:13] <didrocks> oh yeah, configuration error!
[14:13] <didrocks> kenvandine: we need the bot to be in the team
[14:13] <didrocks> kenvandine: it's self-approving the branch :)
[14:13] <kenvandine> i figured
[14:13] <kenvandine> what is the bot's id?
[14:14] <didrocks> ps-jenkins
[14:14] <didrocks> (I didn't create yet-another-bot)
[14:14] <kenvandine> didrocks, done
[14:14] <didrocks> thanks!
[14:14] <kenvandine> do '
[14:15] <kenvandine> so we'll be good when we really want to publish :)
[14:15] <didrocks> right :)
[14:15] <didrocks> kenvandine: I wonder, you didn't setup upstream merger though?
[14:15] <didrocks> kenvandine: because you would have the issue way before :)
[14:15] <kenvandine> that's on my todo list for today
[14:15] <kenvandine> :)
[14:16] <didrocks> ahah, ok :)
[14:16] <didrocks> so at least, that step: done :p
[14:16] <didrocks> kenvandine: I checked for media, go for it :)
[14:16] <kenvandine> we had our first branch merged to trunk yesterday
[14:16] <didrocks> (hud just failed because of the tests and that's what we are fixing)
[14:16] <kenvandine> which is when i noticed the merger wasn't setup
[14:16] <didrocks> \o/
[14:16] <kenvandine> ok, /me publishes
[14:16] <didrocks> thanks!
[14:16]  * kenvandine goes to get more coffee
[14:17] <didrocks> kenvandine: hehe, will do the same here :)
[14:17] <didrocks> ok, so once Unity built and tests pass
[14:17] <didrocks> we can redo QA
[14:17] <didrocks> and HUD
[14:17] <didrocks> and live in a wonderful life, with everything for touch in next!
[14:43] <Laney> ricotz: darkxst: How's empathy 3.8.2?
[14:53] <ricotz> Laney, works here, but i only use it with jabber
[14:53] <Laney> k
[14:53] <ricotz> Laney, i needs folks 0.9 first of course
[14:53] <ricotz> it
[14:54] <ricotz> which can be synced from debian
[14:54] <ricotz> irc 0.9.1-2
[14:54] <Laney> right, need to check if that can be synced
[14:54] <Laney> unless you want to
[14:55] <ricotz> the version is gnome3-staging ppa is already a sync
[14:56] <cyphermox> kenvandine: yeah, hud is fine to publish, I can do it...
[15:02] <kenvandine> cyphermox, thx
[15:16] <attente> Laney: are you able to run gedit through your gnome-terminal?
[15:19] <cyphermox> kenvandine: fwiw I can't get any search results out of hud... :/
[15:19] <cyphermox> scratch that, it's just really slow
[15:19] <kenvandine> on the device or desktop?
[15:19] <cyphermox> on desktop
[15:20] <Laney> attente: huh, apparently not
[15:24] <Laney> attente: what's going on there then?
[15:25] <attente> i'm not sure about the gnome-terminal problem, but the gvim problem is just because of a missing GtkSetting in gtk 2
[15:36] <Sweetshark> jibel: ping?
[15:37] <Sweetshark> jibel: http://people.canonical.com/~j-lallement/libreoffice/binrepo/ <- shows 08-May-2013 as date, any hint why it isnt updated since then?
[15:37] <jibel> Sweetshark, hm, looking
[15:38] <Laney> haha!
[15:39] <Laney> attente:
[15:39] <Laney>   /* Set some env vars to disable ubuntu crap. They'll certainly patch this
[15:39] <Laney>    * out in their package, but anyone running from git will get the right
[15:39] <Laney>    * behaviour.
[15:39] <Laney>    */
[15:39] <Laney>   g_setenv ("LIBOVERLAY_SCROLLBAR", "0", TRUE);
[15:39] <Sweetshark> Laney: lol!
[15:39] <Laney>   g_setenv ("UBUNTU_MENUPROXY", "0", TRUE);
[15:39] <Laney>   g_setenv ("NO_UNITY_GTK_MODULE", "1", TRUE);
[15:39]  * Laney coughs
[15:39] <Laney> UBUNTU ♥ GNOME
[15:43] <Laney> attente: so yeah, that made menus work ... don't know what's up with gedit though
[15:43] <mlankhorst> how evil
[15:45] <kenvandine> oh my!
[15:45] <mlankhorst> https://git.gnome.org/browse/gnome-terminal/commit/?id=564d75080206c9d1e1d750bf45a7c35999cd511e
[15:46] <Laney> oh well
[15:46] <kenvandine> no love!
[15:52] <jibel> Sweetshark, configure: error: unrecognized options: --disable-mozilla, --disable-binfilter introduced by commit df4fd344b7b5d5dfb7cbf2f7a91ed6e86a2aaef8 which make them fatal
[15:53] <jibel> Sweetshark, I'll fix configure and figure out why the job thinks its a good build
[15:54] <attente> Laney, fun stuff..
[15:54] <Sweetshark> jibel: ah yeah, those are obsolete now ;)
[15:54] <Sweetshark> .oO(good riddance)
[15:59] <jibel> Sweetshark, done. The failed builds will be retried tomorrow
[16:00] <Sweetshark> jibel: awesome, thanks!
[16:00] <Sweetshark> jibel: I gave you kudos on the libreoffice list already. ;)
[16:00] <Sweetshark> .oO(cheerleading is my second best talent)
[16:03] <jibel> Sweetshark, heh, thanks!
[16:10] <Laney> yum upgrade to rawhide takes ages to calculate
[16:12] <seb128> didrocks, hey, is there any chance you guys could run all your tests again the new gtk in saucy-proposed to see if it creates any issue (Laney blocked the migration to saucy to let us run tests and stuff before it goes there)
[16:12] <didrocks> seb128: everything is running in raring, do you have a raring ppa?
[16:12] <didrocks> seb128: that would help
[16:12] <seb128> didrocks, ubuntu-desktop ppa has it for raring
[16:12] <didrocks> seb128: will do that tomorrow
[16:12] <seb128> didrocks, thanks
[16:12] <Laney> did the jenkins autopkgtests kick off against it yet?
[16:13] <seb128> Laney, is that autohappening by magic?
[16:13] <Laney> yeah
[16:13] <Laney> for rdeps afaik
[16:13] <didrocks> you mean for unity?
[16:13] <didrocks> or the rest?
[16:14] <Laney> not the same as the daily landing integration tests of course
[16:14] <Laney> archive autopkgtests
[16:15] <didrocks> we don't have any for unity, but I guess, the rest is in jibel's capable hands for the rest of the archive :)
[16:15] <Laney> yeah, that stuff - it works
[16:15] <didrocks> Laney: seb128: mind just poking me about it (the autopilot tests) tomorrow?
[16:15] <Laney> https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/ but doesn't look like it's been triggered yet (looking at "latest builds")
[16:17] <didrocks> Laney: you don't have dynamic view on this jenkins
[16:18] <Laney> oh, I see
[16:18] <Laney> I can never remember how to get to the other one
[16:18] <didrocks> I don't know what jenkins it is for autopkgtests
[16:18] <Laney> plus it's not so good for talking in this channel :-)
[16:20] <Laney> http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/ anyway (for those not blessed with access, it shows that the jobs haven't started yet)
[16:22] <seb128> Laney, do we know when they will start, what trigger them?
[16:23] <Laney> A job which jibel runs on lillypilly
[16:23] <Laney> was just looking for the data but I can't remember where it is
[16:23] <seb128> ok
[16:24] <seb128> it's good that we are doing testing and stuff, but it's still not really obvious what is tested, how and when (at least to me)
[16:24] <Laney> well, the proper plan for autopkgtest is to have it integrated with britney to stop migration
[16:25] <Laney> for that you'll have to have an interface better than jenkins (probably not a difficult task ...)
[16:26] <jibel> seb128, tests will start when a new binary or a new binary dependency on a Source package with an XS-Testsuite header with the value of autopkgtest is available in the archive.
[16:27] <seb128> jibel, where archive is -proposed or archive proper?
[16:27] <Laney> seb128: ah, I found the list - on lillypilly, do: grep -h gtk+3.0 ~j-lallement/QA/adt-data/adt/saucy-proposed/amd64/archive/2013/05/23/*
[16:27] <jibel> seb128, -proposed
[16:28] <seb128> jibel, thanks
[16:29] <seb128> Laney, seems like it worked, like ubiquity got a run after the upload: http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt-ubiquity/
[16:29] <seb128> same for apport
[16:30] <jibel> seb128, there is some details here http://bazaar.launchpad.net/~auto-package-testing-dev/auto-package-testing/trunk/files/head:/doc/
[16:30] <Laney> I wonder if there has ever been a time that I've not had to reconnect to the VPN before using it
[16:31] <seb128> jibel, cool
[16:31] <Laney> oh yes indeed, they have been run
[16:31] <Laney> I was looking for ones which started later
[16:31] <seb128> Laney, ok, looking at "latest rebuilds", they are all green, or were red before
[16:31] <Laney> so green is good ...
[16:31] <seb128> no test that started failing in that run
[16:31] <seb128> so let's wait for the unity tests tomorrow and unblock it if that's ok?
[16:32] <Laney> sgtm
[16:32]  * Laney pushes gnome-terminal to bzr but this gedit problem is really weird
[16:32] <Laney> why wouldn't it run from a terminal?!
[16:35] <desrt> seb128: let's step up our game
[16:35] <desrt> Laney: i have an idea
[16:35] <desrt> let's modify our gtk patches to check if the executable name is "gnome-terminal"
[16:35] <desrt> and if so, ignore all environment variables
[16:36] <attente> doesn't that just make it even more broken for us?
[16:37] <desrt> in order to ensure that users of unpatched git versions of gnome-terminal 'will get the right behaviour' :)
[16:38] <Laney> Ignore profiles, force username to chpe
[16:38] <desrt> i suspect we will never find someone with the username 'chpe' on an ubuntu system :)
[16:40] <didrocks> you are evil guys :)
[16:42] <desrt> meh
[16:42] <desrt> if someone starts to play a game then you should probably make a countermove :)
[16:42] <desrt> ignoring them would just be rude
[16:42] <didrocks> heh
[16:51] <tvoss> desrt, ping
[16:51] <desrt> hey
[16:51] <desrt> round 2?
[16:52] <tvoss> desrt, hey, I'm actually waiting for ricmm to reply to my ping. It's more important that you guys talk :)
[16:52] <sarnold> modify git to remove that code on clone?
[16:52] <tvoss> desrt, might be a good idea to join #ubuntu-touch, too
[16:52] <desrt> too many channels :p
[16:53] <tvoss> desrt, likewise, but a lot of the lifecycle and app model discussions are happening there
[16:55] <jbicha> Laney: were you aware that gnome-terminal was packaged in the gnome3-staging ppa?
[16:56] <Laney> jbicha: I wasn't, then I was, but it wasn't bad anyway
[16:56] <Laney> do you see the gedit weirdness under shell?
[16:58] <jbicha> Laney: uh I haven't had problems with gedit yet except for bug 1182849
[16:58] <ubot2> Launchpad bug 1182849 in Ubuntu GNOME "Some plugins hang gedit" [Undecided,New] https://launchpad.net/bugs/1182849
[16:58] <Laney> the bug here is that you can't launch it from gnome-terminal 3.8 - it hangs
[17:00] <jbicha> it works here but I did have a hang problem until I ran gsettings reset-recursively org.gnome.gedit
[17:02] <jbicha> Laney: also bug 1181393
[17:02] <ubot2> Launchpad bug 1181393 in vte3 (Ubuntu) "Please upgrade to 0.34.5" [Wishlist,New] https://launchpad.net/bugs/1181393
[17:02]  * didrocks waves good evening
[17:02] <Laney> night did
[17:02] <Laney> speedy!
[17:02] <Laney> jbicha: yeah that's on my list for tomorrow
[17:03] <Laney> I don't really have a handle on how to fix bash/zsh to source it though
[17:06] <Laney> not necessarily a blocker of course
[17:09] <jbicha> well it's an annoying regression and nothing really *needs* gnome-terminal 3.8
[17:09] <Laney> sure
[17:10] <Laney> I mean that it's not a blocker for gnome-terminal if the fix is in the shells
[17:11] <jbicha> on the other hand if we want it in 13.10 it's probably better to land it soonish because of the potential for other regressions with the gsettings conversion
[17:11] <jbicha> although I've not really bumped into anything serious
[17:12] <Laney> this gedit thing is disturbing
[17:13] <Laney> ah, 3.8 fixes it
[17:20] <Laney> we have a gtksourceview transition too
[17:23] <seb128> Laney, right, jbicha started that one, I hope it deals with the rdepends as well ;-)
[17:24] <seb128> jbicha, btw please don't start a transition without having the rebuilds ready to follow
[17:24] <Laney> it might have been better to wait until gtk was definitely ready
[17:24] <seb128> yes :/
[17:24] <Laney> oh well
[17:26] <jbicha> I didn't notice that it was a transition :(
[17:27] <Laney> it's not exactly huge
[17:27] <Laney> should be fine
[17:28] <desrt> Laney: http://paste.fedoraproject.org/14052/69329903/
[17:28] <desrt> Laney: chpe conditionalised his setenving
[17:28] <Laney> haha
[17:28] <desrt> you can just ./configure --enable-distro-packaging to disable it now
[17:28] <Laney> that's funny, thanks for poking
[17:29] <desrt> it also no longer pointlessly sets those vars on non-ubuntu systems
[17:29] <Laney> good grief, how can fedora still be calculating this upgrade?
[17:29] <Laney> can yum get stuck in a loop?
[17:29] <desrt> lol
[17:29] <desrt> never underestimate just how bad yum is
[17:30] <Laney> I figured out the problem so don't need to check on rawhide anyway, but now I'm curious as to whether it will finish ...
[17:32]  * Laney leaves it on for a bit and goes off to mow the lawn
[17:32] <Laney> tata
[18:38] <chrisccoulson> Laney, just been out to stirchley wines to get some beer ;)