Bazaar Version Control System

existence of backup.bzr blocks running upgrade a second time

Reported by Orestes Mas on 2008-11-19
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar
High
Parth Malwankar
Launchpad itself
Medium
Unassigned

Bug Description

Bzr throwed an error trying to upgrade a launchpad-hosted-repository format remotely via sftp, using

bzr upgrade sftp://<email address hidden>/~ubuntu.cat/ubuntaires/xerrades/

Traceback provided. I've to admit that I opened another console instance and called "bzr version" while bzr upgrade running in the first console. Perhaps this triggered the error?

Now I'm unable to re-run the "upgrade" command above, because bzr complains about

bzr: ERROR: File exists: '/~ubuntu.cat/ubuntaires/xerrades/backup.bzr': mkdir failed: unable to mkdir

How can I revert changes?

Orestes Mas (orestes) wrote :
description: updated
John A Meinel (jameinel) wrote :

Bazaar itself could provide a way for you to delete that directory, but some of this is an issue with launchpad-bazaar (there may already be an open bug about needing a way to delete the backup dirs from the launchpad hosting.)

At present, there are a couple of options:
1) Use an sftp client that supports recursively deleting directories. I believe NCFTP does, as do quite a few graphical clients
2) Use "hitchhiker" https://edge.launchpad.net/hitchhiker
This piggybacks on top of Bazaar's Transport mechanism to provide access to bzr+ssh and sftp.
I believe you can do something like:
hitchhiker lp:~ubuntu.cat/ubuntaires/xerrades
(Cmd) help
(Cmd) rmtree backup.bzr

Changed in bzr:
importance: Undecided → Medium
status: New → Triaged
Aaron Bentley (abentley) wrote :

Hitchhiker also supports non-interactive mode:
hitchhiker lp:~ubuntu.cat/ubuntaires/xerrades rmtree backup.bzr

Paul Hummer (rockstar) on 2008-12-18
Changed in launchpad-bazaar:
importance: Undecided → Medium
status: New → Triaged
Martin Pool (mbp) on 2009-01-16
Changed in bzr:
importance: Medium → High
Martin Albisetti (beuno) wrote :

I'd propose that we rename the existing backup dir to backup.bzr.1, *.2, etc.
This, in conjunction with delete-after-upgrade should stop making this problem a "high" priority.

Thanks for working on these, Parth. Please mark them inprogress til
they're done.

--
Martin <http://launchpad.net/~mbp/>

Martin Pool (mbp) on 2010-02-15
Changed in bzr:
status: Triaged → In Progress
Martin Pool (mbp) on 2010-03-17
Changed in bzr:
assignee: nobody → Parth Malwankar (parthm)
milestone: none → 2.2.0b1
status: In Progress → Fix Released
Jelmer Vernooij (jelmer) on 2011-06-20
Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments