[05:35] <pitti> Good morning
[07:00] <dholbach> good morning
[07:35] <dholbach> xnox, pgraner, happy birthday! :)
[07:41] <xnox> \o/
[07:45] <xnox> Quarter of a Century.... "In Time" clocks start ticking
[07:46] <infinity> xnox: I'm sure pgraner will be happy to hear you whining about your age. :P
[07:47] <smb> Age... don't talk to me about age...
[07:48] <smb> xnox, So Happy Birthday as well
[07:49] <smb> In other general news: am I the only one that got the feeling that bootspeed in Saucy is not a happy camper?
[07:51]  * xnox just upgraded to my first SSD ever, so for it all flies.
[07:52] <xnox> smb: http://reports.qa.ubuntu.com/bootspeed/arch/amd64/#acer-veriton-02    mostly up & not down.
[07:55] <smb> xnox, Seems to match my wonderful experience of 15s dark screen with a mouse pointer after login screen
[07:55] <smb> xnox, and thats with a SSD
[07:55] <xnox> hmm... i also wonder what that dark screen is.
[07:55] <jibel> and according to bootchart it's an amd64 only regression
[07:55] <xnox> (for me it's shorter but still there)
[07:56] <smb> xnox, Feel like just the decorators not running
[07:56] <pitti> hey xnox, good morning! happy birthday!
[07:56] <smb> jibel, mine is i386
[07:56] <geser> xnox: grats, how many bugs do you have to fix to earn some additional time? or did you inherit enough time? :)
[07:56] <pitti> does anyone have a wireless keyboard and/or mouse? (bluetooth)
[07:57] <xnox> pitti: does an android app count? =)
[07:57] <smb> xnox, jibel, fwiw a bootchart of mine would be on chinstrap
[07:57] <pitti> xnox: well, as long as upower --dump shows that devices' battery and it's in /sys/class/power_supply
[07:58] <pitti> xnox: but it might be a bit atypical
[07:59]  * hyperair has a bluetooth mouse
[07:59] <pitti> hyperair: could you have a look at my last comment in bug 1153488? that's a command whose output I'd like to get
[08:00] <hyperair> i don't recall ever seeing power_supply information for my mouse though..
[08:00] <hyperair> (and the mouse is at home)
[08:00] <hyperair> wait ~8 hours or so and i'll get to it
[08:00] <pitti> hyperair: splendid, thanks
[08:00] <xnox> pitti: no luck here, upower doesn't see it.
[08:01] <hyperair> i've got one of the HID+ unifying adapter mouse/keyboard pairs on me right now though, and i don't see anything in power_supply besides AC and BAT0
[08:02] <pitti> hyperair: ah, do you see them in "upower --dump"?
[08:02] <hyperair> ope
[08:02] <hyperair> nope*
[08:02] <pitti> ah right, that's the Logitech stuff, not Bluetooth
[08:02] <hyperair> yeah that's right
[08:03] <hyperair> the bluetooth mouse is also logitech, but i've never seen it listed in upower's output before
[08:03] <pitti> hm, bug 1066208 and its dupes suggest that it's not uncommon
[08:04] <hyperair> might be for specific mice that actually do report their battery levels
[08:04] <hyperair> i see a mention of apple magic mouse there
[08:04] <hyperair> could it be just that mouse?
[08:05] <pitti> https://launchpadlibrarian.net/120326665/UPowerDump.txt has "Eclipse Touch Mouse"
[08:06] <hyperair> heh haven't even heard of that mouse before
[08:09] <pitti> hyperair: and bug 1086746 has "Logitech diNovo Edge", so it  seems there are more
[08:14] <darkxst> pitti, oh I wonder, maybe https://bugzilla.gnome.org/show_bug.cgi?id=707331 is similar?
[08:18] <pitti> darkxst: could be; check upower --dump?
[08:19] <darkxst> pitti, http://paste.ubuntu.com/6058085/
[08:20] <pitti> darkxst: ah nice, could you attach the output of "grep -r . /sys/class/power_supply/*hid*" to bug 1153488 ?
[08:20] <darkxst> pitti, its not bluetooth
[08:20] <darkxst> its a unifying one
[08:20] <pitti> darkxst: ah, that again; ok, thanks
[08:22] <hyperair> hmm interesting
[08:23] <darkxst> pitti, yeh, well atleast peter's branch fixed the other problem ;)
[08:43] <ev> @pilot in
[08:45] <pkern> ev: Could you pilot https://bugs.launchpad.net/bugs/1214385 please? ;)
[08:51] <ev> sure can
[09:47] <darkxst> Hey ev, any chance you can look at Bug 1219188
[09:49] <darkxst> ev, and super trivial patch on Bug 1189309
[09:52] <ev> darkxst: sure, can do
[10:06] <ev> pkern: bug 1214385 is in the queue for -proposed
[10:32] <mardy> seb128: hi! I need a little help with quilt :-)
[10:32] <seb128> mardy, hey, sure! (funny I was just thinking about pinging you to ask how the patch update is going ;-)
[10:32] <mardy> seb128: "quilt diff" shows all my changes, but with "quilt refresh" the patch doesn't get updated with all of them
[10:32] <xnox> ev: given that touch is read-only, one can check if system-image-development (rw) mode was enabled. If not, collect & report run-away processes.
[10:33] <seb128> mardy, did you modify new files (e.g that were not in the patch before), if you do you need to quilt add the files before changing them
[10:33] <xnox> ev: i like when e.g. pulseaudio goes crazy and starts to eat 12% of CPU, yet killing it "fixes" the problem the respawned instance is back to using peanuts.
[10:34] <mardy> seb128: no, it's a file that was already in the patch
[10:34] <seb128> mardy, weird
[10:35] <seb128> mardy, where are you looking to the patch?
[10:35] <seb128> mardy, quilt refresh updates the version in build-area/source/debian/patches, that's copied over to your vcs when you end the bzr bd-do (if it exit without error)
[10:39] <ev> xnox: mind following up to the email with that, just so we're all talking in the same place? :)
[10:39] <ev> it's a good point
[10:39] <mardy> seb128: mmm... I wonder, maybe it doesn't work because I copied all the build-area directory into another place? (so that I wouldn't lose it with an accidental Ctrl+D)
[10:40] <seb128> mardy, well, quilt refresh should update it whever you are
[10:41] <seb128> mardy, what does "quilt top" says?
[10:41] <seb128> mardy, is that the patch you are working on?
[10:41] <mardy> seb128: yes, "06_uoa.patch"
[10:42] <seb128> mardy, and that patch doesn't get update on quilt refresh? (is the timestamp of the .patch changing?)
[10:45] <mardy> seb128: nope, the timestamp doesn't change, and "quilt refresh" says: "Patch 06_uoa.patch is unchanged"
[10:45] <seb128> mardy, does it does the same if you edit a file listed in that .patch?
[10:47] <pkern> ev: Thank you!
[10:52] <ev> darkxst: what's your full email address? The debdiff for the nm-applet fix just has "darkness@arapiles2"
[10:53] <darkxst> ev, oh that is because I made that on my notebook.. normally use tim@feathertop.org for patches
[10:54] <ev> darkxst: cool, thanks!
[10:54] <mardy> seb128: werid, it says "refreshed", but the timestamp does not change
[10:55] <mardy> seb128: ah! It's modifying the patch in the original build-area directory!
[10:55] <mardy> seb128: so, it looks like quilt internally stores the absolute path of the patch
[10:57] <seb128> mardy, oh, could be, I never tried to do copies arounds like that
[10:57] <seb128> mardy, that would explain it ;-)
[10:58] <mardy> seb128: anyway, it looks like that patch is complete; I'll push my branch soon
[11:02] <seb128> mardy, excellent, thanks!
[11:25] <mardy> seb128: pushed: https://code.launchpad.net/~mardy/shotwell/update-0.15.0pr1
[11:26] <mardy> seb128: will you take it over, or is there something left for me to do?
[11:32] <ogra_> hmpf ... so i merged two binary packages into the same source ... one is Arch armhf, the other is Arch all ... uploading this package it seems the Arch all build is never even attempted
[11:32] <ogra_> http://paste.ubuntu.com/6058571/ is debian/control ... https://launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/0.42 is the package on LP
[11:34] <cjwatson> ogra_: https://bugs.launchpad.net/launchpad/+bug/1063188
[11:34] <cjwatson> ogra_: You could just make it artificially Architecture: any as a workaround, if the Architecture: armhf package can't be made any
[11:35] <ogra_> yeah, that armhf there is pretty valid, we dont want to roll armhf initrds on x86
[11:36] <ogra_> but it just strikes me that i indeed also need different targets in debian/rules for that
[11:53] <seb128> mardy, \o/, I'm taking over from there, thanks!
[12:22] <lool> mdeslaur: Hey!  would you think you could handle merging of latest sbuild?
[12:23] <cjwatson> It has a LOT of cross-building fixes.
[12:23] <lool> mdeslaur: jodh and you are last uploaders, but jodh is currently on leave; we need some cross-build fixes that went into the latest Debian version
[12:23] <mdeslaur> lool, cjwatson: sure, I'll merge it
[12:23] <lool> mdeslaur: awesome; happy to test the cross-building once you're done!   :-)
[12:25] <cjwatson> mdeslaur: Thanks
[14:26] <davmor2> Guys can I just check with the removal of gksudo is the correct way to trigger a graphical sudo event to use pkexec /path/to/app ?  thanks
[14:27] <smb> xnox, Just to let you know, I filed bug 1220252 about what we talked this morning
[14:28] <davmor2> smb: oh I'll go confirm that I thought that was just my hybrid gfx that was causing that but maybe not if others are suffering :)
[14:29] <smb> davmor2, I believe there are others too :)
[15:02] <chiluk> slangasek, thanks for the curl upload last week on https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1179781 can I get some love for the apt debdiffs?
[15:07] <mdeslaur> lool: new sbuild should be available now, fyi
[15:09] <dholbach> pitti, bdmurray: I just had a usb-creator crash and I was directed to https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1218178 which was closed as invalid because of outdated libraries - shall I just go ahead and run ubuntu-bug on the crash file=
[15:09] <dholbach> ?
[15:11] <lool> mdeslaur: \o/  thanks
[15:11] <mdeslaur> np
[15:13] <dholbach> pitti, bdmurray: nevermind, bug filed :)
[15:16] <slangasek> chiluk: so I was hoping infinity might be interested enough in that bug to sponsor the SRUs, but I guess not :)  I'll see what I can do for you today
[15:19] <tkamppeter> Has there anything been changed with the uplod to Saucy? Since yesterday my packages which I uploaded to saucy-proposed and got successfully built by the buildds did not get passed over to saucy release.
[15:19] <chiluk> thanks slangasek
[15:19] <cjwatson> tkamppeter: Your packages are probably blocked for beta-1 preparation
[15:20] <tkamppeter> cjwatson, this mail did not rech me.
[15:20] <cjwatson> Laney: ^-
[15:20] <hallyn_> stgraber: so i'm still getting "iproute:amd64 is not available, but is referred to by another package." on armhf container creation.  should that have been fixed by your isc-dhcp-client update?
[15:21] <stgraber> hallyn_: it should have...
[15:21] <Laney> tkamppeter: It's on the release schedule; will be removed tomorrow
[15:21] <stgraber> hallyn_: it was still reference by lxc-ubuntu... fixing that upstream now.
[15:23] <cjwatson> tkamppeter: Also http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html tells you who/where to contact
[15:25] <tkamppeter> cjwatson, sorry, I was used to these e-mails.
[15:26] <Laney> It's all a bit new with these dynamic blocks and stuff
[15:26] <Laney> I think we'll make it more lightweight in future
[15:26] <stgraber> hallyn_: http://paste.ubuntu.com/6059238/ looks good to you?
[15:28]  * hallyn_ looking
[15:29] <hallyn_> stgraber: well I wouldn't say "good" - i hate to think how hacks like that can accumulate, but it's cleaner than anything i've thought of :)  thanks
[15:29]  * hallyn_ tries it out
[15:34] <hallyn_> stgraber: worked!  pls add my acked-by, thanks
[15:36] <stgraber> hallyn_: pushed
[15:53] <knocte> Cimi: ping
[15:55] <cjwatson> LoganCloud: I hope you're prepared to deal with any GHC ABI changes resulting from your GHC sync.  We were deliberately holding off on that one
[16:25] <Laney> oh dear
[18:53] <arges> hallyn_: hi
[18:58] <hallyn_> arges: hi
[18:59] <arges> hallyn_: i'm taking a look at bug 1100843... not sure if you got anywhere with it.
[18:59] <arges> My plan was to test precise w/ an older kernel since it doesn't seem to be reproduced on Lucid.
[19:00] <arges> But I wasn't sure if there was anything else going on before I embark
[19:07] <hallyn_> arges: no i've not gotten anywhere with it
[19:09] <hallyn_> that is, i've never reproduced
[19:13] <arges> hallyn_: ok i'll take a look at it then. thanks
[19:41] <barry> lool: it seems impossible to update any blueprint work items today
[21:40] <ev> @pilot out
[22:15] <sarnold> slangasek: hello :) Do you 'own' the UbuntuHashes webpage? It came up in bug 1219589 that "ubuntu-docs" isn't the best place to assign bug reports for that page, do you have a recommendation for a better package?  https://help.ubuntu.com/community/UbuntuHashes  https://bugs.launchpad.net/bugs/1219589