psusiso the usplash package has 239 open bugs.  It can no longer even be installed in Ubuntu because plymouth conflicts with it, and is required.  Shouldn't usplash then be dropped, and all bugs invalidated?00:21
micahgpsusi: that's a devel decision, not a bugsquad decision00:21
espen77how do i make a patch for a source package?00:22
psusiwhich part is?  dropping it, or invalidating the bugs of a dropped package?00:22
micahgpsusi: dropping it00:22
psusiok.. so I should file a bug requesting that it be dropped, and if/when it is, then invalidate the bugs?00:22
espen77i already aptget source and fixed code00:23
micahgespen77: here's the process for getting a patch in Ubuntu: https://wiki.ubuntu.com/SponsorshipProcess00:23
espen77micahg: thanx00:23
micahgespen77: thank you for your pending contribution :)00:24
micahgpsusi: yes, you can file a bug and subscribe ubuntu-sponsors to it00:24
psusimicahg, since it's a drop request, shouldn't it be ubuntu-archive instead?  or it needs sponsored first, then to archive?00:25
micahgpsusi: a MOTU needs to ACK it00:25
psusimicahg, roger00:25
espen77isnt there a command to make a diff between .orig.tar.gz and unpacked directory?00:29
micahgespen77: care to hop in #ubuntu-motu to continue this?00:29
espen77oki, ty00:30
psusiwhen using the email interface to lp to change status or assignee, how do you specify which target you are talking about?00:37
kklimondait may not be possible to do that, but ask on #launchpad :)00:38
kklimonda(the email interface could use some love)00:38
micahgpsusi: https://help.launchpad.net/Bugs/EmailInterface00:40
psusimicahg, that's what I've been reading00:43
=== AndrewMC is now known as SpockVulcan
=== SpockVulcan is now known as AndrewMC
micahgpsusi: you shouldn't just close all bugs against a package, they have to be evaluated if any qualify for an SRU04:19
psusimicahg, the package is dead.04:20
micahgpsusi: that's irrelevant, we still have it in supported versions of Ubuntu04:20
psusimicahg, none of them will be fixed... the functionality the package provided was moved into the kernel years ago04:21
psusithe bugs were a mix of filed against wrong package, and should have been expired04:22
psusimostly the latter04:22
micahgpsusi: unless you've read all the bugs, you cannot know that, it's a community supported package in karmic on and in hardy it's in main which means it's canonical supported for another 2 months04:22
micahgpsusi: filed against the wrong package means it needs to be triaged, not closed04:22
psusiI tried closing them out with a nice message explaining that and asking if any issues still persist, a new bug should be filed against linux instead, but slangasek said I should at least get the package removed from the archive first and reopened them.  I've since gotten it dropped from the archive and asked him if it was ok to close all the bugs now and he said yes04:23
micahgpsusi: well, that's generally not how most bugs are handled, generally the only teams that do mass bug closure are the X and kernel teams04:29
micahgand even then, they'll just expire the bugs04:29
psusimicahg, my understanding is that a bug that does not apply to the current release should be closed, unless an SRU is warranted, in which case, a task against the old release should be opened... in this case, such tasks had not been opened, so no SRU was going to be done, so I closed out the tasks against the development release, since they do not apply since the package does not exist there04:31
micahgpsusi: in this case, my guess is most of them weren't triaged, hence an SRU task couldn't be opened since no one new about it04:31
psusiprobably because most of the bugs were unusable/junk ;)04:32
micahgClosing the task in the development release is fine if it's been triaged to the point where it's not an SRUable bug04:32
micahgmost likely because most packages in universe don't have people watching after them04:33
psusialso if it hasn't managed to get triaged to the point where that can be determined within the 3 years since it was filed, I think04:33
micahgpsusi: we don't close bugs because they're old, we can't fault the reporters for our lack of resources04:33
psusia bug report that was filed long ago, and has never been duplicated/confirmed, and whose original reporter has wondered off and no longer applies to current releases does no good to keep open.. we don't fault reporters for lack of resources, but we don't need to keep open bugs that will never be fixed either04:34
micahgpsusi: well, that's the question, is it SRUable or not, that's the only question to ask when reviewing those bugs, if not, close, if yes, triage fully04:35
psusiindeed... I tried to make such determinations last time I reviewed the bugs for that package a few months back... and tried to encorage the reporters to provdide more info to help finish triaging if possible... since that never panned out with any of them, it seems that now the correct thing to do is close them04:37
psusiif someone ever speaks up saying it is still an issue on an old but supported release, I can then figure out of it warrants an SRU or not04:38
psusiand if it does, open a task in that release04:40
micahgpsusi: if you evaluated them before, that's fine04:41
psusimicahg, yea, I supose if I hand't evaluated them indivually before, then I would have set them to incomplete instead of invalid, adn let them either expire on their own, or evalute the responses04:42
micahgpsusi: well, if you hadn't evaluated, mass incomplete is generally frowned upon as well except for the X and kernel teams04:43
psusimicahg, well, what else do you do with bugs against packages that don't exist any longer?  they certainly shouldn't remain valid against the development release04:44
micahgpsusi: triage :)04:44
psusimicahg, nothing to triage against when the package no longer exists04:44
lifelessmicahg: a bug on a gone package is invalid :)04:45
micahglifeless: not if it's SRUable which what I was saying before04:45
ScottKlifeless: If it's in a supported release still I'd suggest wontfix.04:45
lifelessScottK: fair point04:45
micahgpsusi: in most of these cases, there aren't many bugs04:45
psusilifeless, against the development release... it could still be valid against an older release, bug needs a task for that04:45
psusiand yes, likely would get set to wontfix in old release if removed from development04:46
micahgScottK: weren't you the one who warned me against using won't fix unless I was sure?04:46
ScottKI don't think so.04:46
psusithe usplash package has 240 bugs in lp atm... going to get that purged next ;)04:46
micahgpsusi: that's a different beast04:47
psusimicahg, how so?04:47
lifelesspsusi: I think ScottK's point was wontfix in trunk04:49
lifelesspsusi: and a task against older release could be $whatever-is-appropriate04:49
micahgpsusi: it was a core part of Ubuntu, also is it just in natty it can't be used?04:49
ScottKYes.  wontfix in trunk and just open a task against a release if you intend to SRU there.04:50
psusiScottK, if trunk no longer exists?04:50
ScottKpsusi: In that case trunk is a shorthand for "all supported releases".04:50
psusimicahg, package has been obsolete for years, has been dropped from the archive in natty04:51
psusiScottK, I thought trunk always meant development release, and if it was different for previous supported releases, you opened a separate task to track there?04:51
ScottKpsusi: Ubuntu bugs don't say they are against trunk, just that they are against "ubuntu"04:52
ScottKIn theory, perhaps, but if the status is the same for all releases (not going to fix anything) it's a waste of effort and bombarding people's inboxes to try and do per release tasts.04:52
psusiScottK, it can just say ubuntu, or it can say ubuntu(release)... my understanding is that just ubuntu meant development04:52
ScottKpsusi: It does, but how important is it really in a case where no SRU is intended?04:53
psusiScottK, right... which is why you don't bother opening a task against the previous release and just set the trunk to invalid04:53
ScottKI think it's more important to work on fixing stuff than getting the state of the bug database exactly right.04:53
ScottKI've got better things to invest my time in than the merits of invalid/wontfix.04:54
psusiin other words, it is no longer valid in the trunk because the package has been removed, so that status becomes invalid.  If it is valid in a stable release, then a task should be opened for that and it should be fixed, or set to wontfix ( though if yuo know that, why bother opening the task )04:55
micahgpsusi: yep, that sounds good04:56
psusiso I guess next time, I should batch invalidate only New bugs, and any that are confirmed/triaged, should take a look at and get a task opened in the supported release, even if it is set to wontfix04:58
psusior better yet, incomplete rather than invalid05:00
micahgpsusi: no, it's not worth going to incomplete, unless you think it's SRUable, and New bugs might have all the information necessary, the bugs should just be gone through to see if they meet the SRU criteria or not, the devel task should be invalid if the package is not in the archive, if you think it's SRUable, you can ask for a task to be opened and set that to incomplete if there's not enough info05:02
=== tarun is now known as Guest86968
=== Guest86968 is now known as c2tarun
penalvchPlease mark Medium Importance for libreoffice bug 50518806:50
ubot4Launchpad bug 505188 in openoffice.org (Ubuntu) (and 2 other projects) "Impress mis-rotates text saving to .pptx (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/50518806:50
game2bug 662605 seems to have had a relapse, can someone here reset the status?10:50
ubot4Launchpad bug 662605 in unity (Ubuntu) (and 1 other project) "dash - wrong count of remaining items to see (affects: 2) (heat: 12)" [Low,Fix released] https://launchpad.net/bugs/66260510:50
=== zyga is now known as zyga-food
dholbachhttps://wiki.ubuntu.com/UbuntuDeveloperWeek Day 3 starting in 25 minutes in #ubuntu-classroom15:36
=== zyga-food is now known as zyga
bdmurraypatrickmw: do you still have bug 727410 set up?16:09
ubot4Launchpad bug 727410 in gnome-session (Ubuntu Natty) (and 1 other project) "desktop UI does not load after logging as a fuse user via ltsp (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/72741016:09
patrickmwbdmurray: yes I do16:12
bdmurraypatrickmw: maybe look at ~/.xsesssion-errors ?16:13
bdmurraypatrickmw: also do you have a chance to choose your desktop environment? classic coke or new coke?16:14
patrickmwbdmurray: yes, let me try16:15
bcurtiswxclassic or new coke... nice16:15
patrickmwbdmurray: hey hey, classic FTW16:17
bdmurraypatrickmw: so note that and add the output of '/usr/lib/nux/unity_support_test -p'16:19
patrickmwbdmurray, will do, thanks!16:19
bdmurraypatrickmw: actually it might just be a unity not start bug and unrelated to ltsp16:19
CarlFKI am trying to track down a bug report from over a year ago. bug is: "firewire express card not recognized when plugged in" (same for esata ec too)16:40
CarlFKI think it got fixed in jaunty, it is broken in maverick and natty16:40
CarlFKanyone know what package? would have been bugged?16:41
bdmurraypatrickmw: have you used this test case before?16:50
bdmurrayCarlFK: probably linux (the kernel)16:51
CarlFKbdmurray: I thought there was an "hp" (for hot plug) in the name16:51
CarlFK "pciehp.pciehp_force=1"  yay!16:54
CarlFKbdmurray: thanks heaps16:54
nigelbbdmurray: hey, we have a session the day after tomorrow :)16:54
CarlFKpciehp is what I was trying to remember16:54
nigelbbdmurray: I'll probably prepare it some time tomorrow.  If you could take a look and help me with questions on friday, that'd be great :)16:55
bdmurrayCarlFK: I don't see that in linux-source-2.6.38/Documentation/kernel-parameters.txt fwiw16:55
CarlFKbdmurray: grumble.16:55
bdmurraynigelb: of course also if you want me to review what you have I'm happy to do that16:55
nigelbbdmurray: I don't have anything yet.  Will write tomorrow daytime :)16:56
nigelbI'll probably just look at your old sessions which I used as starting points when I was writing a session16:56
bdmurraynigelb: another new launchpad feature worth mentioning would be the package bug reporting guidelines16:57
nigelbbdmurray: okay16:57
bdmurraynigelb: if you goto staging.bugs.launchpad.net/ubuntu/+source/xserver-xorg/+filebug and file a bug you'd see a good example16:58
* nigelb does that16:59
nigelbbdmurray: is staging down?16:59
bdmurraynigelb: that works https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug17:00
bdmurrayyou don't actually need to file it to see them17:00
nigelboh, wow17:01
nigelbNeat feature17:01
bdmurrayactually ubiquity is a better example17:01
bdmurraythere is also a bug reported acknowledgement which appears after the bug report is filed17:03
bdmurraywhich is another way to convey information17:03
nigelbhrm :)17:03
patrickmwbdmurray: which test case?17:05
bdmurraypatrickmw: ltsp and logging into a unity session17:05
patrickmwbdmurray: by used do you mean "successfully logged in"?17:06
bdmurraypatrickmw: yes, have you ever logged in before and had unity running as an ltsp client?17:07
patrickmwbdmurray: not with unity17:07
bdmurraypatrickmw: but unity runs in virtualbox fine?17:07
patrickmwbdmurray: you gave me an idea for something to try17:09
patrickmwbdmurray: standby :)17:09
patrickmwbdmurray: I installed the vbox guest additions to see if that would change anything.  It did not.17:13
bdmurraystgraber: do you think unity should work on an ltsp client?17:14
charlie-tcaReminder: QA meeting at 18:00 UTC in #ubuntu-quality17:39
njinHello, can someone set bug 726008 to medium for me, thanks17:55
ubot4Launchpad bug 726008 in aptdaemon (Ubuntu) "<type 'exceptions.TypeError'>: enable_distro_comp() got multiple values for keyword argument 'component' (affects: 3) (dups: 2) (heat: 1766)" [Undecided,Confirmed] https://launchpad.net/bugs/72600817:55
stgraberbdmurray: nope, ltsp should use a classic gnome desktop, I thought didrocks fixed that17:58
stgraberbdmurray: with some specific hardware it "should" work (like full-intel hardware)17:59
bdmurraystgraber: okay, thanks for the help!18:00
camelinahatI'm a little confused.. I'm new to BugSquad and looking at the mentorship program. I can't see to figure out how to edit my Ubuntu-WikiPage (Or what should be on it once I have)18:07
=== zyga is now known as zyga-afk
camelinahatIs there anyone about who is comfortable with the ubuntu wiki able to assist me? I'm also getting weird errors when trying to update UserPreferences (e-mail is already in use)18:28
yofelcamelinahat: for the wiki just go to the page that you want to be your new wiki page and click on the link to create it18:32
camelinahatyofel: I notice when I login it uses my launchpad.net userID should I use that as my wiki page or a more accurate WikiName?18:33
yofelI used my real name, but there's no rule on that, some people used their ID too18:34
camelinahatAny thoughts on why when I update my UserPreferences I'm getting an error that my e-mail address is already in use? (At no point do I even see an option for e-mail address)18:34
yofelwhat user preferences, the wiki ones?18:35
charlie-tcasince everything is tied to OpenID, it will use whatever email address you gave launchpad18:35
camelinahatcharlie-tca: But the Launchpad one has no problem with my e-mail (no warnings/alerts that it's duplicated/already in use) only on the Wiki18:36
yofelcamelinahat: just where do you try to set that? I can't find it in my wiki preferences18:37
camelinahatyofel: I added a Quick Link, (changed no other options), hit "save" and receive an alert near the top that says "This email already belongs to somebody else. Clear message"18:38
yofelah, I have no quick links set18:39
=== zyga-afk is now known as zyga
penalvchRegarding bug 618024 the OP upgraded to Maverick OOo which fixed the problem, and it's fixed in LibreOffice PPA & Natty. This looks like Fixed Released w/ not SRU or Backportable response. What do you think?19:31
ubot4Launchpad bug 618024 in openoffice.org (Ubuntu) (and 1 other project) "[(U)OOo 3.2.1 Generated PDF-Files cannot be printed with Adobe Reader (affects: 1) (heat: 10)" [Undecided,Incomplete] https://launchpad.net/bugs/61802419:31
CarlFKhttp://dpaste.de/OeMm/  [ 2400.930093] Call Trace:[ 2400.930101]  [<ffffffff815befad>] schedule_timeout+0x26d/0x2e019:38
CarlFKim bugging it - anyone want me to do anything before i reboot?19:40
charlie-tcaright channel?19:40
charlie-tcaIs it a bug that is filed?19:40
CarlFKcharlie-tca: not yet... looking for the cli tool19:42
CarlFK"No pending crash reports."19:43
charlie-tcathere is always https://help.ubuntu.com/community/ReportingBugs#Filing%20bugs%20at%20Launchpad.net19:44
charlie-tcafile without apport19:44
=== ogra is now known as Guest42737
=== Guest42737 is now known as ogra_
AndrewGeeHi. I believe bug 728051 should be changed to wishlist importance. I have forwarded the bug upstream.21:41
ubot4Launchpad bug 728051 in quodlibet (Ubuntu) (and 1 other project) "Relocate files according to metadata (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/72805121:41
CarlFKbug 728033 -22:04
ubot4Launchpad bug 728033 in linux (Ubuntu) "firewire - "blocked for more than 120 seconds" (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/72803322:04
CarlFKwhats the markup to make a ref to another bug?  #371434 didn't work.22:04
yofelliterally 'bug 371434'22:05
ubot4Launchpad bug 371434 in linux (Ubuntu) "PCI ExpressCard hotplug requires pciehp.pciehp_force=1 (affects: 16) (dups: 3) (heat: 101)" [Undecided,Confirmed] https://launchpad.net/bugs/37143422:05
yofel# does nothing22:05
CarlFKnatty install, pretty sure this is under 24 hours old: Mar  2 16:12:29 dhcp45 gnome-session[1543]: WARNING: Could not launch application 'libcanberra-login-sound.desktop': Unable to start application: Failed to execute child process "/usr/bin/canberra-gtk-play" (No such file or directory)22:17
CarlFKwhat package should I bug?22:18
micahgCarlFK: dpkg -S libcanberra-login-sound.desktop22:18
seb128CarlFK, it's a known bug22:18
seb128check the libcanberra open bugs if you want it22:19
CarlFKseb128: more thanks.  i'll ignore it then.22:19
CarlFKThis preeseed line no longer works: d-i apt-setup/local1/repository string http://ppa.launchpad.net/carlfk/ppa/ubuntu natty main22:36
CarlFKknown?  what do I bug?  did I stuff something up?22:36
CarlFKlocal0 line didn't get included either (only 2 I had in preeseed fiile)22:37
javahornhttp://www.voria.org/forum/viewtopic.php?p=4409 -- this issue i am facing, what is the way out?22:49
charlie-tcajavahorn: usually, you will get better responses to support in #ubuntu23:24
javahorncharlie-tca: they directed here!23:25
javahornany idea for bug?23:25
charlie-tcaIs there a bug filed?23:25
charlie-tcathat is not an Ubuntu bug report23:26
charlie-tcafile a bug using "ubuntu-bug linux" in a terminal, explain what is wrong, and let the developers see if they can fix it.23:26
javahorncharlie-tca: i am lost23:28
charlie-tcaUbuntu developers will not work on fixing something from a forum somewhere. They work on fixing bugs filed.23:31
charlie-tcaThe way to report the issue is to file a bug.23:31
charlie-tcaThat lets the developers know there is a problem, and they can work on it.23:31
charlie-tcaYou are giving a reference to someone's forum, and asking for a fix for it. It doesn't happen that way.23:32
javahorncharlie-tca: gmail account comes under OpenID?23:41
charlie-tcaI don't know23:41
javahornsorry i expected more support from ubuntu here or #ubuntu, my windows crashed and i came to ubuntu and no one seem that willing to help out!23:45
chilicuilhi there, what should I do if I want to fix some typos in po/ files?, in bug 725217 typos are in html & po files, the patch attached modify the html files but not the po/ ones, should I fix them as well, or is any other path I should follow?23:48
ubot4Launchpad bug 725217 in ubiquity-slideshow-ubuntu (Ubuntu) (and 2 other projects) "Typos in Edubuntu 11.04 slideshow (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/72521723:48
charlie-tcaI am sorry you feel that way, but giving a forum reference and saying fix this, just is not a good way to look for help.23:48
javahorncharlie-tca: sorry, i did not know the norm here, i will file it23:49
charlie-tcachilicuil: not sure here. Might check with transations, #ubuntu-translations, I think it is, to make sure23:49
charlie-tcaThey deal with the po files, to the best of my knowledge23:50
chilicuilcharlie-tca: I'll do it, thx23:51
charlie-tcajavahorn: all of us are volunteers, both here and in #ubuntu. We just don't have the ability to drop everything to try and fix things23:51
javahorncharlie-tca: accepted, but seeing its prevalence i thought it will be easy go23:52
charlie-tcaIt is only prevalent if you own that machine. I never seen it before23:52
javahorncharlie-tca: to gain ubiquity(sounding bit same to ubuntu, at least first part), it has to run on all kinds of machine!23:54

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