[00:01] <cyphermox> yeah
[03:48] <Mirv> hello
[04:02] <cyphermox> Mirv: hey
[04:02] <cyphermox> I just CC you for an email with the indicators failures
[04:02] <cyphermox> I'm off to bed now
[04:12] <pitti> Good morning
[04:34] <Mirv> cyphermox: ok, thanks
[04:34] <Mirv> morning pitti
[04:34] <pitti> hey Mirv
[07:31] <sil2100> Morning!
[07:32] <Mirv> hello sil2100
[07:45] <darkxst> pitti, hi
[07:46] <darkxst> have you ever tried using python3-pam? it won't even load here ;(
[07:46] <pitti> darkxst: no, I didn't (neither the py2 variant)
[07:46] <darkxst> py2 variant seems to work, but ubiquity-dm is py3
[07:47] <Mirv> sil2100: I contacted the SDK team about the unity8 problem now
[07:49] <Mirv> sil2100: btw when time and before next tick, please check the merge requests from the status page
[07:50] <darkxst> pitti, is there some that is needed to register the module?
[07:51] <darkxst> in python3 I get ImportError: No module named 'PAM'
[07:51] <darkxst> even though it is installed
[07:57] <sil2100> Mirv: ACK
[07:57] <sil2100> Mirv: thanks for dealing with that, I still am a bit amazed that this got pass, if they say it's as bad as it is
[07:58] <sil2100> But anyway, damn, when you started it was all broken anyway, and now even more work...
[07:58] <Laney> guten morgen
[07:59] <sil2100> Mirv: the problem seemed that SDK didn't run any unity8 tests, right? Since I guess if it released, the change didn't break any SDK or Apps tests
[08:00] <sil2100> Mirv: sadly it's not possible for us to run unity8 tests alongside SDK ;/
[08:04] <Mirv> sil2100: yeah, the apparmor+dbus uploads from yesterday seem to cause breakage all over
[08:04] <dpm> morning Laney, while testing the background change functionality in the settings app, I changed the background at some point, but I cannot change it back to the default now. So in summary: help, I'm stuck with the snail background! :)
[08:04] <Mirv> sil2100: yes, the mergers only run unit tests which is at least part of the problem
[08:04] <Laney> dpm: we disabled that for now, so that'll be why
[08:05] <Laney> in fact it never really worked
[08:05] <Laney> do a dconf reset on the key
[08:05] <dpm> which one is it?
[08:05] <Laney> erm
[08:06] <Laney> maybe /org/gnome/desktop/background/picture-uri
[08:07]  * sil2100 sighs
[08:16] <seb128> good morning desktopers
[08:19] <seb128> just for info, new dbus in saucy-proposed is creating issues with tests using dbus
[08:20] <sil2100> Morning!
[08:20] <seb128> tyhicks is working on it
[08:20] <seb128> "the test cases that are ran on the buildds are broken because dbus-daemon now calls aa_is_enabled() in libapparmor"
[08:20] <seb128> "on the buildds, that is returning an error and dbus-daemon is refusing to start :/"
[08:20] <seb128> " that problem is easy to fix and I have a patch in the works - I need to verify that the other test failures are caused by that same issue"
[08:20] <seb128>  
[08:20] <seb128> </status update>
[08:20] <seb128> hey sil2100
[08:22] <seb128> pitti, hey
[08:23] <pitti> hey seb128, bonjuor
[08:23] <seb128> pitti, salut, ça va bien ?
[08:23] <pitti> seb128: FYI, I removed the broken libgtkada from -proposed again
[08:23] <pitti> seb128: oui, et toi ?
[08:23] <sil2100> Thanks for the update! Some of our problems might have been also caused by that
[08:23] <seb128> pitti, très bien, merci !
[08:23] <seb128> pitti, thanks
[08:23] <pitti> seb128: so jenkins is green again, and the FTBFS not an issue any more
[08:23] <sil2100> I jump out for a moment now, since yesterday after UDS it was already too late to do anything ;p
[08:23] <pitti> seb128: ah, I'll as jibel about the excuses for cairo
[08:23] <seb128> pitti, weird, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html still says it is
[08:24] <seb128> pitti, did you just remove it
[08:24] <seb128> or do we need jibel to trigger an update?
[08:24]  * Laney begins updating gst
[08:24] <pitti> seb128: cf. #u-devel
[08:24] <seb128> when things are updated is still magic to me
[08:24] <seb128> danke
[08:25] <seb128> sil2100, how did vUDS track hosting go?
[08:25] <seb128> Laney, hey, good luck with the update ;-)
[08:25] <Laney> scared
[08:41] <seb128> sil2100, Mirv: bug #1051921 is in the sponsoring queue, does it need to be or is that going to be part of the next precise SRU?
[08:41] <ubot2`> Launchpad bug 1051921 in Unity 5.0 "lens-bar-keynavigation periodically writes to /tmp/wut.png" [Medium,In progress] https://launchpad.net/bugs/1051921
[08:44] <Mirv> seb128: that's been handled by others. if it's a potential security issue then cherrypicking would be ok. the 5.0 branch otherwise is stalling on the XIM question.
[08:45] <Mirv> (and testing etc as usual for old style SRUs)
[08:52] <seb128> larsu, sil2100, Mirv: I deleted the buggy dbus from saucy-proposed (they are going to reupload it once they fixed the issue), next indicator run should be green
[08:52] <seb128> sil2100, Mirv: let's wait for a publisher run (so the change is in effect) and we can retry the indicators stack
[08:58] <Mirv> ok. first on my list is the sdk stack which is about to be published soon, hopefully after the publisher run
[09:00] <Mirv> right, it should be fine
[09:05] <Mirv> seb128: I'd guess publisher run has now happened, or how often does it?
[09:06] <seb128> Mirv, "less than half an hour", you can check with "rmadison -S dbus", doing that
[09:08] <seb128> Mirv, not done yet it seems
[09:08] <Mirv> it should say 1.6.12-0ubuntu2 for proposed as well, or nothing?
[09:08] <Mirv> ok, let's wait
[09:11] <seb128> Mirv, it shouldn't have a proposed line
[09:13] <seb128> Mirv, ok, we are good
[09:18] <Mirv> so it seems, relaunching indicators
[09:31] <Mirv> sil2100: please, the MP:s :)
[09:38] <Mirv> well, I can deploy the phone config anyhow
[09:41] <Sweetshark> *grmbl* why are we using this hangouts crap. Still doesnt work
[09:41] <Mirv> Sweetshark: because there is no free replacement
[09:42] <Mirv> but yes, it's relatively crap from user experience point of view (at least on x86 linux)
[09:43] <Sweetshark> Mirv: mumble is a perfect replacement, if you can live without looking at 6-10 distracted nerds that never look straight at the screen but all over the place to check IRC, etherpad, blueprints and whatnot.
[09:44] <czajkowski> Mirv: seems to be worse this time I tried to join a few hangouts yesterday to watch and they dropped
[09:44] <Mirv> Sweetshark: technically correct answer
[09:44] <Mirv> czajkowski: ok, I had no problems but maybe there are networking issues within the infrastructure or something
[09:44] <czajkowski> possibly.
[09:45] <darkxst> xnox, lp:~darkxst/ubiquity/lp1204312
[09:45] <Mirv> Sweetshark: it'd need autouploading of recordings somewhere, though (mumble)
[09:45] <Mirv> and live streaming of pure audio without client
[09:48] <sil2100> Mirv: ;)
[09:51] <Mirv> seb128: now there's some new package in indicators stack, gnome-control-center-datetime, needs new config and run
[09:52] <seb128> Mirv, :-(
[09:52] <seb128> I pinged sil2100 and cyphermox about it yesterday evening
[09:52] <seb128> cyphermox said he would handle it
[09:52] <Mirv> seb128: additionally, the cu2d still thinks indicator-network is eternally running on powerpc, whil actually it's a dependency wait on qmenumodel-dev
[09:52] <Mirv> which also started yesterday evening at some point, and makes indicator build job to stall eternally. I don't know where it's coming from.
[09:53] <seb128> I've no idea about that :/
[09:58] <Mirv> me neither :(
[10:00] <Mirv> seb128: it's somehow related to this latest commit http://bazaar.launchpad.net/~indicator-applet-developers/indicator-network/trunk.13.10/revision/276 which adds the libqmenumodel-dev dependency
[10:00] <seb128> Mirv, that makes sense, it used to build fine on ppc before using qt5
[10:03] <seb128> Mirv, did you try https://wiki.ubuntu.com/DailyRelease/FAQ#I_know_that_I_want_for_one_time_skipping_one_arch_where_my_package_won.27t_built_for
[10:03] <seb128> Mirv, I would skip it once and then we can delete  the ppc binary in the archive
[10:04] <Mirv> seb128: not yet, if it works it should be tried now when this tick is in that shape
[10:04] <seb128> Mirv, yes, try that rather than stopping the run next time
[10:04] <Mirv> sil2100: can you work on that / follow the builds, I should eat at some point? :)
[10:06] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/indicators_add_extra_gnome-control-center-datetime/+merge/182578
[10:06] <Mirv> deployed already for this run
[10:18] <seb128> Mirv, approved
[10:18] <sil2100> Mirv: approved
[10:18] <sil2100> Ah, ok
[10:18] <seb128> lol
[10:18] <seb128> sil2100, sorry, I was not sure you were around so I just changed it
[10:18] <seb128> it's almost lunch time after all ;-)
[10:19] <sil2100> Mirv: I'm taking over everything now, my system seems back usable now
[10:19] <sil2100> (my tick!)
[10:19] <Laney> TRAPPED IN A A GUEST SESSION, SEND HELP
[10:19] <Laney> (the no indicators bug :P)
[10:19] <seb128> lol
[10:19] <Mirv> sil2100: thanks, it's been a rough morning :)
[10:19] <Mirv> /noon/beginningofafternoon
[10:20]  * seb128 sends laney a ctrl-alt-del
[10:20] <sil2100> Laney: /usr/lib/unity/unity-panel-service & ;)
[10:20] <seb128> or that
[10:20] <seb128> in alt-f2
[10:20] <Laney> no, you guys suck!
[10:20] <Laney> gnome-session-quit
[10:20] <sil2100> :<
[10:20] <seb128> ;-)
[10:20] <sil2100> Who would like to quit such a session?!
[10:20] <Mirv> we would definitely need an Asian / Australian / NZ guy to the cu2d vanguards
[10:21] <Laney> well I now have a black screen with a mouse pointer
[10:21] <Laney> the guest session was definitely better than that
[10:21] <sil2100> I think we'll have to transfer someone from our team to NZ
[10:21] <seb128> Laney, logout is quite buggy in saucy, I need to debug it at some point
[10:21] <Laney> in general or in the guest session?
[10:21] <seb128> it does the same on my normal session, I often end up going to a vt and doing ctrl-alt-del
[10:21] <Laney> hmm
[10:21] <Laney> haven't seen it there
[10:22] <Laney> I usually shut down straight away though
[10:22] <seb128> that works
[10:22] <seb128> it's logout that is buggy
[10:22] <Laney> yeah
[10:22] <seb128> and it's like every 3rd try
[10:22] <Laney> sometimes I do that but I didn't notice it hanging like that
[10:22] <seb128> it tends to do it if you try to log out just after log in
[10:22] <seb128> then it goes downhill
[10:22] <Laney> ah I have a unity-greeter crash
[10:22] <seb128> e.g first nautilus seems to exit
[10:22] <seb128> e.g you get no background
[10:23] <Mirv> my shutdown woe is bug #1212142
[10:23] <ubot2`> Launchpad bug 1212142 in sysvinit (Ubuntu Saucy) "Slow shutdown/restart on saucy with sendsigs waiting 10 seconds" [Medium,New] https://launchpad.net/bugs/1212142
[10:23] <seb128> then stuff hang for a minute
[10:23] <seb128> then unity goes away
[10:23] <seb128> then you have an empty screen for another minute
[10:23]  * Laney reports this crash
[10:23] <Mirv> although I'm not sure if it's not been there in various forms for ages, I just did the workaround on 12.04 LTS machine as well to make shutdown nonslow
[10:24] <Laney> we've tinkered a lot in that area this cycle
[10:24] <Laney> upstart / logind
[10:24] <Laney> upstart isn't relevant for the guest session though I guess
[10:25] <seb128> Laney, upstart is what makes you have no indicators :p
[10:26] <Laney> lack of upstart ;-)
[10:26] <seb128> I need to ping robert_ancell about bug #1214504
[10:26] <ubot2`> Launchpad bug 1214504 in unity (Ubuntu) "unity-panel-service not running in non-upstart-sessions on Saucy (including guest session)" [High,Triaged] https://launchpad.net/bugs/1214504
[10:28] <Laney> oh, interesting that it works if you go from lightdm
[10:28] <Laney> didn't know that
[10:31] <seb128> right
[10:34] <tsdgeos> is taking screenshots broken for anybody else?
[10:36] <Laney> http://ubuntuone.com/3616CovHk0RgyA7OvflvF2
[10:36] <Laney> nope, not me
[10:36] <czajkowski> tsdgeos: yes but it does fix itself
[10:37] <czajkowski> if you either A) restart your machine B) do some other restart that seb128 and didrocks told me
[10:37] <tsdgeos> restarting the machine never heps here
[10:37] <tsdgeos> it helps if kill unity and run Plasma though :D
[10:37] <seb128> wfm here, it just sometime gets confused by screen config changes
[10:37] <seb128> e.g if I undock my laptop
[10:42] <Laney> gst done, albeit blocked in proposed until we get libav 9
[10:43] <seb128> k
[10:43] <czajkowski> seb128: I don't even dock my machine and it gets confused
[10:43] <czajkowski> very special
[10:43] <seb128> yeah, no idea about it
[10:44] <Laney> try scrot from the repos
[10:45] <czajkowski> between compiz eating my cpu today and thunderbird gorging on it I am going to strangle my laptop!
[10:46] <Laney> slomo: ^^^ gst done, fyi
[10:47] <slomo> Laney: sorry, i'm making 1.1.4 tarballs now already ;) you can update it again later today :)
[10:47] <Laney> hahaha
[10:47] <Laney> slomo: much easier to take it from debian packages ;-)
[10:47] <seb128> Mirv, sil2100: skipping indicator-network ppc
[10:48] <slomo> Laney: those i'll do tomorrow :)
[10:48] <Laney> perfect
[10:48] <seb128> larsu, did you look at the accountsservice's vendor stuff/do you know how it works?
[10:49] <Laney> mterry might be able to review that
[10:49] <Laney> he'll be integrating it into the greeter after all
[10:49] <seb128> good point
[10:49] <seb128> let's wait for him
[10:50] <larsu> seb128: I know how it works in theory, but I haven't looked at the patch
[10:51] <seb128> larsu, don't bother, we are going to get mterry to review it, he's on the other side of the settings anyway so it makes sense ;-)
[10:51] <larsu> okay :)
[10:51] <sil2100> seb128: k
[10:54] <Mirv> k
[10:55] <Mirv> sil2100: note that your tick is again being blocked by the indicator build phase, everything waits on that
[10:55] <slomo> Laney: so changes are only the camerabin2 and jpegformat move?
[10:56] <Mirv> sil2100: you should abort that, let others finish and then rerun
[10:56] <sil2100> Mirv: can't we just skip the indicator?
[10:56] <sil2100> Like, with cu2d-skip?
[10:56] <sil2100> Mirv: that doesn't work?
[10:57] <Mirv> sil2100: try it out, sure
[10:57] <Mirv> sil2100: I just quickly noted before my telco
[10:58] <Mirv> since I believe nothing significant has yet happend during the last hour progress wise there, because of the stall
[10:58] <Laney> slomo: there's also a bump to the opencv version which is already upstream
[10:58] <sil2100> Mirv: cu2d-skip worked \o/
[10:59] <Laney> slomo: oh and that libtool one that you didn't like
[10:59] <sil2100> Mirv: well, it didn't stall for too long, we lost around 10 minutes (since before datetime was still building)
[10:59] <Mirv> sil2100: right, great! can you paste me the exact command line you used?-)
[10:59] <sil2100> Mirv: ./cu2d-skip indicators indicator-network powerpc ;)
[10:59] <Mirv> cu2d-skip indicators indicator-network powerpc?
[10:59] <sil2100> (without the ;) in the end :D)
[11:00] <sil2100> ;)
[11:00] <sil2100> Yes
[11:00] <Mirv> right, cool :)
[11:00] <slomo> Laney: libtool one?
[11:01] <Laney> slomo: https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/gst-plugins-bad1.0/saucy/view/head:/debian/patches/libtool-force-link-lc
[11:01] <Laney> I didn't get to the bottom of where the circular dep was coming from
[11:01] <slomo> Laney: ah, i'm going to add that to the debian package too now
[11:01] <Laney> ok
[11:01] <Laney> are you hitting that problem too?
[11:01] <seb128> sil2100, Mirv: indicators are good to publish
[11:01] <slomo> Laney: don't have time for debugging the real cause of this... i still think it's a toolchain bug
[11:02] <Laney> it's definitely a change in the toolchain but I can't say if it's a bug
[11:02] <slomo> Laney: yes, i386/kfreebsd-i386/ppc... nowhere else
[11:02]  * Laney nods
[11:02] <seb128> sil2100, Mirv: "<seb128> Mirv, sil2100: skipping indicator-network ppc" ... when I wrote that I had run the skip command
[11:02] <Laney> doko told me to fix the software but he always says that :P
[11:02] <slomo> Laney: it's probably a feature ;)
[11:03] <seb128> sil2100, +1 for the indicator diffs if you want to publish
[11:03] <slomo> Laney: yes, that seems to be the default mode... you have to prove first that it's a toolchain bug, otherwise it's your bug ;) even if a toolchain change caused it to switch from working to broken
[11:03] <Laney> yeah...
[11:04] <sil2100> seb128: ACK
[11:04] <Mirv> seb128: ah, I thought not in there but somehow otherwise. ok.
[11:04] <sil2100> seb128: published, thanks!
[11:04] <seb128> yw!
[11:05] <sil2100> seb128: btw. by any chance, did you pre-NEW and whitelist cordova-ubuntu and cordova-ubuntu-tests already? ;)
[11:05] <seb128> sil2100, no, I didn't
[11:06] <sil2100> I think those are packages that robru prepared
[11:06] <sil2100> Blocking webapps stack ;p
[11:09] <seb128> sil2100, can we get those off the stack?
[11:09] <seb128> there is a ton of files in there with random licences
[11:09] <seb128> I'm not going to have time to NEW review them before lunch
[11:10] <sil2100> Righto
[11:15] <sil2100> seb128, Mirv: first thing: https://code.launchpad.net/~sil2100/cupstream2distro-config/disable_cordova/+merge/182602
[11:15] <Sweetshark> Mirv: http://www.livestream.com/mumblestreaming suggests that the pirate party germany already has some implementation of streaming for mumble. And converting a live stream to a ogg dump should be trivial.
[11:19] <sil2100> seb128, Mirv: and this as well, since we want to have a mention of this rebuild in the changelog: https://code.launchpad.net/~sil2100/libunity-webapps/rebuild_libunity/+merge/182604
[11:27] <Mirv> sil2100: ah so is that latter in archive already?
[11:27] <Mirv> sil2100: the former approved
[11:27] <Mirv> sil2100: force_rebuild should work, yes, if not such a situation
[11:28] <sil2100> Mirv: I know, but as I mentioned, if I do a force_rebuild, there will be no changelog entry why we did the rebuild, no?
[11:28] <Mirv> sil2100: there's a changelog entry "forced rebuild"
[11:28] <sil2100> Mirv: there is? Oh
[11:28] <Mirv> but yes, no packagekit mention
[11:29] <sil2100> Mirv: I guess I'll invalidate the merge request and do the force_rebuild
[11:29] <sil2100> Since no use to loose time
[11:30] <sil2100> Mirv: thanks for approving!
[11:30] <sil2100> Redeploying and re-running in a moment
[11:54] <sil2100> Damn...
[11:54] <sil2100> What's with those LP network problems?!
[11:55] <sil2100> httplib2.ServerNotFoundError: Unable to find the server at api.launchpad.net
[11:55] <sil2100> Will have to re-run some stacks
[12:02] <sil2100> Mirv: sadly... https://code.launchpad.net/~sil2100/cupstream2distro-config/platform_extra_click_pkgs/+merge/182616
[12:02] <sil2100> Mirv: new extra packages coming from click :o
[12:05] <Mirv> approved
[12:06] <sil2100> Thank you!
[12:06] <sil2100> Redeploying
[12:13] <sil2100> Mirv: sometimes I wish we had a better way of dealing with that 'extra packages' thing, I think I need to sit down and think of a better way
[12:15] <Mirv> sil2100: yes, it's definitely already in next cycle's 'to-be-thinked-about' plans, with occasional discussions here. didrocks has the best thoughts on it as usual.
[12:15] <seb128> those seems like they should put the stack on UNSTABLE/manual approving rather
[12:15] <sil2100> Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/webapps_extra_packagekit/+merge/182619
[12:16] <seb128> e.g "things went ok, but you have an extra package pulled in, do you want to publish"
[12:16] <sil2100> seb128, Mirv: right, since right now it's sometimes blocking a stack for longer, or at least putting additional 'paperwork' work on us
[12:17] <seb128> the system could be more clever for sure
[12:17] <seb128> like gnome-control-center-datetime is a binary produced by one of the packages of the stack
[12:17] <seb128> those should be ok without being manually listed
[12:17] <sil2100> seb128: we can also manually override it in the jenkins job temporarily when there's something important (without the need of modifying cu2d-config and redeploying), but it's still just working-around a problem
[12:19] <sil2100> Mirv: pretty please when you have a free moment ;) ^
[12:21] <Mirv> sil2100: there's no such thing.. :)
[12:22] <Mirv> approved
[12:22] <Mirv> the final Qt 5.1.1 just got released an hour ago
[12:22] <Mirv> happily it's identical to the snapshot I already packaged
[12:26] <sil2100> :D
[12:38] <sil2100> Mirv: do you remember if we set a stack to manualpublish, does it require a redeployment? ;/
[12:38] <sil2100> Mirv: i.e. do I have to redeploy now all the stacks just because I want all of them to go into manual mode? ;p
[12:39] <seb128> you shouldn't listen to asac :p
[12:39] <seb128> that manual mode stuff is crazyness
[12:40] <asac> its the opposite ;)
[12:40] <asac> the path to sanity
[12:40] <seb128> stop landing stuff
[12:40] <asac> i am not stopping landing stuff
[12:40] <seb128> sure, until people get on us because stuff are not landing
[12:40] <asac> i am just stopping automatically landing stuff so we can coordinate the landings
[12:40] <asac> we will manually land stuff
[12:40] <asac> one by one
[12:40] <asac> stack by stack
[12:41] <seb128> can you provide us the resources to do the manual work as well?
[12:41] <asac> first those that need something in soon
[12:41] <seb128> those manual review are not going to automagically happen
[12:41] <Mirv> sil2100: no, I don't remember
[12:41] <seb128> who is going to do them
[12:41] <seb128> especially during vUDS hours
[12:41] <asac> seb128: well, we currenlty do it automatically
[12:41] <asac> so we just be an expanded bot
[12:41] <seb128> asac, keep in mind that nobody is going to do manual review for the next 18 hours at least
[12:42] <asac> yeah i hope we can go to automatic after we see an image
[12:42] <seb128> asac, it's going to be vUDS then eod
[12:42] <sil2100> But but but
[12:42] <seb128> asac, I bet you that by tomorrow morning people are going to complain about "why are stuff not landing"
[12:42] <asac> seb128: i sent a mail
[12:42] <asac> to ue-leads/management
[12:42] <seb128> yeah, still
[12:42] <asac> send them to me
[12:42] <seb128> I read it
[12:42] <asac> if they complain
[12:42] <seb128> k, I can do that
[12:43] <sil2100> Well, seb128 is right, since me and Mirv are the ones doing most stack management, cyphermox as well
[12:43] <asac> thats what i said anyway in the mail :)
[12:43] <asac> its not only you who is on vUDS
[12:43] <asac> everyone is
[12:43] <sil2100> seb128: that's why I asked asac to push that info to management and leads
[12:43] <asac> we will still juggle the most essential stuff
[12:43] <sil2100> If it happens
[12:43] <asac> the goal is to go back to automatic
[12:43] <asac> :)
[12:43] <sil2100> Since I don't want to have blood on my hands!
[12:44] <asac> i just dont believe its better to let all stuff land
[12:44] <seb128> let's see
[12:44] <seb128> it's going to be interesting
[12:44] <asac> uncontrolled
[12:44] <seb128> mir didn't land for almost a week
[12:44] <asac> yeah its a first experiment
[12:44] <seb128> they are not going to be happier
[12:44] <asac> yeah. those i woul dlike to take a mnual look at
[12:44] <asac> i dont understand their case
[12:44] <asac> and why it didnt land
[12:44] <asac> for now i assume our gates have catched stuff :)
[12:44] <seb128> because they keep changing abi
[12:44] <asac> catched it upstream, which is a good thing
[12:44] <seb128> so unity-system-compositor and other stuff needs to be rebuilt with the new abi
[12:44] <sil2100> seb128: I guess it should land now, as the jobs are green ;p
[12:45] <asac> seb128: yeah. so thats a valid reason to no land from the looks
[12:45] <seb128> which requires us to publish several of the other stack to unblock mir
[12:45] <sil2100> Indeed
[12:45] <asac> not sure that i am particularly unhappy to nhot have those abi breakages in the image right now :)
[12:45] <seb128> mir is not in the image
[12:45] <asac> seb128: ok so its about unfortunate split of stacks?
[12:45] <seb128> yes
[12:45] <asac> e.g. not all the right pieces can live in their own area?
[12:45] <seb128> we need the unity stack to go through publishing
[12:46] <seb128> because it has some components that needs rebuilding with the new mir
[12:46] <asac> yeah...i think we should change that and introduce like a "one-time-landing-stack"
[12:46] <seb128> e.g unity-system-compositor
[12:46] <asac> where such big things can be staged properly in one shot
[12:46] <asac> yeah understood
[12:46] <seb128> the problem is that stack as grouped as they are because component are inter dependant
[12:46] <seb128> you can't land a new unity without retesting indicators
[12:46] <seb128> because unity changes could break indicators
[12:46] <asac> yeah i get the idea
[12:47] <sil2100> It's a big web of inter-dependent components sadly
[12:47] <seb128> well, anyway
[12:47] <asac> right... it always as like that, so lets check how we can improve our concept
[12:47] <seb128> let's see how things goes
[12:47] <asac> to better capture those cross-stack transitions
[12:47] <seb128> asac, keep in mind also that beta1 is next week and the archive is going to be frozen tomorrow evening
[12:48] <sil2100> Mirv: I'm getting tired of those 'extra packages installed' bugs ;/
[12:48] <seb128> archive = main
[12:48] <seb128> but that includes the indicators
[12:48] <seb128> and unity
[12:48] <seb128> and mir
[12:48] <asac> so we should try to get those juggled in manually
[12:48] <asac> in a working form
[12:48] <asac> i dont think automatic landing would give us that :)
[12:48] <seb128> well, as said manual is fine
[12:48] <seb128> we just need resources to do the manual work
[12:48] <sil2100> seb128, Mirv: asking just in case I missed something in the morning - is it safe to publish the SDK stack?
[12:49] <asac> right. but the point is that i dont see how manual creats more work
[12:49] <seb128> sil2100, it was published earlier?
[12:49] <asac> it just crewates the work visibly up front
[12:49] <asac> rather than in a hidden firedrill afterwards :_
[12:49] <sil2100> seb128: yes, in the morning it seems
[12:49] <seb128> well, it implies somebody to look, review and press the button
[12:49] <sil2100> By Mirv's manual re-publish
[12:49] <seb128> so somebody around to do that
[12:49] <seb128> sil2100, is there any change since?
[12:49] <asac> thats fine. i am sure we can do the button push pretty cheaply and we get more control
[12:49] <asac> during this critical time of development
[12:49] <asac> which should give us a net win :)
[12:50] <seb128> let's see
[12:50] <asac> seb128: we rely on brave folksa everywhere. we will work on creating more redundancy on all stages of the CI engine
[12:50] <asac> so we can go off on holiday :)
[12:50] <asac> or sleep even
[12:50] <seb128> \o/
[12:50] <sil2100> seb128: checking, since there's no packaging change, but need to see in-code
[12:51] <asac> it reqyuires lowering the amount of know how needed to operate these stages
[12:51] <asac> so some up front work needed before we can do that :)
[12:51] <seb128> right
[12:51] <asac> but it IS going to happen :)
[12:51] <seb128> to be fair those are fairly well documented, thanks to didrocks
[12:51] <asac> yeah, still i dont see how i can esaily get 10 folks trainied
[12:51] <seb128> but most people are too busy to read the documentation :p
[12:51] <asac> to help out as a side job
[12:51] <asac> for 2 hours a day or something
[12:52] <asac> but maybe thats easy and just requires us to think about it
[12:52] <seb128> we should include them in the daily stuff
[12:52] <seb128> e.g give them a "tick" (one of the 4 hours publish cycle) while we have other team members around
[12:52] <seb128> and drive them through the process
[12:52] <seb128> reply to questions
[12:52] <asac> seb128: sounds right
[12:53] <asac> i think its easily doable. and mayb we can even improve the engine and way to operate while doing that
[12:53] <asac> and learning from the NEWBIE feedback we will get :)
[12:53] <asac> hehe
[12:56] <sil2100> Shit
[12:56] <sil2100> Mirv: do you know why the heck even after disabling cordova from daily release, it's still on jenkins after redeployment?
[12:57] <sil2100> Mirv: I saw 2013-08-28 14:30:02,307 INFO cordova-ubuntu-tests not configured for daily release. Skipping. <- in the logs, but it did not skip
[12:57] <sil2100> I mean, the prepare jobs are still there ;/
[12:57] <sil2100> hm
[12:57] <sil2100> Mirv: wait
[12:58] <sil2100> Mirv: I think the problem might be that the packages are still in the packages-to-be-released
[12:58] <sil2100> Too bad this is not documented, need to find it in mangers
[13:00] <seb128> ok, I'm going for some exercice, since vUDS starts in an hour...
[13:00] <sil2100> seb128: have fun!
[13:00] <seb128> thanks
[13:01] <sil2100> asac: so, after I'm done with this, should I push for the manual-mode switching? Will you take full responsibility for things not landing when there will be no one to push the button? ;)
[13:01] <asac> sil2100: you will be in sessions for half the day?
[13:02] <asac> sil2100: i can keep folks busy explaining to me why their stuff is safe for a couple of hours
[13:02] <asac> hopefully by then we can go back to automatic
[13:02] <asac> otherwise we have to start manually selecting what is afe
[13:02] <asac> safe
[13:02] <asac> vs. unsafe
[13:02] <sil2100> asac: yes, after that I'm EOD since UDS sessions are ending late in the evening for me here
[13:02] <asac> sil2100: you are going to UDS sessions all day long?
[13:02] <asac> well, would be great that if we need you to push a button that you could still do one or two
[13:02] <sil2100> asac: I'm the client track lead, so I have to be on every session of my track
[13:03] <asac> otherwise just the revert to automatic before EOD
[13:03] <asac> i will talk to cypher and ken
[13:03] <sil2100> But cyphermox should be around for that later
[13:03] <asac> right
[13:03] <asac> mirv/cyhper/ken
[13:03] <asac> strong team
[13:03] <sil2100> And also, if there's something urgent, you can just poke me to publish some stack during UDS even
[13:03] <asac> sil2100: right. so yeah i take full responsibilty for the next couple hours :)
[13:03] <asac> then we see
[13:04] <asac> otherwise i would take responsibilty for whatever lands in the automatic mode
[13:04] <asac> which is even harder to assess if i am willing to do that :)
[13:04] <asac> so i guess its a safe choice
[13:14] <sil2100> Mirv, kenvandine, cyphermox, seb128: https://code.launchpad.net/~sil2100/cupstream2distro-config/go_into_manual_mode/+merge/182633
[13:14] <sil2100> Mirv, kenvandine, cyphermox, seb128: I'll need approval from a few of you before we merge this, as it's a big change
[13:26] <Sweetshark> seb128: how do I start the g+ hangout such that it gets streamed? do you have a helpful link or something?
[13:54] <Mirv> sil2100: do you have the hangout ready, session starts at :00?
[13:54] <sil2100> Mirv: yes, all is prepared!
[13:54] <Mirv> sil2100: coolio :)
[13:55] <Mirv> sil2100: just paste the link to the client-1 channel
[14:09] <seb128> Sweetshark, you don't need to, the track host does that
[14:09] <seb128> Sweetshark, you just need to join the hangout on time
[14:09] <Sweetshark> seb128: alrighty.
[14:10] <seb128> sil2100, I'm not familiar enough with configs to say if that manual mode change makes sense, but it looks fine
[14:10] <seb128> if nobody else replies I can approve it
[14:39] <Laney> seb128: !!!
[14:39] <sil2100> Eeek
[14:39] <sil2100> seb128: thanks!
[14:40] <Laney> I just saw something
[14:40] <seb128> Laney, what did I do?
[14:40] <Laney> nothing, stop being paranoid ;-)
[14:40] <Laney> https://code.launchpad.net/~schwann/ubuntu-system-settings/settings-pick-background-from-gallery
[14:40] <seb128> lol
[14:40] <Laney> how cool is that
[14:40] <Laney> well, will it be
[14:40] <Laney> :P
[14:41] <seb128> Laney, oh, right, kenvandine and gusch are working on it ;-)
[14:41] <seb128> kenvandine is doing the hub and gush using it in the client sides
[14:41] <seb128> system-settings is their testcase for the widget ;-)
[14:41] <Laney> i didn't know that was the new thing
[14:41] <Laney> is that what i am calling the content picker?
[14:41] <seb128> yes
[14:41] <Laney> neat
[14:43] <seb128> Laney, also the OptionSelector is landing, I'm porting battery/sound atm as an example
[14:43] <seb128> I'm going to do one mr by panel and let people port the panels they are working on then
[14:43] <seb128> just for info ;-)
[14:43] <Laney> I'm sure it'll be easy
[14:43] <seb128> yeah, it's trivial
[14:57] <sil2100> cyphermox: indeed, I wanted to switch to manual for all stacks since otherwise we might have to look closer into the dependency chain
[14:58] <sil2100> cyphermox: since there are common components used between touch and desktop
[14:58] <sil2100> cyphermox: for instance, the unity stack is also used, because I guess it's using libunity
[14:58] <sil2100> cyphermox: which is part of the unity stack, no?
[14:58] <sil2100> cyphermox: hud is also used on touch
[15:03] <cyphermox> yes
[15:05] <kenvandine> Laney, check out the video i posted on g+ last night :)
[15:06] <Laney> aye aye
[15:22] <jbicha> dobey: what do you think about just applying the 1 line hack patch darkxst suggests in comment 31 for bug 1163886 ?
[15:22] <ubot2`> Launchpad bug 1163886 in software-center (Ubuntu) "software-center crashed with signal 5 with WebKit 2.0+" [High,Confirmed] https://launchpad.net/bugs/1163886
[15:24] <dobey> jbicha: commenting out that line is not useful
[15:24] <jbicha> do you have an ssd? maybe you need a slower computer to reproduce the bug?
[15:28] <sil2100> seb128: can you check in a free moment if unity-scope-mediascanner is updated in the whitelis?
[15:28] <sil2100> *whitelist
[15:28] <seb128> sorry, leading a session
[15:28] <Laney> sil2100: you can check that, can't you?
[15:28] <seb128> can you ping another archive admin instead?
[15:28] <Laney> ssh to lillypilly, look in ~ubuntu-archive/whateveritis
[15:29] <sil2100> Laney: I wonder if I have access to lillypilly, will have to find the address
[15:29] <Laney> you ought to
[15:29] <Laney> it's people.c.c
[15:35] <dobey> jbicha: sorry am in a session, so concentrating on that right now
[15:39] <sil2100> Laney: ok, will try checking that after this session
[15:48] <sil2100> Laney: works, thanks!
[15:48] <sil2100> seb128: it seems whitelisted, thanks!
[15:48] <Laney> np
[15:48] <Laney> might not work forever though; archive admin stuff is moving to a new box
[15:52] <seb128> sil2100, k
[15:54] <sil2100> cyphermox: so, you think we can ACK the manual publishing?
[15:54] <sil2100> kenvandine: how about you?
[15:54] <sil2100> cyphermox, kenvandine: by manual-publishing I mean manualpublishing mode
[15:54] <kenvandine> sil2100, sorry, let me look
[15:54] <cyphermox> yeah just go for it
[15:54] <kenvandine> great.. if cyphermox can do it :)
[15:54] <sil2100> kenvandine: I already did that, just want to know if you're ok with that ;)
[15:55] <kenvandine> i didn't look at the branch, but i'm sure it's fine :)
[15:55] <kenvandine> i saw the email from asac
[15:55] <sil2100> seb128, Mirv and cyphermox reviewed it, I'll have to redeploy the stacks in a moment
[15:56] <sil2100> kenvandine: btw. my question about -U and -S in the update stack
[15:56] <kenvandine> i think you can use -S
[15:56] <kenvandine> that is the reconfigure branches right?
[15:56] <kenvandine> so you want both
[15:57] <sil2100> So both is safe you think? Since I guess I need to update the jenkins jobs for this as well?
[16:01] <kenvandine> i would think, but i'm not sure
[16:05] <seb128> kenvandine, Laney, tedg, whoever wants to join the system settings session: https://plus.google.com/hangouts/_/5423f0843ea0c49351f4b1f771400ebf2d0e7cc5?authuser=0
[16:05] <Laney> ty
[16:06] <Laney> give me a minute to mess around getting it onto the tablet :|
[16:06] <seb128> Laney, still no mic?
[16:08] <seb128> kenvandine, ^ please
[16:09] <kenvandine> one sec
[16:22] <dobey> jbicha: i don't have an ssd, no. i have a hybrid drive, but it's a 2.5" drive and i think 5400 rpm. so not a 10K RPM power-hungry gaming drive either. and my laptop is an atom cpu with a slow hard drive
[16:27] <jbicha> dobey: I see that darkxst's suggestion was just a workaround and not really a fix
[16:28] <dobey> jbicha: it's not even a workaround
[16:28] <jbicha> it allows Software Center to start here but by breaking the carousel
[16:34] <sil2100> So many things to do ;/
[16:36] <dobey> jbicha: how exactly? you have a corrupted png image in the package itself?
[16:37] <dobey> jbicha: is it possible to see this bug on ubuntu *without* the gnome PPA?
[16:39] <jbicha> dobey: all it needs is webkitgtk 2.0 and this bug is the reason it's not in saucy yet ;)
[16:40] <jbicha> I haven't been able to duplicate with raring or saucy's current webkit
[16:40] <dobey> then why am i being bothered about a bug in webkit?
[16:41] <jbicha> it's not clear whether it's webkit's fault or not
[16:41] <dobey> that clearly sounds like a regression in webkit. webkit X does not have the problem, install webkit Y and the problem appears.
[16:42] <jbicha> that makes sense, but USC's not a very minimal testcase...
[16:43] <dobey> then someone is going to have to isolate what exactly is causing it to happen in software center, and create a minimal test case based on that. making random guesses by commenting out a line of code or deleting a cache directory, isn't a solution
[16:43] <dobey> are you running it in a vm?
[16:43] <jbicha> no
[16:44] <jbicha> the bug does look like it's triggered by the carousel
[16:44] <dobey> if you disable network on your machine completely, so that it can't talk to the server, and log in as guest, and start software-center, does it crash with the same bug?
[16:44] <jbicha> let me try
[16:45] <dobey> jbicha: sure it would. the carousel is webkit
[16:45] <dobey> because if the crash is due to an image being correupted that is downloaded from the network, it should surely not happen when there is no network
[16:46] <dobey> if the crash happens when there is no network, then it can be further isolated to something pre-existing on the system
[16:53] <dobey> jbicha: i need to get lunch now.
[16:53] <dobey> bbiab
[16:59] <sil2100> cyphermox: https://code.launchpad.net/~sil2100/cupstream2distro-config/new_extra_pkgs/+merge/182707
[16:59] <sil2100> cyphermox: can you approve? Thanks!
[17:00] <cyphermox> approved.
[17:02] <sil2100> cyphermox: thanks!
[17:08] <seb128> Laney, lol, that "DO NOT RENAME" seems like the sort of things we should have a test for ;-)
[17:14] <seb128> larsu, still around, I've a gsettings-qt question for you :p
[17:14] <larsu> seb128: yep
[17:15] <seb128> larsu, 1- do we have api documentation somewhere?
[17:15] <larsu> seb128: 1- no :(
[17:15] <seb128> ok, so 2- (I'm too lazy to read the code :p)
[17:15] <larsu> haha
[17:15] <seb128> larsu, 2- do you have a "reset" method?
[17:15] <seb128> I've settings UI where we need to reset keys
[17:16] <seb128> like a button to restore the default launcher config
[17:16] <larsu> seb128: no, but I can add it :)
[17:17] <larsu> actually, there are some docs in the header file...
[17:17] <seb128> larsu, ok, I'm filing a bug then, thanks
[17:17] <larsu> seb128: do you need it from qml or c++?
[17:17] <larsu> or both?
[17:18] <larsu> also, do you need to be able to reset individual keys or a whole schema? (or both?)
[17:19] <larsu> ooh, there's no g_settings_reset_all
[17:19] <seb128> larsu, individual key and qml
[17:19] <larsu> okay, you got it
[17:20] <seb128> but I guess it would be useful to have in the c++ lib as well
[17:20] <larsu> seb128: right, qml uses the c++ lib, so it needs to be :)
[17:20] <seb128> larsu,
[17:20] <seb128> https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1218005
[17:20] <ubot2`> Launchpad bug 1218005 in gsettings-qt (Ubuntu) "Needs an api to reset keys" [Undecided,New]
[17:29] <sil2100> robru: hi!
[17:33] <larsu> seb128: branch attached.
[17:45] <seb128> larsu, danke, going to review that in a bit
[17:45] <seb128> Laney, fyi https://bugs.launchpad.net/ubuntu-system-settings/+bug/1218010
[17:45] <ubot2`> Launchpad bug 1218010 in ubuntu-system-settings "greeter unlock configuration" [Undecided,New]
[17:46] <larsu> seb128: take your time, I'm going out for a run now :)
[17:47] <seb128> larsu, have fun!
[17:54] <sil2100> cyphermox: how much longer are you around?
[18:00] <sil2100> Shiit, we missed another tick by the unity stack
[18:00] <sil2100> robru: ^
[18:00] <sil2100> robru: you'll probably have a lot of work on your tick ;/
[18:01] <sil2100> Still, as mentioned in the e-mail, we're in manual publishing, so anyway all slows down
[18:01] <sil2100> asac will probably be in the morning
[18:15] <robru> sil2100, urg
[18:16] <sil2100> robru: it's madness now...
[18:16] <robru> sil2100, well i'll do my best...
[18:17] <robru> sil2100, should we cancel the unity run?
[18:17] <sil2100> robru: no no, it's going fine right now
[18:17] <sil2100> robru: the nvidia machine is finishing, I need to release that
[18:17] <robru> sil2100, so why did it take more than 4hrs?
[18:17] <sil2100> robru: to tell the truth, it didn't! But don't tell anyone ;)
[18:17] <asac> sil2100: what?
[18:17] <asac> i am still here
[18:18] <asac> sil2100: so this image might be good and we can go back
[18:18] <sil2100> robru: had to re-run it a few times due to wanting it finally RELEASED
[18:18] <asac> just wait till more tests arrive on dashboard
[18:18] <asac> then we can continue and see what happens
[18:18] <robru> sil2100, ahhh, ok
[18:18] <asac> so far we are still 100% :)
[18:18] <asac> so cross your finbers
[18:18] <sil2100> asac: ok, so let's connect about this tomorrow morning - if the results look good, let's switch it back ;)
[18:19] <asac> sil2100: cant i work with ken to get it enabled again?
[18:19] <asac> thought that was possible
[18:19] <asac> sil2100: i really hoped to just turn it on before eod again
[18:19] <sil2100> asac: ah, you mean like today?
[18:19] <asac> yeah... just wait 1h :)
[18:19] <sil2100> Aaah
[18:19] <asac> or tell ken how to do it :)
[18:19] <sil2100> Of course!
[18:19] <asac> it looks like the image is good
[18:20] <sil2100> asac: kenvandine knows how to do that ;)
[18:20] <asac> waiting for final tests from automation and testers and then we just go back
[18:20] <asac> sil2100: cool. so we are safe. thanks!
[18:20] <asac> kenvandine: how long you there?
[18:20] <sil2100> kenvandine: I used -U -S in case you wonder ;p
[18:20] <asac> important stuff to do :)
[18:20] <sil2100> kenvandine: just remember right now unity is still running
[18:20] <sil2100> asac: so if you guys could wait 1 hour just to be safe ;)
[18:21] <asac> sil2100: did we get manual requests for pushing so far?
[18:21] <asac> i didnt hear anything so wonder if anyone was concerned at all :)
[18:21] <asac> sil2100: ok ... but note that this unity is NOT in the iamge we will push, but guess thats clear. we can wait until that is done
[18:21] <sil2100> asac: not yet, I guess people understood that it's like that - and I guess people are busy in UDS too
[18:21] <asac> we have to wait anyway for results
[18:21] <asac> maybe
[18:22] <sil2100> asac: I know I know, but I think libunity is on the image
[18:22] <sil2100> And that's part of the unity stack!
[18:22] <asac> sil2100: not on this image if its still building :
[18:22] <asac> )
[18:22] <asac> maybe next image
[18:22] <asac> i think stgraber is also pushing more images as we speak :)
[18:23] <asac> sil2100: ok thanks. anything to remember when ken opens the floodgates again?
[18:23] <asac> but guess he can do it :)
[18:23] <asac> so yeah. lets do it :)
[18:23] <asac> cu
[18:23] <sil2100> Nooo, I think all is cool
[18:23] <sil2100> eeeh
[18:25] <ogra_> asac, no images, currently everything is stalled
[18:27] <asac> ogra_: ?
[18:27] <cyphermox> sil2100: was this preNEWed? https://code.launchpad.net/~indicator-applet-developers/unity-greeter-session-broadcast/trunk.13.10
[18:28] <ogra_> the first upload of the system image changes had a typo
[18:28] <asac> ogra_: can we promote the current image to current still or is even that not possible anymore? :)
[18:28] <cyphermox> sil2100: I'll be around all day, still at the very least 4 more hours
[18:28] <ogra_> and the android package needs a refresh from phablet.ubuntu.com, it FTBFS
[18:28] <asac> err proposed :) ... in case its good enough
[18:28] <ogra_> asac, we can surely push it to cdimage /current once the tests are done
[18:29] <asac> ogra_: have you done local smoke tests?
[18:29] <asac> maybe popey as well and then wait for the dashboar
[18:29] <sil2100> cyphermox: awesome, thanks - not sure about the preNEWing, I for sure didn't push anyone about it
[18:29] <asac> and go ahead :)
[18:29] <cyphermox> ok, just checking because I saw you had commits
[18:29] <cyphermox> seb128: around for a preNEW review? https://code.launchpad.net/~indicator-applet-developers/unity-greeter-session-broadcast/trunk.13.10
[18:30] <robru> sil2100, seb128: did any preNEW happen for cordova yet?
[18:30] <ogra_> asac, plars claimed he had no 3G on mako ... so i would prefer if popey could do another test
[18:30] <robru> I just landed some packaging fixes from a review pitti did.  but pitti doesn't know how to preNEW despite being an archive admin
[18:30] <sil2100> robru: sadly not...
[18:31] <sil2100> robru: seb128 wanted to, but he saw it having really many files and got preoccupied with some other wor
[18:31] <sil2100> k
[18:31] <pitti> well, I know what kind of things archive admins look out for, that's what I did in my packaging review
[18:31] <cyphermox> robru: as long as the package is reviewed...
[18:31] <pitti> but I've never heard "pre-NEW" before
[18:31] <sil2100> robru: I disabled it from daily until he does that
[18:31] <sil2100> robru: let's push him once he's around
[18:31] <robru> pitti, yeah, I think this 'preNEW' was inviented by didrocks and can only be done by him. he needs to educate other archive admins how to do it.
[18:31] <cyphermox> pitti: it's something didrocks invented to get a review from archive admins before we actually publish to queue, to avoid blocking whole stacks of stuff
[18:32] <pitti> this really sounds like a social process, nothing technical
[18:32] <robru> pitti, the package review was great, thanks very much for that.
[18:32] <sil2100> pitti: it means that someone performs a review as if he would NEW the package, if it's all ok then the daily-release whitelist needs to be updated
[18:32] <sil2100> (as it's in the DailyRelease FAQ)
[18:32] <pitti> just to avoid getting new packages rejected due to packaging bugs which could have been found before
[18:32] <asac> ogra_: thta sounds like a noisy report
[18:32] <asac> lets have someone check it
[18:32] <cyphermox> pitti: https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack
[18:32] <pitti> robru: package NEWing can only be done from https://launchpad.net/ubuntu/saucy/+queue?queue_state=0, there is nothing "pre" in Ubuntu
[18:33] <cyphermox> pitti: there is a slight technical step
[18:33] <robru> pitti, yeah, so didrocks invented this preNEW concept specifically for daily release stuff, it's like a pre-approval before NEWing. it's frustrating that he left for holiday before educating some people how to do this in his absense.
[18:34] <pitti> you can't just upload it without this preNEWing?
[18:34] <robru> pitti, the thing is, if you don't do it, the whole daily release process grinds to a halt.
[18:34] <pitti> and let the next archive admin actually do it?
[18:35] <robru> pitti, that's right, the daily release blocks on getting preNEW approval for new packages.
[18:35] <cyphermox> robru: I don't see how it does, tbh
[18:35] <cyphermox> pitti: there's just a quick bzr pull to do on lillypilly when things are added
[18:35] <robru> cyphermox, well, manual publishing mode
[18:35] <pitti> cyphermox: I certainly can do the bzr pull
[18:35] <cyphermox> robru: yes, but if you manually publish things will still land in the queue
[18:35] <pitti> but I don't know what to actually change in that bzr tree
[18:36] <cyphermox> pitti: nothing at all, actually
[18:36] <cyphermox> it's just syncing files so that the new package is listed, so that when we publish things get synced
[18:36] <pitti> ah
[18:36] <cyphermox> the list of packages to sync from the ubuntu-unity daily-build PPA
[18:36] <pitti> well, I reviewed and I did find a couple of issues
[18:37] <cyphermox> then let's not push it yet ;)
[18:37] <pitti> does that mean it should still be pulled, or does the pull only happen if the reviewer says "all ok"?
[18:37] <robru> cyphermox, I landed fixes for 90% of what pitti asked for (basically everything except some lintian warnings that I wasn't sure how to handle)
[18:37] <pitti> wow
[18:38] <pitti> http://paste.ubuntu.com/6037577/
[18:38] <cyphermox> robru: ok, then let's look at those, we can figure out how to address them
[18:38] <pitti> that's a lot of updates
[18:38] <pitti> robru: the lintian warnings? AFAIR they were trivial, let me dig out my mail
[18:38] <cyphermox> pitti: yeah, but most are irrelevant for this part of the job
[18:38] <pitti> W: cordova-ubuntu-2.8-examples: extra-license-file usr/share/cordova-ubuntu-2.8/examples/qrcode-scanner/js/lib/jsqrcode/COPYING
[18:38] <pitti> W: qtdeclarative5-cordova-2.8-plugin: package-has-long-file-name 72 (82) > 80
[18:38] <robru> pitti, yes, rather trivial. extra license file, and one filename too long
[18:39] <pitti> robru: just drop the COYPING from the .install or dh_installdocs or whatever
[18:39] <robru> pitti, it's not clear to me that deleting that license file is the right thing to do. might make it difficult to sync up with upstream later.
[18:39] <pitti> robru: you can ignore the second one for now
[18:39] <pitti> robru: not delete, just don't install it
[18:39] <robru> pitti, how would I specify that? like 'dh $@ -XCOPYING --fail-missing' or something?
[18:40] <sil2100> cyphermox, kenvandine, robru: for now leave the unity stack to me, I'm working on it
[18:40] <pitti> robru: anyway, as I said these are all the things that I found wrong, not that all of them are important enough to block NEW
[18:40] <robru> sil2100, ok, we are discussing cordova now
[18:40] <pitti> robru: that works, yes
[18:40] <pitti> robru: so the upstream "make install" installs that file?
[18:40] <pitti> robru: because that package produced multiple binaries, so usually you need debian/foo.install files
[18:41]  * pitti checks out the branch
[18:41] <robru> pitti, yeah, I think. well, 'make install' is ours, but upstream is just a blob of js/html stuff
[18:41] <pitti> robru: ah, there:
[18:41] <pitti> usr/share/cordova-ubuntu-*/examples
[18:41] <pitti> in the *.install
[18:42] <pitti> robru: so yes, -XCOPYING is easier than enumerating everything else; just do the -X thing
[18:42] <robru> yeah? how do I exclude a file in the .install file?
[18:42] <seb128> pitti, preNEW is because once it's enabled, things are going to get uploaded every 4 hours
[18:42] <robru> oh ok
[18:42] <seb128> pitti, so you end up with a stack of uploads flooding the queue
[18:42] <pitti> anyway, /me waves good night -- we've got plenty of AAs to do a bzr pull in more convenient time zones
[18:42] <pitti> see you tomorrow!
[18:43] <robru> pitti, thanks again, goodniht
[18:43] <pitti> seb128: ah, makes sense
[18:43] <seb128> pitti, night!
[18:54] <sil2100> cyphermox: are you uber busy now?
[18:55] <sil2100> seb128: I guess you EOD now? ;)
[18:55] <sil2100> pitti: goodnight!
[18:56]  * sil2100 needs a lot of packaging diffs ACKed
[18:56] <seb128> sil2100, I wish
[18:56] <sil2100> By a lot I mean 5
[18:56] <seb128> sil2100, I had 3 vUDS session and added enough backlog to keep me busy until late
[18:56] <seb128> sil2100, just back from dinner, dealing with backlog
[18:56] <seb128> sil2100, feel free to shot diffs to me
[18:56] <sil2100> seb128: ok now that sucks
[18:57] <sil2100> seb128: I'll poke cyphermox with those, no need to make your backlog any longer
[18:57] <sil2100> cyphermox: re-ping
[18:57] <seb128> sil2100, oh, no, that's fine
[18:57] <seb128> sil2100, it's not like reviewing diffs was going to take an hour
[18:57] <seb128> I'm waiting for stuff to build
[18:58] <cyphermox> sil2100: please, just ask what you need to ask, I'm trying to debug something
[18:58] <seb128> I can review diff inbetween
[18:59] <sil2100> seb128, cyphermox: compiz -> jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_compiz_1%3A0.9.10+13.10.20130828.1-0ubuntu1.diff looks *rather* ok now, but I'm a bit confused today
[19:00] <sil2100> seb128, cyphermox: libunity just adding symbols -> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libunity_7.1.0+13.10.20130828.1-0ubuntu1.diff
[19:00] <dobey> jbicha: any luck?
[19:01] <sil2100> seb128, cyphermox: scopes and lenses use new libunity -> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-lens-applications_7.1.0+13.10.20130828.1-0ubuntu1.diff
[19:02] <cyphermox> compiz looks ok to me
[19:02] <sil2100> seb128, cyphermox: new libunity and removal of deprecated scopes -> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scope-home_6.8.2+13.10.20130828.1-0ubuntu1.diff
[19:03] <sil2100> seb128, cyphermox: and finally unity, libunity bump mostly -> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity_7.1.0+13.10.20130828.1-0ubuntu1.diff
[19:03] <seb128> sil2100, compiz: -1
[19:03] <cyphermox> ah?
[19:03] <cyphermox> seb128: what did I miss?
[19:04] <seb128> sil2100, the replaces version is << 1:0.9.10  and changelog is 1:0.9.10+13.10.20130828.1-0ubuntu1
[19:04] <sil2100> Ok, now that bums me down, since I was working 3 hours to get it to PUBLISH
[19:04] <sil2100> Ah, right, shit
[19:04] <seb128> the previous version is 1:0.9.10+13.10.20130822-0ubuntu1
[19:04] <seb128> that's not << 1:0.9.10
[19:04] <cyphermox> indeed
[19:04] <seb128> you need << 1:0.9.10+13.10.20130828.1
[19:04] <sil2100> ;_;
[19:05] <seb128> sil2100, libunity +1
[19:05] <sil2100> Ok, then I'll release it tomorrow then, since I ain't waiting for the tests to finish again
[19:05] <cyphermox> libunity looks fine to me too
[19:05] <seb128> sil2100, sorry for compiz :/
[19:05] <sil2100> No problem ;)
[19:05] <seb128> unity+1
[19:05] <sil2100> I just needed unity-scope-mediascanner out before FF
[19:06] <seb128> the lenses are +1
[19:06] <seb128> sil2100, so all +1 but compiz
[19:06] <sil2100> I'm thinking of maybe how to push it directly without testing
[19:06] <cyphermox> unity-scope-runningapps won't be just for the phone
[19:06] <sil2100> I mean, since it's a packaging change, there's no need to re-run the integration tests
[19:09] <sil2100> I know, I'll do it hackily, but it still needs to build...
[19:09] <jbicha> dobey: yeah it still crashes http://paste.ubuntu.com/6037674/
[19:16] <dobey> jbicha: so unlikely to be caused by incomplete downloads. i'm also inclined to say that even if it were bad data from incomplete downloads or corrupted cache or something, webkit shouldn't crash as a result. it shouldn't be pushing invalid data to the x server
[19:17] <dobey> or trying to push it, anyway
[19:20] <ChrisTownsend> sil2100: Sorry about the compiz replaces version.  When I did that change, 0.9.10 wasn't out out, but my MP didn't get approved until after 0.9.10 was published, hence the screw up.
[19:20] <ChrisTownsend> sil2100: And it didn't occur to me to fix it:-(
[19:23] <sil2100> ChrisTownsend: no problem!
[19:30] <sil2100> See you tomorrow everyone!
[20:43] <darkxst> dobey, it is crashing because of the invalid set_size_request in the _HtmlRenderer
[20:43] <darkxst> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1163886/comments/69
[20:43] <ubot2`> Launchpad bug 1163886 in software-center (Ubuntu) "software-center crashed with signal 5 with WebKit 2.0+" [High,Confirmed]
[20:44] <darkxst> a width of 1 seems to indicate rendering hasnt finished?
[20:48] <darkxst> dobey, so there seem to be 2 issues here really, why does the crash occur when the size request width > 835
[20:49] <darkxst> and why isnt the correct width propagating to the HtmlRenderer sometimes
[20:50] <dobey> darkxst: that sounds like a regression in webkit
[21:39] <darkxst> dobey, indeed it does also crash with no network