point out the backup if the upgrade fails

Bug #185180 reported by James Westby
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Triaged
Medium
Unassigned

Bug Description

From Bruce Korb on the mailing list.

I was trying to follow directions:

$ bzr update
Working tree format 3 is deprecated and a better format is available.
It is recommended that you upgrade by running the command
  bzr upgrade file:///share/st/devbk/simple-cdd-0.3.5/
Tree is up to date at revision 405.
$ bzr upgrade file:///share/st/devbk/simple-cdd-0.3.5/
starting upgrade of file:///share/st/devbk/simple-cdd-0.3.5/
making backup of tree history
file:///share/st/devbk/simple-cdd-0.3.5/.bzr has been backed up to
file:///share/st/devbk/simple-cdd-0.3.5/.bzr.backup
if conversion fails, you can move this directory back to .bzr
if it succeeds, you can remove this directory if you wish
bzr: ERROR: Could not acquire lock [Errno 37] No locks available
/usr/lib/python2.4/site-packages/bzrlib/lock.py:79: UserWarning: lock
on <open file u'/share/st/devbk/simple-cdd-0.3.5/.bzr/checkout/dirstate',
mode 'wb+' at 0xb7c3a0f8> not released
  warn("lock on %r not released" % self.f)
=====================
At this point, I did a number of things to investigate why I could not
get the lock. It turns out, I did a ``yum install'' as root (because you
have to do that as root) and so the lock files were owned by and
only modifiable by root. Oops. (Not your issue, tho.) Meanwhile,
the ``if conversion fails, you can move this directory back'' comment
was pages and pages back in my scroll history and not quite scrolled
off yet. Good thing because future attempts:
======================
$ bzr upgrade file:///share/st/devbk/simple-cdd-0.3.5/
starting upgrade of file:///share/st/devbk/simple-cdd-0.3.5/
making backup of tree history
bzr: ERROR: File exists:
u'/share/st/devbk/simple-cdd-0.3.5/.bzr.backup': [Errno 17] File
exists: '/share/st/devbk/simple-cdd-0.3.5/.bzr.backup'
======================
don't give you that hint. Hint: it would be a good idea to repeat the hint :)
It would have avoided this missive.

Thanks - Bruce

Martin Pool (mbp)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Martin Pool (mbp) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

  tags upgrade
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklv36AACgkQPGPKP6Cz6Itu5wCfcqS5a8EO156W30pirU8LNa8L
3rkAnRpx+USnQFfxsNN+6qo5rg/ka+lf
=MVlU
-----END PGP SIGNATURE-----

Jelmer Vernooij (jelmer)
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
tags: added: simple
Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

I can't find this error message anywhere in brz source now. The only mention of failed conversion is in the help for `brz upgrade`. I think that this bug can be closed as being no longer applicable.

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.