Quoting Debian Bug Tracking System ([EMAIL PROTECTED]): > Processing commands for [EMAIL PROTECTED]: > > > # Automatically generated email from bts, devscripts version 2.9.11 > > # according to the bug log, does not affect sarge; do not reopen, read the > > version-tracking docs! > > close 254113 20031008-1.1 > Bug#254113: Extra space between lines in new version of ttf-freefont > 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. > Bug#254670: (no subject) > Bug marked as fixed in version 20031008-1.1, send any further explanations to > Josh Triplett <[EMAIL PROTECTED]>
As Steve mentioned to me on IRC, I probably need more understanding of version trancking. However, I find some strange logic here. This bug is present in the current version of the package in unstable (either 20051206-2 or 20060126-1 I uploaded yesterday). So, having it NOT displayed among unfixed issues on bugs.debian.org/ttf-freefont is kinda puzzling to me. In short, I find closing a bug *that is present in the most recent version of a package* really strange and disturbing and I really do not see the rationale doing so. After all, if the bug is really RC, you don't want the current version to enter testing, do you? OK, someone reported that the bug is not in 20031008, fine....but this version isn't present in any of our currently supported releases (except woodye?). So, well, I need more explanations to understand and I'm afraid I'll have hard times understanding the logic anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
