[00:09] <jbicha> jcastro: of course, half the Desktop team is either French or Canadian or French-Canadien
[00:09] <jbicha> maybe more than half, I don't really keep track
[00:37] <mdeslaur> jbicha: make sure you don't mix up all three by accident, that would be an insult :)
[00:41] <jbicha> now I'm confused
[04:04] <pitti> Good morning
[06:52] <bkerensa> cyphermox: is there any readily available tool to chart/time how long it takes for a wifi connection to occur?
[06:57] <czajkowski> I'd be very surprised to see cyphermox online at this hour
[07:53] <Sweeshark> moin!
[07:53] <czajkowski> Sweeshark: good morning
[07:56]  * Sweeshark cries. the amd64 ppa-build has been canceled. While I dont know for sure, I assume it was someone seeing it had run out of disc space again.
[07:56] <Sweeshark> And I already removed the subsequentchecks/dev-install and some 100MB from the src-tarball (the latter should have freed some 200MB).
[07:58] <Sweeshark> The more I think about it, the more I come to assume, that it has little to do with changes in libreoffice (which after all killed the big binfilter stuff recently, so should still be smaller than it was before that).
[07:58] <czajkowski> Sweeshark: do you know which build machine it was
[07:58] <czajkowski> I know we are just getting one restarted there
[07:59] <Sweeshark> czajkowski: no, maybe https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-nattytest2/+build/4669264 helps you see which one it was?
[08:01] <Sweeshark> Im assuming now its more the dependencies of libreoffice each growing in size like cancer since we lost the CD-image limit.
[08:02] <Sweeshark> czajkowski: grapping for that straw (that the box was just rebooted), Ill reschedule that build optimistically now.
[08:02] <czajkowski> Sweeshark: it ran out of disc space and hung is why just asked in -ops
[08:02] <Sweeshark> czajkowski: sigh
[08:03] <Laney> happy happy friday
[08:05]  * Sweeshark look at the line in the rules file saying "ENABLE_JAVA=Y" with a lecherous gaze ...
[08:05] <czajkowski> Laney: peeka boo
[08:06] <Laney> hallo thar
[08:06] <Laney> last day?
[08:06] <czajkowski> yarp
[08:06] <czajkowski> been busy so far
[08:06]  * Laney sheds a tear
[08:06] <czajkowski> Laney: bah I'll see you in two weeks ;)
[08:07] <Laney> true that
[08:07] <Laney> is the new job working from home too?
[08:09] <czajkowski> oh hell ya :)
[08:09] <czajkowski> will go to the office for the first few weeks reguarly it's still in london
[08:09] <czajkowski> but I also have about 30-40% of my time to travel through EMEA
[08:10] <Laney> :O
[08:12] <sil2100> seb128: hi! Would you mind if I gave you some packaging diffs to take a look at? Since before publishing stacks, we need to have an archive admin to ACK the packaging changes
[08:13] <sil2100> seb128: it's all in one diff file usually
[08:14] <seb128> sil2100, sure, go for it
[08:14] <sil2100> seb128: SDK stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dee-qt_3.0daily13.06.14-0ubuntu1.diff
[08:15] <sil2100> seb128: and settings stack for now: http://10.97.0.1:8080/view/cu2d/view/Head/view/Settings/job/cu2d-settings-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-system-settings_0.1daily13.06.14-0ubuntu1.diff
[08:15] <sil2100> Both changes are sane from my point of view
[08:17] <seb128> sil2100, the dee-qt one is buggy
[08:17] <seb128> sil2100, the added copyright states
[08:17] <seb128> "either version 3 of the License, or
[08:17] <seb128> + (at your option) any later version."
[08:17] <seb128> but the license is GPL-3 and not 3+
[08:17] <seb128> so you either need to add the + or drop the "or any later version"
[08:18] <sil2100> Ah, right, I see that now, hm
[08:18] <sil2100> Let me check that package
[08:18] <seb128> sil2100, the settings one is fine (it's coming from me so I will not complain :p)
[08:19] <sil2100> seb128: ok, need to fix the copyright then, since it's GPL3 not 3+
[08:19] <sil2100> seb128: but publishing the settings stack ;)
[08:19] <seb128> sil2100, you can publish dee-qt but please fix in trunk
[08:20] <seb128> sil2100, e.g that's a typo, not worth having to retest/respin the stack
[08:20] <seb128> just make sure it's fixed for the next landing
[08:20] <sil2100> ACK :)
[08:22] <sil2100> seb128, Mirv: https://code.launchpad.net/~sil2100/dee-qt/fix_copyright/+merge/169362
[08:24] <seb128> sil2100, approved
[08:24] <sil2100> seb128: thanks! Another quick one, the misc stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Misc./job/cu2d-misc-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gnome-control-center-unity_1.3daily13.06.14.1-0ubuntu1.diff/*view*/
[08:26] <seb128> sil2100, looks fine to me
[08:26] <sil2100> Thanks :)
[08:30] <Laney> fixing g-c-c ftbfs
[08:31] <Laney> looks like goa dropped symbols "that were not part of the public API"... yeah...
[08:32] <Mirv> sil2100: ..appr.. damnit
[08:33] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/qtubuntu/dont_install_test_files_update_standardversion/+merge/169355
[08:34] <seb128> Laney, I fixed it in the vcs already
[08:34] <Laney> oh ok
[08:35] <seb128> Laney, I didn't upload because I was working on some other changes and wanted to batch them
[08:35] <seb128> Laney, sorry I fixed that some days ago but I figured out there was no point to upload the build fix by itself if another upload was coming
[08:35] <Laney> nm
[08:35] <seb128> did I forget to push?
[08:35] <Laney> no, I just didn't pull
[08:36] <seb128> ok ;-)
[08:36] <Laney> well, rather I worked from apt-get source ¬_¬
[08:36] <Laney> you revealed my secret reluctance to use our branches
[08:36] <Laney> BLAST
[08:36] <seb128> I'm looking at libgadu and gmock-test (just stating so we don't dup work)
[08:36] <seb128> lol
[08:37] <sil2100> Erm
[08:37] <sil2100> Mirv: so the -examples package is not valid?
[08:39] <Mirv> sil2100: yeah well it was either adding that or removing it altogether, and apparently Ken knew it was just a test binary (I also sweeped the device image yesterday and nothing uses it, but still kept it around in my branch)
[08:39] <Mirv> makes sense, though
[08:39] <sil2100> Mirv: ok, looking good, approving!
[08:41] <Mirv> thx!
[08:41] <sil2100> seb128: another one, network stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Network/job/cu2d-network-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_telepathy-ofono_0.2daily13.06.14-0ubuntu1.diff
[08:41] <sil2100> seb128: we're missing multiarch here, but we'll be adding that soon
[08:42] <seb128> sil2100, seems fine to me
[08:43] <sil2100> seb128: ok! Publishing, I think that once I do that, telepathy-ofono will land in NEW, since it's possible that it has not been released
[08:43] <sil2100> So it might need NEWing
[08:43] <seb128> ok
[08:43] <seb128> I can review it when it's in there
[08:53] <sil2100> Mirv: I'll re-run the platform stack once the location-service fix gets in
[08:54] <sil2100> Mirv: and publish it (along with the media stack) ;)
[08:56] <sil2100> Mirv: once that is done, I hope you won't mind I finally do some appmenu coding ;p?
[09:03] <Mirv> sil2100: thanks. any appmenu stuff is greatly appreciated, considering we really won't do Qt 5.1.1 upload (arrives probably around August) with the old patch! :)
[09:04] <Mirv> sil2100: you may want to check out the Qt 5.1 beta1 I've made available in a PPA, or just take the latest upstream 'stable' (5.1) branch
[09:04] <seb128> Laney, mono is unhappy about the new automake ... want to have a look?
[09:04] <seb128> Laney, btw do you know if there is any plan to follow debian on mono 3.0.6?
[09:05] <Laney> seb128: I'll pass it on and maybe look later
[09:05] <seb128> ok
[09:05] <Laney> and well, not right now - it's still a bit broken
[09:13] <Laney> (having said that: https://bugzilla.xamarin.com/show_bug.cgi?id=9324)
[09:13] <ubot2`> bugzilla.xamarin.com bug 9324 in packaging "cannot build with automake 1.13" [Normal,Resolved: fixed]
[09:15] <seb128> Laney, seems like an easy fix at least ;-)
[09:15] <seb128> looking at gtk2-engines
[09:16] <Laney> I'll try to dig them out
[09:19] <Laney> is someone fixing the indicators? :-)
[09:19] <pitti> anyone with an nvidia or ati graphics card here?
[09:19] <Laney> i'll do mono then gst
[09:19] <Laney> pitti: yes, I have nvidia
[09:19] <pitti> Laney: would you mind giving me the output of "udevadm info --export-db" on that system?
[09:20] <pitti> (as user is fine)
[09:20] <Laney> pitti: http://paste.ubuntu.com/5764102/
[09:20] <pitti> Laney: cheers
[09:21] <Laney> kein problem!
[09:22] <sil2100> seb128: do you know if there is anything else I need to do for you to be able to NEW a package that's new and not existing yet in the universe?
[09:22] <seb128> sil2100, no, which one needs newing?
[09:23] <sil2100> seb128: telepathy-ofono - it was part of network stack, published an hour ago ;)
[09:23] <sil2100> (through the publish job)
[09:24] <seb128> sil2100, it was not published, at least it's not showing up on https://launchpad.net/ubuntu/saucy/+queue?queue_state=0&queue_text=
[09:24] <pitti> Laney: oh crap, that doesn't have a vendor/product name any more for your card
[09:25] <pitti> Laney: just for completeness, that I can make sure I fix ubuntu-drivers-common properly, "ubuntu-drivers debug" output please?
[09:25] <sil2100> seb128: strange, the publish job says all is ok: http://10.97.0.1:8080/view/cu2d/view/Head/view/Network/job/cu2d-network-head-3.0publish/lastSuccessfulBuild/artifact/packagelist_rsync_network-head/*view*/
[09:25] <sil2100> 2013-06-14 08:43:49,758 INFO Writing packagelist_rsync_network-head for being able to rsync from main machine
[09:25] <sil2100> list is: [('qa', 'head')]
[09:26] <sil2100> I wonder if Didier was doing anything else...
[09:26] <Laney> pitti: yep, http://paste.ubuntu.com/5764117/
[09:26] <pitti> Laney: thanks²
[09:26] <Laney> kkpp
[09:27] <pitti> *chuckle*
[09:28] <pitti> Laney: double negation!
[09:29] <seb128> sil2100, can you retry? the lillypilly checkout was not uptodate
[09:29] <seb128> sil2100, https://wiki.ubuntu.com/DailyRelease/FAQ mentiones "Then, ping an archive admin so that he pulls the modification on lillypilly for the second-safety check process. "
[09:30] <seb128> sil2100, so maybe ofono was not in the safe-to-publish list yet on that side
[09:30] <seb128> sil2100, I've pulled so it should be fine if you retry
[09:31] <pitti> Laney: what does "udevadm test-builtin hwdb /devices/pci0000:00/0000:00:01.0/0000:01:00.0" say for you?
[09:31] <sil2100> seb128: ok, re-publishing then
[09:32] <Laney> pitti: calling: test-builtin
[09:32] <Laney> error reading /etc/udev/hwdb.bin: No such file or directory
[09:32] <Laney> load module index
[09:32] <Laney> unload module index
[09:33] <sil2100> seb128: I thought that pinging the archive admin should be done after publishing
[09:33] <pitti> Laney: ack, thanks; I smell an udev bug for me
[09:33] <Laney> :-)
[09:33] <seb128> sil2100, well the publishing didn't happen because you have a new package which was not in the security-check-list
[09:33] <seb128> sil2100, there is a second list on the other side of the publisher that checks that we don't publish things we are not meant to
[09:34] <seb128> sil2100, that's to avoid having somebody e.g adding "linux" to the ps jenkins and having you guys upload the kernel when you are not supposed to have upload rights for that
[09:35] <sil2100> k
[09:37] <sil2100> hm, the re-run of the publisher probably did not upload anything
[09:37] <sil2100> Since I think it thinks it already did previously ;/
[09:38] <sil2100> 2013-06-14 09:32:08,518 INFO Copying from https://api.launchpad.net/devel/~ubuntu-unity/+archive/daily-build (Release) to https://api.launchpad.net/devel/ubuntu/+archive/primary (Proposed) for saucy series
[09:38] <sil2100> Although it says this?
[09:39] <seb128> sil2100, get a fake commit if you need a version bump?
[09:47] <sil2100> seb128: I wonder if a commit that just adds a changelog entry is enough
[09:47] <seb128> sil2100, should be
[09:51] <sil2100> seb128: ok, I'll try to re-run the stack
[09:51] <seb128> ok
[10:03] <sil2100> seb128: we have an issue in the build scripts, I need to fix that first, sorry about the wait...
[10:04] <seb128> sil2100, no worry, I'm not blocked or waiting on that, I will just review when ready ;-)
[10:10] <mhr3> sil2100, btw did you have a chance to look at the soname bump for unity-core? a check would be appreciated, i basically just ran sed :)
[10:10] <seb128> sil2100, do you know what happened to the unity SRU for raring? it vanished from the queue
[10:10] <seb128> did infinity reject it?
[10:10] <Laney> seb128: See the #-release backlog
[10:11] <Laney> it broke because it expired from launchpad
[10:11] <Laney> they need to start using a staging PPA for SRUs
[10:11] <seb128> Laney, I just looked to http://irclogs.ubuntu.com/2013/06/14/%23ubuntu-release.html and don't have a match for unity
[10:11] <Laney> look for compiz
[10:11] <seb128> oh ok
[10:12] <seb128> pffff
[10:12] <seb128> that's what happen when the SRU team takes over a month to review SRUs for our main desktop
[10:13] <seb128> that's ridiculous
[10:13] <sil2100> seb128: uh, didn't hear anything about it
[10:13]  * seb128 goes to read what happened on the TB discussion 
[10:13] <seb128> sil2100, you will need to get it republished
[10:13] <seb128> and hope infinity takes less than a month this time to review it
[10:14] <sil2100> Mirv: ^
[10:15] <pitti> Laney: FYI, filed as bug 1190947
[10:15] <ubot2`> Launchpad bug 1190947 in systemd (Ubuntu) "[udev] missing vendor/product names of devices (missing hwdb.bin)" [Medium,Triaged] https://launchpad.net/bugs/1190947
[10:16] <seb128> pitti, speaking about systemd, is that logind that suspends my box on lid close nowadays?
[10:16] <Laney> cheers
[10:16] <Laney> not that I noticed any symptoms of this bug :P
[10:16] <pitti> seb128: it's meant to be, anyway; but our g-s-d power plugin also does it; bug 1180513
[10:16] <ubot2`> Launchpad bug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [High,Triaged] https://launchpad.net/bugs/1180513
[10:16] <pitti> seb128: what needs to happen is that g-s-d power inhibits logind's suspend-on-lid (that's done in 3.8, but not in our 3.6)
[10:17] <Laney> ah it manifests itself in s-p-gtk
[10:17] <seb128> pitti, do you know if anyone has filled a bug about "shouldn't suspend during shutdown"? I picked "shutdown" yesterday, closed my lid and found out later than it suspend on the plymouth shutdown logo
[10:17] <pitti> Laney: bug 1186777
[10:17] <ubot2`> Launchpad bug 1186777 in ubuntu-drivers-common (Ubuntu) "Does not show vendor/model name any more" [Undecided,In progress] https://launchpad.net/bugs/1186777
[10:17] <Laney> got it
[10:17] <seb128> pitti, when I woke it up I had 3 seconds of plymouth and shutdown finished
[10:17] <pitti> seb128: I don't know about that one, no
[10:17] <seb128> ok
[10:18] <seb128> is systemd the right component to bug?
[10:18] <pitti> seb128: I guess we need to do that in systemd-shim
[10:18] <pitti> as logind otherwise doesn't know that a shutdown has been requested already
[10:18] <seb128> k, I will talk to desrt when he's online
[10:18] <seb128> pitti, danke
[10:24] <sil2100> seb128: hmmm... I re-published telepathy and hm
[10:24] <sil2100> seb128: I still can't see it in NEW
[10:24] <sil2100> seb128: do we need to wait a moment?
[10:26] <seb128> sil2100, the queue updates every 5 minutes let's wait a few minutes
[10:26] <seb128> sil2100, otherwise we will need didrocks on monday I guess
[10:30] <Laney> is libappindicator going to daily release soon?
[10:30] <Laney> the build failure fix is in trunk
[10:31] <Laney> (it's funny how the fix for that problem everywhere is to disable it)
[10:31] <sil2100> seb128: telepathy-ofono is there \o/
[10:32] <seb128> sil2100, good ;-)
[10:33] <seb128> Laney, same for some of the indicator-* I guess
[10:34] <sil2100> Laney: so, indicators... let me remember the status
[10:34] <seb128> Laney, well, at the same time we have no hurry to fix those build issues, knowing that the next upload will build anyway
[10:34] <seb128> looking to indicators stack on jenkins there are some "scary" changes in there
[10:35] <seb128> e.g port the new format
[10:35] <Laney> didn't check the others
[10:35] <sil2100> Laney: I think we need to release indicators and unity at the same time
[10:35] <Laney> libappindicator looks kind of small-ish since the last release
[10:35] <sil2100> Which would basically mean we'll have to fix up HUD first for the tests to pass
[10:35] <Laney> don't know what the latest change is though
[10:35] <seb128> http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/
[10:35] <Laney> seb128: still it's good to have stuff building in the archive if possible
[10:36] <seb128> http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libindicator_12.10.2daily13.06.14-0ubuntu1.diff
[10:36] <seb128> for example
[10:36] <seb128> +  [ Lars Uebernickel ]
[10:36] <seb128> +  * Merge lp:~larsu/new-indicator-file-format IndicatorNg: update
[10:36] <seb128> +    indicator file format The old file format had some shortcomings: (1)
[10:36] <seb128> +    It was impossible to efficiently reuse a menu for different
[10:36] <seb128> etc
[10:37] <Laney> right
[10:44] <seb128> sil2100, telepathy-ofono NEWed
[10:44] <sil2100> seb128: thank you!
[10:45] <seb128> yw ;-)
[10:46] <Laney> seb128: did you look at bluetooth yet?
[10:47] <seb128> Laney, sort of, I glanced at the log, seems like a case of "turn of Werror", but I didn't start on it ... if you want to fix it, please do ;-)
[10:47] <Laney> haha, OK
[10:47] <seb128> I'm doing some piloting
[10:47] <seb128> I missed my shift earlier in the week, I was too busy on system settings :p
[10:47] <Laney> I think it's going to be that XID has a different type
[10:48] <seb128> well, it has also "variable not used" warnings
[10:48] <seb128> turn off Werror :p
[10:49] <Laney> those are warnings
[10:49] <Laney> found https://git.linaro.org/gitweb?p=people/tomgall/oe/meta-openembedded.git;a=commitdiff;h=9c657f0e6975a283fcc8f3b748c006882fab961a
[10:49] <sil2100> seb128: quick question - are we providing powerpc in the archive?
[10:50] <Laney> yes
[10:50] <seb128> sil2100, what's the real question? we do but qt5-declarative isn't available on it because v8 is not
[10:51] <sil2100> seb128: ah, ok, I was asking because dbus-cpp (a package that will need to be NEWed pretty soon) has broken tests on powerpc and fixing them is non-trivial right now, so I wanted to disable those for powerpc
[10:51] <sil2100> seb128: and have been wondering if that would be acceptable by distro
[10:52] <seb128> it's not ideal, but I wouldn't block things on ppc tests
[11:10] <desrt> seb128: sup?
[11:10] <seb128> desrt, hey
[11:11] <seb128> desrt, <seb128> pitti, do you know if anyone has filled a bug about "shouldn't suspend during shutdown"? I picked "shutdown" yesterday, closed my lid and found out later than it suspend on the plymouth shutdown logo
[11:11] <pitti> hey desrt
[11:11] <desrt> are we sending shutdown requests via systemd?
[11:11] <desrt> or just calling 'shutdown'?
[11:12] <pitti> via logind
[11:12] <desrt> so i added logic to systemd-shim about this....
[11:12] <desrt> surprised to hear that it's not working
[11:13] <desrt> the code is pretty simple....
[11:13] <desrt> https://github.com/desrt/systemd-shim/blob/master/src/power-unit.c#L45
[11:14] <desrt> when it starts a shutdown/reboot it sets 'in_shutdown' to TRUE
[11:14] <desrt> if in_shutdown is true, further suspend/hibernate requests are ignored
[11:16] <mitya57> seb128: thanks for uploading qt4!
[11:16] <seb128> mitya57, yw
[11:22] <seb128> desrt, pitti: my auth.log has "00:05:24 localhost systemd-logind[930]: System is powering down."
[11:22] <seb128> so shutdown was indeed done correctly through logind
[11:26] <desrt> perplexing
[11:26] <seb128> is there any debug info I can provide if that happens again?
[11:27] <seb128> don't worry much, it's a minor issue, I was just wondering wth my suspend led was blinking after shutdown :p
[11:27] <desrt> i wonder if maybe the shutdown was going via the other route instead....
[11:27] <desrt> pitti: did you remove the fallback path to pmutils in logind?
[11:27] <desrt> s/shutdown/suspend/
[11:32] <desrt> seb128: was the shutdown taking a really long time?
[11:32] <desrt> the other thing i remember is that the shim quits after 10 seconds of inactivity....
[11:33] <desrt> so shutdown, wait 10 seconds [shim quits], close lid
[11:33] <desrt> in that case, that variable would be back to false again and the suspend would go through
[11:33] <seb128> desrt, no, 5-10s, the user session took some 5 seconds to close, I saw the plytmouth logo some seconds later and closed the lid at this point
[11:33] <desrt> seb128: 5-10s is still on the order of 10s, maybe....
[11:33] <seb128> could be yes
[11:34] <seb128> if that from the moment the shutdown action is called?
[11:34] <desrt> yes
[11:34] <seb128> could well be 10s then yes
[11:34] <seb128> the user session took almost 10s to close
[11:34] <desrt> sounds right, then
[11:34] <desrt> i'll do a patch to keep the thing alive forever when shutting down or rebooting
[11:34] <seb128> (hate how logout is slower than login)
[11:34] <desrt> i bet that's the issue
[11:35] <seb128> thanks ;-)
[11:43] <pitti> desrt: yes, I did
[11:43] <pitti> desrt: thanks!
[13:25] <tedg> seb128, Are we changing BlueZ versions in Saucy?
[13:25] <seb128> tedg, not planned
[13:25] <tedg> K
[13:25] <tedg> seb128, Do you think that's going to hit in Terrified?
[13:26] <seb128> tedg, we discussed it around february, but bluez5 requires a newer version of linux that the one that was used for some touch images
[13:26] <seb128> and it was not a priority
[13:26] <seb128> we can still re-evaluate if there is a need
[13:26] <tedg> K, I've got no reason to change, just wanting to know for making sure we get porting on the schedule.
[13:26] <seb128> but there was nothing in 5 that we needed for the phone v1
[13:27] <tedg> We might need to for T because of NM using it and not wanting to support an older version for the LTS.
[13:27] <seb128> tedg, I doubt we will update before v1 if there is no strong reason, we don't have resources to waste
[13:27]  * ogra_ doubts touch images will get any newer kernels in T
[13:27] <seb128> tedg, let's see when that happens, meanwhile upstreams can port their code
[13:28] <tedg> Yup, okay.
[14:04] <cyphermox> bkerensa: there isn't. you'll probably just want to take the times from syslog
[14:28] <seb128> jbicha, hey, I saw you tried some bugs about the sound recorder, bug #1159744 is about the issue
[14:28] <ubot2`> Launchpad bug 1159744 in gnome-media (Ubuntu) "replacment for gnome-media" [Undecided,Confirmed] https://launchpad.net/bugs/1159744
[14:29] <seb128> jbicha, basically a contributor ported it to gstreamer1 but the GNOME guys said the component was deprecated and would want to take the patches/make new releases it seems
[14:30] <jbicha> seb128: I'm dropping gnome-media for Ubuntu GNOME, if that fork gets packaged I don't know if we'll include it or not; I mean how often do people need a Sound Recorder app anyway?
[14:31] <seb128> quite some people use one apparently
[14:31] <seb128> it has been requested by oems to our oem team in the past and we had quite some bugs reports about it not working since it's broken
[14:55] <Laney> we should probably remove it meanwhile
[15:03] <seb128> Laney, or just apply the patch from the contributor (would avoid to have to package a new source etc)
[15:03] <seb128> on that note I'm out for some exercice, be back in ~1h
[15:04] <Laney> it doesn't seem to really be a patch ...
[15:04] <seb128> it's mostly a rewrite port yes...
[15:04] <Laney> get him to release, package it with the same packaging and rename the packages
[15:05] <Laney> assuming it works etc
[15:25] <sil2100> Slowly slowly unblocking stacks...
[15:47] <sil2100> seb128: still around ;) ?
[15:48] <Laney> run
[15:48] <Laney> run fast!
[15:49] <sil2100> seb128: could you ACK the diffs? I want to publish the apps stack, here are the diffs:
[15:49] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67daily13.06.14.1-0ubuntu1.diff
[15:49] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_notes-app_1.4daily13.06.14-0ubuntu1.diff
[16:00] <sil2100> robru__: ping
[16:07] <sil2100> kenvandine: ping!
[16:07] <sil2100> kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/remove_powerd_from_packages/+merge/169479
[16:08] <sil2100> kenvandine: could you check that? Since the platform stack does not work right now ;)
[16:11] <sil2100> hmmm
[16:12] <kenvandine> sil2100, done
[16:17] <seb128> sil2100, hey, I'm back, still need me
[16:17] <seb128> ?
[16:23] <qengho> chrisccoulson: I think I'm hitting that same ARM instuction-set problem you discovered in December. What did you do to toolchains then?
[16:23] <qengho> I'm curious if it regressed.
[16:24] <chrisccoulson> qengho, the binutils update was never published (it's waiting on chromium). are you using the one from https://launchpad.net/~canonical-arm-dev/+archive/ppa ?
[16:25] <sil2100> seb128: yes ;)
[16:25] <sil2100> seb128: could you check those diffs and ACK?
[16:25] <sil2100> I'll publish that stack then
[16:26] <sil2100> kenvandine: thanks!
[16:26] <qengho> chrisccoulson: er, hrm. I'm using only stock precise. Did we just change chromium build-flags or -deps?  I don't remember reverting anything here, but I'll check.
[16:26] <sil2100> kenvandine: do I have to redeploy the stack for those changes to take effect?
[16:27] <chrisccoulson> qengho, i suspect it will work if you use the updated binutils, assuming it's the same issue
[16:28] <kenvandine> sil2100, dunno
[16:28] <seb128> sil2100, those diffs look fine to me
[16:28] <sil2100> seb128: thanks!
[16:28] <qengho> chrisccoulson: but I can't rely on that when I give #security source packages, right?
[16:29] <chrisccoulson> qengho, yes. it was always the intention to build with the fixed binutils, and publish that to the security pocket
[16:29] <qengho> chrisccoulson: FWIW: http://pastebin.ubuntu.com/5765160/  SEGV coming up, and a branch into middle of a function is queer.
[16:33] <sil2100> kenvandine: hm, maybe I'll redeploy the stack - it shouldn't hurt, right?
[16:44] <sil2100> kenvandine: yes, it seems that redeployment of the stack was needed ;)
[16:48] <sil2100> kenvandine: ping again ;p
[16:49] <sil2100> kenvandine: it seems the list of packages we added yesterday is not enough...
[16:49] <sil2100> kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/platform_add_extra_packages/+merge/169496
[16:50] <sil2100> robru__: poke me once you're here
[16:58] <Laney> yay, found the right place to poke db5.3 to get it to build
[16:58] <seb128> Laney, great
[16:58]  * Laney smacks the toolchain
[16:59] <sil2100> cyphermox: hi! Maybe you could approve? ^
[16:59] <cyphermox> sure
[17:00] <sil2100> Thanks!
[17:02] <cyphermox> done
[17:02]  * cyphermox goes to grab lunch
[17:02] <sil2100> \o/
[17:13] <sil2100> seb128: !
[17:13] <sil2100> seb128: can you help me with another stack?
[17:14] <sil2100> seb128: the platform stack, it has 3 diffs, there are 2 new packages (will need NEWing)
[17:14] <sil2100> seb128: could you:
[17:14] <sil2100> seb128: 1) ACK the diffs that are here http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/
[17:15] <sil2100> seb128: 2) if they're ok, could you prepare lilly for the 2 new packages: dbus-cpp and location-service?
[17:15] <sil2100> seb128: I would then publish and those two would appear in the NEW queue
[17:15] <seb128> sil2100, is that the packages didrocks prereviewed for NEW yesterday?
[17:16] <sil2100> seb128: yes ;)
[17:16] <seb128> sil2100, diffs look fine
[17:16] <sil2100> seb128: we just disabled the powerpc unit tests for dbus-cpp packaging-wise, since fixing them would take a while (will fix them later)
[17:17] <sil2100> seb128: could you prepare things for publishing so that those can get accepted to the  queue?
[17:17] <seb128> sil2100, I don't know how to do that, let me have a look
[17:17] <seb128> sil2100, what I did earlier was just to pull the new stack config
[17:17] <sil2100> seb128: I think it's the part to upload things to lilly?
[17:18] <seb128> stacks/head/platform.cfg:    dbus-cpp:
[17:18] <seb128> stacks/head/platform.cfg:    location-service:
[17:18] <seb128> sil2100, I think that should be fine, they are already in the stack config
[17:18] <sil2100> location-service is there as well? Ok, since we had those, but we had them on daily_release: False
[17:19] <seb128> sil2100, let's try, if that doesn't work we will fix it on monday
[17:19] <sil2100> seb128: then I'm publishing, if they pop up in the queue, I would be grateful for NEWing ;)
[17:19] <seb128> will do
[17:19] <sil2100> seb128: and now I need to pop out, so see you later and thanks!
[17:19] <seb128> sil2100, it's a good time to call it a week
[17:19] <seb128> sil2100, have a nice w.e!
[17:57] <robru__> sil2100, hi
[18:03] <robru> sil2100, actually I'm running out for breakfast in a minute, apologies for my tardiness. Just email me whatever you were concerned about and I'll take care of it when I get back.
[18:04] <Laney> mlankhorst: do you ever get into a situation where someone overtakes you and then you end up riding uncomfortably fast to keep up with them?
[19:16] <Eggman2013> I have installed ubuntu from a netinstall
[19:16] <Eggman2013> it shows ubuntu base
[19:17] <Eggman2013> i only have the console.  Does anyone know how I get kde or gnome up and running?
[19:29] <sarnold> Eggman2013: try "apt-get install kde-full" as a starting point
[19:29] <Eggman2013> ok thanks
[19:46] <sil2100> robru: hi!
[19:47] <sil2100> robru: I wanted to poke you about the webapps stack
[19:47] <sil2100> robru: since the webapps-linkedin is failing to build due to a test failing
[19:47] <sil2100> robru: could you take care of that? I need to weekend now ;)
[19:47] <sil2100> robru: so see you around!
[20:21] <mlankhorst> Laney: where? on a bike?
[20:22] <mlankhorst> on a bike is simple, I just let them take all the wind and go fast myself :D
[21:02] <Laney> mlankhorst: yeah
[21:03] <Laney> when I feel like it's someone I should be faster than, yet somehow am not
[21:03] <Laney> I did it today up this steep hill and almost died
[21:03] <Laney> overtook him at the end though \o/
[21:06] <mlankhorst> hehehehe
[21:06] <mlankhorst> Laney: I did that a few days ago with 4 bikers all dressed up for it and with real bikes
[21:06] <mlankhorst> but I was taking it easy at the calm, and the wind was against me, so I just let them carry me most of the time
[21:07] <mlankhorst> (me with a normal looking bike, with stuff in my bike bags, when they slowed down i took over and carried them for a bit, was fun, but it left me totally dead at the stables I was heading to)
[21:15] <mlankhorst> Laney: best way to do it is if you only go at 50-60% of your max capacity before yourself
[21:16] <Laney> well that's what i thought happened at first
[21:16] <mlankhorst> you definitely didn't, then :D
[21:16] <Laney> he sped off past me when i was slowing down for some lights so i thought i'd be able to catch up with ease
[21:16] <Laney> but then it wasn't so easy
[21:17] <mlankhorst> some people have trained a lot more than you
[21:17] <Laney> didn't look like a serious biker
[21:17] <mlankhorst> another time I just followed a single biker in his trail, talked to him a bit, he was just taking it easy while I was definitely at 80%
[21:18] <mlankhorst> (turns out a few days ago he did 100+ km in a group of 16 with 34km/h average, forgot exact distance)
[21:19] <Laney> my god