Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't install packages with contao-manager when I have a private package in my composer.json #826

Open
biowebfr opened this issue Oct 18, 2024 · 5 comments

Comments

@biowebfr
Copy link

Contao Manager v1.8.9.

Contao-manager throws me an error when trying to install a package when I have a non-related private package installed:
image

But I don't get any error when not using contao-manager.phar.php but directly composer like so:

composer require markocupic/contao-altcha-antispam --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

Here is my composer.json part with my private package:

     "repositories": [
       {
             "type": "git",
             "url": "[email protected]:BioWeb-git/bioweb-bundle.git"
         }
     ],
     "require": {
         "bioweb/bioweb-bundle": "dev-master",
         ....
      },

Please note that I'm under windows 11, and a colleague of mine doesn't seem to have the issue under MacOS.

@zoglo
Copy link
Member

zoglo commented Oct 18, 2024

Works fine for me if I am using a PAT + the url to the repo.

Did you try using:https://github.com/BioWeb-git/bioweb-bundle.git instead?

@biowebfr
Copy link
Author

Thanks for your answer.

I use PAT too, but the error persists:

image

image

@zoglo
Copy link
Member

zoglo commented Oct 18, 2024

Did you try disabling the composer cloud?

@biowebfr
Copy link
Author

biowebfr commented Oct 21, 2024

Thank you for your answer.

It was already disabled. I tried with it enable and same error.

@aschempp
Copy link
Member

It will not work with the cloud, but it should work locally.

The most likely reason I can think of, is that your web server is not running as the same user as your CLI, and might not have the SSH keys to access the private repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants