V
V
Vit2018-12-23 21:19:09
git
Vit, 2018-12-23 21:19:09

How to fix error in Composer: "Package information from this repository may be outdated"?

There is a public repository on Bitbucket.org
In composer.json it is written:

"repositories": [
        {
            "type": "vcs",
            "url": "https://[email protected]/xxx/package.git"
        }
    ],

Through composer, everything was updated normally until some point. A week ago, an error began to appear in composer:
Failed to update https://[email protected]/xxx/package.git, package information from this repository may be outdated

Couldn't google anything about this error. Can you help me understand what is wrong?
Addendum:
I tried to remove and reinstall the package, got another error:
[RuntimeException]
Failed to execute git clone --no-checkout ' https://[email protected]/xxx/package.git ' '/home/site.ru/dev/vendor/package/package' && cd '/ home/site.ru/dev/vendor/package/package' && git remote a dd composer ' https://[email protected]/xxx/package.git ' && git fetch composer
error: Cannot communicate securely with peer: no common encryption algorithm(s). while accessing https://[email protected]/xxx/package.git/info/refs
fatal: HTTP request failed

Answer the question

In order to leave comments, you need to log in

2 answer(s)
V
Vit, 2018-12-23
@reech

Found the cause: Bitbucket disable support for TLSv1 and TLSv1.1 ef... .

Bitbucket Cloud will be disabling support for TLSv1 and TLSv1.1 effective 1 December 2018.
This will affect all HTTPS traffic to Bitbucket, including:
Git or Mercurial traffic to bitbucket.org
The bitbucket.org Web interface
API calls to api.bitbucket.org
Hosted sites on bitbucket.io
Any other HTTPS traffic not listed here
You should be able to test your connection from the command line:
GIT_CURL_VERBOSE=1 git ls-remote https://bitbucket.org/
This will connect to Bitbucket using the Git client and list the connection parameters. if you see a line like “SSL connection using TLSv1.2” in the output, then you are unaffected; if that line mentions a different version of TLS, then you are affected.

A
Alexander Apokin, 2019-09-04
@apokin

Also, this error can occur if the access rights to the key are incorrect. In case of using a private repository.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question