Issues

Issue #5578 wontfix

Can't pull from read-only private repo (BB-6796)

Antoine Pitrou (Optiflows)
created an issue

I'm trying to pull some changesets from a coworker's repo. Apparently bitbucket is confused and thinks I'm trying to write to that repo:

$ hg pull -r a234e43 ssh://hg@bitbucket.org/d_guillaume/surycat-guillaume
remote: conq: the account owner 'd_guillaume' has exceeded their user limit - write access is disabled to the repository 'surycat-guillaume'.
abandon : no suitable response from remote hg !

This is a pretty big annoyance for our workflow.

Comments (9)

  1. Marcus Bertrand staff

    This is due to a limitation in Mercurial when operating over SSH. We don't have any solution in the works at this time. As a workaround for now, please use https.

    This will be placed on the backlog for future consideration if it can be addressed.

  2. Dmitriy Bolotin

    I have the same problem with our repository.

    $ hg clone ssh://hg@bitbucket.org/milaboratory/mitcr
    remote: conq: the account owner 'milaboratory' has exceeded their user limit - write access is disabled to the repository 'mitcr'.
    abort: no suitable response from remote hg!
    

    It is a problem for us, because our CI server pulls data from repository through ssh using rsa authentification. Is there any other way to solve this problem, except creating a new Bitbucket user for our CI server?

  3. Dylan Etkin

    Hi Antoine,

    I am afraid that we are unable to fix this issue.

    Hg does not allow us to differentiate between the operation you are asking us to perform. We therefore treat all operations as if they will be a write operation.

    Sorry for the trouble, cheers,

    Dylan

  4. Antoine Pitrou (Optiflows) reporter

    Are you sure? I understand hg-ssh only allows you to see the "serve" command, but using some hooks (e.g. pretxnchangegroup) you should be able to filter various kinds of operations. hg-ssh can set some environment variable so that the hook can know which user is trying to do the operation.

  5. Log in to comment