Update fails if branch is empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
I'm using bzr 2.3.3-3 and Win7 32 Bit.
I did the following:
1) run "bzr branch trunk neu -r 0" to create a new branch with no content
2) cd neu
3) bzr update
The result:
=======
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
ValueError: WorkingTree.
bzr 2.3.3 on python 2.6.6 (Windows-
arguments: ['bzr', 'update']
plugins: bzrtools[2.3.1], colo[0.2.1], explorer[1.1.3], fastimport[0.10.0],
launchpad[
news_
svn[1.0.5dev], upload[1.0.0], xmloutput[
encoding: 'cp1252', fsenc: 'mbcs', lang: None
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.
=======
And this is in my .bzr.log:
=======
Thu 2011-06-30 10:37:22 +0200
0.089 bazaar version: 2.3.3
0.089 bzr arguments: [u'update']
0.130 looking for plugins in C:/Users/
0.131 looking for plugins in C:/Program Files/Bazaar/
0.375 encoding stdout as sys.stdout encoding 'cp850'
0.435 opening working tree 'E:/Project/neu'
0.473 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
0.474 Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
ValueError: WorkingTree.
0.477 couldn't find apport bug-reporting library: No module named apport
0.518 Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
IndexError: tuple index out of range
0.524 return code 4
=======
I'm not quite sure if this is the same error from bug #785377, because I did not use merge before, but branch.
Yes, it's the same error, branch is using the same code underneath. If you like, try the same thing in the latest beta, you should get a clear error message rather than a traceback because bug 242175 has landed.