revids that include periods are interpreted as ranges

[Alexander Belchenko]

Robin Luckey пишет:
> I have found several Bzr repositories with revids that include the substring '..' within them. Although these are single revids, bzr interprets them as revid *ranges*, and thus they cannot be passed as parameters to the bzr command line tools.
> 
> For example, lp:nvda contains such a revid in its first revision:
> 
>     http://bazaar.launchpad.net/~nvda-core-dev/nvda/main/revision/1
> 
> The revid for this revision is:
> 
>     svn-v3-list-QlpoOTFBWSZTWbrL2vUAAB1VgAAQABCAQDrrnqAgAFCgaaGRkxBoTIJ6mmaNRwhndFAoNhZjh_YY4a01fOg1ulgNNC2UrzPdXXEnDpX8XckU4UJC6y9r1A..:dbe06fc7-9119-0410-a01d-9dbf589ecbba:trunk:46
> 
> The '..' substring causes bzr to believe this is a range spec, and thus any command line operations that attempt to use this revid as a parameter will fail:
> 
>     $ bzr log --show-id -v --limit 1 -c 'svn-v3-list-QlpoOTFBWSZTWbrL2vUAAB1VgAAQABCAQDrrnqAgAFCgaaGRkxBoTIJ6mmaNRwhndFAoNhZjh_YY4a01fOg1ulgNNC2UrzPdXXEnDpX8XckU4UJC6y9r1A..:dbe06fc7-9119-0410-a01d-9dbf589ecbba:trunk:46'
>     bzr: ERROR: Option --change does not accept revision ranges
> 
> There are dozens of such revids in this repository, and I have found several other repositories affected by this problem. All of the offending revids appear to have been generated during conversion from Subversion.
> 
> Is there any workaround for this problem? Is there any way to escape these revids or to coerce bzr so that they will not be interpreted as ranges?

Is there any reason why you can't use revision numbers instead?