> > 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. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ttf-freefont&dist=unstable
Aha, I better understand now..... > > 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?). > > Uh, 20031008-1.1 is the version in sarge. And so far, the BTS has only Hmmm, I figured out dirreferently from the various release dates but this is something that I anyway overlooked.... > recorded that it's reported in 20051206-1 and 20051206-2, whereas testing > has 20051102-2. So the bug is at least not reported to affect either sarge > or etch at this point. Hmmm, the light is slowly coming in my darkness..:-). Thanks for all the explanations. I'll probably need to report another wishlist bug: have all this information about version tracking go into the doc-debian package and be installed in /usr/share/doc/debian.... Where is this information available right now? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
