bzr revno fails when tip is in the fallback repository

[Christophe Lyon]

Hello,
I have a problem with bzr on the gcc repo in launchpad.

$ bzr revno lp:~christophe-lyon/gcc/4.8-disable-peeling2
bzr: ERROR: Server sent an unexpected error: ('error', 'GhostRevisionsHaveNoRevno', 'Could not determine revno for {svn-v4:138bc75d-0d04-0410-961f-82ee72b054a4:trunk:196812} because its ancestry shows a ghost at {svn-v4:138bc75d-0d04-0410-961f-82ee72b054a4:trunk:196812}')
$ bzr --version
Bazaar (bzr) 2.5.1
Python interpreter: /usr/bin/python 2.7.3

The host is running Ubuntu 12.04 (x86_64).

As discussed on IRC,
$ bzr revno nosmart+lp:~christophe-lyon/gcc/4.8-disable-peeling2
122393
works.

[Matthew Fuller (fullermd)]

This is almost surely something to do with the smart RPC calls 'revno' makes. As mentioned on IRC, bzr 2.1.4 works, which I'm pretty sure is early enough that it's doing mostly (all?) VFS calls rather than smart RPC calls. The nosmart+ addition making it works points in the same direction.

[Paul Collins (pjdc)]

This also happens with "bzr revno lp:charms/trusty/rabbitmq-server", yielding

bzr: ERROR: Server sent an unexpected error: ('error', 'GhostRevisionsHaveNoRevno', 'Could not determine revno for {<email address hidden>} because its ancestry shows a ghost at {<email address hidden>}')

[Ryan Beisner (1chb1n)]

We see this in our OpenStack charm testing. The nosmart+ workaround seems to work, but it is less than ideal to maintain in automated testing.

Example, branches affected: http://paste.ubuntu.com/10628031/

ubuntu@beisner-bastion:~$ uname -a
Linux beisner-bastion 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@beisner-bastion:~$ dpkg-query --show bzr python
bzr 2.6.0+bzr6593-1ubuntu1.1
python 2.7.5-5ubuntu3

ubuntu@beisner-bastion:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty

[Brad Crittenden (bac)]

While far from ideal, if you can upload to a problem branch, making a trivial change to the branch and pushing it back to Launchpad may solve the problem.

[Jelmer Vernooij (jelmer)]

Does anybody still have a branch they can reproduce this with?

[Launchpad Janitor (janitor)]

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