Changelog
bzr-builddeb (0.14ubuntu1) feisty; urgency=low
* revert the smart options patch so that the package gets usable with bzr 0.13 again.
bzr-builddeb (0.14) UNRELEASED; urgency=low
* Compatible with bzr 0.14.
* Drop the silly restriction on only invoking the command from the root
of a branch.
* Add support for non-native full source packages. To do this, just
have orig-dir pointing to the dir containing the upstream tarballs.
This involves a change in behaviour I am afraid. Native packages are
now not the default, so if you have one echo 'native = True' to
global.conf.
* Add support for creating non-native packages from full source branches
by creating the tarball from the branch, rather than the user creating it.
It simply blows away debian/ from the tarball and names it appropriately
in the build dir to get a non-native package where all of and only
debian/ are in the .diff.gz.
* Add support for exporting the upstream code from a bzr branch when in
merge mode. Just use export-upstream with a URI of a bzr branch and that
code will be the .orig.tar.gz of the source package. Please make sure
that you don't grab a different upstream code for the same upstream
version, that could break things horribly. You can also specify the
revision to export with export-upstream-revision to combat this.
* Add support for pulling in the upstream branch when it is local so that
you can build the lastest version. The 'export-upstream-prepull' option
is only availble as a config file option.
* Add an option to stop the build if the above mentioned pull did nothing.
* Add a --short/-S parameter to build source packages and a source-builder
option to configure what it does.
* Change to use the new version of the python-debian API, so that 0.1.1 is
now required.
* Builddeb configuration files that are used in the branch are marked as
non-trusted. This means that you can no longer set any of the builders in
them, as this would be arbitrary code execution. You have to set the
builders in your ~/.bazaar/builddeb.conf now. If you don't like this
change then please propose a scheme that allows you to do what you want,
but doesn't expose people to the security threat.
* Bump the required version of bzr to 0.14~rc1 or greater and less than 0.15.
-- Reinhard Tartler <email address hidden> Tue, 16 Jan 2007 23:16:44 +0100
