[02:36] <vibhav> Can anybody tell me whether LP #871739 is worth a sync?
[02:38] <ajmitch> vibhav: are you sure that applies to the version in precise?
[02:39] <vibhav> lemme see that
[02:49] <vibhav> ajmitch: Yes, The bug can be reproduced in precise
[02:53] <ajmitch> vibhav: given that precise has 2.4.0-5, which had the fix to bring back static libraries (-6 was just a rebuild), syncing wouldn't gain much
[02:55] <vibhav> fine, then ill develop a patch
[02:57] <ajmitch> how'd you check it? I just took a look at the package on my local mirror, it seems to have the .a files
[02:58] <vibhav> I installed it on my VM
[02:58] <vibhav> And the .a files were not present
[02:59] <vibhav> ajmitch: My bad
[02:59] <vibhav> I found em
[03:00] <ajmitch> ok
[03:00] <vibhav> So, should I mark this bug as "Fix Released" ?
[03:00] <ajmitch> fwiw, you can use dpkg-deb -c /path/to/package.deb to list the contents, it's a little quicker than installing
[03:00] <vibhav> thanks
[03:00] <ajmitch> yes, it looks to be fixed so mark it as that
[05:47] <vibhav> IS it safe to apply options that speed up building in pbuilder?
[05:52] <RAOF> vibhav: That depends; do they work? :)
[05:59] <vibhav> RAOF: They work
[05:59] <vibhav> Though they might mess up something
[07:18] <geser> vibhav: which options do you want to apply?
[07:27] <vibhav> geser: https://wiki.ubuntu.com/PbuilderHowto , look at the "Speeding up build-dependencies calculation" and "Speeding up the package installation"
[07:29] <RAOF> vibhav: They're safe.
[07:29] <geser> vibhav: I use those for a long time and didn't have any issues with them (as long as the tmpfs is large enough to build the package :) )
[07:29] <vibhav> thanks RAOF geser
[07:47] <dholbach> good morning
[08:10] <Tribaal> Hi folks, I'm currently trying to fix a small packaging bug on opensc, and my launchpad branch is up for review - would anybody have a minute to spare to tell me if my process is correct (it's my very first time fixing something in Ubuntu)?
[08:18] <vibhav> Do I need to change the "other" non-debian changelog while fixing a bug?
[09:05] <arand> vibhav: There should be no need to patch the upstream changelog, if that's what you're asking, make sure to forward the patch upstream as well.
[09:07] <Tribaal> so, I put a packaging fix branch for review in precise - is there anything else I should do? Like ping somebody or tag it with something?
[09:08] <tumbleweed> Tribaal: propose a merge
[09:08] <Tribaal> tumbleweed, that's done
[11:33] <vibhav> How does one join The Sponsors Team?
[11:37] <Laney> vibhav: by being an Ubuntu Developer and then asking an admin nicely
[12:23] <Tribaal> Laney, what/when should one request sponsorship? I submitted a branch for review a few hours ago - is that all I need to do? Is that what sponsorship is for?
[12:23] <Laney> Tribaal: you should check it appears on http://reports.qa.ubuntu.com/reports/sponsoring/ and if so someone will look at it in due course
[12:24] <Tribaal> Laney, it does, and thanks for the clarification!
[12:24] <Laney> np
[12:25] <Tribaal> Laney, is this page basically the "log of stuff to merge from non-ubuntu members"?
[12:27] <Laney> it's stuff which people would like uploaded but can't do themselves
[12:27] <Tribaal> Laney, makes sense, thanks again.
[12:28] <Tribaal> Laney, last question (promise :) ): how does one become a motu? Not that I intend to, but I'm just curious
[12:29] <Laney> Tribaal: Keep contributing fixes and soon enough someone will tell you to apply (to the Developer Membership Board)
[12:29] <Tribaal> Laney, oh, it's a pull process, not a push :) Interesting. Thanks again for your help
[12:29] <Laney> well, it can be either actually
[12:30] <Tribaal> how much is considered "enough" contribution?
[12:30] <Laney> but a good way to know when to apply is when people assume you already are MOTU, or tell you to hurry up and apply already
[12:30] <Tribaal> haha
[12:30] <Tribaal> ok
[12:31] <Laney> there's no fixed "enough", but less than six months would be unusual
[12:31] <Tribaal> Laney, makes sense
[12:31] <ajmitch> unless you got in early on, when 6 weeks was a long time ;)
[12:32]  * ajmitch wants to rant about libraries that claim to be 'open source' but really aren't free to use
[12:32] <Tribaal> so just for my understanding - being an "ubuntu developer" is being allowed to push to universe or "more"?
[12:32] <Tribaal> the titles are confusing :)
[12:32] <ajmitch> pretty much, it implies you have some upload privileges, whether to a limited set of packages or to universe
[12:33] <Tribaal> ahhh
[12:33] <Tribaal> and so a motu has upload privileges to "universe" while an ubuntu developer might have provileges to only a few packages?
[12:33] <Laney> right
[12:34] <Tribaal> gotcha
[12:34] <Laney> ubuntu developer is the umbrella group
[12:34] <Tribaal> got it
[12:34] <Tribaal> thanks for the clarification
[12:42] <dholbach> Tribaal, please keep asking questions :)
[12:43] <Tribaal> sure, but I don't want to be the annoying newbie (tm) today (it's Friday, and I assume most people are hungover or tired or both)
[12:44] <bregma> the hangover doesn't start until tomorrow
[12:44] <Tribaal> oh? good
[12:45] <dholbach> bregma, do you have plans for the WE already? :)
[12:45] <Tribaal> then: I fixed a packaging problem (a one liner), how do I engage debian about it? Should I do it myself? is it automated?
[12:45] <tumbleweed> it's not automated
[12:45] <Tribaal> do people expect me to fix it as upstream as possible?
[12:45] <Tribaal> and let it "ripple down" into ubuntu when the next debian refresh comes?
[12:45] <dholbach> Tribaal, these are all great questions
[12:45] <dholbach> https://wiki.ubuntu.com/Debian/Bugs#Using_submittodebian_to_forward_patches_to_Debian
[12:46] <dholbach> ^ explains how to use a nice tool to submit fixes to Debian
[12:46] <tumbleweed> put it this way, after you make a package in Ubuntu differ from Debian, you are responsible with keeping it up to date
[12:46] <tumbleweed> (the changes from Debian have to be synced into it by hand)
[12:46] <tumbleweed> so it's in your interest to get it as upstream as possible
[12:46] <Tribaal> ok, easy enough for my one liner, but I can see how that can become a problem :)
[12:46] <dholbach> it's also a matter of timeliness - if we are a few days away from release and have an urgent problem to fix or find that upstream or debian won't take an obvious fix for a longer period of time, it's totally fine to get it into Ubuntu - even if it creates delta
[12:47] <tumbleweed> we recommend making non-urgent changes in Debian, and just syncing them to Ubuntu
[12:47] <tumbleweed> but that's easier when you know the debian maintainer of that package or one of its uploaders...
[12:47] <Tribaal> now the killer question: what defines "urgent"?
[12:47] <tumbleweed> urgent enough for you to want to do it in Ubuntu first :)
[12:47] <Tribaal> haha
[12:48] <dholbach> you'll get a sense of it with a bit of experience - and you can always ask
[12:48] <tumbleweed> and different people have different views on this
[12:49] <Tribaal> so, shameless self-promotion and poll: what do you think about this: urgent or not? https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/872019
[12:50] <tumbleweed> that package is already modified in Ubuntu
[12:50] <Tribaal> indeed
[12:50] <tumbleweed> so go for it
[12:50] <Tribaal> so basically that means "wait for a sponsor to pick up your patch and merge it", or is there another step in the process?
[12:51] <tumbleweed> no, that's abotu it
[12:51] <Tribaal> alright
[12:51] <Tribaal> sweet
[12:51] <tumbleweed> do push it upstream too, if applicable to Debian
[12:52] <Tribaal> not sure it is, for the time being
[12:52] <Tribaal> I need to check
[12:54] <Tribaal> oh it's already fixed in debian :)
[12:54] <Tribaal> sweet
[12:55] <Laney> in that case you should investigate taking their fix instead of doing an ubuntu-specific one
[12:55] <Tribaal> hum ok
[12:55] <Laney> makes for less maintenance in the long term
[12:55] <Laney> :-)
[12:56] <Laney> depends on what their fix is, of course
[12:56] <Tribaal> even if the diff will be null after ubuntu pulls the latest debian version?
[12:56] <Laney> makes for less changes to review at that time
[12:56] <Tribaal> yeah, so that is basically already the case
[12:57] <Tribaal> I reimplemented their exact solution (it's a one liner...)
[12:57] <Laney> got to go to a seminar, sorry
[12:57] <Tribaal> sure thing
[12:57] <Tribaal> nice talking to you Laney
[12:58] <tumbleweed> if upullin gin the latest debian version won't bring new features, and will fix bugs, then that's by far the best solution
[12:58] <tumbleweed> (we're in feature freeze, so new features require release-team approval)
[12:59] <Tribaal> there are new features in the debian package (new upstream version)
[13:00] <Tribaal> this specific fix is however purley a packaging issue (the debian/opensc.install file was missing an entry, basically)
[13:00] <Tribaal> quite the trivial diff
[13:01] <tumbleweed> Tribaal: have you seen bug 935348?
[13:02] <Tribaal> FTBFS - fails to build from source?
[13:02] <tumbleweed> correct
[13:02] <Tribaal> whow
[13:03] <Tribaal> how come I can build it locally?
[13:03] <tumbleweed> good question :)
[13:03] <Tribaal> ah
[13:03]  * tumbleweed tries a local build
[13:03] <Tribaal> precise
[13:03] <Tribaal> this machine is oneiric
[13:03]  * Tribaal newbie
[13:03] <tumbleweed> ah. I recommend setting up a pbuilder / sbuild for test-building
[13:03] <Tribaal> oh, I thought I had that
[13:04] <Tribaal> is that what bzr bd uses?
[13:04] <tumbleweed> also, running the development release is a good idea if you want to find problems :P
[13:04] <Tribaal> indeed, but I don't want to find too many of them at once :P
[13:04] <tumbleweed> Tribaal: no, bzr bd just builds on your machine
[13:04] <Tribaal> oh ok
[13:05] <ogra_> tumbleweed makes it sound as if there were no probs in non dev images
[13:05] <ogra_> :)
[13:05] <Tribaal> :)
[13:05] <tumbleweed> ogra_: I generally find dev releases more stable, yes :)
[13:05] <ogra_> haha
[13:06] <Tribaal> well I will have to switch relatively soon, I'm the last guy in my team not using Precise
[13:06] <Tribaal> will you guys be at UDS?
[13:07] <ogra_> sure
[13:07]  * tumbleweed must still book flights
[13:07] <Tribaal> cool
[13:10] <Tribaal>  so is universe feature frozen as well?
[13:11] <ajmitch> tumbleweed: you'd better, you don't have long :)
[13:12] <ajmitch> Tribaal: yes, feature freeze applies to universe as well
[13:13] <Tribaal> the latest debian package would fix the build for that package :)
[13:13] <ajmitch> you can get freeze exceptions
[13:13] <tumbleweed> there are a few reverse dependencies of opensc. If they'll work with the new version, we can probably sync it
[13:13] <ajmitch> also the freeze just applies to new features, new bugfix releases can be uploaded
[13:13] <Tribaal> oh ok
[13:21] <hrw> freeze... I forgot lesson from ogra - 'upload, nevermind how broken. fixes are accepted later' :D
[13:22] <ajmitch> so this is what ogra_ is teaching people these days? :)
[13:25] <hrw> ajmitch: I think he used lighter description ;)
[13:32] <ogra_> lol
[14:07] <lenios> hi there
[14:07] <lenios> does anybody know if mysql-workbench-gpl will be available for precise? https://bugs.launchpad.net/ubuntu/+bug/53062
[14:14] <Adri2000> lenios: no, unless someone asks for a FeatureFreeze exception and syncs it from debian
[14:14] <lenios> then shouldn't the package be removed?
[14:14] <Adri2000> removed from where?
[14:15] <lenios> because mysql-workbench-gpl:i386 is available, but broken because it's asking for non existing dependencies
[14:16] <lenios> it works when linking libzip2 to libzip1 though
[14:16] <Adri2000> where do you see this package available? I don't see it in ubuntu
[14:16] <Adri2000> there is mysql-workbench in debian though
[14:19] <lenios> oops, my bad, i'm talking about local mirror
[15:03] <lazka> What should I do regarding daily build in a PPA with source format 3.0? I used to append ~revision to the version, but now the orig.tar.gz doesn't contain that and lauchpad rejects the upload because a orig.tar.gz with that name is already there
[15:04] <lazka> Do I need to add the revision to the main version, giving me a new orig for each upload?
[15:20] <geser> IIRC recipes only work with "3.0 (native)" and not "3.0 (quilt)", but probably better ask in #launchpad
[15:23] <lazka> geser, ok, thanks
[15:36] <tumbleweed> geser: apparently quilt is supported these days, if upstream releases are appropriately tagged
[15:36] <geser> oh, that news for me, but I don't know much about recipes
[15:38]  * tumbleweed hasn't played with that feature
[16:25] <phiphi> hello. Who's responsible for packaging the nvidia drivers?
[16:25] <phiphi> Nvidia Driver uninstall is incomplete. Open Source 3D Driver Nouveau remains blacklisted. bug 958848
[16:25] <phiphi> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/958848
[16:39] <tumbleweed> phiphi: tseliot
[16:41] <phiphi> tumbleweed: thank you, subscribed him to the bug.
[16:42] <phiphi> Can somebody confirm the bug? Is my view right, that this is a simple bug?
[16:43] <tumbleweed> phiphi: he's presumably already subscribed to all nvidia driver bugs
[16:44] <tumbleweed> phiphi: if you haven't purged the package, it's configuration files will remain
[16:45] <phiphi> its not a config its the blacklisting of the opensource driver that remains. It gets blacklisted twice and one is removed.
[16:45] <tumbleweed> ah
[16:46] <tumbleweed> the best way to get a bug noticed is to provide a patch
[16:48] <phiphi> Of course. But I'm a packager.
[16:48] <phiphi> Can you guide me to the packaging recipe or whatever, perhaps I can find the bug
[16:51] <phiphi> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/nvidia-graphics-drivers/precise/view/head:/debian/nvidia-current.prerm
[17:24] <hakermania> Hi there! I've got a ready backport for Wallch, version 3.0 actually. I was (quite) recently told to take a freeze exception, any change, or anything that I have to keep in mind?
[17:58] <sivapvarma> how to make the screen shot app in ubuntu to make select area for grab as default option
[17:58] <sivapvarma> that will save me a mouse click each time
[18:00] <hakermania> sivapvarma, open a terminal, go to /usr/share/applications
[18:00] <sivapvarma> ok
[18:00] <sivapvarma> then
[18:00] <hakermania> nano gnome-screenshot.desktop
[18:01] <hakermania> and in Exec field
[18:01] <hakermania> instead of gnome-screenshot --interactive
[18:01] <hakermania> place gnome-screenshot -a
[18:01] <hakermania> save with Ctrl+O and then Ctrl+X
[18:01] <hakermania> now, every time you click on the screenshot icon you will be asked to select an area
[18:02] <hakermania> You can also bind the PrtSc button for this with a little trick, if you're interested... Not very difficult...
[18:03] <hakermania> sivapvarma, you have to be root to edit gnome-screenshot.desktop, of course
[18:03] <hakermania> (sudo nano gnome-screenshot.desktop)
[18:04] <sivapvarma> it seems i like sudo vim gnome-screenshot.desktop :-)
[18:04] <hakermania> ok, did you succeed ?
[18:06] <sivapvarma> hakermania: yeah thanks its working
[18:06] <sivapvarma> what about the dirty hack :-)
[18:07] <hakermania> ok, about the 'dirty' hack now, open a terminal and do sudo mkdir /screenshot_app
[18:07] <sivapvarma> ok before I do what you say
[18:07] <hakermania> ?
[18:07] <sivapvarma> let me tell you what i tried before
[18:07] <hakermania> no, let me finish
[18:08] <sivapvarma> I have created a custom shortcut in keyboard application
[18:08] <hakermania> then do sudo mv /usr/bin/gnome-screensaver /screenshot_app/
[18:08] <sivapvarma> ctrl + print scrn -> gnome-screenshot -a
[18:09] <hakermania> gnome-screenshot*
[18:09] <sivapvarma> it worked for two to three times but did not work later on
[18:09] <hakermania> Ok, sivapvarma, let me tell you know
[18:09] <hakermania> Let me start again
[18:09] <sivapvarma> ok
[18:09] <hakermania> 1) sudo mkdir /screenshot_app
[18:09] <sivapvarma> you mean from home folder
[18:09] <hakermania> 2) sudo mv /usr/bin/gnome-screenshot /screenshot_app
[18:10] <hakermania> from wherever, number (1) will do the same thing, regardless where you run it
[18:10] <hakermania> it will create a directory in root ( / ) anmed screenshot_app
[18:10] <hakermania> named*
[18:10] <hakermania> if you do cd /
[18:10] <hakermania> and then ls
[18:10] <hakermania> you will see it
[18:10] <sivapvarma> ok
[18:12] <sivapvarma> done till now what next
[18:13] <hakermania> 3) sudo nano(or vim) /usr/bin/gnome-screenshot and place this inside: http://paste.ubuntu.com/896777/
[18:13] <hakermania> 4) sudo chmod +x /sreenshot_app/gnome-screenshot
[18:13] <hakermania> 5) Done
[18:13] <hakermania> i'm a genius :P
[18:14] <hakermania> Oh, I got step 4 wrong, it is 4) sudo chmod +x /usr/bin/gnome-screenshot
[18:17] <PaoloRotolo> Hi all!
[18:17] <hakermania> Hi Paolo...
[18:20] <hakermania> sivapvarma, just tried it on my machine and it works like a charm btw
[18:20] <sivapvarma> same here too thanks :-)
[18:20] <hakermania> np
[18:20] <sivapvarma> but where did i mess up while creating the keyboard shortcut
[18:22] <hakermania> I don't know, I never trusted those things... For example, now they have placed for minimize/maximize shortcuts in Beta 12.04 -> Windows Key+Down/Up arrow, but this also causes, because of the windows key button to open the Dash -_-
[18:24] <sivapvarma> ok can we share the screen with tranparent white so that we can clearly notice that screenshot app is running
[18:24] <sivapvarma> shade*
[18:25] <sivapvarma> now whenever i run screeshot I have to search for mouse pointer to make sure it is working
[18:25] <sivapvarma> also that feature  is very intuitive and it should be there
[18:25] <sivapvarma> any ideas on how it can be done
[18:27] <sivapvarma> if you have to tried shutter for example it has such a feature when grabbing an area of the screen
[19:37] <Ramiel> hi. What's a reasonable character for separating official package version from the patched one you're uploading to the ppa?
[19:37] <Ramiel> the patched version contains modifications not applied upstream or in the ubuntu version
[19:38] <Ramiel> it's supposed to be up-to-date with original package, but it's not a newer/early-access/nightly-build/whatever
[19:39] <hakermania> Ramiel, i feel you, i have same question...
[19:39] <Ramiel> I think tilde is not suitable as it won't supersede the version it's chnaging
[19:40] <Ramiel> hakermania: I'm sicerely thinking of changing the package names and make them conflict with original ones...
[19:40] <Ramiel> but it's more than one package and I don't know exactly where the patches become packaged into
[19:43] <astraljava> Ramiel: hakermania: Perhaps you're looking for this? https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage
[19:44] <Ramiel> astraljava: I alredy read that before but someone I unfortunately trusted told me I probably wanted tilde instead of dash
[19:45] <Ramiel> astraljava: a counter is a non-go, do you think it's ok 1:2.10.0-0ubuntu2ppa20120323?
[19:46] <Ramiel> also, how about 1:2.10.0-0ubuntu2.P20120323?
[19:49] <micahg> Ramiel: + is what you're looking for I think
[19:50] <micahg> ahead of the current version behind SRUs
[19:51] <Ramiel> SRUs?
[19:52] <Ramiel> service release updates?
[19:52] <broder> !sru
[19:56]  * Ramiel thinks of using '+'
[19:58] <ajmitch> micahg: currently re-merging phpldapadmin for security fixes, I suppose these also need to make it back to previous releases? :)
[19:59] <micahg> ajmitch: would be nice :)
[19:59] <micahg> ajmitch: I think jdstrand is on deck for community tasks next week
[20:00] <ajmitch> ok
[20:01]  * ajmitch will just try & work through a few on the rc bugs list today
[20:05] <ajmitch>  955 files changed, 78554 insertions(+), 36532 deletions(-)
[20:05] <ajmitch> for flumotion...
[20:05]  * ajmitch wonders how he can phrase the FFe :)
[20:07] <vorian> slight mod?  :)
[20:08] <ajmitch> vorian: new version apparantly is needed to work with python 2.7, so I may be able to bribe someone
[20:08] <vorian> i hear beer works very well
[20:09] <ajmitch> that's what I'm afraid of
[20:11] <Ramiel> thanks all
[20:55] <ajmitch> micahg: did you want me to upload the openclipart debdiff, given that I never restarted the test build? :)
[20:56] <micahg> ajmitch: I did and it finished, I added the bug, I just never finished checking if it needed an FFe :)
[20:57] <ajmitch> micahg: given that the source is there for 2.0, the only options would be revert to the old version or fix it?
[20:58] <micahg> ajmitch: ok, I"ll just upload then :), can wave the need for FFe later if need be
[20:58] <ajmitch> don't base it just on my arguments ;)
[20:58] <ajmitch> for me it was just a nice-to-have
[20:59]  * ajmitch just doesn't like seeing packages uploaded that FTBFS, it gets confusing for people grabbing the source
[20:59] <micahg> yeah, it's a nightmare package to begin with as well (at least there's a bug filed and tagged appropriately)
[21:00] <ajmitch> I think I need a laptop with 16GB of RAM like you have
[21:00] <ajmitch> some of those images took awhile to process
[21:03] <micahg> ajmitch: Build needed 08:31:38, 5523908k disc space
[21:03] <ajmitch> hopefully the buildds are quiet
[21:04] <hakermania> Do i have chances to have a backport in ubuntu 12.04?
[21:05] <micahg> hakermania: I'm not sure if -backports is open yet
[21:05] <micahg> hakermania: wallch should be backportable, sure
[21:05] <hakermania> micahg, why wallch, specifically?
[21:06] <micahg> hakermania: oh, I thought that's what you were going to ask about ;)
[21:06] <hakermania> micahg, yes that's what I'm asking about, but initially you was like 'nah, backports are off for now', but then you were 'Wallch should be fine' :P
[21:07] <hakermania> was/were
[21:07] <micahg> hakermania: we discussed opening backports early, not sure if that ever happened
[21:08] <ajmitch> it required an LP change iirc
[21:10] <hakermania> micahg, do I need any special process or what's mentioned here is enough -> https://help.ubuntu.com/community/UbuntuBackports?
[21:11] <hakermania> meant https://wiki.ubuntu.com/UbuntuBackports
[21:11] <micahg> hakermania: that's fine, but 12.04 backports isn't open yet AFAIK
[21:12] <hakermania> micahg, not yet? But I was told to do so prior to beta 2, which comes in 6-7 days
[21:13] <micahg> hakermania: if you're updating the package in 12.04, you'll need a freeze exception at this point as backports isn't open or wait until Q and backport from there
[21:49] <hakermania> micahg, i'm not an expert or something :P What's 'Q'? I understood FFe though :P
[21:51] <micahg> hakermania: the letter after P, an entity in the Star Trek universe, a placeholder for the next Ubuntu release
[21:52] <micahg> *next release after precise
[21:52] <hakermania> micahg, nice one :P But I want it IN precise :O FFe?
[21:56] <hakermania> Afterall, untill Q wallch will have many changes
[22:09] <hakermania> micahg, !
[22:18] <micahg> !ffe| hakermania
[22:19] <hakermania> micahg, I know what it is, the only way to get it in precise is FFe. I just need you to tell me that I'm right B-)
[22:19] <micahg> hakermania: well, -backports is part of precise and enabled by default
[22:20] <micahg> just with a lower pinning so they're not selected by default
[22:21] <hakermania> micahg, so, you mean that a new version of Wallch can be make it in Precise while Precise is out? Through Update manager or something? What do you suggest?
[22:24] <micahg> hakermania: the user has to explicitly choose to upgrade to the version in backports
[22:24] <hakermania> micahg, i see. How can I update the version of wallch on usc?
[22:30] <micahg> hakermania: your choices are FFe or backport (needs to wait until it opens for P or until it gets uploaded to Q)
[22:33] <hakermania> micahg, both of the choices will result in new version of wallch in usc?
[22:34]  * micahg isn't sure how backports in USC works
[22:36]  * hakermania doesn't know what to do
[22:36] <micahg> FFe will upgrade everyone, backport will make it available for everyone, just not sure how that's displayed in USC
[22:38] <hakermania> Oh, then I'll go with a FFe, definitely
[22:53] <hakermania> micahg, many thanks, bye