|
Home > Archive > Debian Developers > July 2005 > question: bugfixes in experimental?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
question: bugfixes in experimental?
|
|
| Harald Dunkel 2005-07-31, 2:48 am |
| Hi folks,
I've got a problem with marking broken packages as fixed.
If there is (lets say) a grave functionality bug for package
"M" in unstable or testing, then a bugfix in experimental
doesn't help me. (I made very bad experiences with experimental,
e.g. broken version numbers, currupted apt system, etc., so this
stuff won't be installed on my PC.)
Shouldn't it be some kind of policy to mark a bug as fixed,
only if the fix is available on the same level as the previous
broken package?
Regards
Harri
| |
| Don Armstrong 2005-07-31, 2:48 am |
| On Sun, 31 Jul 2005, Harald Dunkel wrote:
> I've got a problem with marking broken packages as fixed.
Fixed generally means that the bug has been fixed in an NMU, IE, by
someone not the maintainer; fixed-in-experimental is the tag that
usually means that the bug in question has actually been fixed in
experimental.
The proper solution for this issue is versioning support in the bts
which has already been implemented. [See #247066 and friends.]
Don Armstrong
--
Tell me something interesting about yourself.
Lie if you have to.
-- hugh macleod http://www.gapingvoid.com/archives/batch20.php
http://www.donarmstrong.com http://rzlab.ucr.edu
| |
| Laszlo Boszormenyi 2005-07-31, 2:48 am |
| Hi,
On Sun, 2005-07-31 at 08:11 +0200, Harald Dunkel wrote:
> Shouldn't it be some kind of policy to mark a bug as fixed,
> only if the fix is available on the same level as the previous
> broken package?
There's a semi-policy IMHO, you can tag[1] the bugs instead of closing
them, so there's a fixed-in-experimental for example. You can also tag
the bug as sarge, etch, whichever contains the bug. Say, if the bug
exists in sarge _and_ etch, then you fix the bug for Etch, but instead
of closing it, remove the etch tag. Then, fix the bug for Sarge, and
say it is important enough that the volatile project accept it, so
you close the bugreport. Otherwise you better close it anyway, as you
don't have other way to make the fix into Sarge; well, maybe with the
upcoming revisions as it happeded with Woody and earlier.
Regards,
Laszlo/GCS
[1] http://www.debian.org/Bugs/Developer#tags
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|