Hide Forgot
Description of Problem: Downloaded new glibc version and attempted to "freshing" with: rpm -Fvh glibc-* failed because of conflicts bettween glibc-...i386.rpm and glibc-...i686.rpm Version-Release number of selected component (if applicable): How Reproducible: everytime Steps to Reproduce: 1. see above 2. 3. Actual Results: freshen failed ... I had to select inividual files to freshen Expected Results: Since i686 was installed, that would have been selected and the i386 package ignored Additional Information: This may be one of those "working as designed" in which case I will resubmit as an RFE.
rpm has no way to tell what the intent is when given multiple packages that differ only in arch, either of which would "work", on the command line. While an affinity scheme with the arch of the old package could be worked out, that doesn't exactly handle the case of cpu athlon installed glibc-*.i586 upgrade choices glibc-*.i386 glibc-*.i686 even if the existing platform scoring mechanism within rpm, usually used as an affinty metric between a new package and the cpu were to be generalized to check the old (but there can be several, for example, kernel, packages installed, with different arch's!) package as well. Any deterministic policy mechanism for choosing packages is bound to miss the intent somehow/somewhen. What needs doing IMHO is finer grained dependencies to track explicit functionality, arch is far too slippery for a reliable choice. That will happen eventually, but, for now, make your own choice clear on the rpm command line.