[Bug 562380] Re: bzr push from 2a to older format may corrupt branch?

[Launchpad Bug Tracker]

This bug was fixed in the package bzr - 2.1.4-0ubuntu1

---------------
bzr (2.1.4-0ubuntu1) lucid-proposed; urgency=low

  * Update watch file to use 2.1 series.
  * New upstream release.
   + Fix file descriptors leaks in dirstate compiled extension. LP: #583486
   + Refuse to stack on repositories in incompatible formats. LP: #562380
   + Don't delete nested trees/repos. LP: #572098
   + Fix 'bzr switch' crash when a 'ConfigurableFileMerger' is used. LP: #559436
   + Fix compatibility with older smart servers. LP: #528041
   + Fix symlinks addition. LP: #192859
   + Properly unversion children of unversioned directories. LP: #494221
   + Lock configuration files in '~/.bazaar' for updates. LP: #525571
   + Fix 'bzr commit <symlink>'. LP: #128562
   + Fix `lp:` urls when behind an http proxy. LP: #558343
   + Stop using edge.launchpad.net. LP: #583667
 -- Max Bowsher <_ at maxb.eu>   Tue, 17 May 2011 09:54:17 +0100

** Changed in: bzr (Ubuntu Lucid)
       Status: Fix Committed => Fix Released

-- 
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/562380

Title:
  bzr push from 2a to older format may corrupt branch?

Status in Bazaar Version Control System:
  Fix Released
Status in Bazaar 2.0 series:
  Fix Released
Status in Bazaar 2.1 series:
  Fix Released
Status in Launchpad itself:
  Fix Released
Status in “bzr” package in Ubuntu:
  Fix Released
Status in “bzr” source package in Lucid:
  Fix Released

Bug description:
  I had an older branch on launchpad that I did some work on today.
  Somewhere along the line it seems to have gotten corrupted as I now
  get tracebacks when doing bzr log, bzr diff -r latest:1, and several
  other commands. (Will attach .bzr.log for those)

  The launchpad branch is here.  It was not in 2a format when I started
  work this morning but as part of trying to get rid of the tracebacks,
  I pushed the upgrade branch button in launchpad:

    https://code.launchpad.net/~toshio/bzr-gtk/handle-dirty-patches

  The branch I have locally is in 2a format.  I've pushed that to
  another location on launchpad in case it's useful:

    lp:~toshio/bzr-gtk/test-push

  bzr client version 2.0.5

  This is more or less what I've done (reconstructed from my shell's
  history)

      bzr merge # Pull latest revisions in from lp:bzr-gtk
      bzr commit
      vim diff.py # Make a small addition to diff.py
      bzr status
      bzr diff
      bzr commit
      # Decide I should have been more verbose in my comments
      bzr uncommit
      bzr status # Check that my changes are present
      vim diff.py # Add extra comment
      bzr commit
      bzr push # remembered location lp:~toshio/bzr-gtk/handle-patch-fix

  I then checked what was going on on launchpad and found that the web
  viewer wasn't showing the latest revisions so I decided to check what
  the branch showed when I branched it.

      cd ..
      bzr branch lp:~toshio/bzr-gtk/handle-patch-fix
      cd handle-patch-fix
      ls
      bzr log
      # Traceback

  After getting the traceback I tried a variety of things.  It looks
  like things that touch history (bzr diff -r latest:1, bzr log) are
  hitting the corruption.  Things that don't touch history (bzr status,
  bzr info) are not.  I also pressed the button in the launchpad UI to
  upgrade the format as I thought that it migt be something in the on-
  the-fly repository conversion.  (Note: when I branch lp:~toshio/bzr-
  gtk/handle-patch-fix currently, it does not retrieve a 2a format
  branch even though the launchpad UI says the update has finished).