| Summary: | rubygem-execjs: FTBFS rubygems NoMethodError | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Jun Aruga <jaruga> | ||||
| Component: | rubygem-execjs | Assignee: | Pavel Valena <pvalena> | ||||
| Status: | CLOSED EOL | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rh-ror42 | CC: | pvalena | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-14 13:06:50 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Jun Aruga
2016-10-19 14:55:59 UTC
Created attachment 1212193 [details] Patch - reverse order of enabled SCLs Hi Jun, thank you for reporting. As Vít Ondruch suggested, this is an error caused by [1] and changing the order of enabling of the SCLs does solve the issue (see attached diff). [1] http://pkgs.devel.redhat.com/cgit/rpms/ruby/commit/?h=rhscl-2.3-rh-ruby23-rhel-7&id=ddcdf2b199fae3a0689b8bf4e75ea650a6433d19 Pavel,
Thank you for your checking.
Okay.
When I ran below code, I got above error.
rubygem-execjs.spec
```
%prep
%setup -n %{pkg_name}-%{version} -q -c -T
%{?scl:scl enable %{scl} %{scl_nodejs} - << \EOF}
%gem_install -n %{SOURCE0}
%{?scl:EOF}
```
But when I changed the code
from
```
%{?scl:scl enable %{scl} %{scl_nodejs} - << \EOF}
```
to
```
%{?scl:scl enable %{scl_nodejs} %{scl} - << \EOF}
```
It worked successfully.
So, maybe do we want it to work on on any case including %{scl}?
Such as
- %{?scl:scl enable %{scl} %{scl_nodejs} - << \EOF}
- %{?scl:scl enable %{scl_nodejs} %{scl} - << \EOF}
- %{?scl:scl enable %{scl_foo} ... %{scl} ... %{scl_bar} - << \EOF}
Hi Jun,
our additional testing revealed that only in case `%gem_install` is encapsulated (follows the SCL enabling) the error occurs. This is unavoidable, in current state of scl-utils, and it will be documented.
Also, in this specific case, you can remove the `%{scl_nodejs}` enabling preceding %gem_install entirely. It is not needed anymore.
I the second case, when the tests are run, the order of enabling does not matter.
(In reply to Pavel Valena from comment #3) > Hi Jun, > > our additional testing revealed that only in case `%gem_install` is > encapsulated (follows the SCL enabling) the error occurs. This is > unavoidable, in current state of scl-utils, and it will be documented. > Also, in this specific case, you can remove the `%{scl_nodejs}` enabling > preceding %gem_install entirely. It is not needed anymore. > > I the second case, when the tests are run, the order of enabling does not > matter. Hi Pavel, Okay in the specific case: rubygem-execjs, I could see that it worked successfully after removing `%{scl_nodejs}` in the part of %gem_install. Red Hat does not currently plan to provide any further changes to this collection in a Red Hat Software Collections update release. This software collection is nearing the retirement date (May 2019) after which customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/ In accordance with the Red Hat Software Collections Product Life Cycle, the support period for this collection has ended. New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be made available for this collection. Customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/ |