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
A bug with virtual packages #756
Comments
|
Same thing happens also with the package |
|
A workaround for affected users is to avoid the package versions currently provided by packagist: fxpio/composer-asset-plugin#268 (comment) |
|
I just have registered:
to reserve the vendor namespaces on packagist. |
|
OK I'll make sure to cleanup the files for those bower-asset/punycode & jquery packages. I guess now that you block the vendor name it's safe and won't happen again. |
|
@Seldaek Thanks! |
Coming from here, I think this is the right place for this report:
Besides the issues it caused for users of the composer-asset-plugin, there are some bugs on the packagist platform itself:
bower-asset/jquerypackage on packagist. Even though there is avirtual package with that name and this newly registered version does not show up in the interface,
it has two versions listed in the package info json:
https://packagist.org/p/bower-asset/jquery%242fab1ac0b638d1cc9c9b51a810c84229e91af63a84e7f1c44cf3829aeca1107d.json
The text was updated successfully, but these errors were encountered: