Guido Günther <a...@sigxcpu.org> writes: > On Mon, Aug 10, 2009 at 10:01:35AM +0300, Jari Aalto wrote: > >> Package: git-buildpackage >> Version: 0.4.55 >> Severity: wishlist >> >> >> In situation, where the debian/changelog has already been prepared for the >> new version, the import command calls dch, which bails out: >> >> ... >> branch 'master' >> git ['merge', 'upstream/2009.0810', '--no-summary'] [] >> Merge made by recursive. >> dch ['-v', '1:2009.0810-1', 'New Upstream Version'] [] >> dch: fatal error at line 978: >> New version specified (1:2009.0810-1) is less than >> the current version number (1:2009.0810-1)! Use -b to force. >> dch returned 25 >> Dch failed. >> Import of ../procmail-lib-2009.0810.tar.gz failed >> rm ['-rf', '../tmpP1evFJ'] [] >> r...@jondo /srv/deb/debian/procmail-lib/procmail-lib.git cat >> lib-stebbens/proclint >> >> SUGGESTION >> >> In git-buildpackage, please check if VERSION heading like is already >> found in debian/control and issue a not, and ski dch step. An example: > ^^^^^^^ > changelog?
Correct. > In this workflow you never want to call dch so just use --no-dch. > Cheers, The developer doesn't necessarily remember that entry was added. Especially when it happens that project is worked on, interrupted, other work is none and only later come back to the task. If possible, just peek the debian/chnagelog for existing string. Or check output of dpkg-parsechnagelog to determine if dch call is needed. Jari -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
