/srv/irclogs.ubuntu.com/2012/09/30/#ubuntu-bugs.txt

xnoxLogan_: yeah, unlike debian we don't auto-close bugs because (i) this package is still in previous releases (ii) the package might be reintroduced later (iii) it's actually useful information01:36
Logan_xnox: kk02:11
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
maprerihelp12:31
mapreriSorry i used /amsg by mistake12:33
om26erHi! could anyone on Quantal with nvidia binary driver please see if bug 1058391 is happening13:39
ubot2Launchpad bug 1058391 in unity "[nvidia] Desktop rolls over vertically when i open the dash or hud" [Critical,New] https://launchpad.net/bugs/105839113:39
abuchbinderHi! I'm trying to backport a patch into Lucid--it's an isolated bug, simple patch, comes with a test suite, and fixes a loses-user-data bug. Good candidate for SRU, I think.14:23
abuchbinderThe bug is here: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/105908514:23
ubot2Launchpad bug 1059085 in vim "recovery silently deletes data in large files." [Undecided,New]14:24
abuchbinderAh, convenient. So, if anyone's around--what's the next step here? Do I format a debdiff? Make a bzr branch? If this were Debian, I'd send in a debdiff, but Ubuntu seems to have changed processes at some point. What do I do next for an SRU?14:24
penguin42abuchbinder: https://wiki.edubuntu.org/StableReleaseUpdates14:26
penguin42abuchbinder: https://wiki.ubuntu.com/StableReleaseUpdates  (that's the same I think, but from the ubuntu.com )14:28
abuchbinderRight; I've got that, but how do I format the actual patch?14:28
penguin42abuchbinder: I've not done SRUs, but debdiffs seem OK, but if you can do a bzr branch they seem happier14:29
penguin42oh that page doesn't have that on does it14:30
penguin42abuchbinder: http://developer.ubuntu.com/packaging/html/fixing-a-bug.html14:31
=== emma is now known as em
abuchbinderSo, I want to do an SRU, and I made a branch here: http://bazaar.launchpad.net/~adam-buchbinder/ubuntu/lucid/vim/vim-large-file-recovery/revision/5814:59
abuchbinderErr, here: https://code.launchpad.net/~adam-buchbinder/ubuntu/lucid/vim/vim-large-file-recovery14:59
abuchbinderI filed a bug here: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/105908515:00
ubot2Launchpad bug 1059085 in vim "recovery silently deletes data in large files." [High,Triaged]15:00
penguin42abuchbinder: Did you see my http://developer.ubuntu.com/packaging/html/fixing-a-bug.html post before you dropped off before?15:00
abuchbinderAh, missed it. Thanks!15:02
penguin42abuchbinder: I think it might be worth editing the bug description to note that precise and quantal already have versions new enough15:04
=== Jikan is now known as Jikai
abuchbinderI made a branch and linked it to the bug. So now I run pbuilder to test it, and then run 'bzr lp-propose' to propose merging. There's no extra steps because it's an SRU?15:04
penguin42abuchbinder: I've not done SRUs, just non-SRU fixes15:06
abuchbinder(Edited to specify Lucid in the bug report.)15:08
penguin42abuchbinder: I'd give it a few days and see if anyone responds to your bug and then if you don't get a response see if you can find someone to prod15:08
TJ-abuchbinder: the main thing with SRUs is the patch should usually be in the development release already, and/or upstream. It can vary, though.15:11
penguin42TJ-: Looking at packages.u.c precise and quantal have vim versions after the one referenced in teh bug15:13
TJ-penguin42: We usually check to see if upstream has fixed the issue. If so, we try to backport the same patch with minor fixups if necessary. If the code-base has changed too drastically then a stand-alone patch is acceptable.15:15
=== yofel_ is now known as yofel
abuchbinderTJ: Yeah; that's what I did.15:37
abuchbinderSee: https://code.launchpad.net/~adam-buchbinder/ubuntu/lucid/vim/vim-large-file-recovery/+merge/12716115:37
abuchbinderPlease let me know if this is reasonable, or if I should be doing something else process-wise.15:37
TJ-abuchbinder: You'll be good to go, then :)15:39
abuchbinderThanks, everyone! I'll be back to nudge people if the patch doesn't get looked at in a few days.15:42
=== jbicha is now known as Guest28143
=== Guest28143 is now known as jbicha_
=== jbicha__ is now known as jbicha
=== glebihan_ is now known as glebihan

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!