Re: How to deal with fixed but open bugs

To: debian-devel@lists.debian.org
Subject: Re: How to deal with fixed but open bugs
From: Jakub Wilk <jwilk@debian.org>
Date: Thu, 30 Jul 2015 13:08:52 +0200
Message-id: <[🔎] 20150730110852.GA9284@jwilk.net>
Mail-followup-to: debian-devel@lists.debian.org
In-reply-to: <[🔎] 20150730034849.GC23607@virgil.dodds.net>
References: <[🔎] 87egjq49ty.fsf@vostro.rath.org> <[🔎] 20150730034849.GC23607@virgil.dodds.net>

* Steve Langasek <vorlon@debian.org>, 2015-07-29, 20:48:

Normally, such a bug is closed with 'close' rather than 'fixed'; thedifference between these two commands being *whether* to continueshowing the bug as a going concern.

Normally, you should close a bug by sending a message toNNNNNN-done@bugs.debian.org, not by the "close" control command.


Reference: DevRef§5.8.2

--
Jakub Wilk

Reply to:

References:
- How to deal with fixed but open bugs
  - From: Nikolaus Rath <Nikolaus@rath.org>
- Re: How to deal with fixed but open bugs
  - From: Steve Langasek <vorlon@debian.org>

Prev by Date: Re: Ad-hoc survey of existing Debian git integration tools
Next by Date: Re: Adding support for LZIP to dpkg, using that instead of xz, archive wide
Previous by thread: Re: How to deal with fixed but open bugs
Next by thread: Re: How to deal with fixed but open bugs
Index(es):
- Date
- Thread