affects bzr-builddeb
summary "Default build_type in empty branch should be normal, not
merge"
On Tue, 2011-05-03 at 12:09 +0000, Alexandros Frantzis wrote:
> With the latest changes in trunk the errors have gone away, but the
> command still doesn't work correctly (at least not as I would expect):
>
> $ bzr init hello && cd hello
> $ bzr merge-upstream ../hello-2.7.tar.gz --package hello --version 2.7 --distribution natty
> Using version string 2.7.
> An entry for the new upstream version has been added to the changelog.
> $ bzr st
> added:
> debian/
> unknown:
> debian/changelog
> $ ls
> debian
>
> The tarball contents aren't included in the branch.
I guess the detection mechanism doesn't see any files and thus considers
the packaging branch a merge branch. I'm filing a separate bug about
this.
affects bzr-builddeb
summary "Default build_type in empty branch should be normal, not
merge"
On Tue, 2011-05-03 at 12:09 +0000, Alexandros Frantzis wrote:
> With the latest changes in trunk the errors have gone away, but the
> command still doesn't work correctly (at least not as I would expect):
>
> $ bzr init hello && cd hello
> $ bzr merge-upstream ../hello-2.7.tar.gz --package hello --version 2.7 --distribution natty
> Using version string 2.7.
> An entry for the new upstream version has been added to the changelog.
> $ bzr st
> added:
> debian/
> unknown:
> debian/changelog
> $ ls
> debian
>
> The tarball contents aren't included in the branch.
I guess the detection mechanism doesn't see any files and thus considers
the packaging branch a merge branch. I'm filing a separate bug about
this.
Cheers,
Jelmer