| === Hurtz_ is now known as Hurtz | |
| [08:11] <j_f-f> Moin. Please set the Importance of Bug #1315762 to Wishlist | |
| [08:57] <igorssh> when i plug in my phone on android, i'm getting Unable to mount SAMSUNG_Android Unable to open MTP device '[usb:005,002]' | |
| [08:57] <igorssh> shat could be wrong? | |
| [09:26] <j_f-f> igorssh: You must first -> Setup-> More Setup-> USB connection->Connect memory with pc | |
| [09:27] <j_f-f> Please set the Importance of Bug #1315776 to Wishlist | |
| [09:37] <igorssh> j_f-f: where do i find this setup? | |
| [10:39] <sdfsd> Hi, I have a feeling that this is a bug in Ubuntu 14. Could anyone help me out. Thanks a lot | |
| [10:39] <sdfsd> http://askubuntu.com/questions/459654/ubuntu-14-04-drivers-for-broadcom-bcm43142 | |
| [11:15] <sdsdf> Hi could anyone help me with this ? askubuntu.com/questions/459654/ubuntu-14-04-drivers-for-broadcom-bcm43142 ? I am desparately stuck with this for the past 1 week. Please ? | |
| [13:09] <sdsdf> What is meant by an Exec Format Error ? | |
| [13:11] <penguin42> what gave you that? | |
| [17:07] <hggdh> /bans | |
| [17:08] <tsimpson> !test | |
| [17:08] <ubot5> Testing... Testing... 1. 2.. 3... ( by the way, remember that you can use /join #test ) | |
| [21:11] <amigamagic> hi, is this the right channel to report a package with a bug fixed in svn but not updated yet in ubuntu repositories? | |
| [21:26] <amigamagic> please, could someone triage this bug: http://bugzilla.abisource.com/show_bug.cgi?id=13596 ? | |
| [21:26] <ubot5> bugzilla.abisource.com bug 13596 in Editing - Key/Click Bindings "Shift-control text selection no longer works" [Normal,Resolved: fixed] | |
| [21:26] <teward> amigamagic: is there an ubuntu bug for it | |
| [21:27] <teward> rather than an upstream bug | |
| [21:27] <teward> (and by "upstream" we mean at the bug tracker of the actual program/project) | |
| [21:28] <amigamagic> teward, "is there an ubuntu bug for it" was a question? | |
| [21:28] <teward> correct | |
| [21:28] <teward> if the answer is no then there's nothing for us to triage | |
| [21:29] <amigamagic> ok, now I understand what you mean | |
| [21:29] <teward> amigamagic: for us to "triage" a bug, the bug must: (a) exist and be filed against launchpad. (b) be confirmed either by the triager or multiple other people. (c) be ready for a developer in Ubuntu (for packages in Main), or be ready for the community (in Universe) to work on it. | |
| [21:30] <teward> really (a) and (c) are the most critical | |
| [21:30] <teward> b is interesting, because I get bugs on my radar which aren't marked 'confirmed' but i eventually test and confirm it exists | |
| [21:30] <teward> given that someone's stated steps to reproduce the bug | |
| [21:30] <teward> (aka a 'test case') | |
| [21:33] <amigamagic> it's a very annoying (to me, at least) bug for the program abiword, and it has been fixed from february on the upstream. The steps to reproduce it are very simple: the CTRL-SHIFT-CURSOR_KEY to select text doesn't work anymore in the current version in ubuntu repositories. It worked in previous versions. | |
| [21:34] <teward> amigamagic: you'll have to follow the Stable Release Update procedures that rbasak linked you | |
| [21:34] <amigamagic> if you want, I could create the bug report on launchpad | |
| [21:34] <teward> but without a bug filed on this on Launchpad, there's nothing to apply to the SRU | |
| [21:34] <teward> yes, you should do that, if you want an SRU to fix these kinds of things | |
| [21:34] <teward> amigamagic: which version of Ubuntu is affected by this | |
| [21:35] <amigamagic> 14.04 | |
| [21:35] <teward> !info abiword trusty | |
| [21:35] <teward> boo | |
| [21:35] <ubot5> abiword (source: abiword): efficient, featureful word processor with collaboration. In component universe, is optional. Version 3.0.0-4ubuntu1 (trusty), package size 1098 kB, installed size 4269 kB | |
| [21:35] <teward> laggy you are | |
| [21:35] <amigamagic> exactly that | |
| [21:35] <teward> oooo it's in universe | |
| [21:36] <teward> you can file a bug report but ultimately it's up to the community to prepare debdiffs/patches for it | |
| [21:36] <teward> (meaning that even if the bug is "triaged" it'll be "fixed soon (tm)" | |
| [21:36] <teward> but there's no timeline for fixing, really) | |
| [21:37] <amigamagic> but the bug is already fixed from more than 2 months in the svn of the original package mantainer | |
| [21:37] <amigamagic> and there is a patch fix in that bug report too | |
| [21:37] <teward> but where is the original package maintainer, in Debian? | |
| [21:37] <teward> mainly the point stands that in Ubuntu someone in the community has to do the bug triage, and create the debdiff and such, and while I could, i'm in the middle of working on nginx | |
| [21:38] <teward> (it'd still need sponsored to get uploaded to the repos though) | |
| [21:38] <teward> note to self: 50 Ubuntu VMs is confusing, keep only a few. | |
| [21:38] * teward grumbles | |
| [21:38] <brainwash> I can prepare the branch (already did for 3.0.0-4ubuntu1) | |
| [21:39] <brainwash> we had to include patches from stable to fix 2 major issues | |
| [21:39] <teward> less work for me ^.^ | |
| [21:39] * teward goes back to stabbing nginx's build rules | |
| [21:40] <amigamagic> hi brainwash | |
| [21:40] <brainwash> hey amigamagic | |
| [21:40] <brainwash> but it's "only" abiword after all, not many people care about it anymore | |
| [21:40] <brainwash> especially since ubuntu always ships a somewhat broken version of it :) | |
| [21:41] <amigamagic> yes brainwash I know. I think I should uninstall it after all. | |
| [21:41] <amigamagic> Being that I was on a virtual machine, I wanted to waste less space for a word processing program. | |
| [21:41] <brainwash> but we can fix this issue, just need the launchpad report to get started | |
| [21:42] <amigamagic> ok I will file that | |
| [21:42] <teward> brainwash: if you don't have bugcontrol i can mark it triaged, so long as there's enough details for it to be worked on by someone :) | |
| [21:42] <teward> otherwise enjoy | |
| [21:42] <brainwash> for 14.10 I expect that a new stable release will be ready | |
| [21:43] <brainwash> no bugcontrol yet, despite having over 3500 karma from bug report activities :D | |
| [21:43] <teward> lol | |
| [21:43] <teward> you'd have to apply for bugcontrol status | |
| [21:44] <brainwash> I know | |
| [21:44] <teward> i have bugcontrol status, i'll set it triaged for ya :) | |
| [21:44] <teward> i have to go stab a few other bugs anyways | |
| [21:44] <amigamagic> is this the page where I should file the report? https://launchpad.net/abiword | |
| [21:44] <brainwash> but I usually bother other people to triage reports or change the status | |
| [21:44] <teward> amigamagic: if you have a 14.04 box it's easier to do `ubuntu-bug abiword` | |
| [21:44] <teward> from the command line or the dash | |
| [21:44] <brainwash> which is rarely the case | |
| [21:44] <teward> rather than file it manually by hand | |
| [21:45] <teward> brainwash: yeah, for 'nginx' it's usually "Check with teward, he is usually watching" | |
| [21:45] <teward> but before that i just bothered here :) | |
| [21:45] <amigamagic> teward, I'm on a xubuntu vm... it's the same thing? | |
| [21:45] <teward> amigamagic: yeah, as long as it's xubuntu 14.04 | |
| [21:45] <amigamagic> yes | |
| [21:56] <amigamagic> https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1315949 | |
| [21:56] <ubot5> Ubuntu bug 1315949 in abiword (Ubuntu) "SHIFT-CTRL-CURSOR_KEY combos don't work anymore to select text" [Undecided,New] | |
| [22:00] <teward> that patch needs DEP3 tags | |
| [22:00] * teward downloads and modifies accordingly | |
| [22:02] <teward> FYI the patch doesn't apply cleanly | |
| [22:02] <teward> it may need tweaked | |
| [22:11] <amigamagic> I will check if it's applied in that way in the svn main commit | |
| [22:12] <teward> it's probably got something to do with quilt | |
| [22:12] <teward> but i'm pretty sure brainwash is familiar with these things | |
| [22:18] <amigamagic> abiword devs have applied that patch to their stable branch: http://svn.abisource.com/abiword/branches/ABI-3-0-0-STABLE/src/af/ev/gtk/ev_UnixKeyboard.cpp | |
| [22:19] <teward> amigamagic: i meant that the patch itself doesn't cleanly apply to Quilt | |
| [22:19] <teward> s/to Quilt/via Quilt/ | |
| [22:19] <teward> which is the tool for debian package patch management | |
| [22:19] <teward> i can manually create the patch if i have to and then still quote Origin | |
| [22:19] <teward> but meh | |
| [22:20] * teward has other things to do | |
| [22:20] <amigamagic> ah sorry, I don't know that tool | |
| [22:23] <teward> no probledm | |
| [22:23] * teward is bored and is already making the patch :P | |
| [22:25] <amigamagic> teward, thanks :) | |
| [23:25] <amigamagic> what's a cherry-pick ? | |
| [23:27] <jtaylor> selecting a patch from a branch to apply to an older version | |
| [23:27] <jtaylor> typically backporting bugfixes from newer versions/development version to older versions | |
| [23:33] <teward> ^ | |
| [23:33] <teward> jtaylor: -4ubuntu1 becomes what with a typical sru, -4ubuntu2 or -4ubuntu1.1 ? | |
| [23:33] <teward> the security team version document says .1 | |
| [23:33] <jtaylor> 1.1 | |
| [23:33] <teward> okay, that's what i thought | |
| [23:33] <jtaylor> it depends on the versions in newer releases | |
| [23:33] <teward> I've screwed that up twice before though | |
| [23:34] <teward> jtaylor: what about abiword | |
| [23:34] <jtaylor> it can also be 1.12.04.1 | |
| [23:34] <teward> which is what i'm asking about (because amigamagic's bug) | |
| [23:34] <jtaylor> for precise | |
| [23:34] <teward> it's -4ubuntu1 in Trusty | |
| [23:34] <jtaylor> -4ubuntu1.1 is ok there | |
| [23:35] <jtaylor> a more qualified version would be required if utopic were released already | |
| [23:35] <teward> but it's not :) | |
| [23:35] <jtaylor> as trusty and utopic have the same version | |
| [23:35] <jtaylor> as utopic is devel its next ersion will be ubuntu2 so 1.1 is ok | |
| [23:38] <teward> right | |
| [23:39] <teward> or it may have an even higher version if it's updated in Debian before release, right, jtaylor? | |
| [23:39] <teward> amigamagic: also, unrelated FYI to what jtaylor and I are discussing, debdiff uploaded for consideration. :P (bzr still doesn't want to work right for me) | |
| [23:40] <jtaylor> yes debian always updates the first number | |
| [23:40] <jtaylor> -2 in this case | |
| [23:41] <teward> brainwash: in the off chance you're still around, there's a debdiff attached to that bug | |
| [23:41] * teward yawns | |
| [23:42] <teward> i gotta stop stabbing nginx source code, it's giving me a headache | |
| [23:45] <amigamagic> thanks for the info guys... What's a debdiff? | |
| [23:45] <amigamagic> a diff to apply to a deb package? | |
| [23:45] <teward> amigamagic: it's basically a diff for a deb package | |
| [23:45] <teward> amigamagic: FYI, you need to fill out the SRU template. https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template | |
| [23:46] <teward> and put it in the description | |
| [23:46] <teward> well, someone does | |
| [23:46] * teward won't :P | |
| [23:47] <amigamagic> you mean on the description of the bug on launchpad? | |
| [23:48] <teward> correct | |
| [23:49] <teward> impact of the bug, a test case for reproduction, potential of regression, and other info | |
| [23:49] <amigamagic> ok I will try... | |
| [23:49] <teward> if you're unsure of the regression potential we can poke around and guesstimate, but judging as this is an upstream patch, it's probably got very low regression potential | |
| [23:50] <teward> s/judging as/judging on the fact that/ | |
| [23:50] <amigamagic> I agree | |
| [23:52] <teward> (note: it's not normal for me to venture outside of the nginx package when it comes to debdiffs. But i was bored :P) | |
| [23:53] <teward> jtaylor: what's the consideration for -4ubuntu1.1 vs. -4ubuntu2 or something? whether the version bump, even a small one, will conflict with $nextrelease ? | |
| [23:53] <teward> (where $nextrelease is whatever the next subsequent release is in the series of Ubuntu releases) | |
| [23:55] <jtaylor> you always need an upgrade path to the next release | |
| [23:55] <jtaylor> so the version in the next release must be higher | |