Proper warning on reused UUIDs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
I discovered this while trying to reproduce an error where bzr-svn was erroneously saying that I needed to set append_
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/Users/
return the_callable(*args, **kwargs)
File "/Users/
ret = run(*run_argv)
File "/Users/
return self.run(
File "/Users/
return self._operation
File "/Users/
self.cleanups, self.func, *args, **kwargs)
File "/Users/
result = func(*args, **kwargs)
File "/Users/
exclude=
File "/Users/
result = unbound(self, *args, **kwargs)
File "/Users/
result = WorkingTree3.
File "/Users/
result = unbound(self, *args, **kwargs)
File "/Users/
*args, **kwargs)
File "/Users/
possible_
File "/Users/
self.cleanups, self.func, self, *args, **kwargs)
File "/Users/
result = func(*args, **kwargs)
File "/Users/
self.
File "/Users/
self.
File "/Users/
overwrite=
File "/Users/
override_
File "/Users/
revid = builder.
File "/Users/
return unbound(*args, **kwargs)
File "/Users/
(revid, self._new_
AssertionError: Unexpected revision id <email address hidden> != <email address hidden>
bzr 2.2.0dev1 on python 2.6.1 (Darwin-
arguments: ['/Users/
encoding: 'UTF-8', fsenc: 'utf-8', lang: 'en_US.UTF-8'
plugins:
bookmarks /Users/
bzrtools /Users/
colo /Users/
disable_pycurl /Users/
email /Users/
externals /Users/
grep /Users/
keychain /Users/
launchpad /Users/
netrc_
news_merge /Users/
qbzr /Users/
rewrite /Users/
svn /Users/
*** 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.
Related branches
Changed in bzr-svn: | |
milestone: | none → 1.0.4 |
Changed in bzr-svn: | |
status: | Triaged → Fix Committed |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in bzr-svn: | |
status: | Fix Committed → Fix Released |
I'm not quite sure what causes this yet, but it might be related to the caching issues you were reporting on the mailing list this week.