-
Notifications
You must be signed in to change notification settings - Fork 24
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
Package not found #40
Comments
The problem occurred because of the recent changes in #31 |
@edgardmessias do you know why |
The problem occurs because of bower.json in the master contains version. The code
The AliasPackage override LazyCompletePackage in loop |
If run That is, it is a BUG in |
Looks like https://asset-packagist.org/p/bower-asset/scriptaculous-bower/272df73d58bc6d747a9187005aff5cb61e0ddd304020286e3082092f551b26e6.json is still reporting version dev-1.9.0-dev: {
"packages": {
"bower-asset/scriptaculous-bower": {
"1.9.0": {
"uid": 1331895,
"name": "bower-asset/scriptaculous-bower",
"version": "1.9.0",
"version_normalized": "dev-1.9.0-dev",
"type": "bower-asset", |
This change has not been for production. @SilverFire @hiqsol , Do you have date to put this change into production? |
No, it is not deployed yet. Will do it during day |
Sorry, not today, still several things to do. |
Thank you, works as expected. |
I am including the following package
from bower through asset-packagist which used to work since today. Now it gives a message that the package exists but is rejected by composer. I stripped down the
composer.json
toWhen running composer install I am receiving the following error message
This used to work before, if I change the requirement to
^1.8
it works and1.8.1
is installed. The message is kinda weird because 1.9.0 is present and composer even knows about it.Not sure if it is a problem with asset-packagist, but nor the original bower package neither the entry at asset-packagist.org have changed lately.
The text was updated successfully, but these errors were encountered: