bzr-builddeb --export-upstream uses bzr revision from changelog and not from config/command-line
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-builddeb (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: bzr-builddeb
1. use a .bzr-builddeb/
2. use a bzrREV in changelog version
3. run bzr bd --merge
result: it produces orig.tar.gz from bzrREV
expected result: produce orig.tar.gz based on default.conf values
This bug feels like a general design problem. As a rule of thumb, command line arguments should strictly dominate config files which in turn should strictly dominate implicit automagic.
ii bzr 1.17-1 easy to use distributed version control system
ii bzr-builddeb 2.2~ubuntu2 bzr plugin for Debian package management
ii bzrtools 1.17.0-1 Collection of tools for bzr
example branch: https:/ /code.edge. launchpad. net/~asac/ +junk/LP415572. example
just branch it and run bzr bd;
Result: revision 9 is exported as orig.tar.gz, while an upstream revision is configured in default.conf