FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 07-10-2010, 05:21 PM
 
Default Bug about possibly incomplete bugfix

(I asked this on IRC more than an hour ago, got no reply, so here goes
it to the list.)

What's the policy when you think that a change made due to a FIXED bug
needs more changes? Should you just comment it, fill another bug or
change the state (I can't do the later, anyway)?

As an example (the one I am dealing with, bug 283744), I found out a
package was changed to add a behavior which wasn't documented in the
ebuild.

On one hand, the suggestion to add elog messages should belong to the
original bug (now RESOLVED FIXED).

But on the other hand this is a new problem introduced by the fix for
that first bug, and then should have its own request.

(And, as I can't change the first bug - which is FIXED, a separate bug
would be initially marked as OPEN, which suits the case of a new, IMHO
still unsolved issue.)

But what's the most polite thing to do?

--
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg
 
Old 07-10-2010, 05:28 PM
Alan McKinnon
 
Default Bug about possibly incomplete bugfix

On Saturday 10 July 2010 19:21:28 Nuno J. Silva wrote:
> (I asked this on IRC more than an hour ago, got no reply, so here goes
> it to the list.)
>
> What's the policy when you think that a change made due to a FIXED bug
> needs more changes? Should you just comment it, fill another bug or
> change the state (I can't do the later, anyway)?
>
> As an example (the one I am dealing with, bug 283744), I found out a
> package was changed to add a behavior which wasn't documented in the
> ebuild.
>
> On one hand, the suggestion to add elog messages should belong to the
> original bug (now RESOLVED FIXED).
>
> But on the other hand this is a new problem introduced by the fix for
> that first bug, and then should have its own request.
>
> (And, as I can't change the first bug - which is FIXED, a separate bug
> would be initially marked as OPEN, which suits the case of a new, IMHO
> still unsolved issue.)
>
> But what's the most polite thing to do?


Open a new bug and refer to the old one. Let the bug owner decide what's the
best thing to do next.



--
alan dot mckinnon at gmail dot com
 
Old 07-11-2010, 05:33 PM
 
Default Bug about possibly incomplete bugfix

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On Saturday 10 July 2010 19:21:28 Nuno J. Silva wrote:
>>
>> What's the policy when you think that a change made due to a FIXED bug
>> needs more changes? Should you just comment it, fill another bug or
>> change the state (I can't do the later, anyway)?
[...]
>
> Open a new bug and refer to the old one. Let the bug owner decide what's the
> best thing to do next.

Did that. At least now it will show up as a bug to be solved.

--
Thanks for your reply,
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg
 

Thread Tools




All times are GMT. The time now is 02:58 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org