Bug 483054
| Summary: | lots of file conflicts between mvapich2 multilib packages. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Alexander Todorov <atodorov> |
| Component: | releng | Assignee: | Nick Petrov <npetrov> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Alexander Todorov <atodorov> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.8 | CC: | dledford, dmach, gozen, mikem, pmatilai, sghosh, syeghiay |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| URL: | http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=6228592 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-19 13:39:17 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: | |||
Adding package owner and rpm owner to CC. Doug, can the conflict be fixed in the package or we need to patch rpm to skip the check? mvapich2 was not intended, not is it supported, to be multilib on ia64. For all other arches, %{_libdir} is embedded in the file paths and so no conflicts occur, but of course on ia64 the 64bit %{_libdir} is the same as the 32bit one. According to the file list contents for the errata, ia64 is *not* supposed to be multilib.
Moving to rel-eng. See comments #2 and #3 I haven't found mvapich* in comps or distill config. Doug, aren't these packages pulled via deps? Multilib respects deps, so if a package is multilib, it pulls all it's deps as multilib. Strike comment #5 please. I've grepped probably old comps - the packages are in compat-arch-support group. Should mvapich2.i386 be removed only from ia64 or from both ia64 and x86_64? Only from ia64. We added it to compat-arch-support for x86_64/i386 but had not intentions of it or mvapich being added as multilib on ia64. Doug, there seems to be lots more conflicts between mvapich packages than between mvapich2 ones. See the link in comment #9. These look like arch independent files. Probably best to split them into noarch sub package and make mvapich require it. What do you think ? mvapich2 is not present in latest nightly builds for ia64 but there are still file conflicts for mvapich-1.1.0-0.3143.4.el4 package. See: http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=6943299 Doug, should we remove mvapich.i386 from ia64 as well? Yes please ;-) |
Description of problem: Lots of file conflicts between mvapich2 multilib packages on ia64 Version-Release number of selected component (if applicable): mvapich2-1.2-0.p1.4.el4 How reproducible: Always Steps to Reproduce: 1. Install RHEL4.8, @everything 2. Download all compatlayer packages 3. Try to install them (or mvapich2 only) Actual results: File conflicts. rpm transaction fails. Expected results: Additional info: Filing against distribution because there's no mvapich2 component in bugzilla. mvapich{2} is new package in RHEL4.8. It's not in 4.7. See above URL for detailed log of all failures.