bzr bd --native is ignored if merge=True is set in config file
Bug #655277 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-builddeb |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
I have a new package in a tree at lp:~serge-hallyn/user-mounts/devel. If debian/
serge@sergelap:
Building using working tree
Running in merge mode
Purging the build dir: /home/serge/
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
bzr: ERROR: [Errno 2] No such file or directory: '/home/
If debian/
3.0 (native)
then it works.
Related branches
lp://staging/~jelmer/bzr-builddeb/655277-build-type-enum
- James Westby: Approve
-
Diff: 63 lines (+10/-8)2 files modifiedcmds.py (+7/-7)
debian/changelog (+3/-1)
Changed in bzr-builddeb: | |
status: | Fix Committed → In Progress |
Changed in bzr-builddeb: | |
status: | In Progress → Fix Committed |
Changed in bzr-builddeb: | |
milestone: | none → 2.7 |
Changed in bzr-builddeb: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is because that file existed previously. You have to remove it from bzr explicitly by using "bzr rm debian/ source/ format" .
I guess we could handle this a bit nicer and automatically update the dirstate before exporting.