-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Branch aliases are broken for replacements #2626
Comments
ping |
Not sure if related but I have been having trouble requiring an exact package version based on the git hash ( |
@kbond This has nothing to do with this issue. the reference locking is not an alias at all. and it is logical that it uses the dev-master metadata. It is only a hack at the level of the git installation (which also means that a dist download would not use this reference locking). You should avoid using such locking whenever possible |
I see, so it only works correctly if I include the package as a "custom" repository? |
no, it only works fine if the dependencies of dev-master are the same (or at least compatible) with the dependencies you expect, and you install from source. The reference locking has no impact at all on the dependency resolution |
This doesn't seem to be an issue at all (see FriendsOfSymfony/FOSRestBundle#656 and FriendsOfSymfony/FOSRestBundle#705). |
@xabbuh It is an issue. FOSRestBundle simply managed to find a workaround. but it is still broken. I even managed to write a testcase reproducing it (see the linked PR) |
@xabbuh to be clear, FOSRestBundle should not need to explicitly alias |
@stof I understand what you mean. But as far as I can see, the problem is with the symfony/framework-bundle dependencies which don't require self.version but |
@xabbuh No. Requiring |
@stof But how should that work? |
@xabbuh the requirement on symfony/symfony allows to install |
@stof I was confused since FOSRestBundle doesn't require |
@xabbuh hmm, in their case, they are indeed not requiring it (which also means that they are not really testing against Symfony 2.2 as the 2.4 packages will match the dependencies of FrameworkBundle 2.2 and be used). But there is still a bug in composer anyway |
@stof Yes, I can confirm the bug. It's easily reproducable with a {
"require": {
"symfony/framework-bundle": "dev-master",
"symfony/symfony": "dev-master"
}
} Works with Composer 1.0.0-alpha7 but not with 1.0.0-alpha8. |
@xabbuh yeah indeed. And it is exactly what the testcase I submitted is doing |
@stof Ah, didn't see the test case yet. Sorry for the confusion. |
Please see #2805 for a potential fix. |
It looks like a replacement does not replace the aliased version anymore based on the branch alias: https://travis-ci.org/FriendsOfSymfony/FOSJsRoutingBundle/jobs/17469579
The text was updated successfully, but these errors were encountered: