[00:13] <lfaraone> ScottK: when uploading, can I include the changes currently in proposed since they have been verification-done for both kernels?
[00:13] <ScottK> lfaraone: Yes.  I already talked to mdeslaur about doing it that way.
[00:14] <lfaraone> ScottK: Okay. I'll have an upload later tonight.
[00:14] <mdeslaur> lfaraone: please file a bug and attach a debdiff, we need to build it in a special way if it's a security update
[00:15] <lfaraone> mdeslaur: Can do. (I have my system set up according to the Security Team's build system guidelines, but I imagine my upload to -security would be rejected anyway)
[00:16] <mdeslaur> lfaraone: yes, we need to build it in a special security team PPA that doesn't have -updates enabled in it
[00:16] <lfaraone> mdeslaur: ah, okay.
[00:16] <mdeslaur> lfaraone: please subscribe "ubuntu-security-sponsors" to the bug, and we'll process it
[00:19] <mdeslaur> lfaraone: thanks!
[00:53] <cjohnston> jtaylor: did you upload shiboken?
[00:53] <xnox> barry: Laney: is it my turn to merge and upload emacs24?! fairly succulent upload from rob ;-)
[00:54] <barry> xnox: if it fixes the bugs i'm seeing, sure :)
[00:55] <xnox> barry: it switches from gtk2 -> 3.
[00:55] <barry> xnox: emacs24.?
[00:55] <xnox> barry: I have bugs with python-mode.el it is not launching ipython3 for me, no matter how hard I try to bend it to do so
[00:55] <xnox> barry: yeah.
[00:56] <barry> xnox: sid's just gotten 6.1.1-1 but i tend to run from bzr head ;)
[00:57] <xnox> i run from bzr as well, but i pull each time i spot a bug.
[00:57] <barry> xnox: still emacs 24.2 right?
[00:57] <xnox> so not very often.
[00:57] <barry> (i think 24.3 isn't yet released)
[00:57] <xnox> yeah, still 24.2+1-2
[00:57] <xnox> whatever that means.....
[00:58] <barry> yeah ;)
[01:01] <xnox> that wasn't so hard - my script that branches lp:debian/foo and lp:ubuntu/foo and then does bzr merge - just worked. Now only need to come up with a changelog entry ;-)
[07:01] <jtaylor> hm wait if we skip raring and do rolling, does than mean I can leave shiboken broken? :)
[09:00] <Laney> xnox: woo
[10:24] <xnox> jtaylor: well, I think i had one person requesting for shibroken to be unbroken.
[10:25] <tumbleweed> patches welcome?
[10:43] <mitya57> http://paste.ubuntu.com/5587520/ — python-launchpadlib uses python-keyring? seriously?
[10:43] <mitya57> when will people just switch to SecretStorage? :)
[13:18] <tumbleweed> dholbach: any chance of moving community-1303-rolling-release before the plenaries? I have a prior dinner arrangement, and that's one of the few vUDS sessions that interests me
[13:21] <dholbach> tumbleweed, I think slangasek scheduled it there - Steve: what's your opinion? ^
[13:22]  * tumbleweed doesn't have to be there, just if it won't cause conflicts, I'd like to
[13:56] <slangasek> dholbach, tumbleweed: I didn't schedule it, just created the blueprint
[13:57] <slangasek> presently, I'm not even finding it on the schedule
[13:58] <dholbach> slangasek, today, 18:15
[13:59] <slangasek> dholbach: ah yes
[14:00] <slangasek> dholbach, tumbleweed: anyway, please check with pgraner/rickspencer3 about moving it
[14:14] <dholbach> tumbleweed, moved to 16:00 utc
[14:14] <tumbleweed> yup, thanks
[15:34] <lfaraone> mitya57: I think it uses SS in Debian, but it's currently broken in Debian.
[15:40] <mitya57> lfaraone: broken in which way?
[15:43] <mitya57> and no, it doesn't (python-secretstorage is not in wheezy)
[15:44] <mdeslaur> mitya57: hard to use secretstorage on a server, no?
[15:45] <lfaraone> mitya57: ah, that's te problem that causes bugs.debian.org/702352 then :)
[15:48] <tumbleweed> lfaraone:  https://rbtcollins.wordpress.com/2013/01/24/launchpadlib-without-gnome-keyring/ (we should document that somewhere in launchpadlib)
[15:50] <lfaraone> tumbleweed: hm, I still get the same exception
[15:51] <tumbleweed> lfaraone: I don't pretend to know how to tame python-keyring
[15:52] <lfaraone> tumbleweed: it sounds like a dbus problem, not a python-keyring problem.
[15:52] <tumbleweed> well, if you could make python-keyring not attempt to talk to anything on dbus...
[15:52] <tumbleweed> and the dbus thing sounds like a client + server mismatch
[15:55] <tumbleweed> lfaraone: that bug is clearly in keyring rather than launchpadlib
[15:55] <tumbleweed> (re your found...)
[15:55] <lfaraone> tumbleweed: oh, oof.
[15:58] <tumbleweed> (or the service on the other side of DBus, what ever that is in your desktop)
[15:58] <tumbleweed> at any rate, not lplib
[15:58] <lfaraone> tumbleweed: reassigned and will retitle
[15:58] <tumbleweed> \o/ less bugs in my packages :)
[16:25] <mitya57> maybe it's a good idea to make python-keyring use secretstorage, not their own buggy implementation
[16:26] <tumbleweed> mitya57: send them a patch
[16:26] <mitya57> tumbleweed: will do, after UDS :)
[22:30] <foxx> hmm - would anyone happen to know of the best way to make start-stop-daemon redirect stderr/stdout to a file? theres plenty of discussion, but no solid answers.. want to avoid using wrapper scripts because they arent always guaranteed to kill the child pid
[22:44] <ESphynx> Did Precise have some kind of multi arch support? i.e. can I put libraries in /usr/lib/x86_64-linux-gnu and expect them to work?
[22:45] <foxx> nm found a safe wrapper - https://gist.github.com/rbranson/638792
[22:45] <ESphynx> all the way since Natty, right... So Oneiric and Precise should be OK with it?
[23:13] <foxx> tumbleweed: i see what you mean by packaging gets easier with time.. what took me hours before, now only takes me a few minutes
[23:14] <foxx> tumbleweed: gonna do a full write up on all these experiences and use this bamboo project as an example for how to build packages.. hopefully will help others in future
[23:23] <bizhanMona> foxx: I am very much interested to know about your experiences
[23:24] <foxx> bizhanMona: ill pm you once the article is up, which shoudl be tomorrow :)
[23:25] <bizhanMona> foxx: thanks so much I will looking forward to it.