Closed andreaskienast closed 1 year ago
I've fixed this very issue by adding the following snippet to src/PackageSelection.php
, line 181:
if ($repo instanceof FilterRepository) {
$repo = $repo->getRepository();
}
However, this didn't solve the issue entirely. While debugging what Composer does I found out that Composer has a map that marks a certain package as "resolved" and thus ignored any other repository. I understand that the current behavior of Satis is somewhat streamlined with Composer, but that breaks our entire case.
We found another way to solve our home-made issue. Sorry for the noise.
Describe the bug In our project, we have a
satis.json
file containing many repositories with the optioncanonical: false
. We need this as we have packages separated by their major version distributed in different repositories. It seems that somewhere between 9d7911b5 and b57a707a all repositories withcanonical: false
are ignored.To Reproduce The most basic satis.json that already fails:
Please note that the repositories are private, but Satis never tries to access them at all anyway.
Outcome
Expected behavior I expect that the mentioned repositories are fetched and archives are downloaded, which worked at least with commit 9d7911b5.
Additional context The project is based on Symfony 5.4, where
composer/satis
is an additional requirement. Runningcomposer satis:build
andbin/satis build
show the same behavior.