BUGabundohumm seb128 is not here00:01
BUGabundopedro neihter00:01
BUGabundoshould I upstream https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/40324800:01
ubot4Launchpad bug 403248 in gnome-power-manager "DIM will dim my screen even when not idle" [Undecided,New]00:02
BUGabundoor is it karmic related?00:02
=== asac__ is now known as asac
=== nhandler_ is now known as nhandler
=== nhandler_ is now known as nhandler
=== Pici` is now known as Pici
=== bdefreese2 is now known as bddebian
=== WelshDragon is now known as Fluffles
=== jarlen_ is now known as jarlen
=== ejat is now known as e-jat
caabug 403387 is not assigned a package, the bug itself is about audacious, but the the problem in this case is that the corresponding version audacious-plugings isn't in karmic yet10:23
ubot4Launchpad bug 403387 in ubuntu "audacious has broken dependencies in karmic" [Undecided,New] https://launchpad.net/bugs/40338710:23
caashould it be assigned to audacious or audacious-plugins?10:24
caathe merge of audacious-plugins is bug 39961710:26
ubot4Launchpad bug 399617 in audacious-plugins "Please merge audacious-plugins 2.1-1 (universe) from Debian unstable (main)" [Wishlist,In progress] https://launchpad.net/bugs/39961710:26
=== yofel_ is now known as yofel
thekorn /exit11:15
diverse_izzueis this where i wanna be for the ubuntu hug day today?12:49
yofeldiverse_izzue: yes, welcome :)12:49
diverse_izzueok, question. say i cannot reproduce a bug which is "new" in a newer version of the program. should i mark it as "invalid" or "fixed"?12:50
yofeldiverse_izzue: I would set the bug to 'Incomplete' and post that I was unable to reproduce the issue in the newer version and ask the reporter if he is able to reproduce it with the newer version. After that I would go with the rules for Incomplete bug without a response if he doesn't answer. If he answers that he can't reproduce it as well then I would set the status to 'Invalid'12:53
yofeluse 'Fix Released' only when there really was a Fix released for this exact issue.12:54
trothigaryofel, does newer in this context imply newer in the same version of ubuntu?13:00
yofeltrothigar: actually I would also ask him to check the bug in a newer ubuntu release if a newer one is available since the bug might be already fixed there. Although if the reported version is obsolete in his ubuntu release then he should try to reproduce it with his never version first.13:20
trothigaryofel, so if the bugs fix in a later version, isn't it still a bug in the earlier version (assuming the earlier version is still within its supported time)?13:22
yofeltrothigar: that would then become a question if the newer package should be backported to the older release. But I'm not to confident about this myself, so maybe somebody else could comment on that?13:24
hggdhif the bug is critical enough to justify a backport, and it is possible to, then it will be backported13:36
hggdhplease see https://help.ubuntu.com/community/UbuntuBackports for more details of the process13:37
maxbBackports don't require critical bugs13:38
hggdhyeee. Indeed. Sorry, just wake up13:38
maxbBackports just require adequate testing to establish justifiable belief that it will work on the older release and not break other things.13:39
maxbThis is a problem, because now we have PPAs, people generally can't be bothered13:40
hggdhthis is a point where the PPAs disrupted the process13:41
hggdhdiverse_izzue, going back to your original question: if you find a bug on a newer release of a package then: (1) if the package is from a PPA, or erternal, contact the authors directly; (2) if the package is from Ubuntu, open a bug on it; (3) if the package is the pure upstream version (either dist point or trunk), open the bug upstream13:44
hggdhdiverse_izzue, if you cannot reproduce a bug on a newer version, as yofel said, enter a comment about it, mark incomplete, and wait a bit. The bug -- if indeed fixed on a newer release -- is actually to go to Fix Released, with a comment that13:47
hggdhthe fix for the current user release may be implemented if the reporter requests it ("Nominate for Release"), and the fix does not require extensive rebase. Otherwise it is either a backport request, or no fix on reporter's release13:49
yofelhm, that reminds me... The official backport procedure is to create a new bug in <release>-backports. But I've seen bugs that just had an affects of -backports added, is that a valid way too or should that be converted into a seperate backport request?13:51
yofels/affects of/affects on/13:53
hggdhyofel, ideally, you create a bug in <release>-backports14:07
hggdhit is not a good thing to have many different actions on the same bug14:07
=== d0ntKn0w is now known as d0ntKn0w_
=== d0ntKn0w_ is now known as d0ntKn0w__
=== d0ntKn0w__ is now known as d0ntKn0w
daz_hey guys, hope someone can help me, I've not sure if I've done the right thing or not15:21
daz_I've put the following bug against compiz -> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/39146115:21
ubot4Launchpad bug 391461 in compiz "Compiz Slow on Karmic w/ NVIDIA and 2.6.30 Kernel" [Undecided,New]15:22
daz_just not sure if I was right to do so, could be a driver issue but no idea how to figure out what the culprit is. any advice?15:22
=== andrea-bs_ is now known as andrea-bs
=== micahg1 is now known as micahg
Kamusinis gnome bugzilla website a litle overloaded?19:01
KamusinI can't load any url19:01
pedro_Kamusin, that's "normal"19:02
BUGabundohey fellow ubunteros21:59
Hellow'ello BUGabundo22:01
BUGabundohello Hellow22:03
BUGabundoI bet you get that a lot22:09
BUGabundoand when you are going to leave, do you change it to _goodby_ ?22:09
BUGabundohey seb12822:49
seb128hi BUGabundo22:50
BUGabundooh it was a reconnect22:50
BUGabundosorry to have bothered you :)22:50
yofelhm, what is one supposed to do with an old bug report about a package that was only released in hardy and intrepid?23:23
=== asac_ is now known as asac

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