-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Branden Robinson wrote: > reopen 246285 > found 246285 1.0.2-2 > close 246285 1.2.3dfsg1-3 > thanks > > On Thu, Jan 12, 2006 at 12:48:41PM -0800, Debian Bug Tracking System wrote: >> I tested 1.1.4-2 (current sarge) and confirmed the presence of the bug. >> >> I tested 1.2.3dfsg1-3 (current etch) and found that the bug no longer >> occurs. >> >> Accordingly, marking as done. > > Hi, Max. > > When closing a bug under these circumstances, you're supposed to put a > "Version:" pseudo-header in your -done message. > > Bug reports should be closed by sending email to [EMAIL PROTECTED] > The message body needs to contain an explanation of how the bug was fixed. > > [...] > > Where applicable, please supply a Version line in the pseudo-header of your > message when closing a bug, so that the bug tracking system knows which > releases of the package contain the fix. > > http://www.debian.org/Bugs/Developer > > I'm repairing the situation with a technique prescribed by Steve Langasek.
Oh, OK. I freely admit to being inexperienced with the Debian BTS. My interpretation of the above was that it was not applicable in this case, since I don't know which version fixed it, only that is was fixed at some point between the two versions that I tested. It is quite likely it was fixed in 1.2.0-1, but I'm not easily able to tell for sure. Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) iD8DBQFD0SYMfFNSmcDyxYARAociAJ93tusPxcfL5vUQrhXsolNa4IsO3gCdHOVe HsXl56xbvJsk2v1AmZp79F8= =KaeP -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
