-
Notifications
You must be signed in to change notification settings - Fork 547
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
The etc gem dependency causing a Gem::LoadError error #2283
Comments
I'm probably going to revert this change in the next Passenger, as it was aimed at helping already broken ruby installs. In the meantime does specifying in the Gemfile the same version of the etc gem that is included with your ruby help? That way hopefully when bundler resolves Passenger's dep it will choose the same version. |
Yes, specifying etc v1.0.1 in the Gemfile helps, but I do not see this as a good solution going forward. If the etc gem is somehow missing from the ruby installation, then it should be included explicitly. Just a documented advice should be sufficient. |
Hello, do you know when Passenger with the fixed gemspec is expected? |
6.0.6 is released with the fix. |
Thanks! |
Please follow the steps below if you have found an issue with Passenger, or would like to request a feature.
Post to Stack Overflow instead if you are not sure, or if you have a question about your configuration.
Issue report
Fill in as much as possible so that we can understand, find and fix the problem.
Are you sure this is a bug in Passenger?
Please read our troubleshooting and debugging guides first:
https://www.phusionpassenger.com/library/admin/troubleshooting/
https://www.phusionpassenger.com/library/admin/
The problem is caused by a new gem dependency introduced in v6.0.5 via #2124.
The problem does not surface for v6.0.4.
Please try with the newest version of Passenger to avoid issues that have already been fixed
v6.0.5 is the latest one right now.
Question 1: What is the problem?
Be as detailed as possible in your descriptions, include any logs and stack traces (don't just cut/paste the error, provide some logging before that too).
(if you are requesting a feature instead of reporting an issue, describe here what you have in mind and how it would help you)
Your answer:
The gem is installed normally (
bundle install
):But when asset precompilation is initiated (
bundle exec rails assets:precompile
), it fails:Question 2: Passenger version and integration mode:
Your answer:
v6.0.5 Standalone
Question 3: OS or Linux distro, platform (including version):
Your answer:
Amazon Linux 2, x86_64
Question 4: Passenger installation method:
Your answer:
[x] RubyGems + Gemfile
[ ] RubyGems, no Gemfile
[ ] Phusion APT repo
[ ] Phusion YUM repo
[ ] OS X Homebrew
[ ] source tarball
[ ] Other, please specify:
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Your answer:
Ruby v2.6.3 (from the amzn2 yum repo), Rails v5.2.4.2, Bundler v1.17.3
Question 6: Are you using a PaaS and/or containerization? If so which one?
Your answer:
No.
Question 7: Anything else about your setup that we should know?
Your answer:
Nothing else right now.
We strive for quality and appreciate you taking the time to submit a report! Please note that if you want guaranteed response times and priority issue support we encourage you to join our enterprise customer base. They also provide us with the means to continue our high level of open source support!
The text was updated successfully, but these errors were encountered: