=== chilicuil_away is now known as chilicuil
=== chilicuil is now known as chilicuil_away
[07:20] <dholbach> good morning
=== Logan_ is now known as Guest76402
=== Logan__ is now known as Logan_
=== yofel_ is now known as yofel
=== Tonio_ is now known as Tonio_aw
=== chilicuil is now known as chilicuil_away
=== almaisan-away is now known as al-maisan
=== Tonio_aw is now known as Tonio_
=== al-maisan is now known as almaisan-away
[14:41] <shadeslayer> hi, I was wondering if someone could advise me a bit about spaces in .link files
[14:42] <shadeslayer> the original file has spaces in the folder name, causing dh_link to parse the link file improperly
[14:43] <shadeslayer> so something like : /usr/share/foo/b a r should be linked to /usr/share/foo/bar
[14:52] <geser> and you have to keep the filename with spaces too?
[14:54] <geser> have you tried escaping or using "? if neither works then you probably have to do it by hand in debian/rules
[14:59] <Zhenech> shadeslayer, spaces in debhelper files are evil, avoid em
[15:00] <shadeslayer> geser: the problem is more in the dir name
[15:00] <shadeslayer> it's /usr/share/f o o/bar
[15:00]  * shadeslayer is still playing around
[15:06] <shadeslayer> okay so, this is what I'm using : /usr/share/wallpapers/Dryland\ -\ Third\ Edition\ -\ The\ Map/contents/contents/images/1920x1200.jpg /usr/share/netrunner/ubiquity/background.jpg
[15:06] <shadeslayer> does not work :(
[15:07] <shadeslayer> http://paste.kde.org/616130/
[15:09] <shadeslayer> and I think dh_link just ignores the escapes
[15:11] <shadeslayer> ah well, manually it is
[15:31] <geser> shadeslayer: what might also work: /usr/share/wallpapers/Dryland*/contents/contents/images/1920x1200.jpg /usr/share/netrunner/ubiquity/background.jpg
[15:32] <geser> (if I read the code correctly and assuming that the first part will expand to exactly one file)
=== Tonio_ is now known as Tonio_aw
[17:28] <achiang> hello, process question. for an MP like this, should i subscribe ubuntu-sponsors, or do i wait for reviewers to pick it up first? https://code.launchpad.net/~achiang/appmenu-gtk/memleaks-787736-780602/+merge/136550
[17:29] <micahg> achiang: that has nothing to do with ubuntu-sponors
[17:29] <micahg> you're asking to merge into an upstream branch
[17:30] <achiang> micahg: i see. so presumably once it's merged, the upstream team could make an upload to precise-proposed?
[17:31] <micahg> achiang: if they make a release , or you can take the patches after they're merged into the trunk branch and try to get them uploaded to precise-raring
[17:31] <achiang> micahg: got it
[17:31] <achiang> thanks
[17:31] <micahg> achiang: it sounds like they're already committed to trunk though...
[17:32] <achiang> micahg: eh? it was a backport of upstream trunk into the precise branch
[17:32] <micahg> achiang: that branch is labeled as trunk, as this is a desktopish package, maybe ask them how to proceed here
[17:32] <achiang> alrighty, thanks
[18:16] <radu> hi
[18:17] <radu> I have a question regarding SRUs
[18:17] <radu> I'm looking at this bug assigned to the hundred papercuts team: https://bugs.launchpad.net/hundredpapercuts/+bug/1052481
[18:18] <radu> this bug is irrelevant for raring, because of changes to nautilus between 3.4 and 3.6. What would I have to do if I want to get it fixed in quantal and precise?
[18:19] <radu> the bug itself is easy to fix, but how do you go about getting the fix added in the stable version?
[18:29] <xnox> radu: you nominate the bug for correct series and adjust status per-series. like I have now done.
[18:30] <radu>  xnox: ok thanks.
[18:31] <xnox> radu: if you need similar help for other bugs, #ubuntu-bugs is the channel. Those folks know everything about bug management =)
[18:31] <micahg> xnox: actually, SRU is more MOTU land than -bugs, -bugs is about triage mostly whereas SRU is a dev thing
[18:32] <xnox> micahg: sure, but in this case the real question was "i need this to be targetted at two releases, excluded dev release. how do I do this in launchpad bug tracker?"
[18:33] <xnox> unless I misunderstand.
[18:33] <micahg> right, so, only bug control (and teams that are members of it) and drivers can target, but only drivers + devs can approve AIUI
[18:33] <radu> well, this is my next question - if I add a patch with a fix, how do I go about finding someone to sponsor it for upload in the stable release?
[18:34] <micahg> so, if you actually want tasks instead of a nomination, you have a better chance here
[18:34] <xnox> radu: now, the next step is to follow sru procedure & adjust the bug description (which is amost ok now) and now create debdiff attach to the bug and subscribe ubuntu-sponsors.
[18:35] <radu> aha, so I subscribe ubuntu-sponsors and wait for someone to review it. Excellent, thanks
[18:35] <xnox> radu: then sponsors will upload it, sru team accept it, then everyone needs to verify that it fixes the problem and then it will be released into updates.
=== Tonio_aw is now known as Tonio_
[20:35] <ESphynx> xnox : ping
[20:35] <xnox> ESphynx: what is nobody sponsoring your upload?
[20:35] <xnox> *sigh*
[20:36] <ESphynx> nonone is and dardevelin is what the hecking me :P
=== lifeless_ is now known as lifeless
=== Todd__ is now known as Todd