Can't push new branch to staging

Bug #608347 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I tried to push a new branch to staging, and got the following error:

  bzr: ERROR: Target directory bzr+ssh://bazaar.staging.launchpad.net/~bjornt/clouddeck/buildout-newest-offline2 already contains a .bzr directory, but it is not valid.

< rockstar> BjornT, hm. I wonder if that might be an artifact of the.
            staging codehosting not cleaning up after itself.
< rockstar> BjornT, so, first, file a bug. Second, I fixed it so you.
            should be good now.
< abentley> BjornT, I get "PermissionDenied" when I try to read.
            .bzr/branch-format
< abentley> rockstar, Are you suspecting database ID reuse?
< rockstar> abentley, yes.
< abentley> Yeah, that seems likely.
< rockstar> abentley, so maybe we need to clear out the dirs on staging.

Revision history for this message
Paul Hummer (rockstar) wrote :

We need to chat with the losas about this.

tags: added: canonical-losa-lp
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Medium
Curtis Hovey (sinzui)
Changed in launchpad:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.