| === bigbash is now known as bigbash_away | ||
| === bulldog98_ is now known as bulldog98 | ||
| === Tetsuo55_2 is now known as tetsuo55 | ||
| Cheesehead | Event: Wisconsin LoCo is running an IRC Bug Jam, Sunday 1700 UTC (four hours from now), #ubuntu-us-wi. Great training opportunity for people new to bugs. | 12:52 |
|---|---|---|
| trinikrono | aloha bugsquad i remember that we where told not to post follow up comments since launchpad introduced the expired on incomplete reports, but the HowToTrigage page still has it here https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating | 15:34 |
| === erhesrhsrtb54vyh is now known as Elbrus | ||
| hggdh | trinikrono: corrected, thank you for raising it | 16:20 |
| trinikrono | :D no problem hggdh | 16:20 |
| ashams | Cheesehead: Waiting and will invite ppl from Egypt LoCo team :D | 16:29 |
| Cheesehead | ashams: Wonderful! | 16:32 |
| Cheesehead | Wisconsin LoCo Bug Jam training session will begin in #ubuntu-us-wi in 5 min. http://loco.ubuntu.com/events/ubuntu-us-wisconsin/1178/detail/ | 16:56 |
| === yofel_ is now known as yofel | ||
| === erhesrhsrtb54vyh is now known as Elbrus | ||
| crog | Cheesehead: a big factor is if you know the person, and the relationship | 18:48 |
| crog | ignore... | 18:48 |
| Cheesehead | crog: Hey, I post in the wrong channel sometimes, too! | 18:49 |
| sbte | hi, is there a way for developers to see private bugs reported for their own project in the ubuntu bug tracker? | 19:22 |
| sbte | because I'm a developer of emesene myself, and heard from someone that there are a lot of private bugs with useful backtraces | 19:23 |
| trinikrono | sbte: i believe once you are in bug control you should be able to see it? | 19:23 |
| sbte | yes, in your own project I think, but I'm talking about the bugs reported in https://bugs.launchpad.net/ubuntu/+source/emesene | 19:24 |
| sbte | not https://bugs.launchpad.net/emesene | 19:24 |
| sbte | trinikrono, ^ | 19:24 |
| charlie-tca | sbte: as a bugcontrol member, when I go to https://bugs.launchpad.net/ubuntu/+source/emesene I see 76 bugs | 19:26 |
| charlie-tca | Many of them are indeed private | 19:26 |
| charlie-tca | but I can access all of them | 19:26 |
| trinikrono | so i thought correct charlie-tca ? | 19:27 |
| charlie-tca | Looks like a lot of SIGSEGV faults | 19:27 |
| charlie-tca | trinikrono: yes | 19:27 |
| sbte | charlie-tca, I see only 48, of which 47 are actually invalid, but I don't feel like spending time on marking them all as such | 19:28 |
| jtaylor | sbte: does your application handle some kind of private data like passwords etc that might show up in stacktraces? | 19:28 |
| charlie-tca | There are no bugs listed for https://bugs.launchpad.net/emesene because the project itself does not use launchpad to track the bugs | 19:28 |
| charlie-tca | The 48 you see are the ones not marked "private" | 19:28 |
| sbte | jtaylor, no, it does handle passwords, but they can't appear in backtraces | 19:28 |
| sbte | charlie-tca, I know, we use github | 19:29 |
| sbte | but if the private bugs are actual bug, it's useful if we fix them | 19:29 |
| charlie-tca | The private bugs "they" referred to are the ones you are not seeing | 19:29 |
| sbte | charlie-tca, yep, and I was wondering if there was a way for the emesene-team to see them | 19:30 |
| charlie-tca | As the upstream developer, you can ask for bugcontrol privileges for emesene, and it will normally be granted | 19:30 |
| charlie-tca | I do not have the authority to do it, though | 19:31 |
| trinikrono | post the link to the bug control wiki page now? | 19:31 |
| charlie-tca | You should ask during the week, either pedro_ or bdmurry, I think | 19:31 |
| sbte | charlie-tca, ok, thanks. will do | 19:32 |
| charlie-tca | trinikrono: we normally don't require the upstream developer to go through the same process | 19:32 |
| charlie-tca | but they only work their own project bugs, too. | 19:32 |
| trinikrono | i have applied to bug control charlie-tca ;) | 19:34 |
| charlie-tca | That's great! You should be ready for it. Your work is good | 19:34 |
| sbte | oh, found the wiki, says i need to ask jcastro | 19:35 |
| sbte | i'll see if he's around in ayatana | 19:35 |
| charlie-tca | Okay | 19:35 |
| === paultag is now known as taggerdoodles | ||
| ashams | Hi I need help on this | 19:55 |
| ashams | Are the following two bugs dupes | 19:55 |
| sbte | charlie-tca, trinikrono, thanks for the help | 19:55 |
| ashams | https://bugs.launchpad.net/ubuntu/+source/evince/+bug/287646 | 19:55 |
| ashams | https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/730495 | 19:55 |
| charlie-tca | ashams: no, they are not duplicates. Under Unity, if compiz is broken, nothing will work right, so they had to wait for it to be fixed to test evince | 19:59 |
| charlie-tca | back when the bug was filed against evince, compiz did not get used even | 20:00 |
| ashams | charlie-tca: thank you :D | 20:00 |
| sbte | charlie-tca, got my bug control access, thanks for the help again | 20:08 |
| sbte | do you happen to know if the launchpad API has something that allows you to do this: | 20:09 |
| sbte | for bug in emesene: bug.closed(invalid) | 20:09 |
| sbte | would be neat | 20:09 |
| charlie-tca | Very good! You are welcome | 20:09 |
| charlie-tca | I don't know the scripting side of things. | 20:10 |
| sbte | because most bugs were reported with a really old version of emesene and don't apply anymore | 20:10 |
| sbte | and I don't feel like closing 70 bugs manually | 20:10 |
| jtaylor | launchpad has an api wher you can do that | 20:11 |
| jtaylor | https://help.launchpad.net/API/launchpadlib | 20:12 |
| jtaylor | a useful tool for experimenting is lp-shell | 20:12 |
| sbte | jtaylor, thanks, I'll check it out | 20:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!