Re: How to handle unreproducible RC bugs when the submitter is MIA?
Quoting Frank Küster ([EMAIL PROTECTED]): > Dear release team, > > #297181 is unreproducible, and the submitter has not answered to our > questions for a while. I am quite confident that this bug is really > PEBCAK, or more specifically a local misconfiguration, or some old > locally installed Emacs lisp files lying around. > > I do not think that this bug justifies auctex's removal from testing; on > the other hand, I don't think it would be proper to lower its severity > before we know more. But we cannot know whether the submitter will > answer again and allow us to decide, and possibly fix or reassign, > before sarge is frozen. > > How should this bug be handled? On a pure logic reasoning, it seems to me that the only solutions you have are either: -close the bug and assume your diagnostic for it to be a local misconfiguration -keep it and lower its severity as you obviously seem to think that it is not RC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to handle unreproducible RC bugs when the submitter is MIA?
On Fri, Apr 01, 2005 at 12:05:59PM -0600, Steve Greenland wrote: > On 01-Apr-05, 10:08 (CST), Frank K?ster <[EMAIL PROTECTED]> wrote: > > I do not think that this bug justifies auctex's removal from testing; on > > the other hand, I don't think it would be proper to lower its severity > > before we know more. But we cannot know whether the submitter will > > answer again and allow us to decide, and possibly fix or reassign, > > before sarge is frozen. > > How should this bug be handled? > Downgrade it, tag it as unreproducible (or whatever that exact tag is), > and don't worry about it. It's clearly not 'grave', since it doesn't > seem to affect anyone else, and presumably the submitter is not the only > Debian auctex user . Just to confirm, this is the release team's policy on handling such bugs. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: How to handle unreproducible RC bugs when the submitter is MIA?
On Fri, 2005-04-01 at 22:22 +0200, Frank Küster wrote: > (bugs in maintainer scripts are a policy violation) I don't recall policy saying that maintainer scripts "must" be entirely bug free. Obviously they _should_ be bug free, but bugs in maintainer scripts aren't always RC. -- Thomas Hood <[EMAIL PROTECTED]>
Re: How to handle unreproducible RC bugs when the submitter is MIA?
Thomas Hood <[EMAIL PROTECTED]> wrote: > That is, if the package > isn't unusable by everyone (if the bug only affects some users) then the > bug is not grave. > > If the bug is unreproducible then it can't be the case that the package is > unusable to everyone. So I'd say that a downgrade is justified. Well, maybe it is "only" serious (bugs in maintainer scripts are a policy violation), or maybe it is in fact only important. But it's hard to find out. And I would not be too surprised if it turned out to be a bug in a different package, some package rarely installed with auctex or other Emacs add-ons that rely on similar features (auctex runs its configure script from the maintainer script). And in this case I think it would be a serious bug in that other package. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: How to handle unreproducible RC bugs when the submitter is MIA?
On 01-Apr-05, 10:08 (CST), Frank K?ster <[EMAIL PROTECTED]> wrote: > I do not think that this bug justifies auctex's removal from testing; on > the other hand, I don't think it would be proper to lower its severity > before we know more. But we cannot know whether the submitter will > answer again and allow us to decide, and possibly fix or reassign, > before sarge is frozen. > > How should this bug be handled? Downgrade it, tag it as unreproducible (or whatever that exact tag is), and don't worry about it. It's clearly not 'grave', since it doesn't seem to affect anyone else, and presumably the submitter is not the only Debian auctex user . Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to handle unreproducible RC bugs when the submitter is MIA?
> Severity: grave > Justification: renders package unusable At http://www.debian.org/Bugs/Developer#severities, "grave" is glossed as: makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. I interpret "users" here as "all users" because the "important" severity is glossed as: has a major effect on the usability of a package, without rendering it completely unusable to everyone which seems to be meant to contrast with "grave". That is, if the package isn't unusable by everyone (if the bug only affects some users) then the bug is not grave. If the bug is unreproducible then it can't be the case that the package is unusable to everyone. So I'd say that a downgrade is justified. Of course, I may be misinterpreting the severity tags. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to handle unreproducible RC bugs when the submitter is MIA?
Dear release team, #297181 is unreproducible, and the submitter has not answered to our questions for a while. I am quite confident that this bug is really PEBCAK, or more specifically a local misconfiguration, or some old locally installed Emacs lisp files lying around. I do not think that this bug justifies auctex's removal from testing; on the other hand, I don't think it would be proper to lower its severity before we know more. But we cannot know whether the submitter will answer again and allow us to decide, and possibly fix or reassign, before sarge is frozen. How should this bug be handled? I'm cc-ing -devel, because this question seems to be of general interest. Please note that I am not subscribed to -release (but get mail to -devel or the bug address). Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
