Bazaar

ERROR: Revision ... not present in ... trying to branch libsndfile repository

Bug #216533 reported by Wesley J. Landaker
This bug report is a duplicate of:  Bug #177874: upgrading to rich-root-pack fails. Edit Remove
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Undecided
Unassigned

Bug Description

It's possible this is a duplicate, but none of the others seem to match. I get this failure (not a crash) when I try to branch the libsndfile public repository, e.g.:

$ bzr version
Bazaar (bzr) 1.3
  Python interpreter: /usr/bin/python 2.4.5.final.0
  Python standard library: /usr/lib/python2.4
  bzrlib: /usr/lib/python2.4/site-packages/bzrlib
  Bazaar configuration: /home/wjl/.bazaar
  Bazaar log file: /home/wjl/.bzr.log

Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
http://bazaar-vcs.org/

bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.
$ bzr init-repo --rich-root .
$ bzr branch http://www.mega-nerd.com/Bzr/libsndfile-pub
http://www.mega-nerd.com/Bzr/libsndfile-pub is permanently redirected to http://www.mega-nerd.com/Bzr/libsndfile-pub/
bzr: ERROR: Revision {<email address hidden>} not present in "86/tree_root-20070514095449-84ho81zmb73q7q7y-1.kndx".
/usr/lib/python2.4/site-packages/bzrlib/lockable_files.py:110: UserWarning: file group LockableFiles(<bzrlib.transport.http._pycurl.PyCurlTransport url=http://www.mega-nerd.com/Bzr/libsndfile-pub/.bzr/repository/>) was not explicitly unlocked
  warn("file group %r was not explicitly unlocked" % self)

I also tried with --rich-root-pack and got a *different* failure, but I see that has already been reported.

Revision history for this message
Andrew Bennetts (spiv) wrote :

I can't reproduce this with bzr.dev. Can you try upgrading to 1.4.1rc1?

Changed in bzr:
status: New → Incomplete
Revision history for this message
Andrew Bennetts (spiv) wrote :

Oops, yes I can. (I forgot to do the "bzr init-repo --rich-root" the first time around)

Changed in bzr:
status: Incomplete → Confirmed
Revision history for this message
Wesley J. Landaker (wjl) wrote :

FWIW, the reason I used --rich-root was because when I tried it in a --rich-root-pack directory it failed and when I went to report that (which got a different error), I saw that was a known bug. I didn't see a bug on normal --rich-root reported, so hence this report.

Anyway, I ended up just trying a normal pack-0.92 repository and it finally worked, so it's not a show stopper, but I *always* use --rich-root-pack and have never had trouble until now, so it's surprising.

Revision history for this message
Andrew Bennetts (spiv) wrote :

Probably a duplicate of bug 177874?

Revision history for this message
Wesley J. Landaker (wjl) wrote :

Maybe it's a duplicate of that, but I'm not sure about that. If you try with --rich-root-pack you get a failure and if you try with --rich-root you get a failure, but the error messages are DIFFERENT. Of course, it's possible they have the same underlying cause.

Anyway, marking this as a duplicate is probably okay as long as when one is fixed, the other is fixed as well. =)

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 216533] Re: ERROR: Revision ... not present in ... trying to branch libsndfile repository

Wesley J. Landaker пишет:
> *** This bug is a duplicate of bug 177874 ***
> https://bugs.launchpad.net/bugs/177874
>
> Maybe it's a duplicate of that, but I'm not sure about that. If you try
> with --rich-root-pack you get a failure and if you try with --rich-root
> you get a failure, but the error messages are DIFFERENT. Of course, it's
> possible they have the same underlying cause.
>
> Anyway, marking this as a duplicate is probably okay as long as when one
> is fixed, the other is fixed as well. =)

Yes, of course, you're right. Once bugfix 177874 will be ready you may test
it to ensure that your bug is also fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.