bzr merge-upstream should adjust debian/changelog directly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-builddeb |
Fix Released
|
Wishlist
|
Jelmer Vernooij | ||
bzr-builddeb (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: bzr-builddeb
When using bzr merge-upstream to pull a new revision, debian/changelog should automatically be updated with the recommended version number and "New Upstream snapshot" when pulling from trunk, or "New Upstream version" when pulling from an appropriate tag. In the simple case where there are no conflicts, this allows the user to simply use debcommit to push the updated state of the package to the bzr repository for the package. In the more complex case, the user may need to adjust a couple things before being able to use debcommit, but can use dch normally to further update the changelog in preparation for debcommit. For extra portability between distributions and compatibility with standard practice when using VCS management of packaging, the special target "UNRELEASED" should be used in the changelog when it is updated (e.g. dch -v 1.2.3+bzr7477-1 -D UNRELEASED "New upstream snapshot").
Related branches
Changed in bzr-builddeb: | |
importance: | Undecided → Wishlist |
Changed in bzr-builddeb: | |
status: | Fix Committed → Fix Released |
Hi,
Thanks for the report. I think I agree. Or at least I've forgotten why it doesn't
actually do it and just tells you what to do.
I think it might just have been that it was the easy thing to do.
Thanks,
James