Since we have no firewall or proxy infrastructure in-place that might explain this problem, the last thing I tried is running composer install -no-plugins and voilá: It's installing just fine. Downloading PackageA and PackageB through the browser also works fine. It's always the same package that a particular project gets stuck downloading, but it's not the same (as in ProjectA gets stuck on PackageA, ProjectB gets stuck on PackageB). Running composer install -vvv shows that it literally just gets stuck on some (random) packages. I'm running on macOS Catalina 10.15.3, PHP 7.4.3, Composer 1.10 (tried with 1.9 too), Symfony Flex 1.6.2 and I've tested it with two different projects that are using the very same (private) registry:Įvery time I try to do a fresh full install ( rm -rf vendor/ rm composer.lock composer install -vvv), the installation will ultimately fail/halt due to some packages that can't be downloaded. I've already had a brief conversation with (over on ) about this particular issue I'm currently facing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |