Crashed on 'Update to this revision'

Bug #755006 reported by Vadim Peretokin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Expired
Undecided
Unassigned
QBzr
Incomplete
Undecided
Unassigned

Bug Description

Using 1.1.2:

Run command: bzr update -r revid:<email address hidden>
bzr: ERROR: bzrlib.errors.NoSuchRevision: BzrBranch7(file:///home/vadi/Systems/vadi-mapper/) has no revision <email address hidden>

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 926, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 1126, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 691, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 713, in run
    return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/cleanup.py", line 135, in run_simple
    self.cleanups, self.func, *args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/cleanup.py", line 165, in _do_with_cleanups
    result = func(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/qbzr/lib/commands.py", line 788, in run
    return run_subprocess_command(cmd, bencoded)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/qbzr/lib/subprocess.py", line 888, in run_subprocess_command
    return commands.run_bzr(argv)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 1126, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 691, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/pymodules/python2.6/bzrlib/commands.py", line 713, in run
    return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/cleanup.py", line 135, in run_simple
    self.cleanups, self.func, *args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/cleanup.py", line 165, in _do_with_cleanups
    result = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/builtins.py", line 1419, in run
    revno = branch.revision_id_to_dotted_revno(revision_id)
  File "/usr/lib/pymodules/python2.6/bzrlib/decorators.py", line 140, in read_locked
    result = unbound(self, *args, **kwargs)
  File "/usr/lib/pymodules/python2.6/bzrlib/branch.py", line 377, in revision_id_to_dotted_revno
    return self._do_revision_id_to_dotted_revno(revision_id)
  File "/usr/lib/pymodules/python2.6/bzrlib/branch.py", line 397, in _do_revision_id_to_dotted_revno
    raise errors.NoSuchRevision(self, revision_id)
NoSuchRevision: BzrBranch7(file:///home/vadi/Systems/vadi-mapper/) has no revision <email address hidden>

You can report this problem to Bazaar's developers by running
    apport-bug /var/crash/bzr.1000.2011-04-08T20:16.crash
if a bug-reporting window does not automatically appear.

affects: bzr-explorer → bzr
Revision history for this message
Martin Pool (mbp) wrote :

Hi,

I'm sorry you hit this problem.

bzr 1.1.2 is ancient. Please upgrade to 2.3 or 2.4beta, and let us know if the problem recurs. If you have trouble upgrading, just ask.

Changed in bzr:
status: New → Incomplete
Revision history for this message
Vadim Peretokin (vperetokin) wrote :

I'm subscribed to the PPA and have:

$ bzr --version
Bazaar (bzr) 2.3.1

installed. I was using the bzr explorer at the time that error occured.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 755006] Re: Crashed on 'Update to this revision'

Can you tell us how you ran that command? Did you type or paste that
revision id by hand, or did it come out of bzr explorer somehow?

Martin

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

It came out of bzr explorer - I used the UI and selected the update menu
entry somewhere.

Revision history for this message
Alexander Belchenko (bialix) wrote :

Vadim Peretokin пишет:
> It came out of bzr explorer - I used the UI and selected the update menu
> entry somewhere.

It seems you have invoked the update menu from the log window, qbzr's
qlog. qlog can show you log for multiple branches, in this case you
might try to update your current branch to revision from another
branch. Can you confirm it was your case? Have you invoked qlog from
shared repository folder maybe?

Give us more details on what's going on, please.

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

On Wed, Apr 20, 2011 at 1:53 AM, Alexander Belchenko <email address hidden> wrote:

> Vadim Peretokin пишет:
> > It came out of bzr explorer - I used the UI and selected the update menu
> > entry somewhere.
>
> It seems you have invoked the update menu from the log window, qbzr's
> qlog. qlog can show you log for multiple branches, in this case you
> might try to update your current branch to revision from another
> branch. Can you confirm it was your case? Have you invoked qlog from
> shared repository folder maybe?
>
>
Yeah, that was probably the case. I was confused how updating works and was
tired of merging each time someone else changed their branch, wihch resulted
in a bunch of deletions and reinsertions... it worked, but it looked wrong.
So this time, since I had no local changes, I tried updating from the main
branch. (lp:vadi-mapper, although quite often bzr seems to think that the
main one is another branch someone did that's never updated) and got this
error.

> Give us more details on what's going on, please.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/755006
>
> Title:
> Crashed on 'Update to this revision'
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/755006/+subscribe
>

Revision history for this message
Alexander Belchenko (bialix) wrote :

So, I think you don't want `Update to XXX` actually, but perhaps 'Pull this revision' action.
It does not mean this bug is incorrect though. But perhaps we need to handle this error in qlog itself.

But I think bzr should not die with traceback anyway.

Revision history for this message
Alexander Belchenko (bialix) wrote :

I've tried to reproduce it with the following simple steps:

C:\Temp\1>bzr init a
Created a standalone tree (format: 1.14)

C:\Temp\1\a>bzr mkdir foo
added foo

C:\Temp\1\a>bzr ci -m 1
Committing to: C:/Temp/1/a/
added foo
Committed revision 1.

C:\Temp\1>bzr branch a b
Branched 1 revision(s).

C:\Temp\1\b>bzr mkdir bar
added bar

C:\Temp\1\b>bzr ci -m2
Committing to: C:/Temp/1/b/
added bar
Committed revision 2.

C:\Temp\1>bzr qlog a b

And I've tried to update 'a' branch to 'b' tip. I've got the following message in qupdate dialog:

Run command: bzr update -r revid:<email address hidden>
bzr: ERROR: branch has no revision <email address hidden>
bzr update --revision only works for a revision in the branch history

But there is no traceback though.

Changed in qbzr:
status: New → Incomplete
Revision history for this message
Alexander Belchenko (bialix) wrote :

Vadim, I'm not sure how to reproduce your traceback. If you can describe the exact steps you did it may help.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Bazaar because there has been no activity for 60 days.]

Changed in bzr:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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