[04:57] <pitti> Good morning
[05:01] <Tm_T> sv/aelyu sv
[05:19] <pitti> Tm_T: I hope it was your cat and not your password :)
[05:20] <Tm_T> pitti: heh, I managed to post something? I had two irssis running on top of each other, I simply tried to close this nicely but ended up killing the processes
[05:21] <Tm_T> I wonder how that whole mess even happened
[07:45] <sil2100> Morning! Damn, I overslept, went to sleep too late
[07:45] <didrocks> sil2100: hey, how are you?
[07:46] <didrocks> (apart from this oversleeping ;))
[07:46] <seb128> good morning desktopers
[07:46] <seb128> hey didrocks, sil2100
[07:46] <didrocks> salut seb128!
[07:46] <sil2100> didrocks: hi! After python-qt4 got finally published, I had to re-run indicators twice - since for the first time we had some failures on one machine
[07:46] <sil2100> didrocks: I wonder how it looks now
[07:46] <didrocks> sil2100: but it didn't publish?
[07:47] <didrocks> sil2100: from what I see, not really good
[07:47] <didrocks> sil2100: I propose that we unblock that with a hangout if you don't mind
[07:47] <didrocks> (after your coffee)
[07:50] <sil2100> Well, yesterday it failed 4 tests on one machine, I re-run it but didn't see the results, hope it all looks ok - I also ran unity with whole-ppa enabled, but I'll look at the stacks in a moment and know what's up
[07:51] <didrocks> sil2100: shouldn't we have this hangout? all the stacks tests fail and I prefer that we debug together
[07:51] <didrocks> (you can see in 2 minutes that all the stacks failed btw :p)
[07:54] <sil2100> Need VPN to work with a cherry on top pleaase
[07:54] <sil2100> :D
[07:54] <didrocks> heh, is it failing for you?
[07:54] <didrocks> (and can you please answer by yes or no on the hangout question? :p)
[07:58] <sil2100> Ok, ready
[07:58] <sil2100> Let's hang out
[08:00] <sil2100> didrocks: hm, why are those tests failing now I wonder? Yesterday at night they actually ran with the new python-qt
[08:01] <sil2100> didrocks: this is the first run I made: <IP_ADDRESS>:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.2check/196/
[08:01] <sil2100> The second one was the same, but hm, strangly also the same number of failures
[08:02] <sil2100> And now suddenly the sip problem again
[08:02] <didrocks> sil2100: https://plus.google.com/hangouts/_/2175b6828a78257a1bc2f4243a84d6bb5ad5c333 in case you didn't receive the notification :)
[08:03] <Laney> g'morning
[08:04] <seb128> Laney, hey, how are you?
[08:04] <Laney> pretty good thanks
[08:05] <Laney> you
[08:05] <Laney> ?
[08:05] <mlankhorst> morning!
[08:06] <mlankhorst> Laney: I learned that I shouldn't try to overtake, or even try to tail, bikers who wear special glasses..
[08:06] <Laney> special glasses?!?!?!?!
[08:06] <seb128> Laney, I'm good thanks, enjoying the not-so-warm-yet temperature of the morning
[08:06] <Laney> hah, I remember now - today was supposed to be storm day
[08:07] <mlankhorst> biker glasses or something, those that don't allow air to pass to the eyes
[08:07] <Laney> oh yes
[08:07] <mlankhorst> http://www.bikester.nl/344505.html things like those
[08:07] <Laney> too fast? :P
[08:07] <mlankhorst> definitely!
[08:10] <Laney> I should get some bike shorts
[09:01] <sil2100> didrocks: hmmm, it seems the Apps tests for ati are having some problems
[09:01] <didrocks> sil2100: have you poked upstream? they should help fixing those :)
[09:01] <sil2100> didrocks: http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/170/label=autopilot-ati/console
[09:02] <sil2100> Hard to say what's up, since it looks a bit hanged ;p
[09:02] <sil2100> It doesn't want to finish!
[09:02] <didrocks> jibel: hey, do you have time to have a look? ^ quite stuck on the webcreds part
[09:03] <jibel> didrocks, sure, looking
[09:03] <didrocks> thanks
[09:03] <sil2100> jibel, didrocks: I saw some errors in the tests, i.e. in the autopilot parts, but still, it's hanged
[09:10] <seb128> Laney, hey, did you see andyrocks updated the patch for nautilus/trash segfault? in case you didn't start on it let it to me, I've another patch I want to include in the upload
[09:10] <Laney> seb128: yeah I'm looking at it atm as it happens
[09:11] <seb128> Laney, k, please don't upload then, just commit to the vcs
[09:11] <Laney> it does fix the crash but it's not /right/
[09:11] <Laney> you get a warning about the signal handler not existing
[09:11] <seb128> oh?
[09:11] <Laney> don't know why
[09:12] <jibel> didrocks, sil2100 autopilot process is running but is waiting on something (it's looping on [pid 13445] select(5, [4], [], [], {0, 500000}) = 0 (Timeout))
[09:13] <jibel> didrocks, sil2100 there is the following message in dbus.log, I don't know if there is a relation:
[09:13] <jibel> start: Job is already running: hud
[09:13] <jibel> Failed to activate service 'com.canonical.hud': timed out
[09:13] <sil2100> hmmm
[09:14] <jibel> didrocks, sil2100 I cannot connect to the KVM to see what's happening on the screen, the java plugin is broken again
[09:14] <darkxst> seb128, if I get g-s-d 3.8 ready to run with g-c-c 3.6, can we get that onto the ubuntu-desktop ppa?
[09:15] <darkxst> although not real sure on the whole ibus situation, currently that is disabled in the gnome3 builds
[09:16] <seb128> darkxst, g-s-d 3.8 and g-c-c 3.6 ... sounds good, I will review it if you get it working, once step at the time is better
[09:17] <sil2100> jibel: hm, so what can we do now besides killing the job?
[09:17] <sil2100> That's the first time this is happening, maybe it's just a singular case?
[09:17] <sil2100> jibel: not sure if it makes sense to block all other test jobs
[09:18] <jibel> plugin fixed, wrong alternative
[09:18] <darkxst> seb128, ok, will do
[09:18] <seb128> darkxst, thanks
[09:18] <didrocks> sil2100: just a note, don't touch the webcreds stack please :)
[09:18] <sil2100> didrocks: ACK ;)
[09:18] <didrocks> thx!
[09:20] <jibel> sil2100, didrocks so on the screen, everything is there (launcher, menus, ...) and responsive, just autopilot which is waiting for something
[09:22] <jibel> sil2100, it could be a broken tests waiting for an event that'll never happen? I saw something similar when autopilot was trying to reach an icon that was out of the screen on the launcher.
[09:25] <jibel> sil2100, I kill the webbrower_app test
[09:27] <sil2100> jibel: hm, it might be, since I saw some errors in the webbrowser tests when looking at the logs
[09:28] <sil2100> So something might have been broken, but it will be hard to see what - normally everything is handled by timeouts, so it should be impossible
[09:28] <sil2100> As we're using Eventually() for every waiting condition, which has a default 10 second timeout
[09:28] <jibel> sil2100, anyway, it was the last test and all 78 ran http://<IP_ADDRESS>:8080/view/cu2d/view/Autopilot%20Release%20Testing/job/autopilot-saucy-daily_release/170/testReport/
[09:29] <sil2100> But so many failed?
[09:29] <jibel> sil2100, 23 failed
[09:29] <sil2100> jibel: thanks! Let me check that and re-run later, thanks for the analysis ;)
[09:37] <didrocks> sil2100: indicators passed! (one test failing, below the threshold)
[09:37] <didrocks> hud*
[09:37] <didrocks> now indicators?
[09:37] <didrocks> sil2100: hud in manual publication apparently
[09:37] <sil2100> First I re-run Apps
[09:38] <didrocks> let's cross fingers :)
[09:42] <sil2100> In the meantime, let me publish HUD - it's safe to use with old unity (just tested)
[09:44] <sil2100> didrocks: http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/HUD/job/cu2d-hud-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_hud_13.10.1daily13.06.19-0ubuntu1.diff/*view*/ <- look ok, can I publish? ;)
[09:46] <didrocks> sil2100: +1 :)
[09:47] <seb128> \o/
[09:49] <Laney> seb128: ok, got a fix ...
[09:49] <Laney> let me attach it upstream and push to bzr
[09:50] <seb128> Laney, great, thanks
[09:50] <Laney> It changes how it does the disconnection because I didn't understand why it was already disconnected :P
[09:50]  * Laney prepares to get abused a bit
[09:50] <seb128> lol
[09:51] <sil2100> didrocks: can I publish the apps stack? As it's deping on webcreds
[09:52] <sil2100> (all tests passed \o/)
[09:54] <sil2100> I guess it's ok to publish ;)
[09:58] <didrocks> sil2100: sure sure, I trust you, and you don't need me if there is no packaging change for an ack!
[09:59] <didrocks> sil2100: so, indicators now?
[10:00] <sil2100> Yesss ;)
[10:01] <Laney> seb128: ok pushed
[10:01] <Laney> yay indicators
[10:01] <seb128> Laney, thanks
[10:06] <didrocks> Laney: tests didn't pass yet, don't declare victory :)
[10:11] <didrocks> seb128: the unity_gtk_modules tests never passed since we added it, can we have attente having a look?
[10:11] <didrocks> sil2100: I think we should force the publication even if the tests are failing as it's the unity_gtk_modules ones, wdyt?
[10:18] <didrocks> sil2100: as all the other tests seem good
[10:18] <didrocks> apart from those flacky unity gtk module ones
[10:18] <didrocks> right?
[10:19] <sil2100> Yep, and I upgraded and checked: new indicators don't seem to break old unity
[10:19] <didrocks> ok :)
[10:19] <sil2100> didrocks: should I just run the publish job then?
[10:19] <sil2100> (without force)
[10:19] <didrocks> sil2100: yeah, I guess then it will be in manual publication, but at least, we'll see why :)
[10:19] <sil2100> Lots and lots of packaging changes to browse through! Uh oh ;)
[10:19] <didrocks> sil2100: I removed libical1 from the list FYI
[10:20] <didrocks> sil2100: or maybe, let's wait for the next iso to clean that
[10:22] <didrocks> sil2100: have you restarted the version? bamf changes still works with old unity?
[10:22] <seb128> didrocks, do you guys need extra testers? I can opt in the ppa if wanted
[10:23] <didrocks> seb128: if you can upgrade bamf without the rest, that would be helpful, please
[10:23] <sil2100> didrocks: I installed new bamf and ran a guest session
[10:24] <seb128> ok, from what ppa? ubuntu-unity/daily-build/ubuntu saucy?
[10:24] <sil2100> didrocks: and unity wasn't broken, launcher worked, pips appearing, switcher ok
[10:24] <didrocks> sil2100: waow, that's awesome seeing the port! :)
[10:24] <didrocks> seb128: ubuntu-unity/daily-build saucy, yet
[10:24] <sil2100> didrocks: I'm checking the diffs now ;)
[10:24] <didrocks> yeah*
[10:24] <didrocks> sil2100: doing the same as well to not loose time, but good practice for you :)
[10:25]  * didrocks snifs seeing no trailing comma on gnome-screensaver
[10:26] <didrocks> jbicha!!! :p
[10:28] <sil2100> didrocks: hmmm, libusermetrics should export symbols in .symbols? Since it's C++ and the symbol names are mangled ;/
[10:29] <didrocks> sil2100: yeah, it passed and built on all archs though. So it will be interesting to see with pete how it works now
[10:29] <didrocks> sil2100: maybe the check is only run on the same arch now
[10:31] <seb128> didrocks, sil2100: new bamf works fine on saucy
[10:31] <didrocks> (thanks seb128
[10:31] <seb128> np
[10:31] <sil2100> didrocks: besides those small things the diffs look ok
[10:31] <sil2100> didrocks: how do you think, can I publish?
[10:31] <sil2100> s/how/what
[10:31] <didrocks> sil2100: there is maybe an issue on http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libindicator_12.10.2daily13.06.19-0ubuntu1.diff
[10:32] <didrocks> -usr/share/libindicator/80indicator-debugging /usr/share/libindicator/
[10:32] <didrocks> in debian/libindicator-tools.install
[10:32] <didrocks> and +usr/share/libindicator/80indicator-debugging /usr/share/libindicator/
[10:32] <didrocks> in debian/libindicator3-tools.install
[10:32] <didrocks> without any replaces: from libindicator3-tools against libindicator-tools
[10:32] <didrocks> let's see what files are shipped exactly by the current version
[10:32] <didrocks> and what files are shipped with the new version
[10:32] <sil2100> Now that you mention it, indeed
[10:35] <didrocks> ok ./usr/share/libindicator/80indicator-debugging is a file
[10:35] <seb128> Laney, pitti, jasoncwarner_: btw I just uploaded a gtk update with a patch to fix the segfault after upgrades bug
[10:35] <didrocks> sil2100: so missing Replaces :/
[10:35] <sil2100> Noooo~!
[10:35] <didrocks> ted! this is clearly not your first package
[10:36] <didrocks> sil2100: ok, let's see if we can rebuild just that package
[10:36] <sil2100> didrocks: without running the check job?
[10:36] <Laney> seb128: good work, so it wasn't in nautilus
[10:36] <didrocks> sil2100: or with, it doesn't take that long
[10:37] <Laney> you might want to reassign the bug then
[10:37] <seb128> Laney, no, it was gtk not refreshing is icon cache correctly when the one on disk was changing
[10:37] <didrocks> sil2100: tip of trunk is rev 498
[10:37] <didrocks> +  * Automatic snapshot from revision 498
[10:37] <didrocks> ok, no additional commit
[10:38] <Laney> fair
[10:38] <seb128> Laney, good point ... done ;-)
[10:39] <didrocks> sil2100: I'm tempted to directly push to trunk to speed up the process, the diff is here: http://paste.ubuntu.com/5780054/
[10:39] <didrocks> sil2100: any opinion?
[10:39] <didrocks> urgh, one sec
[10:39] <didrocks> seb128: http://paste.ubuntu.com/5780058/
[10:39] <didrocks> sil2100: ^
[10:41] <sil2100> Ah, ok, you mean the first one, yes?
[10:41] <didrocks> sil2100: the second one
[10:41] <seb128> didrocks, http://bazaar.launchpad.net/~indicator-applet-developers/libindicator/trunk.13.10/revision/498
[10:41] <didrocks> hum
[10:41] <didrocks> interesting
[10:41] <didrocks> sil2100: I haven't committed back :p
[10:41] <seb128> didrocks, NULL means "turn off" apparently
[10:41] <sil2100> ;)
[10:42] <didrocks> seb128: ignore my diff :p
[10:42] <seb128> k
[10:42] <didrocks> http://paste.ubuntu.com/5780066/
[10:42] <didrocks> sil2100: seb128: this should be more within context ^ :p
[10:43] <sil2100> didrocks: yes, much better now ;)
[10:43] <sil2100> I prefer this version than the 3 ;p
[10:43] <didrocks> ahah
[10:43]  * didrocks pushes upstream
[10:44] <didrocks> sil2100: so, rebuild only libindicator please
[10:44] <sil2100> o>
[10:44] <didrocks> the test taking few minutes, we can afford them running
[10:44] <didrocks> sil2100: all the other packaging changes are +1 for me, so then, we can force the publication
[10:45] <sil2100> didrocks: the check job still has the libical added, yes?
[10:45] <sil2100> Rebuilding!
[10:45] <didrocks> sil2100: yep, after all, let's remove it once we get a new iso :
[10:45] <didrocks> :)
[10:51] <seb128> didrocks, yeah, looks fine to me
[10:51] <didrocks> great!
[11:07]  * sil2100 still waiting for armhf of libindicators to start building
[11:07] <sil2100> ;|
[11:08] <didrocks> sil2100: well, we are waiting on the tests as well, right? as unity tests are running?
[11:09] <didrocks> sil2100: are you sure it's not built? looking at the ppa, only amd64 is still building
[11:09] <sil2100> Aaah!
[11:09] <sil2100> hahah, sorry, misread amd64 for armhf
[11:09] <sil2100> ;)
[11:09] <didrocks> :)
[11:09] <didrocks> ETOOMANYA ;)
[11:43]  * ogra_ grins about didrocks and sil2100  .... and wonders what they will do once we have arm64
[11:47] <didrocks> ogra_: I'll buffer overflow my head I think :)
[11:47] <ogra_> haha
[11:50] <sil2100> didrocks: could you nominate to precise? https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1192216 ;)
[11:50] <ubot2> Ubuntu bug 1192216 in bamf (Ubuntu) "Bamf is not building in jenkins due to missing coverage xml and xunit formatted tests" [Undecided,New]
[11:50] <sil2100> I mean!
[11:50] <sil2100> To raring!
[11:50] <sil2100> ;p
[11:50] <didrocks> sil2100: is it something we should really backport? we don't have merger to precise
[11:50] <didrocks> ah :)
[11:50]  * sil2100 needs coffee
[11:50] <didrocks> ok
[11:50] <sil2100> ;(
[11:51] <didrocks> sil2100: if it's fixed in saucy, please change the main status :)
[11:53] <ogra_> broken signon-ui deps made all image builds explode today (for all arches) ... is someone on that ?
[11:56] <Laney> it was discussed at some length in #ubuntu-devel this morning
[11:56] <Laney> component-mismatches don't get checked by proposed-migration
[11:57] <ogra_> yeah
[12:23] <didrocks> sil2100: seb128: still same failures on unity_gtk_module tests FYI, but I guess good to publish the indicators stack
[12:24] <seb128> didrocks, k
[12:58] <attente> sil2100, the tests didn't pass for you even after https://code.launchpad.net/~attente/unity-gtk-module/edit-undo-fix/+merge/169207?
[12:59] <sil2100> attente: hi! I'm not sure, since I remembered that one of your fixes fixed those tests, but then I saw that they were failing since at least a week now, so not sure hmm
[13:06] <attente> sil2100, i think it's the same problem looking at the recent jenkins logs; that edit-undo test is causing all the other ones to fail
[13:08] <attente> if we merge this MP in, then maybe it'll be fixed
[13:11] <seb128> sil2100, didrocks: ^ just get that pending fix merged and enjoy working tests? :-)
[13:14] <Sweetshark> seb128: https://launchpadlibrarian.net/142834255/libreoffice_1%3A4.1.0~beta2-0ubuntu1~ppa3_1%3A4.1.0~beta2~incompleteinternals1-0ubuntu1~ppa7.diff.gz <- the mother of all hacks
[13:15] <seb128> Sweetshark, does it work? ;-)
[13:15] <sil2100> Uh
[13:15] <sil2100> attente: approving!
[13:16] <Sweetshark> seb128: locally yes, but if it holds on the ppa buildds: we will see -- still building ....
[13:16] <attente> :)
[13:16] <Sweetshark> seb128: removing the object files before installing frees some 10GB for sure ...
[13:17] <Sweetshark> seb128: we should have a hangout soonish to talk about how to set up a proper split build ...
[13:19] <seb128> Sweetshark, ok, I'm not sure I know enough about the topic to be useful in an hangout discussion .... maybe better to bounce some details/reading via email first?
[13:20] <Sweetshark> seb128: yep. its not super urgent.
[13:30] <attente> seb128, i just did an upload of indicator-keyboard to the ppa, can you try it out? https://launchpad.net/~attente/+archive/indicator-keyboard
[13:31] <seb128> attente, sure
[13:32] <seb128> attente, why did you split the schemas in its own binary?
[13:33] <attente> seb128, i wanted gnome-control-center to only depend on the schema and not the indicator
[13:36] <seb128> attente, the proper way is to put the key is gsettings-desktop-schemas
[13:36] <attente> now that i think about it, i probably should've uploaded all the other ibus engines as well since some may be incompatible with 1.5
[13:36] <seb128> in*
[13:36] <seb128> attente, if that's a key supposed to be shared by components
[13:37] <seb128> attente, that's where most of the schemas for most desktop settings are
[13:37] <attente> seb128, ok, i'll move it over
[13:37] <attente> funny thing is that was where i had it originally
[14:01] <seb128> attente, do you handle upgrades in some way? my test users had 4 layouts before I restarted my session with french as default and now it has only english
[14:21] <dobey> desrt, jbicha, or anyone really: do you know how i can get my Alt_L key to work properly in GNOME 3.x again? i can't find a setting to make it work right, and it's not working right in terminal, emacs, firefox, or lots of apps :(
[14:25] <attente> seb128, it doesn't handle migrations of old layouts. i'll see if i can write a postinst script
[14:25] <seb128> attente, thanks, postinst is the wrong level though
[14:26] <seb128> attente, usually it's better to do it in the code, like a migration gsettings key and do the migration if it's unset
[14:26] <seb128> attente, the packaging system might not have access to user dirs if they are encrypted, or on nfs not mounted
[14:26] <seb128> attente, you can maybe have a look at how GNOME did the migration, I guess they handle it in some way
[14:27] <attente> seb128, sure, thanks
[14:28] <jbicha> dobey: works here, maybe you set Alt_L as a keyboard shortcut somewhere; do you still have the problem with a new clean user account?
[14:31] <dobey> jbicha: i never set just Alt_L as a shortcut. it works fine under Unity. and ALt_L+drag, and Alt_L+tab work fine in gnome. :-/
[14:31] <seb128> jbicha, gnome-session 3.8 seems fine to me, if you want to upload
[14:32] <seb128> attente, good news is that your indicator and settings panel work great for me ;-)
[14:32] <seb128> attente, great work!
[14:32] <seb128> attente, I've just a problem with the icons used for the keymap ... how do you determine those?
[14:33] <dobey> and i've looked through all the keybinding settings in dconf-editor to see if something obvious was screwing with it, but didn't see anything
[14:33] <attente> seb128, the icons are in the ubuntu-mono package
[14:33] <dobey> jbicha: oh, and Alt_L does the right thing, if i press Super+Alt_L+whatever, which is really weird
[14:34] <attente> seb128, we ended up throwing them all into there as svgs generated by the indicator source package
[14:34] <attente> but what's the issue exactly?
[14:35] <attente> (i know there's at least one bug with the icon not switching properly when "new windows are set to use the default source")
[14:35] <dobey> and Alt_R works as normal, but using it for everything is really annoying, especially with the extra long space bar on this keyboard
[14:41] <seb128> attente, http://ubuntuone.com/3cwRL3UgG6bP0VTsIfbJuf ... is that normal icons?
[14:41] <seb128> attente, sorry took me a bit to take a screenshot, there is a bug in saucy, if you undock your laptop it seems the screenshot try to snap content on screens that are off
[14:42] <seb128> attente, the coloring is buggy (maybe that's because I don't use the default theme) and french should be "Fr", not "FA"
[14:42] <attente> seb128, ok. i have a good idea of what's happening there
[14:43] <seb128> attente, out of that problem things work great for me as a "multiple layout user"
[14:43] <attente> *phew*!
[14:43] <seb128> attente, I don't use ibus nor write any language that require it, so I can't really test ... but our g-s-d based indicator was only doing keyboard layouts so what we got there is already great and enough to replace it
[14:46] <attente> seb128, ok, no problem, i'll fix up these issues so that we can push for more users testing
[14:47] <seb128> attente, I will try to unblock the ibus 1.5 situation meanwhile
[14:47] <seb128> that will be a first thing needed
[14:47] <seb128> attente, oh, other problem ... you will need to port unity-greeter, they have a custom keyboard indicator in there, which reads the old config key
[14:47] <attente> seb128, unblock in what way?
[14:48] <attente> seb128, ack
[14:48] <seb128> attente, we are still having ibus 1.4 as our default ibus version, I guess your indicator work only with 1.5?
[14:48] <seb128> attente, I will just kick in another discussion on the desktop list about ibus 1.5 and what are/were the blocker issues for upgrading to 1.5
[14:49] <attente> seb128, yeah, i mean, i guess we could try to get it working with 1.4, but no idea what kind of new issues that will cause
[14:51] <seb128> attente, don't bother about that, we will need to upgrade to 1.5 at some point ... one of the main blocker for me was that it didn't play nicely with our old GNOME keyboard stack, which was blocked on having an indicator
[14:51] <seb128> so with some luck we can just unblock that now
[14:51] <seb128> ;-)
[14:52] <attente> ah, gotcha :)
[14:57] <sil2100> didrocks: in case you missed our talk with attante - the unity-gtk-module test failures should be fixed!
[14:57] <didrocks> sil2100: I flyed over the discussion and I'm delighted :)
[14:57] <sil2100> didrocks: it seems attente made a fix branch that I probably even tested in the past (but probably forgot to approve), and it was waiting in ether
[14:57] <seb128> didrocks, the fix he submitted some time ago was waiting for somebody to review it :p
[14:57] <sil2100> So I should probably say 'oops my bad!'
[14:57] <didrocks> attente: you should konw, poke kindly, then yell :p
[14:58] <didrocks> know*
[14:58] <didrocks> sil2100: tsss :p
[14:58] <didrocks> well, great that's fixed :)
[14:58] <didrocks> sad that unity-panel-service crashes and don't respawn in that case
[14:58] <mhr3_> seb128, ouch, my gedit is using 318mb of ram, it's been running for quite a while, but i was really loading anything huge there :/
[14:59] <seb128> mhr3_, was *not*, I guess?
[14:59] <mhr3_> seb128, right, sorry
[15:00] <mhr3_> seb128, and cups-browsed 330mb... damn
[15:00] <mhr3_> seb128, at least zeitgeist-fts isn't the biggest thing anymore :P
[15:03] <didrocks> mhr3_: tssss tsss tsss, don't try to find any excuse! you will still have the zeitgeist stamp to me! :)
[15:04] <mhr3_> didrocks, come on, it's clear now, zeitgeist is behaving like other services, so it's completely normal :P
[15:05] <seb128> bah, nm-applet/n-m got unhappy again and xchat-gnome nm integration disconnects when wifi disconnect
[15:05] <seb128> mhr3_, can I just blame your box? :-)
[15:05] <didrocks> mhr3_: tsssss :p
[15:05] <seb128> mhr3_, for the memory usage
[15:06] <mhr3_> seb128, no :p
[15:07] <attente> didrocks, duly noted ;)
[15:07] <mhr3_> seb128, but i'll forgive you the cups part, it's new code iirc
[15:07] <seb128> mhr3_, still mention it to tkamppeter
[15:08] <seb128> mhr3_, zeitgeist-fts is using 300m here if you want processes that eat memory :p
[15:08] <mhr3_> seb128, ah, you must lots of data, it's just 220mb here :)
[15:08] <mhr3_> hm, i loose words
[15:09] <mhr3_> think that's caused by the memory leaks
[15:09] <seb128> tkamppeter, hey, is there a known bug about "/usr/lib/cups/notifier/dbus dbus://" processes hanging around all day?
[15:09] <seb128> tkamppeter, I've a stack of those
[15:09] <seb128> mhr3_, ;-)
[15:18] <mdeslaur_> seb128: how does this work? https://code.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.13.04
[15:18] <mdeslaur_> seb128: will something push that as an SRU if jenkins "released" it?
[15:19] <mdeslaur_> or is that inaccurate and I should upload it manually as an SRU?
[15:19] <seb128> mdeslaur_, see https://launchpad.net/ubuntu/raring/+queue?queue_state=1
[15:20] <seb128> mdeslaur_, and cyphermox did the precise one, which is waiting there: http://launchpadlibrarian.net/142680700/libdbusmenu_0.6.2-0ubuntu0.2_source.changes
[15:20] <mdeslaur_> ok, slightly confused as I had just looked there and didn't see it in the queue
[15:20] <seb128> mdeslaur_, weird ...
[15:20] <seb128> mdeslaur_, they have a 2 steps process through a stagging ppa for SRUs, so maybe that created some delay
[15:21] <seb128> mdeslaur_, https://launchpad.net/~ubuntu-unity/+archive/sru-staging if you want to check diffs and stuff
[15:21] <seb128> hum, though the diff is with the previous daily in that case
[15:21] <mdeslaur_> seb128: awesome, thanks
[15:21] <seb128> so not very useful
[15:22] <seb128> but you get the content at least
[15:22] <seb128> mdeslaur_, yw
[15:39] <cyphermox> mdeslaur_: there's a jenkins button to push for that sru
[15:39] <seb128> cyphermox, seems like sil2100 pushed it for the stack in raring
[15:39] <cyphermox> yeah
[16:39] <seb128> Laney, btw there is a new glib out if you need a break from qml at some point ;-)
[16:40] <Laney> so there is
[16:41] <Laney> I'll look at it after I get this MPed
[16:42] <seb128> Laney, no hurry, I'm just mentioning it ;-)
[16:42] <Laney> yeah but it seems like a good opportunity to do something different ...
[16:42] <Laney> oh, looks like I'm patch piloting tomorrow anyway
[16:43] <tkamppeter> seb128, what's on with CUPS?
[16:44] <seb128> tkamppeter,
[16:44] <seb128> lp        1223  0.0  0.0   6484  1420 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://
[16:44] <seb128> lp        1224  0.0  0.0   6484  1424 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://
[16:44] <seb128> lp        1225  0.0  0.0   6484  1420 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://
[16:44] <ubot2> Launchpad bug 1223 in gcursor (Ubuntu) "gcursor: typo in description" [Medium,Fix released] https://launchpad.net/bugs/1223
[16:44] <seb128> ....
[16:44] <ubot2> Launchpad bug 1130 in xfwm4-themes (Ubuntu) "duplicate for #1224 unmet dependancy in xfwm4-themes" [Medium,Fix released] https://launchpad.net/bugs/1130
[16:44] <ubot2> Launchpad bug 1225 in glom (Ubuntu) "Glom: missing dependency - PostgreSQL" [Low,Fix released] https://launchpad.net/bugs/1225
[16:45] <seb128> ubot2, stupid bot
[16:45] <ubot2> Factoid 'stupid bot' not found
[16:45] <seb128> tkamppeter,
[16:45] <seb128> $ ps aux | grep "cups/notifier" | wc -l
[16:45] <seb128> 101
[16:45] <tkamppeter> seb128, there was a bug report about this /usr/lib/cups/notifier/dbus dbus://, I think larsu has fixed such a thing some time ago.
[16:45] <seb128> well, it's back it seems
[16:45] <seb128> tkamppeter, https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/959195
[16:46] <ubot2> Ubuntu bug 959195 in indicator-printers (Ubuntu) "65 cups notifier processes running" [Undecided,Fix released]
[16:46] <tkamppeter> seb128, probably it needs refixing after every small change in the system.
[16:50] <seb128> tkamppeter, that's fixed after doing what was suggested in https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/959195/comments/9
[16:50] <ubot2> Ubuntu bug 959195 in indicator-printers (Ubuntu) "65 cups notifier processes running" [Undecided,Fix released]
[16:50] <seb128> it was maybe a leftover config, I will watch for it
[16:50] <seb128> on that note, doing a break, bbiab
[16:50] <tkamppeter> seb128, the bug seems to be in indicator-printers and the fix was done in precise, by creating subscriptions with timeout so that if indicator-printers dies that the subscriptions it leaves behind go away within 15 minutes.
[17:04]  * didrocks waves good evening
[17:45] <Sweetshark> just in case anyone pinged me around 1700UTC please redo, my session died.


