| === roadmr is now known as roadmr_afk | ||
| === roadmr_afk is now known as roadmr | ||
| === dkessel_ is now known as dkessel | ||
| === roadmr is now known as roadmr_afk | ||
| === Jikai is now known as Jikan | ||
| === roadmr_afk is now known as roadmr | ||
| === roadmr is now known as roadmr_afk | ||
| === roadmr_afk is now known as roadmr | ||
| === roadmr is now known as roadmr_afk | ||
| === roadmr_afk is now known as roadmr | ||
| === ara is now known as Guest56698 | ||
| === greyback__ is now known as greyback | ||
| Laibsch | Can I manipulate the status of bugs' release pockets? | 16:32 |
|---|---|---|
| Laibsch | IOW, set all karmic bugs to wontfix | 16:32 |
| Laibsch | https://launchpad.net/ubuntu/karmic/+bugs | 16:32 |
| Laibsch | I want to do this with the e-mail API: https://help.launchpad.net/Bugs/EmailInterface | 16:33 |
| teward | AIUI "Won't Fix" is a unique, controlled-access status... | 16:38 |
| Laibsch | does that answer my question in any way? | 16:41 |
| Laibsch | if it is relevant, I can set that status without any problem via the web interface | 16:41 |
| teward | Laibsch: that's the first thing I was checking, yes. :P | 16:45 |
| Laibsch | then I do not understand the answer | 16:46 |
| Laibsch | -v, please | 16:46 |
| * teward never gave you a full answer | 16:46 | |
| Laibsch | are you playing games with me? | 16:49 |
| * Laibsch is starting to get annoyed | 16:49 | |
| teward | no, i'm not sure of the answer, so i'm searching too | 16:49 |
| teward | so patience, or wait for someone who knows the system better to answer (I asked #launchpad as well since they may know even more) | 16:51 |
| Laibsch | bbl | 16:54 |
| teward | well i haave an answer to Laibsch's initial question - thanks to cjwatson in #launchpad for it, because the documentation didn't show the functionality | 20:25 |
| teward | going to put out a serious question: is there any reason the bugs listed at https://launchpad.net/ubuntu/karmic/+bugs should be left open, or can we mark them as "Won't Fix" if we have the rights to? | 21:50 |
| penguin42 | I don't see why they should remain open - obviously only the karmic part of bugs that have parts for multiple versions | 22:00 |
| teward | correct | 22:01 |
| penguin42 | I'd be tempted to kill off the new and confirmed and see what's left | 22:01 |
| teward | i've already made a huge list of commands to send to edit@bugs to close them all... I'mma redo it to target new and confirmed for now... | 22:01 |
| teward | maybe triaged. | 22:01 |
| teward | new confirmed and incomplete actually | 22:02 |
| penguin42 | yeh | 22:04 |
| teward | hggdh: ^ (related to the PM I sent) | 22:07 |
| teward | in case you want to loop in your opinion publicly :) | 22:07 |
| hggdh | heh | 22:09 |
| hggdh | they can be either invalid or wontfix, provided that a blurb is given asking to open a new bug on a supported release | 22:10 |
| teward | heh. a lot of these appear to be Fix Released for the main bug task... | 22:10 |
| hggdh | so it would be a backport -- which will not happen. As such, safe to close wontfix. | 22:11 |
| teward | mhm | 22:13 |
| teward | i'm going to close the 6 karmic bugs against amsynth all at once as "Won't Fix", so lets see if I did this right... I'll add a form comment manually after... too bad there's no email interface for staging, then i would be able to test this a lot more thoroughly... | 22:18 |
| teward | well, goody, it worked. | 22:26 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!