Bug 412811
Summary: | /etc/rpm/macros _transaction_color inconsistency | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Philippe Troin <phil> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | pmatilai, pnasrat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-03 18:35:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Philippe Troin
2007-12-05 20:36:11 UTC
Transaction color is a bit mask with 2 bits that determines how dependencies between ELF32 and ELF64 executables and libraries are to be resolved. 1 == ELF32 2 == ELF64 The value should likely be "3" everywhere these days. Why the value differs has to do with how the machines were configured. All versions of rpm since RHL9 (and rpm-4.2.2) have used "3" as the default value for transaction_color for 3+ years. Anaconda writes it in .. some cases as a workaround to an ancient bug. The difference between those two "mostly similar" systems is that other one is an Intel and the other one is AMD and the output from this differs: $ python -c "import rhpl.arch; print rhpl.arch.canonArch" The macros file with transaction color gets written if the above says x86_64 but not if it's ia32e like reported on Intel x86_64 systems. Ok, this line can be safely deleted then. Thanks for the info. Phil. |