[06:49] <dholbach> good morning
[07:38] <dholbach> hey... can you guys please help with the sponsoring queue?
[07:39] <dholbach> we're at 95 requests!
[07:46] <Noskcaj> dholbach, I'm not sure if that's an achievement or a fail
[07:47] <Noskcaj> bdrung, I've made the audacity branch, can you take a look? It should be in your emails
[07:49] <dholbach> Noskcaj, a bit of both ;-)
[08:22] <lifeless> asd
[08:22] <lifeless> bah, sorry.
[08:40] <rbasak> dholbach: how can I politely remove https://code.launchpad.net/~jackweirdy/vidalia/680192/+merge/178623 from the sponsorship queue?
[08:40] <rbasak> (I'm not sure how MPs map into the queue)
[08:41] <infinity> rbasak: Just reject the MP.
[08:42] <rbasak> infinity: I don't see any obvious way to do that. Am I missing some permission somewhere?
[08:42] <rbasak> I can only change status to Needs review, Merged, or Work in progress.
[08:42] <infinity> Possibly.  The 'status' field is editable if you have the right permissions on the branch.
[08:42] <infinity> I'll reject it for you.
[08:42] <rbasak> Thanks
[08:46] <dholbach> rbasak, yes, if in doubt, just ask in here and somebody will do it for you
[08:46] <dholbach> I think it's TB members and LP admins
[08:46] <rbasak> I see. Thanks!
[08:47] <dholbach> I'm not too happy with the setup myself and don't know the reasons for it, but on the other hand, there's always somebody around
[08:47] <dholbach> infinity, happy birthday! :)
[08:47] <infinity> dholbach: Nope, core-dev was added to the group a while back.
[08:47] <dholbach> ah, awesome!
[08:47] <infinity> (So please, stop bugging TB for it)
[08:47] <infinity> rbasak: ^
[08:48] <rbasak> Thanks.
[08:48]  * rbasak should do more core work and apply for core dev.
[08:48] <infinity> Yes, you should.
[08:48] <dholbach> yeehaw
[08:48] <infinity> You're one of the few left on my "would gladly sponsor for core dev" short list.
[08:48] <rbasak> Thanks :)
[09:11] <Noskcaj> Should FFe syncs have the sponsors team unsubscribed till the FFe is granted?
[09:14] <iulian> Noskcaj: Yes because it wouldn't make sense to have the sponsors subscribed if there's nothing to sponsor.
[09:14] <Noskcaj> iulian, ok, thanks
[09:43] <asac> anyone knows if https://lists.ubuntu.com/mailman/listinfo/ubuntu-patches was used at some point? it says HIGH VOLUME, but doesnt have an archive
[09:43] <asac> or is archiving intentional disabled?
[09:44] <cjwatson> asac: Yes, archiving is intentionally disabled, but mails still go out
[09:44] <cjwatson> merge-o-matic sends mails there
[09:45] <cjwatson> I know it still works because occasionally I get bounces :-)
[09:45] <asac> cjwatson: ok... so its not an automatic debdiff service :)? had hoped for that
[09:46] <asac> (for everyhting)
[09:46] <asac> just mom
[09:46] <cjwatson> You may be unaware of everything that MoM does ...
[09:46] <cjwatson> It does more than just merges with respect to Debian
[09:47] <asac> ok... dont need the details now
[09:47] <cjwatson> The code predates me being involved in MoM, but I believe that it announces all changes in Ubuntu
[09:48] <asac> interesting. i guess i might just try to subscribe :)
[09:48] <cjwatson> Well, possibly not all; it probably won't mention syncs
[09:48] <cjwatson> I tend to think that saucy-changes is a more useful list for this kind of thing, since you can check debdiffs for the tiny fraction that you actually care about
[09:49] <ogra_> ++
[09:49] <cjwatson> I think in the case of a merge from Debian, the patch on ubuntu-patches will only contain the new debdiff versus the base version in Debian
[09:50] <cjwatson> But, ubuntu-patches basically is an automatic debdiff service, albeit probably a limited one in some ways
[09:52]  * cjwatson tries to summon Monday morning brainpower to work on proposed-migration for the :any stuff
[09:53]  * ogra_ could only offer some of his jetlag 
[09:55] <Noskcaj> Is it worth converting debdiffs to branches if i lack the power to upload them?
[09:55] <cjwatson> No
[09:55] <cjwatson> Debdiffs are just as easy to apply
[09:55] <Noskcaj> ok
[09:57] <Noskcaj> Can someone please explain why http://reqorts.qa.ubuntu.com/reports links the oneric bug tracker?
[10:14] <smartboyhw> dholbach, how do I tell in the sponsorship queue which packages can I sponsor? (It's nice to include that as a feature in the report)
[10:14] <dholbach> smartboyhw, that'd be very hard to implement - right now it's a static page only
[10:15] <smartboyhw> dholbach, OK
[10:16] <smartboyhw> hmm, it's easy somehow
[12:15] <pitti> Good morning
[12:15] <mdeslaur> @pilot in
[12:51]  * dholbach hugs mdeslaur
[13:01]  * mdeslaur hugs dholbach back
[13:21] <nickguletskii> Hi, I would like to ask if there is a change of https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/987714 getting fixed in precise? This bug breaks multiarch support for no good reason (an empty file "is not in sync with other instances of the same package" somehow)
[13:22] <nickguletskii> chance*
[13:34] <cjwatson> nickguletskii: Hm, dpkg bug I think.  Somebody should confirm in a chroot environment whether quantal's dpkg behaves the same way; I suspect it doesn't.
[13:36] <nickguletskii> cjwatson: It seems that the quantal version of libsensors4 doesn't have that file, so I can't replicate.
[13:37] <nickguletskii> heh, weird, it does
[13:38] <cjwatson> nickguletskii: You don't have to replicate with the quantal version of libsensors4
[13:38] <cjwatson> You can probably just take a precise chroot and manually upgrade it to quantal's dpkg
[13:38] <nickguletskii> cjwatson: My bad, it does have .placeholder in .install, it just doesn't exist in the filesystem
[13:38] <nickguletskii> cjwatson: You are right, this is probably a dpkg bug...
[13:39] <OrokuSaki> @hallyn Hi! I was wondering if you could help me out with lxc 1.0 sometime.. its not working for me.. I am using 0.9X instead.. when I run lxc-info -n android, I don't have a pid. Kernel is 2.6.35.. Does this perhaps have to do with /sys/fs/pstore? My kernel does not have pstore.. I may try to backport it
[13:39] <udevbot> Error: "hallyn" is not a valid command.
[13:40] <OrokuSaki> Of couse, I don't have fanotify or apparmor either
[13:41]  * cjwatson tries a test upgrade
[13:41] <cjwatson> (needs quantal's liblzma5 too)
[13:43] <cjwatson> nickguletskii: Yep, quantal's dpkg is fine, so a backport *should* be possible; not trivial since the code was rearranged somewhat
[13:43] <chrisccoulson> i've just rebooted my laptop, and it now only boots to a grub prompt.  anyone like to help me out here? :)
[13:43] <cjwatson> chrisccoulson: https://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell
[13:44] <chrisccoulson> cjwatson, thanks
[13:44] <cjwatson> chrisccoulson: BIOS or UEFI?
[13:44] <nickguletskii> cjwatson: so it's very unlikely that it will happen?
[13:44] <cjwatson> nickguletskii: I didn't say that :-)
[13:45] <chrisccoulson> cjwatson, UEFI
[13:45] <cjwatson> chrisccoulson: With or without secure boot?
[13:46] <chrisccoulson> cjwatson, it's with secure boot
[13:46] <cjwatson> chrisccoulson: Just a theory but might you perhaps have saucy-proposed enabled, upgraded grub2 last Wednesday, and didn't upgrade between then and rebooting?
[13:46] <nickguletskii> cjwatson: I can't find a relevant bug (I can only find the .placeholder problem in libsensors4)... Should I ask in #ubuntu-bugs about filling out a bug report?
[13:47] <cjwatson> nickguletskii: Er, you don't need a new bug - I reassigned this one to dpkg
[13:47] <chrisccoulson> cjwatson, yeah, that's entirely possible
[13:47] <cjwatson> chrisccoulson: *ritual mockery for having saucy-proposed enabled*
[13:47] <chrisccoulson> heh
[13:47] <cjwatson> chrisccoulson: "configfile /EFI/ubuntu/grub.cfg"
[13:47] <cjwatson> then get back into a real system and upgrade to a grub version actually intended for human consumption
[13:48] <cjwatson> and disable saucy-proposed :)
[13:48] <nickguletskii> cjwatson: thank you very much :)
[13:48] <chrisccoulson> cjwatson, aha, that looks better. Thanks!
[13:48]  * chrisccoulson owes cjwatson a beer
[13:49] <cjwatson> You can repay me by answering my question from last week :-)
[13:49] <cjwatson> 11:41 <cjwatson> chrisccoulson: firefox-testsuite needs to be updated to depend on fonts-liberation, not ttf-liberation - I think I have commit access but which branch(es) do I need to commit to?
[13:49] <nickguletskii> bye :)
[13:49] <chrisccoulson> cjwatson, ah, i think i've committed that to trunk
[13:49] <cjwatson> Oh good, thanks
[13:50] <chrisccoulson> i was going to upload it when i do the firefox 24 upload later
[13:50] <cjwatson> Yeah, no desperate rush, I just didn't want it to drift past release
[13:50] <chrisccoulson> sure, no problem
[13:50] <chrisccoulson> right, switching back to my proper machine now :)
[13:52] <smoser> hm..
[13:52] <smoser> $ sudo ifquery --list --allow auto
[13:52] <smoser> [sudo] password for smoser:
[13:52] <smoser> ifquery: failed to lock lockfile /run/network/.ifstate.lock: Bad file descriptor
[13:52] <smoser> that does'nt look right. expecially since
[13:52] <smoser>  /etc/network/if-up.d/upstart
[13:52] <smoser> uses it.
[13:53] <smoser> it seems /run/network/.ifstate.lock was created around the time my system booted.
[13:53] <smoser> slangasek, ^ you have any explanation that make that just my system ?
[14:13] <hallyn_> OrokuSaki: (replied to the pm)
[14:13] <smoser> bug 1226067
[14:14] <hallyn_> OrokuSaki: oh, looks like ppa version hasn't been built since i pushed the fix to git, lemme make sure
[14:15] <hallyn_> no, it hasn't.  starting a build now
[14:37] <OrokuSaki> Sweet! hallyn! thanks! =)
[15:13] <slangasek> smoser: nothing specifically... if the lock file is hanging around, that seems like an 'ifup' call may have crashed?
[15:13] <smoser> slangasek, maybe. reproduces in stock cloud iamge.
[15:20] <smoser> slangasek, https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1226067
[15:20] <smoser> nothing really sticks out at me in the system.
[15:28] <lamont> if saucy complains that gnome-control-center-unity is not part of ubuntu, is that me, or saucy?
[15:29] <smoser> arges, ping.
[15:30] <arges> smoser: hi
[15:30] <smoser> please see bug 1160490
[15:30] <arges> yes
[15:31] <arges> smoser: ok i see it
[15:38] <arges> smoser: as an experiment can you test 0.7.44 from debian unstable? and see if it has the same issue?
[15:43] <gQuigs> I was wondering if all the desktop related lucid bugs on here: http://people.canonical.com/~ubuntu-archive/pending-sru.html could just be closed
[15:43] <gQuigs>   for example: xserver-xorg-video-openchrome, gnome-power-manager and moon (moonlight)
[15:43] <gQuigs> I was told I would need someone on the SRU team to get close them out
[15:43] <alberts> mdeslaur: Hi! Can you look at fix for nautilus - https://code.launchpad.net/~albertsmuktupavels/nautilus/white-screen-fix/+merge/180231
[15:46]  * mdeslaur looks
[15:48] <smoser> arges, well, 0.7.44-0ubuntu2 *does* have it (saucy)
[15:48] <smoser> i can quick try with 0.7.44 from debian though
[15:48] <arges> smoser: actually n/m, looking at the usptream changes
[15:49] <smoser> arges, k. fwiw, reproduce was just 'boot a cloud image'
[15:49] <smoser> (also i see this on my laptop though)
[15:49] <arges> smoser: yea setting it up now and debugging
[15:55] <mdeslaur> alberts: sorry, I don't have enough nautilus knowledge to be able to understand the impact of that fix. Perhaps you could get someone from the desktop team to approve it?
[15:58] <alberts> mdeslaur: how to do that?
[15:58] <arges> smoser: found a patch that fixes it
[15:58] <arges> http://anonscm.debian.org/hg/collab-maint/ifupdown/rev/fb3055c2c4f0
[15:59] <arges> smoser: whats teh best way to approach this? create new debdiffs for the regression?
[16:00] <smoser> for raring, i think you just upload a new package into -proposed.
[16:00] <smoser> that has a new package version > propposed version
[16:00] <alberts> mdeslaur: can you look also at this - https://code.launchpad.net/~albertsmuktupavels/ubuntu-themes/restore-space-between-applications-and-places-in-gnome-panel-raring/+merge/178242. It is simple fix which already is included in saucy, but I think it should be included in raring too.
[16:01] <mdeslaur> alberts: for the nautilus issue, perhaps ask seb128 in #ubuntu-desktop about it?
[16:01] <arges> smoser: ack. i'm on it
[16:01] <mdeslaur> @pilot out
[16:01] <alberts> mdeslaur: ok
[16:04] <gQuigs> how about SRUs from 11.10?  Can they just be closed? : see bug 853507
[16:06] <smoser> arges, but i think first thing is fix in saucy. i dont think SRU team will move that to -updates as athe bug is right now.
[16:06] <arges> smoser: will do saucy first
[16:15] <slangasek> smoser, arges: if you want the SRU team to know not to copy the package to -updates, you'd better set the verification-failed tags...
[16:17] <smoser> done
[16:19] <arges> slangasek: smoser: so i found the fix for the regression. how should i handle this? submit a new debdiff with both patches (the one that fixes the race and the fix for teh regression?)
[16:19] <slangasek> arges: submit an incremental patch against the packages currently in saucy + -proposed
[16:19] <arges> slangasek: ok this is in bug 1226067
[16:20] <slangasek> yep
[16:22] <arges> this might be a good testcase to add to ifupdown
[16:24] <ari-tczew> ampelbein_: can we forward this one to Debian? or it's Ubuntu-specific? (https://launchpad.net/ubuntu/+source/synfig/0.64.0-1ubuntu2)
[16:25] <ampelbein_> ari-tczew: As far as I can tell, debian doesn't have multiarched boost yet.
[16:26] <ampelbein_> Or has it? I didn't check for some time.
[16:27] <ari-tczew> ampelbein_: I don't know, as well.
[16:28] <ampelbein_> ari-tczew: So, if Debian doesn't have it yet, the patch would be very wrong to send to debian.
[16:29] <ari-tczew> sure
[16:43] <arges> slangasek: ok. so bug 1226067 has the patches for P/Q/R as well (since they are affected.)
[17:39] <utlemming> anyone around to help debug 13.04 to 13.10 device permission issuses?
[17:39] <utlemming> after upgrading from 13.04 to 13.10 I lost the ability to manage USB disks, use printers, audio, webcam and networking
[17:39] <utlemming> pretty much discovered that 13.04 to 13.10 makes my laptop largely unusable
[17:40] <utlemming> I was able to fix audio and webcam, but everything else is fubar'd
[17:40] <utlemming> I am really thinking of reverting back to 13.04
[17:48] <smoser> arges, i'll upload to saucy "right now" unless someone else is doing that.
[17:56] <arges> smoser: cool., nobody else is sponsoring afaik
[18:22] <dobey> pitti, jibel: hey. i uploaded an ubuntuone-credentials last week, and for some weird reason, the autopkgtest run failed, but i got no e-mail about it failing. and the failure makes no sense to me. :(
[18:33] <dobey> has uscan or something gone weird recently? i just did a bzr merge-upstream on a branch, and ".bz2" has been appended to the version number
[18:34] <Laney> dobey: isn't it the missing make check target?
[18:35] <dobey> Laney: that's what the error says, but given the exact same tests ran fine previously, and that the tests require a built tree and everything, i find it hard to believe that is a valid error. did adt-run do something to change to a different working directory without an unbuilt tree, to run the tests, recently?
[18:36] <dobey> and that the only change in that upload was to add a dep in debian/control…
[18:37] <Laney>   * adt-run: Fail tests if they exit with nonzero if "allow-stderr"
[18:37] <Laney>     restriction is set. Thanks Robie Basak! (LP: #1210503)
[18:37] <Laney> probably that
[18:38] <Laney> I guess it erroneously used to pass
[18:39] <dobey> oh, ugh
[18:43] <dobey> Laney: of course, that still doesn't explain why I was never notified about the failure when it did start happening. :)
[18:43] <dobey> Laney: anyway, any idea about the ".bz2" being appended to the version when i do merge-upstream?
[18:43] <Laney> No idea
[18:44] <Laney> have a look at uscan --verbose --report {,--debug}
[18:50] <dobey> well, that verifies that it's apparently uscan doing it :-/