Ezio Melotti added the comment:

> (FTR, the Bitbucket https URIs are not private, this may be yet another bug.)

This should be fixed with ebed4eccab36.

The error reported by the tracker was "('invalid token', 90)", and was caused 
by:

>>> old = 'max(ancestors(branch("%s")))-outgoing("%s"))' % (patchbranch, base)
>>> commands.diff(repo.ui, repo, rev=[old, patchbranch])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 2319, in 
diff
    node1, node2 = scmutil.revpair(repo, revs)
  File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py", line 497, in 
revpair
    l = revrange(repo, revs)
  File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py", line 549, in 
revrange
    m = revset.match(repo.ui, spec)
  File "/usr/lib/python2.7/dist-packages/mercurial/revset.py", line 1046, in 
match
    raise error.ParseError(_("invalid token"), pos)
mercurial.error.ParseError: ('invalid token', 90)

The problem was an extra ')', and 
http://mail.python.org/pipermail/python-dev/2011-November/114704.html told me 
which one had to be removed.  Bitbucket remote repos should now work.

----------
nosy: +ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue414>
_______________________________________________________
_______________________________________________
Tracker-discuss mailing list
Tracker-discuss@python.org
http://mail.python.org/mailman/listinfo/tracker-discuss

Reply via email to