[03:36] <pitti> Good morning
[03:37] <pitti> desrt: could be that suspend was blocked once, and then our systemd patch tried it anyway? I haven't uploaded the dropping of the patch yet
[03:41] <bratsche> Morning pitti
[03:41] <pitti> bratsche: hey Cody, long time no see! How are you?
[03:41] <bratsche> Pretty good, pretty good.. how are you doing?
[03:42] <pitti> overcoming ubuflu from last week's sprint, quite fine otherwise
[03:42] <pitti> still happy in my upstream qa role
[03:42] <bratsche> Very cool
[04:54] <mlankhorst> g'morning
[08:04] <Laney> morning!
[08:04] <didrocks> hey Laney!
[08:04] <Laney> hey didrocks, how's it going?
[08:04] <didrocks> Laney: I'm good, thanks! just beeing awake from 1am to 5am, but well… :)
[08:04] <didrocks> yourself?
[08:04] <Laney> still jetlagged?
[08:04] <didrocks> seems so :)
[08:05] <Laney> I had something similar on Sunday night but slept for over 12 hours on Saturday, so ...
[08:05] <Laney> went climbing yesterday outside in the amazing sunshine which seems to have tired me out enough to fix it
[08:05] <mlankhorst> :>
[08:06] <didrocks> Laney: I came back on Sunday (well, leaving on Saturday), so hopefully, it will get fixed tomorrow :)
[08:06] <mlankhorst> I'm sad to have missed you all on client sprint, but I did some nice horseback riding on sunday, trip was supposed to be 2 hours but it became 3, weather was great
[08:07] <Laney> nice!
[08:07] <mlankhorst> most important thing I learned was that a 'calm canter' isn't :)
[08:11] <mlankhorst> or worse, it probably is...
[08:13] <Laney> good for developing the thigh muscles eh
[08:14] <mlankhorst> definitely, I did some biking yesterday too, there's some definite improvement compared to a few months ago
[08:15] <mlankhorst> I didn't even get slowed down that much by a strong headwind
[08:21] <Laney> rockin'
[08:21]  * Laney dist-upgrades the desktop to saucy
[08:21] <mlankhorst> rarin'
[08:22]  * mlankhorst is installing raring desktop on panda, just to see if there's hw acceleration available or not, and then to check if that will still work on 1.14 with -ignoreabi
[08:23] <Laney> thought we considered panda desktop to be dead
[08:23] <mlankhorst> unfortunately it is blocking upgrade to 1.14 xserver :/
[08:23] <Laney> "Please restart the computer to begin using your updated software [Restart] [No other option] [No close button]"
[08:23]  * Laney grr
[08:24] <Laney> right click -> quit works
[08:25] <Laney> oh, but then refuses to run update-manager -d
[08:25] <mlankhorst> yep, quite fun!
[08:26]  * mlankhorst was having some fun with plymouth + mir today, turns out that there was no input support yet in mir, so no way to hook it up to plymouth
[08:53] <tjaalton> ogra_: so, about what was discussed yesterday about panda et al. there has never been a blob for it on the main archive, so installing it has always resulted in a sub-optimal experience, especially on quantal & raring which don't have unity2d anymore
[08:53] <tjaalton> ogra_: so I don't see how it could block any xorg update
[08:54] <ogra_> tjaalton, the blob is preinstalled since precise
[08:54] <ogra_> and is in the archive as well in resctricted
[08:54] <tjaalton> ogra_: on what?
[08:54] <tjaalton> huh?
[08:54] <ogra_> on the panda desktop images
[08:54] <tjaalton> I've always needed the ppa
[08:54] <tjaalton> anyway, raring is broken already, right mlankhorst?
[08:55] <ogra_> http://paste.ubuntu.com/5640860/
[08:55] <mlankhorst> tjaalton: not 100% sure, it installs with swrast, so if we only care about sw acceleration there's no blocker in moving to 1.14
[08:55] <ogra_> raring is fine and was released
[08:55] <ogra_> i have not a single bug about any graphics related regressions
[08:56] <mlankhorst> and the drivers for pandaboard were EGL or GLES already, no OpenGL support
[08:56] <ogra_> yes
[08:56] <tjaalton> still sounds incredible that it's blocking the x86 world from moving on
[08:56] <ogra_> and compiz works fine on it
[08:56] <ogra_> not different to nexus7
[08:56] <ogra_> tjaalton, i was told we will not get any updates on the x86 binary side either
[08:57] <mlankhorst> erm doesn't nvidia drivers already work for 1.14?
[08:57] <ogra_> at least nobody is assigned to work on it
[08:57] <tjaalton> ogra_: we have drivers for 1.14 already since february
[08:57] <tjaalton> or march for fgrlx
[08:58] <tjaalton> where can I find the omap image?
[08:58] <mlankhorst> but anyway pandaboard never had libgl drivers, so the only way compiz works is with swrast or a modified version to use the EGL libraries or something
[09:00] <ogra_> tjaalton, on cdimage
[09:00] <tjaalton> omap image for raring that is. I only see precise on cdimages.u.c/release
[09:00] <mlankhorst> tjaalton: there is a raring usb image
[09:00] <mlankhorst> that's the one you need :/
[09:01] <tjaalton> oh found it
[09:01] <ogra_> http://cdimage.ubuntu.com/releases/raring/release/
[09:01] <ogra_> its an SD card image .... needs an USB stick/disk as target media
[09:02] <ogra_> note that i would have preferretd to keep the nexus7 image (we even have updated tegra drivers for 1.14) ...
[09:02] <seb128> hey desktopers
[09:03] <didrocks> salut seb128!
[09:03] <didrocks> seb128: team meeting report reminder (think about modifying it btw ;))
[09:04] <tjaalton> ogra_: yeah I was blind, downloading atm..
[09:04] <ogra_> mlankhorst, note that SWRAST wont be usable (unless it sped up a lot it is more like a slideshow than a desktop)
[09:04] <mlankhorst> ogra_: and normal compiz IS usable? it uses opengl which panda doesn't support
[09:04] <ogra_> it uses the gles implementation which linaro worked on for two years
[09:05] <seb128> didrocks, hey, yeah I was about to do that, I just added sil2100 and Mirv to the team first
[09:05]  * mlankhorst checks
[09:05] <didrocks> seb128: excellent!
[09:07] <mlankhorst> ogra_: hm seems you're right, still I'll try to find out if omap works on 1.14 if I specify -ignoreABI, it probably should unless it does some deep hooking into xserver
[09:08] <ogra_> omap4 or omap ?
[09:08] <mlankhorst> omap4
[09:08] <ogra_> i dont think the binary blobs work
[09:09] <mlankhorst> it's just the xserver part that matters
[09:09] <ogra_> they likelly just need a recompilation gainst the new abi
[09:09] <ogra_> but there is nobody working with us who could do that
[09:09] <ogra_> and it might need kernel changes which we will not do
[09:09] <ogra_> (iirc the latter was the blocker)
[09:10] <tjaalton> it's not using the blob now?
[09:10] <ogra_> it is
[09:11] <ogra_> a quantal blob with a quantal kernel
[09:11] <tjaalton> on raring?
[09:11] <ogra_> and there is no intention to update either afiak
[09:11] <ogra_> yes
[09:11] <tjaalton> so much for backport stacks then :/
[09:11] <ogra_> kernel and blob are supposed to stay the same until we can drop the image
[09:12] <tjaalton> when is that?
[09:12] <ogra_> well, feel free to backport/forward port the 1700 patches the TI kernel ships
[09:12] <tjaalton> no, I'd drop it asap :)
[09:12] <ogra_> tjaalton, i wish i knew ... likely once we dont need any testing of xorg apps on arm anymore
[09:13] <tjaalton> who runs those now?
[09:13] <tjaalton> or needs
[09:13] <tjaalton> on saucy anyway
[09:13] <ogra_> convergence
[09:14] <mlankhorst> ogra_: so why not simply do the same as we are doing for precise, and offer a quantal xserver for pandaboard too
[09:14] <mlankhorst> if we already do that for the kernel anyway
[09:14] <ogra_> you should probably talk to slangasek about that
[09:15] <mlankhorst> assuming -ignoreABI doesn't work
[09:15] <mlankhorst> but I'm upgrading to 1.14 now to find out :-)
[09:15] <ogra_> :)
[09:24] <Mirv> seb128: thanks!
[09:26] <seb128> Mirv, hey, yw ;-)
[09:29] <pitti> bonjour seb128, ça va ?
[09:30] <seb128> pitti, salut, oui, et toi ?
[09:31] <pitti> seb128: mieux qu'hier, merci
[09:31] <pitti> no fever any more, and jetleg by and large gone
[09:31] <xclaesse> argh, I enabled the gnome3-team (and staging) ppa, now gnome-terminal's menu bar is back to the window instead of in unity's panel
[09:32] <xclaesse> probably because they have both an app menu and a window menubar
[09:32] <xclaesse> which makes no sense... :(
[09:32] <didrocks> xclaesse: yeah, you shouldn't use this ppa if you want a working unity session
[09:32] <didrocks> xclaesse: we didn't include all the latest components for some reasons… :)
[09:33] <xclaesse> so far it is the only slightly annoying bug I see :)
[09:33] <seb128> pitti, great
[09:40] <mlankhorst> ogra_: seems to start and composite when I recompiled xf86-video-omap and added -ignoreABI to load the blob part
[09:41] <ogra_> ah, sounds good
[09:41] <ogra_> see if it crashes after a while though :)
[09:41] <mlankhorst> ideally we could get a recompile though, nothing majorly was reworked but some internal structs did get shuffled around
[09:44] <mlankhorst> hm first crash when I was changing backgrounds, I'll try unmodified since it wasn't that stable before I upgraded to begin with
[09:58] <Laney> seb128: hey, how's it going? do we have a BP for the settings work? and a current one for user session stuff?
[09:59] <seb128> Laney, hey, I'm good, thanks. How are you?
[09:59] <seb128> had a good trip back?
[10:00] <Laney> aching!
[10:00] <Laney> the trip was good, then I slept lots and then went climbing yesterday :-)
[10:00] <Laney> out at a quarry nearby
[10:00] <seb128> hehe, some exercice is good to kick the remaining bits of jetlag out :p
[10:01] <seb128> Laney, blueprints:
[10:01] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/client-s-use-upstart-user-sessions
[10:01] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/client-touch-system-settings
[10:01] <seb128>  
[10:01] <seb128> they are pretty empty atm
[10:01] <Laney> sure, just wanted to make sure they were there
[10:01] <Laney> merci
[10:01] <seb128> I'm not sure yet how to really populate the settings one, we are sort of blocked on having the container app usable to be able to test things
[10:02] <seb128> but that doesn't stop us to play with qml meanwhile
[10:02] <Laney> well, currently we need to get up to speed on qml/sdk anyway
[10:02] <seb128> right
[10:30] <darkxst> Hey seb128, Laney
[10:32] <Laney> hi darkxst
[10:32] <Laney> how's it going?
[10:32] <darkxst> ah good, enjoying the cold weather! not so good for climbing though ;)
[10:33] <Laney> cold? :(
[10:34] <darkxst> well Melbourne cold about 13 today
[10:35] <Laney> ah, yeah, suppose it's getting on into autumn there
[10:35] <Laney> should be up to 21 here today which is pretty good for the time of year
[10:35] <darkxst> yeh I think we are back to mid 20's for the rest of the week
[10:36] <darkxst> anyway, pitti wasn't too keen on the idea of adding another api to packagekit for l-s
[10:36] <Laney> did you speak to upstream?
[10:36] <darkxst> pk upstream?
[10:36] <pitti> well, "get available locales" isn't really package specific
[10:36] <Laney> yeah
[10:36] <Laney> or gcc
[10:36] <pitti> it might fit into accountsservice slightly better
[10:37] <pitti> but I think it should just go into g-c-c's region panel
[10:37] <pitti> instead of depending on a new API which hasn't even been discussed/accepted upstream yet
[10:37] <Laney> well I was expecting it to be discussed upstream first
[10:38] <Laney> don't really care where it lives - just the initial idea of an l-s API seemed the wrong level
[10:38] <Laney> not upstreamable at all
[10:39] <darkxst> Laney, I seriously doubt g-c-c would take that language stuff either way
[10:39] <Laney> yeah?
[10:40] <darkxst> they wanted to add a button "install languages"
[10:40] <pitti> they have had designs for that for quite a while
[10:41] <darkxst> I don't know if those designs were actually approved?
[10:43] <darkxst>  I guess the packagekit stuff (what-provides etc) would be ok, but I don't think they will take any of the ubuntu specific langugae changes
[10:45] <pitti> but that isn't an ubuntu specific problem
[10:45] <darkxst> pitti, who else uses language packs?
[10:45] <pitti> (neither figuring out the set of allowed locales, nor installing additional packages for a language)
[10:45] <pitti> darkxst: all distros have extra packages that are language specific; this isn't limited to langpacks
[10:46] <pitti> but anyway, "which packages do I need for language XX" is already provided by aptdaemon and PK
[10:46] <pitti> (what-provides LANGUAGE_SUPPORT)
[10:46] <darkxst> yes I am using that bit
[10:46] <pitti> what we discussed yesterday was "which locales are available"
[10:46] <pitti> which is essentially parsing and de-duping /usr/share/i18n/SUPPORTED
[10:47] <pitti> or "locale -a" if you only want already installed locales
[10:51] <darkxst> pitti, ok will do it that way
[10:52] <Laney> neat
[10:52] <pitti> l-s already does that in Python, so the logic exists already
[10:56] <darkxst> I didnt really want to duplicate l-s logic, but if thats the best option then I will
[10:57] <pitti> the l-s logic will go away at some point
[10:57] <pitti> (i. e. when the g-c-c region panel is functional enough)
[10:57] <darkxst> ok
[13:29] <xclaesse> seb128, didrocks: dunno who packages empathy in ubuntu, but you guys probably wants to pick https://git.gnome.org/browse/empathy/commit/?id=add79d54e3c0149a2c336077d1e37c60d54c5ace
[13:30] <seb128> xclaesse, thanks
[13:30] <seb128> xclaesse, is that bug #1177285 ?
[13:30] <ubot2`> Launchpad bug 1177285 in gnome-online-accounts (Ubuntu) "gnome-control-center crashes on fill_contact_info_grid: assertion failed: (spec != NULL) after few seconds after opening online accounts " [Undecided,Confirmed] https://launchpad.net/bugs/1177285
[13:30] <xclaesse> the commit is in master & 3.8 because we don't support older versions
[13:31] <xclaesse> but all versions are affected
[13:31] <xclaesse> 3.6 crash as well
[13:31] <xclaesse> seb128, exactly that crash
[13:31] <seb128> xclaesse, good, it was on my list of things to look at since we received some reports about it
[13:32] <seb128> xclaesse, thanks for the ping ;-)
[13:32] <xclaesse> seb128, the reason is that gabble hardcode vcard fields supported by Google (fn, n and photo) but recently google decided to add url
[13:32] <xclaesse> so another fix will arrive in gabble as well, but empathy shouldn't crash even if gabble does something wrong :)
[13:32] <seb128> right
[13:33] <seb128> xclaesse, does it apply to 3.4 as well? (that's the current lts version)
[13:33] <xclaesse> seb128, probably, I tested only with 3.8 and Guillaume tested with 3.6
[13:33] <seb128> ok, I will have a look
[13:33] <seb128> thanks
[13:34] <mlankhorst> seb128: forcing pandaboard with -ignoreABI on 1.14 seems to be unstable, but it works if I run with the franken xserver we were using for testing tegra against 1.14, so we could do a custom xserver-xorg-core package to keep pandaboard working
[13:34] <xclaesse> hm
[13:34] <xclaesse> 3.4 does not have libempathy-gtk/empathy-user-info.c
[13:34] <xclaesse> code was moved, let me check
[13:35] <seb128> mlankhorst, nice, well I guess it's up to you (xorg team) to figure out what solution you prefer, hold on the xorg update or find a workaround like that
[13:35] <ogra_> well, talk to security too
[13:36] <ogra_> they will have to care for it for 9 months
[13:36] <mlankhorst> the xserver package will be identical, it will just have an extra patch to revert to the old ABI.
[13:37] <mlankhorst> it would be similar to what we were doing with -lts-quantal rename
[13:38] <xclaesse> seb128, not tested, but that should fix the bug in 3.4: http://cgit.collabora.com/git/user/xclaesse/empathy.git/commit/?h=backport&id=d015077538b66554ed75194a47446b84d8081769
[13:38] <seb128> xclaesse, thanks
[13:38] <mlankhorst> seb128: but if upstream essentially doesn't maintain the omap drivers any more, does it really matter whether xserver receives any security updates?
[13:40] <ogra_> mlankhorst, well, if x86 recieves a security update, arm shoould at least not ftbfs
[13:40] <mlankhorst> it won't
[13:41] <seb128> mlankhorst, I'm not too concerned about the security issues for that specific image
[13:41] <mlankhorst> it will be an extra package, like xorg-server-lts-quantal was
[13:41] <ogra_> given we use a binary copy of a quantal kernel anyway, i doubt secutiry matters, it only matters if your change adds work for the security team when applying fixes in general
[13:42] <ogra_> extra paackage ?
[13:43] <mlankhorst> doing the same thing for tegra would cause it to break, so I think it's better just to add a different xserver that is omap specific only
[13:45] <ogra_> for tegra there are updated drivers
[13:45] <mlankhorst> yeah that's what I mean, and there is already a script to do just that renaming in an automated fashion :)
[13:45] <ogra_> (we just have to update the package)
[13:46] <mlankhorst> so if the omap install image just adds xorg-omap, and xserver-xorg-core-omap, things would work
[13:47] <ogra_> if you can handle that on a package level that would be fine
[13:47] <ogra_> special casing seeds for a single subarch isnt really an option
[13:47] <mlankhorst> yeah I never intended that
[13:48] <seb128> Laney, pitti: since the logind updates, my screensaver doesn't unlock from lightdm
[13:48] <seb128> is that a known issue?
[13:48] <seb128> like if I start a guest session, logout from it, I'm back to unity-greeter, I enter my user password, that sends me to my session but screen is still locked
[13:49] <seb128> before that was sending me back to an unlocked session
[13:49] <Nafallo> seb128: two-factor auth, sort of ;-)
[13:49] <Nafallo> making sure you remember your password :-P
[13:50] <seb128> double single factor != double factor :p
[13:50] <Nafallo> it's an anti-aging device.
[13:50] <Nafallo> heh, I know. I've got quadruple auth in most places, as it is :-)
[13:51] <mlankhorst> ogra_: is it also possible to do an image with a PPA pinned to a higher priority so it will always grab the xserver from there instead of main archive?
[13:51] <ogra_> mlankhorst, PPAs are no option for official images
[13:51] <Nafallo> fingerprint, password, yubikey server and google auth :-)
[13:51] <mlankhorst> aw too bad
[13:51] <ogra_> (might change but until now that was a TB policy)
[13:52] <pitti> seb128: yeah, needs an upload of lightdm; it works for me (running lightdm from the PPA)
[13:52] <seb128> pitti, ok, as long as it's known, thanks
[13:52] <pitti> yes, it is
[13:52] <mlankhorst> ogra_: in that case rename is the only option then :/
[13:52] <pitti> seb128: actually, it's in the u-desktop PPA: https://launchpad.net/~ubuntu-desktop/+archive/ppa/+build/4535913
[13:55] <seb128> pitti, nice, will try that, danke!
[14:17] <Laney> pitti: actually it's in proposed
[14:17] <Laney> I didn't notice it hadn't migrated though - let me check why that is
[14:17] <Laney> seb128: ^
[14:18] <seb128> Laney, thanks
[14:19] <Laney> hrm
[14:23] <seb128> Laney, looking at the changelog I guess lightdm-kde-greeter needs to be rebuilt with the new soname?
[14:23] <Laney> yeah, on it
[14:23] <seb128> cool
[15:06] <Laney> bah BAH
[15:06] <Laney> lightdm has a versioned dev package
[15:21] <Laney> ...and the new pcfile is bugged
[15:30] <seb128> Sweetshark, qengho, Laney, mlankhorst, tkamppeter, attente, desrt: hey, it's meeting time
[15:30] <mlankhorst> g'day mate
[15:30] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2013-05-07
[15:30] <attente> hey
[15:30] <seb128> I hope all those who were in Oakland had an ok trip back
[15:31] <seb128> slight change of format this week, we start by the "desktop platform/apps" subteam and didrocks will handle the second part of the meeting of the ps integration part
[15:31] <seb128> let's get started
[15:31] <seb128> Sweetshark, hey, there?
[15:31] <mlankhorst> so I'm excused? :p
[15:31] <desrt> seb128: we're seriously having a meeting today?
[15:31] <seb128> mlankhorst, no, xorg is part of the desktop platform :p
[15:31] <desrt> so we can all update on what we did during our swap day? :)
[15:32] <didrocks> mlankhorst: nice try btw ;)
[15:32] <mlankhorst> well was worth a shot!
[15:32] <seb128> desrt, well, you can do a public update of what you got done during the sprint ;-)
[15:32] <desrt> fair enough.
[15:32] <seb128> community was not there
[15:32] <qengho> I wasn't either!
[15:33] <seb128> ok, no Sweetshark, he's working from California this week so I'm not sure he's online yet
[15:33] <seb128> qengho, hey
[15:33] <desrt> speaking of those working from cali
[15:33] <desrt> larsu: ping
[15:33] <larsu> desrt: yep?!
[15:33] <seb128> qengho, you missed some fun ;-)
[15:33] <qengho> seb128: so, I don't know what I'm supposed to say this time.  New format, eh?
[15:33] <desrt> larsu: go wake up Sweetshark :)
[15:34] <desrt> oh -- and desktop team meeting
[15:34] <Laney> same content, just a different split I think
[15:34] <seb128> qengho, the status update format didn't change, we just do split subteam for the order
[15:34] <seb128> didrocks' also wanted to change a bit the format for ps integration to go by topic rather than people
[15:34] <qengho> I worked on chromium-browser.  Trying to get more system libraries into the build so that it links on 32-bit hardware.  Testing the various combinations.
[15:34] <seb128> but that apply less to us since most of our topic have only 1 person working on them
[15:35] <seb128> e.g chromium, libreoffice, ...
[15:35]  * Laney goes
[15:35] <seb128> qengho, thanks
[15:36] <Laney> • logind transitions, a lot of them. The archive is almost complete (everything ported or with a consolekit dep added)
[15:36] <qengho> Oh, I packaged libv8 too.  It should be useful to others ere.
[15:36] <qengho> here.
[15:36] <Laney> • gstreamer 1.0.7 uploaded
[15:36] <Laney> • Clearing my outstanding merges (3 left)
[15:36] <Laney> • Just right now discovered that lightdm's qt pcfile is broken, so switched to fixing that. It's needed to fix lightdm-kde, which blocks lightdm from transitioning currently.
[15:36] <Laney> • Next up: think about blueprints for UDS, if any, and start looking at QML.
[15:36] <Laney> \0
[15:37] <seb128> Laney, thanks
[15:37] <seb128> mlankhorst, hey
[15:37] <mlankhorst> I've been putting some work in plymouth-mir, works but no input support yet, further work is postponed until mir api becomes more complete. Investigation into upgrading to 1.14, more testing for touch bug 56578. Preparing upload of lts-raring to precise-proposed.
[15:37] <ubot2`> Launchpad bug 56578 in mlview (Ubuntu) "Please sync mlview (universe) from unstable" [Undecided,Fix released] https://launchpad.net/bugs/56578
[15:37] <mlankhorst> https://bugs.freedesktop.org/show_bug.cgi?id=56578
[15:37] <Laney> is panda back from the dead now?
[15:38] <mlankhorst> I'm going to do a lts-style rename for panda xserver + xf86-vido-omap
[15:38] <ubot2`> Freedesktop bug 56578 in Server/Input/Core "race condition with active/passive grabs when opening menus with touch" [Normal,Assigned]
[15:38] <mlankhorst> it seems to be stable with the abi reverts I was using for testing tegra touch
[15:40] <seb128> great
[15:40] <seb128> mlankhorst, thanks
[15:40] <mlankhorst> np, off to the store, bbs
[15:40] <seb128> tkamppeter, hey
[15:41] <seb128> no tkamppeter?
[15:41] <seb128> attente, hey
[15:42] <attente> seb128, hi
[15:42] <attente> more gnome-control-center region panel patching, getting the keyboard indicator to work in the panel, debugging autopilot test cases in unity-gtk-module
[15:42] <attente> this week, wrap up two items related to indicator-keyboard, then start to port it to Ubuntu touch
[15:42] <desrt> attente: did you get the module landed finally?
[15:42] <attente> desrt, no not yet
[15:43] <desrt> one of these days... :)
[15:43] <seb128> attente, did you get the tests to run?
[15:43] <attente> ha.. yeah..
[15:43] <attente> seb128, yeah
[15:43] <attente> it turned out they were failing because of the keyboard indicator :S
[15:43] <seb128> what is blocking landing then? only waiting on the #ps integration team?
[15:44] <attente> we still have patched versions of gtk
[15:44] <attente> in archive
[15:44] <seb128> right, well that's a chicken egg problem :p
[15:44] <attente> this is true..
[15:44] <attente> who should i talk to about this?
[15:44] <seb128> the unity-gtk-module doesn't need to an unpatched gtk to land, does it?
[15:45] <seb128> well, if you think things are ready from your side, let's just ask didrocks/cyphermox in the second part of the meeting
[15:45] <seb128> or sil2100
[15:45] <attente> ok
[15:45] <seb128> I think it's up to them to land the source
[15:45] <seb128> your indicator-appmenu mr got approved
[15:45] <didrocks> sil2100 would know
[15:45] <seb128> then we just need to drop the gtk patches
[15:45] <didrocks> he wrote some notes that he had to revert it
[15:45] <seb128> attente, thanks
[15:45] <didrocks> so better to check once he's back :)
[15:45] <seb128> didrocks, right, he said it was due to autopilot 1.3 breaking compat or something
[15:46] <didrocks> yep
[15:46] <seb128> let's discuss it later
[15:46] <seb128> desrt, your turn ;-)
[15:46] <desrt> so i spent a lot of last week recovering from a sunburn
[15:46] <desrt> but not as bad as seb128
[15:46] <seb128> lol, I'm good again no worry ;-)
[15:47] <desrt> while that was going on, i mostly finished the GtkMenuTracker which will be used as the basis of all consumer implementations of GMenuModel (gtk, gtk-on-mac, unity-gtk, unity-qml and gnome-shell)
[15:47] <desrt> also, at kenvandine's request i started working on a qmlscene-type program based on GApplication.... that was a bit frustrating, but i got some pretty good ideas from it
[15:48] <desrt> which led me towards a conversation with thomas and thomas about how actions will work in unity apps -- and bumped GActionDescription way up my priority list: going to start working on that soon
[15:48] <desrt> also had more conversations about our C APIs.....
[15:48] <desrt> finally, landed the suspend support in systemd-shim, removing the logind depend on pm-utils and breaking everyone's laptop's suspend in the process
[15:48] <desrt> gonna try to fix that up today :)
[15:48] <desrt> (fin)
[15:49] <seb128> desrt, did you manage to reproduce the second suspend issue?
[15:49] <seb128> it does it in a reliable way here
[15:50] <seb128> second suspend -> suspend not working the second time
[15:50] <desrt> no
[15:50] <desrt> it's always working for me
[15:50] <seb128> hum, k
[15:50] <desrt> from the session indicator, right?
[15:50] <seb128> let me know if you need details
[15:50] <seb128> yes
[15:50] <desrt> i'm pretty sure it's a race
[15:50] <seb128> on a  32bit install (if that makes a difference)
[15:50] <desrt> like, a signal getting emitted before it is being watched for on the client side
[15:50] <desrt> and then it gets missed
[15:51] <desrt> i'm reading code and pinging lennart -- the dbus protocol is slightly underspecified in this area
[15:51] <pitti> seb128: do you have indicator-session from trunk? (the logind-ified one)?
[15:51] <desrt> one of those 'specification by sole implementation' (systemd) things
[15:51] <seb128> pitti, no, I've stock saucy
[15:51] <pitti> actually, it hit saucy 18 minutes ago, thanks cyphermox
[15:51] <seb128> oh, nice, will try that
[15:51] <desrt> pitti: should this fix it, then?
[15:52] <seb128> well the interface it's using works the first time
[15:52] <pitti> I don't know -- suspend is always working here
[15:52] <seb128> so it's not totally incompatible with logind
[15:52] <desrt> tre interesa
[15:52] <pitti> it talks to upower, so I guess that "already pending" error might actually come from upower
[15:52] <pitti> (we had a case like that last week)
[15:52] <Laney> I just tried double (triple) suspending, worked every time
[15:53] <Laney> so yeah, try the new i-session and see what happens
[15:53] <seb128> you guys all run indicator-session from trunk?
[15:53] <seb128> ok
[15:53] <desrt> seb128: update to the new indicator and let me know.  could be there is actually no issue at all here.
[15:53] <seb128> will do after the meeting
[15:53] <seb128> desrt, thanks
[15:53] <seb128> ok, did I forget anyone?
[15:53] <seb128> otherwise my summary:
[15:53] <seb128>  * quite some discussions at the sprint, mostly focussed on trying to figure out the details for indicators and system settings
[15:54] <seb128>  * looked at cleaning some of the deprecated libs from our current images, also reviewed what is still using python2
[15:54] <seb128>  * started merges on debian
[15:54] <seb128>  * some blueprint work
[15:54] <seb128>  * updated gtk 3.8.1 in the ppa, trying to get that ready for saucy
[15:55] <seb128> cyphermox fixed the overlay-scrollbar issue so we are getting close
[15:55] <Laney> oh wow, he did?
[15:55] <Laney> good job
[15:55] <seb128> yes
[15:55] <larsu> wow, thanks cyphermox!
[15:55] <seb128> https://code.launchpad.net/~mathieu-tl/overlay-scrollbar/fix-second-use/+merge/162507
[15:55] <seb128> needs a review/approval still
[15:55] <cyphermox> yup
[15:56] <seb128> but I verified locally, it works for me (and gtk 3.6 still works fine)

[15:56] <seb128> ok
[15:56] <seb128> otherwise, small not before ending the first part of the meeting
[15:56] <seb128> note
[15:57] <seb128> Sweetshark, qengho, Laney, mlankhorst, tkamppeter, attente, desrt, didrocks, kenvandine, cyphermox, Mirv, others: vUDS is next week, if you have any session you want to have (or that you think others should have), please register a blueprint and get it targetted for the uds sprint
[15:58] <cyphermox> ack
[15:58] <kenvandine> ack
[15:58] <seb128> would be good to also chase other teams so they register blueprints if needed
[15:58]  * desrt will probably be away this week
[15:58] <Mirv> ackie
[15:58] <sil2100> o/
[15:58] <seb128> desrt, you were not going to register a session anyway I guess? ;-)
[15:58] <seb128> sil2100, hey
[15:58] <desrt> seems unlikely :)
[15:59]  * desrt could go hang out with cyphermox for mini-ubz
[15:59] <seb128> on the note of people being away, please try to deal with blueprints for vUDS today if you can
[15:59] <seb128> quite some people are off starting tonight for the end of week
[15:59] <seb128> national holidays wed&thursday and swap days from last week
[15:59] <didrocks> seb128: I don't have anything really important to discuss at vUDS anyway
[16:00] <didrocks> so rather waiting for people inviting :)
[16:00] <seb128> didrocks, ok
[16:00] <Laney> wed AND thurs!
[16:00] <didrocks> (if needed)
[16:00] <Laney> you french!
[16:00] <seb128> on that note, we are just on time for second half of the meeting
[16:00] <didrocks> ok, maybe let's start the second part of the meeting :)
[16:00] <sil2100> seb128: ok, will deal with my blueprint-related things later today
[16:00] <seb128> if nobody has comments or questions
[16:00] <seb128> comments/questions?
[16:00] <seb128> sil2100, thanks
[16:01] <seb128> ok, seems not
[16:01] <didrocks> cyphermox, Mirv, sil2100, kenvandine, robru: hey guys! hope that you trip back went well :)
[16:01] <didrocks> your*
[16:01] <seb128> didrocks, your turn
[16:01] <didrocks> let's go over the important topics from https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=0
[16:01] <sil2100> I thought I would get crazy during my trip back though, never again!
[16:01] <didrocks> do not forget to update it btw as it's our communication guide :)
[16:01] <sil2100> Ok
[16:02] <Mirv> yeah, never again, as always when crossing the Atlantic. but alive, so "well" :)
[16:02] <didrocks> heh
[16:02] <didrocks> as a reminder, I won't be there until next Tuesday
[16:02] <didrocks> so I will surely put some of the tasks assigned to me on you guys :)
[16:02] <didrocks> ok, let's start
[16:02] <sil2100> No problem ;)
[16:02] <didrocks> robru: "Splitting webapps and have that on daily release"
[16:02] <didrocks> with kenvandine's help
[16:02] <didrocks> I saw some good progress
[16:03] <didrocks> seems we still have some issue to get fixed, right?
[16:04] <didrocks> …no robru? ok, we pushed back the meeting for him. I hope that next week he'll be there on time at least… (the meeting is quite late for some people like Mirv, starting early)
[16:04] <didrocks> kenvandine: around?
[16:04] <robru> hey, just woke up, sorry
[16:04] <kenvandine> yup
[16:04] <didrocks> robru: just in time! :-)
[16:04] <didrocks> robru: hope you have some coffee ;)
[16:04] <didrocks> robru: so, what's up on webapps?
[16:05] <robru> almost ;-)
[16:05] <robru> didrocks, I have branches pushed to fix most things.
[16:05] <Mirv> 12h since I started my work day :)
[16:05] <robru> didrocks, the only thing I can't fix is twitter, need alex abreu to write a manifest.json fro it
[16:05] <didrocks> robru: ok, let's see how it goes ;) are you confident to get it in with autopilot tests for next week?
[16:06] <robru> didrocks, there's an issue with jenkins not having the build-dep in thePPA so it complains of rules.mk again
[16:06] <didrocks> yeah, I commented on the MP, ping vrruiz for it I guess
[16:07] <robru> not too confident with autopilot, not sure the status of it. seems incomplete/bitrotten. but the linter script I wrote can detect basic issues ;-)
[16:07] <robru> and it can be expanded to detect new issues as we find them
[16:07] <didrocks> robru: ok, let's try at least without autopilot for next week :)
[16:08] <didrocks> next topic is disabling indicators, this is done cyphermox, isn't it?
[16:08] <cyphermox> yup, done
[16:08] <didrocks> do you mind updating the spreadsheet?
[16:08] <didrocks> next one is finishing the doc when putting S in distro, cyphermox, can you please send me an email with your notes so that I can update it?
[16:09] <cyphermox> I was thinking we should finish all of it before
[16:09] <cyphermox> but sure, I'll send what I have now
[16:09] <didrocks> cyphermox: ok, if this week, some are needed, like unity and so on, do you mind giving a hand to the person doing it?
[16:09] <didrocks> as I won't be around :)
[16:09] <didrocks> cyphermox: if so, writing the doc next week is fine to me
[16:09] <cyphermox> well I can send what I alreday have now, then we'll add whatever else
[16:10] <didrocks> sure :)
[16:10] <didrocks> thanks cyphermox
[16:10] <didrocks> I finally found time to do the Vcs-Bzr ignoring + collecting commits for all mainline commits \o/
[16:10] <didrocks> (some part was on the plane, not at the bar :p)
[16:10] <cyphermox> awesome.
[16:10] <didrocks> I'll archive it
[16:10] <didrocks> (see second tab)
[16:11] <didrocks> sil2100: hey! touch building in next ppa, what's the status?
[16:11] <sil2100> hmm
[16:12] <sil2100> Hard to say, since there wasn't much things I knew since I le
[16:12] <sil2100> *I left the sprint
[16:12] <Mirv> I wonder if I should have the Qt/SDK stuff as a separate item
[16:12] <didrocks> Mirv: would make sense, please, feel free to edit
[16:12] <sil2100> Mirv: ^
[16:12] <didrocks> Mirv: kenvandine: did you look at that since Friday?
[16:12] <Mirv> platform seems fine, but still hitting utah with sdk
[16:12] <Mirv> for my part
[16:13] <kenvandine> yeah
[16:13] <kenvandine> all the web cred bits are there for touch
[16:13] <kenvandine> according to the spread sheet, it's basically all done
[16:13] <sil2100> I would say all what is left is the e-mail probably, but will have to double check the stacks to be sure
[16:13] <sil2100> And then just the e-mail
[16:13] <didrocks> sil2100: Mirv: kenvandine: so for next week, do you mind finishing the autopilot 1.3 transition (with robru I guess) in all stacks and having everything delivered in next? UTAH should feel a little better from what I know
[16:13] <sil2100> I can do that later as well, if didrocks wouldn't be around
[16:14] <sil2100> ACK
[16:14] <kenvandine> didrocks, it wasn't better this morning :/
[16:14] <didrocks> sil2100: yeah, just take the item and discuss between you guys :)
[16:14] <didrocks> kenvandine: hum, let me check we don't dist-upgrade anymore
[16:14] <robru> didrocks, hey, is it true that one failing webapp stops the whole webapps stack from being published?
[16:15] <didrocks> kenvandine: we don't dist-upgrade anymore, mind checking with the QA guys?
[16:15] <didrocks> robru: right, it's "per stack"
[16:15] <didrocks> robru: the stack is validated or rejected
[16:15] <kenvandine> didrocks, who should i talk to?
[16:15] <didrocks> that's why the stack should be own by the same team
[16:15] <Mirv> om26er has many autopilot 1.3 branches at https://code.launchpad.net/~om26er
[16:15] <didrocks> kenvandine: ping on #qa gema or anyone in the QA team
[16:15] <robru> didrocks, any way to change that? there are 40 webapps and any one of them is likely to be broken at some point... we really need to be able to release them independently. that was the whole point of splitting them, so we can release only the ones that need fixes...
[16:16] <didrocks> robru: well, then, the team need to fix them :) it will only rebuild those having changes, if they are broken, they need to be fixed
[16:16] <didrocks> robru: we are validating the whole stack in integration tests
[16:16] <robru> didrocks, ok, but it doesn't really make sense to hold back the whole stack just because one minor/obscure one is broken.
[16:16] <didrocks> Mirv: ah, nice! so it's just a question of tracking if they are merged
[16:17] <didrocks> robru: well, that's working quite fine for most of the stacks, as they are owned by the same team, we can divides stack, but as it worked for the past 6 months, I'm not keen on that
[16:17] <robru> didrocks, it's not like these are critical libs where one broken one breaks the whole experience; users are only likely to care about a few of the 40 apps, better to get them "all the working ones" and only hold back the broken ones
[16:17] <didrocks> robru: maybe you want to discuss that during vUDS? would be a good topic, but all the original design is based on that. I'm surprised you didn't get it before :)
[16:18] <didrocks> robru: if we don't support or care on what we deliver, we should remove the app
[16:18] <kenvandine> robru, the issue is if one app fails the tests, it could be because of a regression in libunity-webapps that the other webapps don't use
[16:18] <robru> didrocks, well the situation before was that all webapps in one branch meant you had to re-release all of them every time you wanted to fix just one of them. I thought the *whole point* of what i was working on all last week was to split them up into *independent* branches so they could be released *independently*.
[16:18] <kenvandine> like maybe webapp-foo is the only webapp that uses feature A from libunity-webapps
[16:19] <didrocks> robru: yeah, if you have one fix somewhere, it will release only this fix
[16:19] <kenvandine> we shouldn't let libunity-webapps get publshed
[16:19] <didrocks> robru: instead of pushing 40 binary packages to distro, only one being changed
[16:19] <didrocks> for instance
[16:19] <sil2100> robru: it's just the case of integration tests failing - if integration tests are failing, it means the failure will be visible to the user
[16:19] <sil2100> So that's why it has to be done so I think
[16:19] <didrocks> in practice, this is working way better than what you may think, and forcing us to deliver all working components
[16:20] <robru> sil2100, no integration tests on webapps yet ;-)
[16:20] <sil2100> robru: boo... ;(
[16:20] <didrocks> robru: well, they are, but not activated yet :)
[16:20] <didrocks> robru: we can discuss that at vUDS if you want to open a session on it
[16:21] <didrocks> let's go to next topic
[16:21] <robru> didrocks, ok, but it doesn't make sense to me that AngryBirds app (which is basically a stub, it has no features) can be broken, and this holds back important ones like GMail or amazon
[16:21] <didrocks> robru: well, we can fix AngryBirds then
[16:21] <didrocks> that would make more sense to me, as we know exactly the day it broke
[16:22] <robru> didrocks, well it broke from the beginning :-P
[16:22] <didrocks> robru: it should have never been broken :p
[16:22] <didrocks> or never published if broken
[16:23] <robru> didrocks, alright, then I might push a branch disabling some apps then.
[16:23] <didrocks> robru: sounds good to me
[16:24] <didrocks> I guess the rest of the list is under control and linked to the previous discussion (basically having autopilot 1.3 transition done, touch published to next ppa, get everything green, check with qa on UTAH)
[16:24] <didrocks> isn't it?
[16:24] <didrocks> sil2100: kenvandine: Mirv: you are mainly the ones holding those actions ^
[16:24] <kenvandine> the utah errors are cobbler failures
[16:24] <kenvandine> yeah
[16:24] <Mirv> about so
[16:24] <sil2100> Yes
[16:24] <didrocks> kenvandine: ok, so UTAH is using cobbler wrongly again, need to get them fixing it… :/
[16:25] <didrocks> so, now, some new incoming work for fun :)
[16:25] <didrocks> unity raring SRU
[16:25] <kenvandine> i just asked them
[16:25] <didrocks> Mirv: do you have time for that one? Basically delivering a SRU for raring with current unity raring
[16:25] <sil2100> Mirv: weren't you working on that? ^
[16:25] <didrocks> Mirv: it's about checking that the bugs are fine
[16:25] <sil2100> Ah, raring!
[16:25] <sil2100> Duuuh
[16:25]  * sil2100 keeps confusing raring and precise
[16:25] <didrocks> and make a manual publishing if everything all right :)
[16:26] <Mirv> yeah, I've also the precise SRU waiting for a patch pilot :)
[16:26] <didrocks> as it's builed daily in the daily-build ppa
[16:26] <Mirv> didrocks: I don't yet have a touch on the practicalities of the delivery
[16:26] <Mirv> otherwise I'm fine with checking
[16:26] <didrocks> Mirv: yeah, no need for a patch pilot for this one :) just having kenvandine or cyphermox doing the manual publication for you
[16:26] <didrocks> Mirv: so look at the ~ubuntu-unity/daily-build ppa for the indicators and unity stacks
[16:26] <kenvandine> Mirv, let me know when it's ready
[16:26] <didrocks> look at the generated changelogs
[16:26] <Mirv> ok, will do
[16:26] <didrocks> bugs associated
[16:27] <didrocks> and hop! upload if things are following SRU rules :)
[16:27] <kenvandine> i'm on pilot duty tomorrow :)
[16:27] <didrocks> (upload being manual publishing)
[16:27] <didrocks> so should be easy ;)
[16:27] <kenvandine> but i'll be out tomorrow morning, so just email me
[16:27] <Mirv> sounds like a good list
[16:27] <didrocks> Mirv: with luck utah would run and you will get test results even! :)
[16:27] <didrocks> Mirv: mind adding it yourself to the spreadsheet?
[16:28] <robru> didrocks, can you tell a little bit about how/when we plan to transition from PPA to start releasing directly into saucy?
[16:28] <sil2100> We just remove the dest PPA from the configs
[16:28] <sil2100> IIRC
[16:28] <didrocks> robru: I guess we have enough for this week with the touch to have it built in next
[16:28] <didrocks> robru: so I thought about next week, wdyt?
[16:28] <Mirv> didrocks: ok, done
[16:28] <kenvandine> wfm
[16:28] <didrocks> thanks Mirv :)
[16:29] <robru> didrocks, well, I don't know what the status of the other stacks is like, but Friends as released for raring has a really horrible crasher bug in saucy due to some library API breakage, so I have a fix that I want released into saucy quite urgently ;-)
[16:29] <didrocks> kenvandine: cyphermox: sil2100: Mirv: robru: a small note, it seems the cu2d-* command doesn't work since they restarted jenkins, cyphermox will check with qa about it, meanwhile, use the web UI.
[16:30] <kenvandine> ok
[16:30] <Mirv> didrocks: I don't have the access rights still there
[16:30] <sil2100> ACK :)
[16:30] <cyphermox> yeah, just wiating to hear back about it
[16:30] <didrocks> robru: ok, for that one, you can get in touch with cyphermox, he knows how to transition (quite simple, but better to pair) :)
[16:30] <didrocks> robru: and let's transition friends to be saucy! :)
[16:30] <didrocks> Mirv: yeah, the request is pending (but people on holidays)
[16:30] <cyphermox> hmm,, sauce.
[16:30] <robru> didrocks, cyphermox so it's possible to just do friends direct to saucy without affecting other stacks?
[16:30] <Mirv> didrocks: ok, thanks
[16:31] <didrocks> robru: it is :)
[16:31] <cyphermox> robru: assuming it doesn't need other pieces of the stack, yes it should
[16:31] <didrocks> as cyphermox did with indicators
[16:31] <didrocks> ok, last but not least… (sorry, have a lot this week)
[16:31] <didrocks> sil2100: it's for you!
[16:31] <sil2100> ?!
[16:31] <didrocks> sil2100: so, mhr3 wants to get 100scopes merged back to saucy unity trunk
[16:32] <sil2100> !!
[16:32] <didrocks> sil2100: so just sync with him, you will have to disable the experimental stack once done and add to head/unity.cfg the scopes
[16:32] <mhr3> sil2100, piece of cake, right? :)
[16:32] <sil2100> Is it *ready*? Since I didn't look at it for a while, and Paweł told me during the sprint about some regression they were trying to fix in unity
[16:32] <sil2100> didrocks: ok, will do ;)
[16:32] <didrocks> just target "next" for this week, we'll go over the sauce next week :)
[16:32] <robru> cyphermox, I guess this is what I need: https://code.launchpad.net/~robru/cupstream2distro-config/friends-saucy/+merge/162712
[16:32] <didrocks> sil2100: yeah, it is from what I know of :)
[16:33] <didrocks> robru: you need to change ppa to  ubuntu-unity/daily-build and remove the "dest" line
[16:33] <cyphermox> robru: yeah, just wiating for the updated diff
[16:33] <sil2100> didrocks: ok, I'll add it to the spreadsheet
[16:33] <cyphermox> didrocks: ^ cf. diff
[16:33] <didrocks> cyphermox: ah nice! :)
[16:33] <didrocks> sil2100: thanks a bunch (and good luck) :)
[16:34] <cyphermox> actually
[16:34] <cyphermox> robru:  ppa: ubuntu-unity/daily-build-next  should remove -next
[16:34] <didrocks> cyphermox: good catch!
[16:34] <didrocks> ok, I don't think we need everyone to stay to transition friends to saucy, any question before wrapping up?
[16:35] <cyphermox> not from me
[16:35] <cyphermox> robru: let's get this finished, I'm starving :)
[16:35] <robru> cyphermox, just pushed it
[16:35] <didrocks> thanks Mirv, sil2100, robru, cyphermox, kenvandine :) see you next week (and don't break everything meanwhile :p)
[16:35] <cyphermox> ok
[16:35] <robru> didrocks, thanks
[16:35] <kenvandine> didrocks, enjoy!
[16:35] <sil2100> didrocks: ok! Have a nice holiday!
[16:36] <didrocks> thanks ;) good luck guys!
[16:36] <Mirv> thank you :)
[16:36] <sil2100> didrocks: and see you next week as well, we'll be informing you about the progress probably during that time anyway ;)
[16:36] <didrocks> sil2100: think about updating the spreadsheet, best way to communicate!
[16:36] <seb128> heh
[16:37] <seb128> didrocks, sil2100: what's the status of the gtk unity menu landing?
[16:37] <didrocks> yeah, now that the meeting is over, let's go on that one :)
[16:37] <didrocks> sil2100: you wrote "We're reverting the addition now since it would basically break unity"
[16:37] <didrocks> sil2100: what did you mean?
[16:38] <robru> cyphermox, wow, that diff just doesn't want to update on launchpad. I promise I fixed it though
[16:41] <cyphermox> yup, looks good
[16:41] <cyphermox> robru: do you have all the same commits in raring as in trunk for friends?
[16:42] <cyphermox> yeah, looking good
[16:43] <cyphermox> I think as soon as didrocks wants to stamp it, it's good :)
[16:43] <cyphermox> didrocks: you're in the review list, wanna just approve it or whatever?
[16:43] <robru> and then can somebody redeploy it and everything? I need to get this fix out asap ;-)
[16:44] <didrocks> cyphermox: I trust you, do you think I should look at it? (the discussion is enough for me to say "ok")
[16:44] <cyphermox> no
[16:44] <didrocks> cyphermox: so go ahead ;)
[16:44] <cyphermox> it's just that you're in reviewers somehow ;)
[16:44] <didrocks> robru: tired of getting crash reports? :p
[16:44] <cyphermox> robru: yeah. just waiting for it to get merged
[16:44] <robru> didrocks, we had three separate bugs reported just for this one thing. I wish people would stop reporting duplicate bugs.
[16:45] <cyphermox> robru: well..
[16:45] <robru> didrocks, best was that the guy who reported the third such bug went back and marked the two *older* ones as duplicates of *his*.
[16:45] <cyphermox> we kind of encourage them to report duplicate bugs and have us dedup, rather than mixing things up
[16:45] <cyphermox> heh
[16:45] <didrocks> robru: ahah, because "mine" is more important :)
[16:46] <robru> launchpad should know to prefer the oldest bugs by default when duplicates are being marked ;-)
[16:46] <cyphermox> Mirv: also, I'm patch pilot today, so I can help you ;)
[16:46] <robru> kenvandine, https://code.launchpad.net/~robru/friends/fix-threads-init/+merge/162692 can you approve this? trivial fix for a critical crasher in saucy
[16:47] <kenvandine> robru, done
[16:47] <robru> kenvandine, thanks
[16:48] <robru> alright, so now it's time for breakfast. back in a few ;-)
[16:48] <didrocks> FYI, utah just passed on the 100scopes thingy
[16:48] <didrocks> so there is hope for the touch stack! :)
[16:48] <didrocks> robru: enjoy ;)
[16:56] <attente> sil2100, hey
[17:03] <cyphermox> robru: no rest API makes it a little difficult to even update the jobs...
[17:04] <cyphermox> as soon as retoaded fixes that I'll update the jobs and we'll be able to release
[17:04] <didrocks> cyphermox: I've quickly rewritten https://wiki.ubuntu.com/DailyRelease/MovingNewRelease#Step_two:_once_release.2B-1_is_opened, feel free to edit it
[17:06] <didrocks> cyphermox: I've archived the disabling indicators as well as it's done
[17:08] <cyphermox> ok
[17:12]  * didrocks waves good evening, see you next week!
[17:13] <cyphermox> robru: ok, stuff is updated!
[17:14] <cyphermox> robru: so everything is ready for friends to be landing?
[17:21] <sil2100> attente: hi! Today I'm off, but let's talk tomorrow if it's not a problem
[17:21] <sil2100> attente: in the meantime - https://code.launchpad.net/~sil2100/unity-gtk-module/minor_ap_fixes/+merge/162851
[17:21] <sil2100> attente: in what timezone are you?
[17:22] <attente> sil2100, ah, sorry, wasn't aware
[17:22] <attente> i'm UTC-0500
[17:23] <attente> er. i guess UTC-0400
[17:24] <sil2100> attente: ok, so let's talk tomorrow :) Since I need to go now sadly
[17:24] <sil2100> See you then!
[17:24] <attente> sil2100, this looks good, thanks!
[17:28] <cyphermox> robru: friends started.
[17:35] <robru> cyphermox, yeah, everything is ready! thanks
[18:07] <Sweetshark> tedg, larsu: https://bugs.freedesktop.org/show_bug.cgi?id=64115 <- tricky one, do you know of any relevant fixes as candidates to be SRUed for precise?
[18:07] <ubot2`> Freedesktop bug 64115 in UI ": UI: menus are not dynamically changing under unity" [Normal,Needinfo]
[18:22] <robru> cyphermox, still around?
[18:23] <cyphermox> yeah
[18:23] <cyphermox> robru: watching friends build
[18:24] <robru> cyphermox, https://code.launchpad.net/~robru/cupstream2distro-config/disable-broken-apps/+merge/162858 these two apps fail the stack and shouldn't, so I'm disabling them until one of the webapps developers can fix them.
[18:25] <cyphermox> ack
[18:26] <robru> now to fix twitter... ;-)
[18:26] <cyphermox> ;)
[19:03] <tedg> Sweetshark, Interesting, I guess we need to know if it's only on Precise.
[19:04] <tedg> Sweetshark, We didn't change that much in indicator-appmenu for raring except to pull out HUD to it's own package.
[19:05] <tedg> Sweetshark, Added myself to CC
[19:21] <Sweetshark> tedg: thx
[22:45] <danilos> jasoncwarner, hi, jam has a problem with his unity after upgrade; who can help him out since both seb128 and didrocks are asleep?
[22:45] <desrt> mterry: hey.  is there any way to get deja-dup to run a hook script pre-backup?
[22:48] <robru> desrt, I bet the new upstart user sessions could be configured to run something right when deja-dup starts
[22:49]  * desrt wants it to run just before the backup starts, and for the backup to wait until it's done
[22:50] <robru> desrt, in that case, why not port deja-dup to just use upstart for its backup scheduling? then it would be really easy ;-)
[22:50] <desrt> that's actually a pretty good idea
[22:51] <robru> I bet mike would appreciate it ;-)
[23:03]  * desrt has devised a way to shrink his ~/code/ directory from ~6GB down to ~15M
[23:04] <TheMuso> desrt: Let me guess. Delete it. :p
[23:04] <desrt> basically, it's a mix of the following: use jhbuild dvcs_mirror with a directory in ~/.cache/
[23:04] <desrt> and make use of alternates when cloning
[23:05] <TheMuso> ah ok.
[23:05] <desrt> then, write a command (i call 'git tuck') that does this:
[23:05] <desrt> git stash -u
[23:05] <desrt> git prune; git repack -a -d -l
[23:05] <desrt> then nukes the working directory, keeping only the .git
[23:05] <desrt> and erases the index too
[23:05] <robru> wow. then what, you just check out what you need?
[23:06] <desrt> basically this will remove any object that's in the upstream repository from the local git object db
[23:06] <desrt> (ie: standard git-clone --reference type stuff)
[23:06] <desrt> but the next biggest thing in a git repo is all of the unpacked files (99% of which are unmodified)
[23:06] <robru> oh, I see, so you only keep the stuff you're working on, discarding whatever stuff has been accepted upstream
[23:07] <desrt> so this does a stash -u to store any changes you might have and then throws everything away
[23:07] <desrt> any local commits/branches you have are also saved
[23:07] <desrt> that's the beauty of git repack -l
[23:07] <desrt> it keeps only objects not found in the upstream repo
[23:08] <robru> desrt, what if you want to check out an old commit for testing purposes (say, bisecting a bug?) do you have to redownload all the objects?
[23:08] <desrt> well
[23:08] <desrt> if you still have the stuff in ~/.cache then you're OK
[23:09] <desrt> otherwise, yes, you have to download it again
[23:09] <desrt> the purpose of this is to get everything into the minimum possible size for backups
[23:09] <robru> desrt, I haven't paid much attention to disk usage in a long time, but my ~/src/ is only 1.1GB, so that's not bad. your trick won't work because mine's almost exclusively bzr.
[23:09] <desrt> :(
[23:10] <robru> desrt, good point. I personally don't see much value in backing up stuff that's already online, though. even my "local changes" are pushed to a branch somewhere.
[23:10] <desrt> i often get into a situation where i'll build up a fair amount of local changes (due to hacking on a plane or something) that don't get pushed
[23:11] <robru> yeah, gotta remember to push once you land ;-)
[23:11] <desrt> and for projects that i hack seriously on i usually have reams of local branches