Hi, On Sat, 2007-07-28 at 07:30 -0700, Daniel Burrows wrote: > Package: bugs.debian.org > Severity: normal > > debbugs occasionally doesn't close bugs for me after I've uploaded > a new version of a package with appropriate Closes: tags in the changelog. > > It doesn't happen often enough for me to have a lot of data points at the > tips of my fingers, but the last upload that did this was aptitude 0.4.6.1-1. > This was an upload that included two new changelog entries, and only closed > bugs in the entry for 0.4.6-1; none of these bugs were closed automatically. > Perhaps debbugs is confused by versions that are never uploaded to the > archive? (AFAIK this is totally legitimate to do)
So far as I can tell, this was caused by the fact that the changes file for 0.4.6.1-1 only includes the entry for that version and not 0.4.6-1 also - in which case, dak had no way of knowing the upload affected the bugs fixed in the earlier version. Comparing http://packages.qa.debian.org/a/aptitude/news/20070726T061703Z.html and http://packages.qa.debian.org/c/cryptkeeper/news/20070730T231129Z.html (randomly chosen as a recent NEW package): Source: aptitude [...] Version: 0.4.6.1-1 [...] Changes: aptitude (0.4.6.1-1) unstable; urgency=low . * New upstream release (includes scripts I missed in the last release). Files: versus Source: cryptkeeper [...] Version: 0.7.666-2 [...] Closes: 433566 Changes: cryptkeeper (0.7.666-2) unstable; urgency=low . * debian/copyright: added informations about files under LGPL license. . cryptkeeper (0.7.666-1) unstable; urgency=low . * Initial release. (Closes: #433566: ITP: cryptkeeper -- encfs system tray applet for GNOME - Debian Bug report logs) Files: I'd suspect that the aptitude upload should have been built using "dpkg-buildpackage -v0.4.6-1". Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
