[Bug 796375] Re: bzr crashed with ValueError in set_root_id(): WorkingTree.set_root_id with fileid=None

[Apport retracing service]

*** This bug is a duplicate of bug 733789 ***
    https://bugs.launchpad.net/bugs/733789

Thank you for taking the time to report this crash and helping to make
Ubuntu better.  This particular crash has already been reported and is a
duplicate of bug #733789, so is being marked as such.  Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Attachment removed: "Dependencies.txt"
   https://bugs.launchpad.net/bugs/796375/+attachment/2166883/+files/Dependencies.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/796375/+attachment/2166884/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/796375/+attachment/2166885/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 733789
   bzr crashed with ValueError in set_root_id()

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

Title:
  bzr crashed with ValueError in set_root_id(): WorkingTree.set_root_id
  with fileid=None

Status in “bzr” package in Ubuntu:
  New

Bug description:
  Binary package hint: bzr

  I don't know much about bzr, so I'll just describe what I was doing,
  and the setup. I have this project that I want to release eventually,
  and I was just changing the repository scheme from something personal
  to something more conducive to sharing. I guess when you're replanting
  trees, they have a tendency to fall on you.

   I created three new branches in a single shared repository: the
  actual tree "release", then a branch from that called "trunk", then a
  third branch from trunk called "my". I then proceeded to make changes
  to the "my" branch. Specifically, I did "bzr merge -r1
  /filesystem/oldbranch", from the original, non-shared stacked-branch
  of the original tree. (That is, it had another parent tree, but it
  also had the only copy of the recent changes that I wanted to
  incorporate into the new branch.)

  Then, when I ran 'bzr update' inside of the "my" branch, bzr crashed.
  I have no clue what went wrong. However, I was able to commit my
  changes to the my branch, and if I can successfully merge them
  upstream, then I'll be happy. Of course, if I can't update my branch
  after the project goes public, I'll have some issues. Maybe I'll need
  to replant again.

  P.S. I am pretty certain that I was bending not only this
  implementation of bzr, but also its design intentions.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: bzr 2.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  BzrDebugFlags: set()
  BzrVersion: 2.3.1
  CommandLine: ['/usr/bin/bzr', 'update']
  CrashDb: bzr
  Date: Sun Jun 12 18:15:35 2011
  ExecutablePath: /usr/bin/bzr
  FileSystemEncoding: UTF-8
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  InterpreterPath: /usr/bin/python2.7
  Locale: en_US.UTF-8
  PackageArchitecture: all
  Platform: Linux-2.6.38-8-generic-i686-with-Ubuntu-11.04-natty
  ProcCmdline: /usr/bin/python /usr/bin/bzr update
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  PythonVersion: 2.7.1
  SourcePackage: bzr
  Title: bzr crashed with ValueError in set_root_id(): WorkingTree.set_root_id with fileid=None
  UpgradeStatus: Upgraded to natty on 2011-05-18 (25 days ago)
  UserEncoding: UTF-8
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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