bzr push confused by existing pack file
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I did a bzr push over sftp to savannah. Due to a dropped connection the push failed. I broke the lock forcefully, but I doubt that waiting for the lock to time out would have changed a thing. Full log attached. Subsequent pushes faild this way:
$ bzr push
Using saved push location: sftp://<email address hidden>
Doing on-the-fly conversion from <RepositoryForm
This may take some time. Upgrade the repositories to the same format for better performance.
bzr: ERROR (ignored): GraphIndex('sftp://<email address hidden>
bzr: ERROR: Generic path error: 'dz0ksu1rtwr7m5
Running sftp manually I could see that the file in question did in fact exist. It wasn't mentioned in the pack-names intex, though.
I guess bzr should remove / overwrite the old pack instead of dying.
| Martin von Gagern (gagern) wrote | #1 |
| Robert Collins (lifeless) wrote | #2 |
| Robert Collins (lifeless) wrote | #3 |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: 2a sftp |
So, on SFTP rename-over-the-top fails, and the reason the pack already exists is a dropped SFTP connection during a prior attempt to do the same push. We should indeed remove an existing pack in this case as we're inside the critical section && know its not in use.