[01:01] <Hew> Is it appropriate to ask a user to install a package from Intrepid on their Hardy system to test if their issue has been solved?
[01:01] <bdmurray> Not really.
[01:03] <Hew> bug #203144 was marked as fixed in Debian, so I think it would be useful for the reporter to test with the latest version in Intrepid. What's the best way to do this? Should I ask them to test on an Intrepid livecd?
[01:08] <bdmurray> Testing with a LiveCD is a good idea but I don't think alpha 1 every came out
[01:12] <Hew> bdmurray: yea, looks like it has been postponed to me as well. They could do it on a daily build, but there's no rush so I'll follow it up later on with an alpha. Thanks for your help :-)
[01:13] <bdmurray> Hew: No problem
[01:44] <greg-g> uh oh, my LP karma is starting to go down, dang summer internship interfering with bug triaging :)
[02:26]  * amireldor_ is away: I'm busy, sorry
[02:26] <Hobbsee> !away | amireldor_
[02:26]  * amireldor_ is back (gone 00:00:08)
[02:27]  * amireldor_ is away: I'm busy, sorry
[02:27]  * amireldor_ is back (gone 00:00:02)
[02:27] <amireldor_> Hobbsee, sorry i was testing ex-chat features
[02:28] <Hobbsee> amireldor_: i'm sure that's not a feature.  i'ts a bug :)
[02:28] <Hobbsee> amireldor_: and please, not in #ubuntu and such.
[02:29] <amireldor_> Hobbsee, nah, the bug is inside my brain :) i'm a loco team leader hence the LoCo
[02:29] <Hobbsee> heh
[03:13]  * amireldor_ is away: I'm busy, sorry
[10:15] <gnomefreak> i cant remember the link to subscribe to all bugs in a project in LP can someone give me an example please
[10:16] <RAOF> gnomefreak: https://edge.launchpad.net/do/+subscribe
[10:16] <RAOF> Bon apetit
[10:17] <gnomefreak> RAOF: thanks
[10:18] <gnomefreak> :( this might not work
[10:21] <gnomefreak> ha thanks RAOF i did get it to work
[15:28] <motin_0> Hey guys
[15:28] <motin_0> I am running into falsely reported duplicates
[15:28] <motin_0> how can I revert a bug's duplication status?
[15:29] <motin_0> by having the bug falsely reported against the other one, it is not getting the attention it deserves, and other bugs which really are duplicates cannot be marked as such against it because it is already marked as a dupe...
[15:31] <motin_0> Here is the false duplicate: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/105251
[15:32] <motin_0> as the marked dupe target is "Fix Released", this bug will _never_ get fixed...
[15:33] <motin_0> I have been triaging bug the last 6 hours
[15:34] <motin_0> there are many bugs that would benefit from the ability to choose "Wishlist" importance, and adding the "feature-request" tag - but I do not have account privileges to do so...
[15:35] <motin_0> how can I apply for a membership in the bug squad?
[15:35] <motin_0> check my related bugs: https://bugs.launchpad.net/~motin  you will find that I am a genuine ubuntu supporter and a valid triager
[15:42] <techno_freak> motin_0, you can go to "mark as duplicate" link on the left, and remove the shown bug number, click change
[15:43] <motin_0> techno_freak: I get an error message when trying that, sorry
[15:43] <motin_0> no wait
[15:44] <motin_0> motin_0: there is simply no number there
[15:44] <techno_freak> motin_0, if you are not in bug control but would like to change, please report it here so people can look at it and change it as required. if you would like to apply for bug control, ping bdmurray
[15:44] <techno_freak> motin_0, i just now unmarked it from a duplicate
[15:44] <motin_0> techno_freak: ok great
[15:44] <motin_0> I guess I'll be posting my proposed changes here until bdmurray gets back to me
[15:45] <techno_freak> motin_0, then comment it to the bug report
[15:45] <motin_0> thanks techno_freak
[15:46] <motin_0> now those bugs are correctly sorted
[15:47] <techno_freak> motin_0, welcome :)
[15:48] <bliZZardz> techno_freak , you did not answer a corollary to motion_0's Q : what is the criteria for membership in the BugSquad?
[15:50] <techno_freak> bliZZardz, read /topic
[15:50] <techno_freak> motin_0, read /topic
[15:51] <motin_0> techno_freak: thanks, just applied
[15:55] <bliZZardz> Q : if compiz is not part of the repos(before Gutsy), should all the bugs(which conform to it) be marked 'Invalid'? (https://wiki.ubuntu.com/Bugs/Responses also states the same) - i wanted to confirm this.
[15:58] <techno_freak> bliZZardz, bugs on compiz over which release?
[15:59] <bliZZardz> techno_freak : check that link - search for 'compiz' in that page.
[16:00] <bliZZardz> techno_freak : or read my prev msg carefully :)
[16:01] <techno_freak> bliZZardz, it clearly states ""So the first step will be to find out which package version they have installed. In the event that it is not from the Ubuntu repository the bug should be set to Invalid. ""
[16:02] <techno_freak> bliZZardz, so you have to first comfirm whether the compiz version is the one in ubuntu repos or not
[16:02] <techno_freak> if it is not, then mark it as invalid
[16:15] <techno_freak> frustration building up over bug #38512 :[
[16:53] <motin_0> Hi all
[16:54] <motin_0> I have a suggestion to change the importance of a certain bug from "Wishlist" to "Confirmed", since it's status is "Fix Released": https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/96103
[17:04] <techno_freak> motin_0, wishlist to confirmed for a fix released bug?
[17:04] <motin_0> techno_freak: yeah, at least not keeping "Wishlist" since the bug was never a wishlist bug to start of with
[17:05] <techno_freak> motin_0, fix released is a higher level to confirmed, so you need not change a fix released to confirmed
[17:05] <techno_freak> motin_0, importance is different from status
[17:06] <motin_0> techno_freak: yeah I am clearly mixing it up since I do not have an insight in what importance levels are available
[17:06] <techno_freak> motin_0, if you are not clear please do not do anything without getting clarified here
[17:07] <techno_freak> motin_0, may be asking the one who marked it as wishlist and fix released might also help
[17:07] <motin_0> techno_freak: no, I wouldn't and can't change the importance
[17:08] <motin_0> techno_freak: as a learning case, what would be an appropriate Importance level? is it even relevant to care about the Importance level for Fix Released bugs? it would only be for historical reasons
[17:09] <techno_freak> motin_0, importance is marked for triaged bugs, so we know how important is to attend the bug. once it is fix released, then you need not worry too much about anything until someone reopens the bug
[17:10] <motin_0> techno_freak: ok great, then I can move on
[17:10] <motin_0> thanks
[17:45] <motin_0> Ok guys, now I'm finishing my 8h bug triaging - thanks for the support
[17:57] <Iulian> motin_0: 8 hours - that's great!
[17:58] <motin_0> Iulian: yeah and I'm totally starved and very craving for some human contact atm :P so I'm off to a house-warming party. cheers all!
[18:58] <\sh> bdmurray: ping
[18:58] <\sh> bdmurray: bug #243767
[20:03] <ppp> Should I raise a bug on problems with the patched NVIDIA .09 driver on Intrepid? The driver is patched by an Ubuntu dev to get it working on the 26.6.26 kernel. Asking due to it being patched
[20:13] <bdmurray> \sh: pong
[20:14] <\sh> bdmurray: please reply to my comment on bug #243767 :) thx :)
[21:21] <lupo__> hello everybody
[21:22] <lupo__> i'm looking for the right place to report a bug in the kde-guidance package
[21:25] <lupo__> ah, got it. never mind :)
[21:45] <ppp> Since no one replied, I reported it amongst other bugs on Intrepid alpha in https://bugs.launchpad.net/ubuntu/+bug/243817