-
Notifications
You must be signed in to change notification settings - Fork 5
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
sass-embedded installs x86_64-linux-gnu version and then fails on another machine #70
Comments
I believe this is an upstream issue related to this rubygems/rubygems/issues/4269 . We have |
Ugh, I think this may be a new upstream issue. Which Bundler & RubyGems version are you using? |
@deivid-rodriguez definitely an upstream issue. I was able to confirm that this happens on
vs
Seems that upgrading rubygems also solves the issue. I guess a note in README of the required rubygems version could be enough as older version mixed with older Bundler makes the error message unnecessarily hard to figure out. |
Oh, that's great to hear! Given the coincidence in time I thought it was actually the other way around and that yesterday's releases (RubyGems 3.3.23 and Bundler 2.3.23) broke something. |
The |
Given the different output of Bundler 2.3.22 and Bundler 2.3.21, I think this PR might be the reason that 2.3.22 was able to report the correct error message but 2.3.21 was not behaving correctly: rubygems/rubygems#5875 |
The native gem will have |
Only with the combination of There isn't much I can do here. If you have different mixes of rubygems/bundler versions you need to support, you may want to lock it to the |
@ntkme unfortunately that won't work as we have other gems we need to set the platform for. I'm assuming it wouldn't be possible to release a just |
I have downgraded the gem to version 1.6.2 until it (one way or another) becomes usable on Heroku again |
A plain Assuming you are checking in the In my very limited test, I found that:
What’s the |
My
and this Gemfile.lock
will fail to deploy on Heroku. So basically if you ran
The problem with this approach is that Bundler will happily reapply this the moment it has to regenerate the lockfile. You can check with the Gemfile I've given that if you add any other gem (for ex. |
|
@d4rky-pl In my test above, depending on the |
|
@d4rky-pl From the two tests I did above you see Edit: Actually, it is the default version of bundler that comes with rubygems making the difference. |
Here are a few conclusions:
|
Actually, there is another way out for it to work on heroku. If you use rubygems |
I'm frankly not sure if this is a Bundler issue or what but it only happens with
sass-embedded
.When I add the gem to the Gemfile in Docker locally and then run
bundle
, it installsx86_64-linux-gnu
version. It then fails on the CI withThe Gemfile.lock includes both version without the platform pin and with:
Removing the platform pin manually works and
bundle
no longer adds it until I update any of the gems, in which case it's getting re-added and the problem resurfaces.I tried looking for a solution everywhere, searched through Bundler and RubyGems issues and I can't figure this one out. Is this a problem with how the gem is released or am I doing something wrong?
The text was updated successfully, but these errors were encountered: