-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: git-buildpackage Version: 0.4.13 Severity: normal
As I understand it, the workflow for using snapshots is: 1) make some changes 2) commit them 3) call git-dch --snapshot --auto to update the changelog (don't commit it) 4) call git-buildpackge --git-ignore-new to build the snapshot 5) test the snapshot 6) call git-dch --release 7) commit the changelog 8) call git-buildpackage to build the release This works fine, unless you have export-dir set to ../build-area/. Then gbp does an export of the current HEAD in step 4, which doesn't include my uncommitted changelog containing the snapshot. So you end up with a build with the same version number as the last release, defeating the purpose of snapshots. I can get around this by adding a step: 4.5) commit the snapshot changelog But that leads to a lot of commits related to just updating the changelog for snapshots. I'm not sure how to fix this. Perhaps doing a copy instead of an export when export-dir and ignore-new are specified, or adding a new command-line parameter indicating that this is desired. Thanks for a great program, Cameron - --- System information. --- Architecture: amd64 Kernel: Linux 2.6.22-1-vserver-amd64 Debian Release: lenny/sid 990 unstable steveholt.hopto.org 990 unstable localhost 990 unstable debian.camrdale.org 500 testing debian.camrdale.org 500 stable debian.camrdale.org - --- Package information. --- Depends (Version) | Installed ===================================-+-================= devscripts (>= 2.10.9) | 2.10.16 git-core (>= 1:1.5.0.1-1) | 1:1.5.3.8-1 python (>= 2.4) | 2.4.4-6 python-support (>= 0.7.1) | 0.7.6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHvIeYDx924g0gNq0RAjmNAJ0V9MfHl5XxZtHBpYCcykapQNz1JgCbBd8U hBaZfeLOyrvwVXx/lVvG7fc= =TSZr -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
