Package: bugs.debian.org Version: 20051127 A question on handling mistakes with version tracking has arisen.
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote: > A number of changes have been made to [EMAIL PROTECTED] [1] to > support this. Firstly, the 'close' and 'reassign' commands now take > extra version arguments, as follows: > > close 1234567 1.1 > reassign 1234567 example-package 2.0-1 > > The 'reopen' command takes an optional submitter argument, so it was > difficult to get a version in here unambiguously. Instead, we've > introduced a new 'found' command, which says "I've found the bug in this > version of the package". You can use this whether the bug is open or > closed; if the bug's closed and you give a version more recent than the > last recorded fixed version, the bug will be considered open again. > > found 1234567 1.3-2 > > 'found' is now preferred to 'reopen' except when reopening bugs that > were closed without a version (e.g. closed as invalid). In bug#340838, Andrea Mennucc asks for the bts command (in devscripts) to offer "fixed" and "unfixed" options: fixed as a synonym for the new close command and unfixed to correct errors made in using fixed: > Suppose moreover that somebody sends a > > $ bts close #wrongbugnumber #version > > where #wrongbugnumber is a mistyping: then it > would be useful to have a command > > $ bts unfixed #wrongbugnumber #version > > to correct the former. But I don't know the canonically correct way to do this: actually, does the BTS have a correct way of cancelling "fixed in version XXXX" commands? If not, please could one be implemented. Thanks, Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
