Bug 1105898
| Summary: | Differenet behaviour with yum RPMs install between 5.9 and 6.5 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Andrejus Chaliapinas <andrejusc> |
| Component: | rpm | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5 | CC: | james.antill, jzeleny, packaging-team-maint, pmatilai |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 07:49:15 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: | |
| Embargoed: | |||
|
Description
Andrejus Chaliapinas
2014-06-08 21:02:10 UTC
This change is in rpm, not yum so switching component. This is an intentional change in rpm >= 4.6.x, but one that hasn't perhaps been adequately communicated in RHEL 6 context. For that reason, a compatibility mode has been introduced in this RHEL-6 errata to give users more time to adapt to the new behavior: https://rhn.redhat.com/errata/RHBA-2013-1665.html Note that use of this compat mode is actually not recommended, and that this option is RHEL-6 only, RHEL-7 will not have it as it is only provided as a temporary migration aid. Hi Panu, I need additional explanation of that introduced compatibility mode. Errata says: With this update, Red Hat Enterprise Linux 5 backwards-compatibility option, "%_strict_script_errors macro", has been added. The default behavior of Red Hat Enterprise Linux 6 does not change with this update and users that do not demand this option specifically are not advised to use it. Does it mean that usage/addition of "%_strict_script_errors macro" into RPM spec will make it behave in a way it was on RHEL 5.9? I.e. exit code 1 will be properly propagated through yum and into shell? If not adding this macro - what is alternative to indicate from inside RPM spec that some step has failed and exit with return code of 1? Not that clear from such documentation %_strict_script_errors is a runtime configuration option that needs to be enabled on the systems where the former scriptlet error behavior is wanted, it does not affect builds in any way. Could you specify how exactly (in which file) that runtime configuration option needs to be added/enabled? Could anyone respond with more information here in regards to my comment #6? Its a macro, set to non-zero to enable in a macro configuration file. Or better yet, dont - as the notes say its use is discouraged unless you really know what you're doing. Further enquiries to the appropriate RHEL support forums please, this is a bug tracker only. |