[01:16] <Ubugtu> New bug: #84997 in ubuntu-docs (main) "Firestarter is not in main" [Undecided,Unconfirmed]  https://launchpad.net/bugs/84997
[02:06] <CIA-4> Ubuntu Documentation: brian * r3803 ubuntu/keeping-safe/C/keeping-safe.xml: Changed firestarter repo resolves lp bug 84997
[02:06] <Ubugtu> Malone bug 84997 in ubuntu-docs "Firestarter is not in main" [Undecided,Unconfirmed]  https://launchpad.net/bugs/84997
[03:06] <kupesoft> Hi all (=
[03:07] <kupesoft> I'm going to rewrite https://help.ubuntu.com/community/UbuntuWirelessRouter.
[03:07] <kupesoft> The article is confusing, seriously lacking in content, and it's children documents (BridgingNetworkInterfaces) need work to.
[03:07] <Madpilot> kupesoft, go for it, someone will review it informally at some point
[03:08] <kupesoft> *too
[03:08] <kupesoft> The article is so bad, imho, I've put an outline and a mission statement of sorts at https://help.ubuntu.com/community/UbuntuWirelessRouter/New
[03:08] <kupesoft> Have I taken the right steps so far?
[03:11] <kupesoft> Madpilot: thanks,
[03:12] <Madpilot> don't forget that the wiki has the ability to revert changes, so don't worry too much about changing a page - someone can always go back and retrieve stuff, if needed
[03:26] <kupesoft> I've created the new article at https://help.ubuntu.com/community/UbunutRouter - can I use that a place development for a little while before the article is ready and  I link it to the main wiki?
[03:35] <Madpilot> kupesoft, was the typo in that URL deliberate? ;)
[03:35] <kupesoft> of course not !
[03:35] <kupesoft> Can you delete the page for me?
[03:36] <Madpilot> sure
[03:36] <kupesoft> Thanks,
[03:37] <Madpilot> last I checked, I'm one of only about four people with deletions privs on help.u.c/c...
[03:38] <kupesoft> I know, I looked up on the launchpad group,
[03:38] <kupesoft> *you
[03:51] <Ubugtu> New bug: #85008 in xubuntu-docs (main) "Typo in Xfce Mount Plugin description - "umount"" [Undecided,Unconfirmed]  https://launchpad.net/bugs/85008
[04:05] <ryukent> Trying to create a new page on the ubuntu wiki, but keep getting "You are not allowed to edit this page" for new pages.... does anyone know if adding is currently suspended?
[05:58] <CIA-4> Ubuntu Documentation: bhuvan * r3804 generic/serverguide/C/installation.xml:
[05:58] <CIA-4> Ubuntu Documentation: Fix the installation instructions for LAMP.
[05:58] <CIA-4> Ubuntu Documentation: Patch by: Matthew Flaschen
[11:57] <kupesoft> Anyone want to proofread https://help.ubuntu.com/community/Router for me?


