dh-make and merge-upstream choke on orig.tar.bz2 imports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-builddeb (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: bzr-builddeb
I tried to do a package from scratch where upstream releases bz2 tarballs. This doesn't seem to work:
First, create a test bz2 (happens with any other tarball as well, though):
mkdir /tmp/test; cd /tmp/test
echo hello > readme.txt
tar cjf foo_1.orig.tar.bz2 readme.txt
rm readme.txt
Now try to bzrify it:
$ bzr dh-make --bzr-only --v3 -Derror foo 1 foo_1.orig.tar.bz2
Fetching tarball
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
version.
File "/usr/lib/
package_name, version, use_v3=use_v3)
File "/usr/lib/
force_gz=not use_v3)
File "/usr/lib/
_error_
File "/usr/lib/
raise FileExists(
FileExists: File exists: 'foo_1.
The same happens if I try to merge-upstream in an already existing packaging directory.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bzr-builddeb 2.4.2
ProcVersionSign
Uname: Linux 2.6.35-14-generic x86_64
Architecture: amd64
Date: Thu Aug 12 14:57:59 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: bzr-builddeb
Hi,
Found the problem. Should be fixed in the next upload.
As a workaround, you can just not put the tarball that you want to use in the location
that the command wants to put it in. It will be wasteful, but should avoid this error.
Thanks,
James