[Bug 701940] Re: Pack moved to obsolete_packs, but still referenced in pack-names

[Martin Packman]

** Tags added: affects-twisted

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bzr in Ubuntu.
https://bugs.launchpad.net/bugs/701940

Title:
  Pack moved to obsolete_packs, but still referenced in pack-names

Status in Bazaar Version Control System:
  Fix Released
Status in Bazaar 2.2 series:
  Fix Released
Status in Bazaar 2.3 series:
  Fix Released
Status in “bzr” package in Ubuntu:
  Fix Released
Status in “bzr” source package in Maverick:
  Fix Released

Bug description:
  Using bzr 2.2.2 and bzr-svn 1.0.4 on ext3, 'bzr update' of a checkout
  of svn://svn.twistedmatrix.com/svn/Twisted/trunk began to fail
  starting with this error:

  Unable to obtain lock file:///var/lib/buildbot/twisted/ held by buildbot
  at illidan [process #11682], acquired 0 seconds ago.
  Will continue to try until 15:47:11, unless you press Ctrl-C.
  See "bzr help break-lock" for more.
  bzr: ERROR: No such file: u'/var/lib/buildbot/twisted/.bzr/repository/packs/49ef04533e5410f03a9e1f78b25083b0.pack': [Errno 2] No such file or directory: u'/var/lib/buildbot/twisted/.bzr/repository/packs/49ef04533e5410f03a9e1f78b25083b0.pack'

  The build system proceeded to delete the checkout and on subsequent
  build attempts tried to do a new checkout, using the same shared
  repository.  Those checkouts all failed with just:

  bzr: ERROR: No such file:
  u'/var/lib/buildbot/twisted/.bzr/repository/indices/49ef04533e5410f03a9e1f78b25083b0.rix':
  [Errno 2] No such file or directory:
  u'/var/lib/buildbot/twisted/.bzr/repository/indices/49ef04533e5410f03a9e1f78b25083b0.rix'

  maxb had me check for a corresponding pack file and I found it in
  obsolete_packs/ alongside all of the index files.  Once those were
  moved to packs/ and indices/ respectively, the checkout was able to
  succeed.

  There was an interval of about six hours between the last working
  update and the first failing update, with no intervening system
  crashes/reboots/etc.

  Since this was all part of an automated system, I didn't have a chance
  to see what process might have been holding the lock referenced in the
  first failure message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzr/+bug/701940/+subscriptions