[09:33] <Mirv> Saviq: do you have something to improve bug #1611733 with? I thought I have seen a lot of AP problems with xenial, but then again now that I think of they might have been a lot worse before than for example that UITK log in the report. I remember you were also talking at some point about introspection problems with Qt 5.5+


[05:25] <george_e> I've run into a packaging problem with my daily build...
[05:25] <george_e> My package depends on libqtwebkit-dev on Maverick+.
[05:25] <george_e> ...but those same files are provided by libqt4-dev on Luxid.
[05:26] <george_e> *Lucid
[05:26] <george_e> How can I list build dependencies for multiple Ubuntu releases in the same control file?
[05:26] <george_e> Is there any special syntax I can use?
[05:30] <nigelb> george_e: Hi, you should maybe ask in #ubuntu-packaging for packaging related help.
[05:30] <george_e> nigelb: Oh, okay. Thanks!
[05:30] <nigelb> There are probably more people lurking there who can help you :)
[05:30] <george_e> Great.
[05:32] <RAOF> george_e: The short answer is: you can't (easily).  It'd be easiest to have two recepies.
[05:33] <george_e> RAOF: So create a separate daily build for Lucid then?
[05:33] <RAOF> george_e: That's what I'd do.
[05:33] <george_e> Okay.
[05:34] <wgrant> george_e: Can't you just depend on 'libqtwebkit-dev | libqt4-dev (<< version-that-removed-them)'?
[05:35] <george_e> wgrant: What would that syntax look like for Lucid?
[05:35] <george_e> libqt4-dev (<<lucid)    ?
[05:35] <wgrant> It needs to be a package version.
[05:36] <wgrant> Perhaps << (4:4.7.0)
[05:36] <george_e> wgrant: Okay, I see.
[05:36] <george_e> Would this be preferable to creating a separate recipe?
[05:37] <george_e> ...or am I creating extra headaches?
[05:37] <wgrant> If it works, this is probably far more maintainable.
[05:37] <wgrant> No need to maintain two branches.
[05:38] <george_e> wgrant: Okay. I'll give it a shot. No harm in trying I guess.
[05:38] <wgrant> Indeed.
[08:40] <akoskm-> hi! variables presented on https://help.launchpad.net/Packaging/SourceBuilds/Recipes the what I can use when forming package name?
[08:52] <mrevell> Hi akoskm-
[08:52]  * mrevell reminds himself of the page
[08:53] <mrevell> akoskm-, Take a look at this part of the page: https://help.launchpad.net/Packaging/SourceBuilds/Recipes#Version numbers and substitution variables
[08:54] <mrevell> You'll want to paste that into your browser, thanks to the spaces introduced by Moin's anchor name.
[08:54] <mrevell> Or just scroll down to the "Version numbers and substitution variables" part of the page.
[08:54] <Mkaysi> How is it possible that old bug is duplicate of new bug?
[08:56] <akoskm-> mrevell: thanks! I was referring to that part. So, those are the only variables?
[08:57] <akoskm-> because I'm importing my master branch from git, so it would be good to, example include the commit-id of last git import in the package name
[08:57] <mrevell> akoskm-, Oh, I believe so, yes. jelmer or bigjools may be able to cinfirm if there are other variables you can use.
[08:58] <jelmer> hi mrevell, akoskm-
[08:58] <akoskm-> jelmer: hi
[08:58] <jelmer> akoskm-, newer versions of bzr-builder support a {git-commit} variable that will contain the git commit sha
[08:58] <akoskm-> \o/
[08:59] <jelmer> akoskm-: however, that version is not (yet) deployed on Launchpad.
[09:00] <akoskm-> jelmer: thank you! any suggestions how to temporary solve this, while while the new builder reaches launchpad?
[09:00] <jelmer> akoskm-, you can still include the bzr revno in the version, but I don't think there's a work around to include the git commit sha
[09:00] <jelmer> akoskm-, the relevant bug is bug 620132
[09:01] <tumbleweed> what's the point of putting a commit id in the version? they don't increase? (IIRC this was discussed on debian-devel a while back)
[09:01] <tumbleweed> I guess there's no other way to annotate what was built, but putting it in the changelog would probably be preferable
[09:02] <akoskm-> tumbleweed: easier to track packages between different platforms, we have releases for mac, windows, etc. bzr versions are known only here
[09:03] <akoskm-> so including a piece of git commit-id can cleary identify the source version
[09:04] <tumbleweed> yeah for bzr-builder there probably isn't a better solution
[09:04] <akoskm-> jelmer, mrevell: thank you again!
[09:04] <mrevell> No problem. Thanks jelmer¬
[09:06] <jelmer> mrevell: ¬ to you too :P
[09:07] <mrevell> jelmer, Haha, I have a new keyboard that I'm getting used to :)
[09:51] <Laney> can someone help me ensure that mono is built on rothera or vernadsky if I sync it shortly?
[09:53] <wgrant> Laney: You want to test that the fix works?
[09:53] <wgrant> Because I thought it usually failed on those.
[09:53] <Laney> elmo upgraded the kernel
[09:53] <wgrant> Ah.
[09:53] <wgrant> Both of them are busy at the moment, but when they're done, sure.
[09:53] <Laney> so we want to see if that changes things at al
[09:53] <Laney> cheers, give me a ping when that is
[09:53] <wgrant> Looks like vernadsky will be done in a minute or so.
[09:55] <wgrant> Laney: OK, it's done. All i386 non-virt builders are on manual.
[09:55] <wgrant> So sync away, I will bump the prio and unmanual vernadsky.
[09:55] <Laney> ok
[09:55]  * Laney hits the button
[09:56] <Laney> syncpackage: Request succeeded; you should get an e-mail once it is processed.
[09:57] <Laney> wgrant: ^
[09:58] <wgrant> bigjools: How often does the PCJ job run?
[09:58] <bigjools> wgrant: 5 mins
[09:58] <bigjools> it's in with MAIN
[09:58] <wgrant> Ah :(
[09:59] <bigjools> see bug 770721
[09:59] <bigjools> we need an EXPEDITED or something
[09:59] <wgrant> I thought it was done with run_jobs, but I guess that was IDSJ.
[09:59] <bigjools> that's the nice thing about the job system, so many different ways to run a job....
[10:00] <wgrant> Mmm, ParallelLimitedTaskConsumer with TwistedJobRunner...
[10:00] <bigjools> we could use PG's NOTIFY
[10:00] <wgrant> Ew.
[10:01] <bigjools> nothing wrong with that
[10:01] <wgrant> We'll have a perfectly good message queue soon.
[10:01] <wgrant> ™
[10:01] <bigjools> FSVO soon
[10:01] <wgrant> OK, copied.
[10:01]  * wgrant bumps.
[10:01] <wgrant> Oh damn.
[10:02] <wgrant> Missed zirconium.
[10:02] <Laney> haha
[10:02] <wgrant> Let me fix.
[10:04] <wgrant> OK, now building on vernadsky :)
[10:04] <Laney> cheers
[10:04] <Laney> see you in an hour ... ;)
[10:04] <bigjools> heh
[10:05] <wgrant> Let's hope this works.
[10:05] <Laney> upstream said he thought it was a kernel bug
[10:06] <nigelb> I assume this the one where you said "sad" when the build was a success?
[10:06] <Laney> the very same
[10:07] <nigelb> fun. :)
[10:08] <Laney> https://bugzilla.novell.com/show_bug.cgi?id=705190 for those following along at home
[11:16] <Laney> wgrant: it failed, but oops — got started on verdansky again :-( Can you give it to roseapple if you're able?
[11:16] <Laney> verdansky was busy with a build but I got unlucky with the timing and it finished just when I gave it back
[11:21] <Laney> wgrant: also, looks like you let zirconium disabled
[12:34] <gmb> PPA uploads are working, it just looks bad: https://launchpad.net/bugs/798957 | https://launchpad.net/ | Help contact: gmb | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad
[12:34] <gmb> Argh
[12:34] <gmb> Is what I meant to do.
[13:04] <radifar> hi everyone
[13:04] <radifar> anyone know what this mean?
[13:04] <radifar> Error in Translation: 'msgstr' is not a valid PHP format string, unlike 'msgid'.  Reason: In the directive number 1, the character 'G' is not a valid  conversion specifier.
[13:05] <radifar> I've got that message when I'm trying to review the translation in here:
[13:05] <radifar> https://translations.launchpad.net/web-erp/trunk/+pots/weberp/id/+translate?show=new_suggestions
[13:10] <danilos> radifar, most likely a problem with %G being used in a string inproperly marked as php-format
[13:10] <danilos> radifar, let me take a look
[13:12] <danilos> radifar, yeah, you need to file a bug against web-erp pointing at that message so they can fix it
[13:12] <danilos> radifar, you can probably start at https://bugs.launchpad.net/web-erp/+filebug
[13:13] <radifar> okay, thanks danilos
[13:13] <radifar> I'll try that one
[13:13] <danilos> radifar, tell them to remove "php-format" from that message (and if it gets inserted automatically, to use no-php-format style comment as described in gettext documentation)
[13:14] <radifar> okay
[13:24] <gvallarelli> Hi all
[13:25] <gvallarelli> I'm using the launchpadlib and I've got an issue
[13:25] <gvallarelli> with the login
[13:26] <gvallarelli> that's the error http://pastebin.com/rHBaxb8q
[13:51] <RichiH> are there any known problems with LP atm?
[13:52] <RichiH> 2061canistellaunchpad190 & 2061canistellaunchpad188 -- i am unable to change my email address
[14:03] <bigjools> are you asleep gmb? :)
[14:04] <gmb> bigjools: No, got stuck in an in-depth review.
[14:04] <bigjools> tough collision of roles
[14:04] <gmb> bigjools: Yeah.
[14:05] <gmb> gvallarelli: Hmm. I've never seen that error before.  Can you be more specific about your problem? Are you getting an error message when you try to change your email address?
[14:07] <gvallarelli> gmb, a trasparent proxy I suppose
[14:08] <gmb> gvallarelli: That would seem the most likely cause. Let me see if I can reproduce it here, just to be sure it's not staging being weird.
[14:08] <gvallarelli> gmb, thanks
[14:10] <gmb> gvallarelli: I'm not having any problems logging in normally or anonymously, I'm afraid.
[14:11] <gmb> So I suspect that a transparent proxy might be your problem. I don't know how to work around that.
[14:11] <gvallarelli> gmb, thanks I'll investigate
[14:11] <gmb> ok
[14:13] <beatpanic> gmb, hi! I'll add more info, gvallarelli is a colleague of mine, who is experimenting with launchpad too. we'are NATed and have a transparent proxy, maybe the issue could be also this? (that I have used launchpadlib previously) thanks
[14:14] <gmb> beatpanic: That could well be the problem, but I don't know the best way to fix it, I'm afraid.
[14:14] <beatpanic> gmb, no problem, thanks anyway for your help!
[14:15] <gmb> np
[15:09] <mars> gmb, ping
[15:27] <gmb> mars: Hi
[18:04] <bdmurray> It looks to me like the subscribers portlet is sorted z->a
[21:05] <bgamari> How can one delete a source tarball from a PPA?
[21:06] <bgamari> I accidentally uploaded an incorrect .orig tarball and now Launchpad refuses to take packages since the new .orig differs from the original
[21:07] <kiko> you'll need to rev the version
[21:07] <kiko> there's no way around it
[21:08] <bgamari> hmm
[21:08] <bgamari> that's really unfortunate
[21:08] <bgamari> Is there a reason this is such a hard rule?
[21:09] <doko> how do I look at bug #507062 (always times out)
[21:10] <bgamari> kiko: How would you recommend I bump the version? The correct version number is 1.5.0
[21:10] <bgamari> kiko: I could bump it to <IP_ADDRESS>
[21:10] <bgamari> kiko: but that seems really yucky
[22:56] <maxb> bgamari: I'd probably choose 1.5.0+real in this sort of circumstance