timeout from a locked repo doing bzr push

Bug #1017591 reported by ilogue
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

When pushing from bazaar after replacing a .svg file, I got this message (twice):

<Fault 380: 'An unexpected error has occurred while updating a Launchpad branch. Please report a Launchpad bug and quote: OOPS-2d7687da8991fdcc1d86d2453c3117a4.'>


Should I be worried about my repository's state?

Jelmer Vernooij (jelmer)
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

It looks like this error is being caused by the fact that the remote branch is still locked. This is a bug in Launchpad - it should at least be giving you a better error message.

This doesn't say anything about the state of your repository.

You can probably work around this error by forcibly breaking the lock on the server; this should not be an issue unless you have any other processes actively trying to write to this branch.

Revision history for this message
ilogue (ilogue) wrote :

The remote branch is lp:houston

When I run bzr info lp:houston it doesn't show any locks.

I didn't know about locks so I read this:

I can also still push without any problems, it was just that single commit.
So I have no further issue, I just reported because it told me to :)

William Grant (wgrant)
tags: added: codehosting-ssh lp-code oops
Curtis Hovey (sinzui)
tags: added: timeout
tags: removed: oops
Curtis Hovey (sinzui)
summary: - Fault 380 on bzr push
+ timeout from a locked repo doing bzr push
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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