On Fri, 14 Mar 2008 21:06:09 +0000 Debian Bug Tracking System wrote: > Hello, > > I'm closing this bug as I just uploaded mcs 0.7.0 (which fix this issue) > to debian unstable.
Well, I'm glad to hear that mcs 0.7.0 is supposed to fix the two issues (even though I haven't yet had the opportunity to check whether it actually does). Anyway, is closing the bugs with a -done command the most proper action? It completely bypasses BTS version tracking, doesn't it? What I recently proposed was reassigning the two bugs to package libmcs1 version 0.6.0-1. At that point the bugs would have been closed with proper version information by a "Closes" directive in the changelog (or else by a -done command with explicit version information). Or am I completely off-track? -- http://frx.netsons.org/progs/scripts/refresh-pubring.html New! Version 0.6 available! What? See for yourself! ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgp0F3kI5HoBo.pgp
Description: PGP signature
