Another case of "checksum mismatch"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Triaged
|
High
|
Unassigned |
Bug Description
I'm encountering another “checksum mismatch” issue that may or may not be related to this one, but is certainly not related to the one I had before. Error message:
bzr: ERROR: checksum mismatch: 'c5cdb6209aac60
zsh: exit 3 bzr up
Log section:
Thu 2010-12-23 20:01:23 +0100
0.040 bazaar version: 2.2.0
0.040 bzr arguments: [u'up']
0.051 looking for plugins in /home/lalo/
0.084 looking for plugins in /usr/lib/
0.090 encoding stdout as sys.stdout encoding 'UTF-8'
0.125 opening working tree '/repo/
0.157 bzr-svn: using Subversion 1.6.13 ()
0.456 Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
old_tip = branch.
File "/usr/lib/
result = unbound(self, *args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib/
possible_
File "/home/
stop_revision, overwrite, limit=limit)
File "/home/
project=
File "/home/
pack_hint = self._fetch_
File "/home/
use_
File "/home/
parent_revmeta)
File "/home/
report_
File "/home/
return unbound(*args, **kwargs)
File "/home/
reporter.
File "/home/
if self._last_progress > progress:
File "/home/
if self._last_progress > progress:
File "/home/
if self._last_progress > progress:
File "/home/
return self._apply_
File "/home/
self.
TextChecksumMis
0.456 Transferred: 14kB (46.3kB/s r:0kB w:0kB u:14kB)
0.456 return code 3
What I believe happens is that two of the revisions committed by other developers today weren't committed in the “root” of the project source tree, and so bzr-svn/subvertpy doesn't see one or both of those revisions as being part of the ancestry. Looking at the commit on trac, it gives the “location” as branches/
I committed revision 44073, using bzr-svn, then my colleague committed 44074 which had the trailing path in the location, then I tried to “bzr up” and it said I was already up to date, at which point I started expecting trouble later. Then I committed 44075-79 and 44091, which were fine because no files conflicted with '74, then he committed 44092 and now I can neither update or commit.
I tried this with 1.0.4 (rel), trunk (branch), and 1.1 (branch), because I remembered something about there being already a fix for this, but although the symptoms look similar, it's apparently a rather different problem.
Changed in bzr-svn: | |
milestone: | none → 1.1.0 |
Changed in bzr-svn: | |
milestone: | 1.1.0 → 1.1.1 |
On Thu, 2010-12-23 at 19:21 +0000, Lalo Martins wrote: 38ac50f695fd679 6d6' != '4fe50dc7365f7b 45a45967f4ff488 f01' in branches/ news_and_ event_publishin g:44092
> Public bug reported:
>
> I'm encountering another “checksum mismatch” issue that may or may not
> be related to this one, but is certainly not related to the one I had
> before. Error message:
>
> bzr: ERROR: checksum mismatch: 'c5cdb6209aac60
> zsh: exit 3 bzr up
Have you tried this in a clean branch? The main issue with this kind of
error is broken data in the existing repository.
Cheers,
Jelmer