On Thu, 2008-05-22 at 10:24 -0700, Cameron Dale wrote: > On 5/22/08, Neil Williams <codehelp@debian.org> wrote: > > On Wed, 2008-05-21 at 21:20 -0700, Cameron Dale wrote: > > > Unless you released 2.25-1 somewhere else, merge the unreleased 2.25-1 > > > and 2.26-1 changelog entries into one 2.26-1, otherwise the bugs > > > probably won't get closed automatically. > > > > Wrong - all the sponsor has to do is use '-v2.25-0 -sa'. dpkg-genchanges > > collates all Closes: entries in whichever versions the maintainer > > chooses to include by using the -v option. All bugs listed in > > the .changes file will be closed by that upload. > > Thanks for the tip. FWIW though, you have to explicitly specify a > version that actually exists in the changelog or you get a .changes > file that lists ALL the changelog entries (and closes all bugs ever > listed). True - I was expecting 2.25-0 to be before the first changelog entry. Adapt the command as necessary. > It's probably a bug in dpkg-dev that it behaves this way, > given what the manpage says. Not sure, because you do need to specify a version *prior* to the first one you want listed so if there are no other changelog entries, you do need to specify a -0 or whatever. -- Neil Williams <codehelp@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part