authorization failed messages for successful push

Issue #11117 closed
Robin Becker created an issue

Yesterday I started to get messages abort: authorization failed messages for hg push even when the push succeeds. My colleague also had the same experience; this happens on various /rptlab/repos for me replabrobin. Example commands

C:\code\hg-repos\preppy>hg ci -m"remove some space; bump version to 2.3.4"

C:\code\hg-repos\preppy>hg push
pushing to https://bitbucket.org/rptlab/preppy
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
abort: authorization failed

C:\code\hg-repos\preppy>hg out
comparing with https://bitbucket.org/rptlab/preppy
searching for changes
no changes found

C:\code\hg-repos\preppy>hg --version
Mercurial Distributed SCM (version 3.3.2)
(see http://mercurial.selenic.com for more information)

Copyright (C) 2005-2014 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

this 'aborted' push is actually 8b905ca.....

A debug push to /rptlab/reportlab de929ae.... with a slightly older client

C:\code\hg-repos\reportlab\tests>hg push --debug
pushing to https://bitbucket.org/rptlab/reportlab
using https://bitbucket.org/rptlab/reportlab
sending capabilities command
using auth.bitbucket.* for authentication
bitbucket.org certificate successfully verified
query 1; heads
sending batch command
using auth.bitbucket.* for authentication
searching for changes
all remote heads known locally
sending branchmap command
using auth.bitbucket.* for authentication
sending branchmap command
using auth.bitbucket.* for authentication
preparing listkeys for "bookmarks"
sending listkeys command
using auth.bitbucket.* for authentication
3 changesets found
list of changesets:
7b766b1ce59a05cca4d47a937afa51446349ef25
f0bfab1d9277116c8924dd8d04ad0fd8e91aaf74
de929aeece0244ac32124083abce07844173e39e
bundling: 1/3 changesets (33.33%)
bundling: 2/3 changesets (66.67%)
bundling: 3/3 changesets (100.00%)
bundling: 1/3 manifests (33.33%)
bundling: 2/3 manifests (66.67%)
bundling: 3/3 manifests (100.00%)
bundling: .hgignore 1/5 files (20.00%)
bundling: reportlab/platypus/tables.py 2/5 files (40.00%)
bundling: src/reportlab/__init__.py 3/5 files (60.00%)
bundling: src/reportlab/platypus/tables.py 4/5 files (80.00%)
bundling: src/reportlab/rl_config.py 5/5 files (100.00%)
sending unbundle command
sending 18572 bytes
using auth.bitbucket.* for authentication
sending: 18/36 kb (50.00%)
sending: 18/36 kb (50.00%)
[HgKeyring] Keyring URL: https://bitbucket.org/rptlab
[HgKeyring] Username found in .hg/hgrc: replabrobin
[HgKeyring] Looking for password for user replabrobin and url https://bitbucket.org/rptlab
[HgKeyring] Keyring password found. Url: https://bitbucket.org/rptlab/reportlab, user: replabrobin, passwd: ************
********
using auth.bitbucket.* for authentication
bitbucket.org certificate successfully verified
sending: 36/36 kb (100.00%)
sending: 36/36 kb (100.00%)
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 3 changesets with 6 changes to 5 files
preparing listkeys for "phases"
sending listkeys command
using auth.bitbucket.* for authentication
preparing pushkey for "phases:7b766b1ce59a05cca4d47a937afa51446349ef25"
sending pushkey command
sending 0 bytes
using auth.bitbucket.* for authentication
[HgKeyring] Keyring URL: https://bitbucket.org/rptlab
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/rptlab/reportlab, user: replabrobin, passwd: ************
********
using auth.bitbucket.* for authentication
bitbucket.org certificate successfully verified
abort: authorization failed
^^^^^^^^^^^^^^^^^^^^^^^^^^^ 

Official response

  • Amber Van Hecke staff

    After much consideration, we’ve decided to remove Mercurial support from Bitbucket Cloud and the API. Mercurial support will be officially removed on June 1, 2020.

    The decision to deprecate was not easy as we knew there were customers (like yourselves) who were currently using Mercurial for versioning their code. Ultimately we concluded that sunsetting Mercurial support will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.

    That said, if any critical Mercurial issues arise over the coming months, please reach out to our support team. Our goal is to continue offering the same Mercurial experience you have today, until June 1, 2020.

    Read on to learn more about what led to this decision, timeline, and migration resource support.

Comments (4)

  1. Amber Van Hecke staff

    After much consideration, we’ve decided to remove Mercurial support from Bitbucket Cloud and the API. Mercurial support will be officially removed on June 1, 2020.

    The decision to deprecate was not easy as we knew there were customers (like yourselves) who were currently using Mercurial for versioning their code. Ultimately we concluded that sunsetting Mercurial support will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.

    That said, if any critical Mercurial issues arise over the coming months, please reach out to our support team. Our goal is to continue offering the same Mercurial experience you have today, until June 1, 2020.

    Read on to learn more about what led to this decision, timeline, and migration resource support.

  2. Log in to comment