-
Notifications
You must be signed in to change notification settings - Fork 69
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
No build error but gem not created #319
Comments
I have a similar problem when trying to install a gem... I've tried rebuilding but no success:
|
I'm looking into this tonight. |
I apologize for this. The change of hosting providers was not quite seamless 😉 Because of a tight time frame with ShellyCloud closing, I ended up temporarily deploying rails-assets.org to a hosting provider other than Digital Ocean, but just a few minutes ago I flipped the switch and now everything is pointed at one of Digital Ocean's data centers. In my panic to get the infrastructure set up, I forgot one symlink which caused your gems to get built correctly and then put in entirely the wrong place 💥 Of course, I fixed this in the process of moving the servers to DO. It should be resolved now. These work for me:
Please let me know if you continue to have issues. Thanks for your patience. |
Thanks ! |
Sorry to bother you again but I didn't notice some of my other gems have the same issue:
It wasn't an ideal time to import all of my packages 😆. Could you do something about them too ? Thank you for your time ! |
They will be done momentarily. They are in the build queue. |
Thank you |
Thanks @hut8 |
The following gem is a dependency for
xire28--behavior-google-map-info-window-ujs
but the build process seems to have failed without issuing any error.I get this message when updating using bundler:
I tried to create a new release (tag v1.0.3) but I got the same result.
When I added the component on his own and got an other gem (issue #318) :
rails-assets-xire28--behavior-google-map-marker-ujs
and it worked.Not sure why it failed, could you have a look at it or simply delete the gem ?
The text was updated successfully, but these errors were encountered: