Description of problem: with a recent update, nspr and nspr-devel for f16 conflict Version-Release number of selected component (if applicable): nspr-4.9.1-2.fc16.x86_64 How reproducible: always Steps to Reproduce: With both nspr and nspr-devel installed, do: yum update Actual results: Transaction Check Error: file /usr/lib64/libnspr4.so conflicts between attempted installs of nspr-devel-4.9.1-2.fc16.x86_64 and nspr-4.9.1-2.fc16.x86_64 file /usr/lib64/libplc4.so conflicts between attempted installs of nspr-devel-4.9.1-2.fc16.x86_64 and nspr-4.9.1-2.fc16.x86_64 file /usr/lib64/libplds4.so conflicts between attempted installs of nspr-devel-4.9.1-2.fc16.x86_64 and nspr-4.9.1-2.fc16.x86_64
Since the file layout doesn't seem to have changed over the last few releases, I suppose the failure must have been caused by something external - change of yum/rpm policy, /lib64 /usr/lib64 symlinking, etc.
The changes in file system layout did not happen until f17 so they should not affect f16. I made sure not to bring unwanted changes from f17 to f16. I'll attched a diff between the spec to illustrate.
Created attachment 603720 [details] diffs between f16 and f17 spec files The f17 ones has the adjustments to account for the Usr/Move file layout change whereas the f16 has none as they aren't needed not wanted.
Mats, please provide the output of command: rpm -qa nspr nspr-devel
I'm looking at the contents of the new rpm files: $ rpm -qlp nspr-4.9.1-2.fc16.x86_64.rpm |grep -w so /lib64/libnspr4.so /lib64/libplc4.so /lib64/libplds4.so $ rpm -qlp nspr-devel-4.9.1-2.fc16.x86_64.rpm |grep -w so /usr/lib64/libnspr4.so /usr/lib64/libplc4.so /usr/lib64/libplds4.so Looking at the history of the nspr.spec file in f16, I don't see any recent changes related to these files.
Mats, in addition, please also provide the output of the following command: ls -ld /usr/lib64/lib*4.so /lib64/lib*4.so (I assume you still have an old nspr packages installed.)
# rpm -qa nspr nspr-devel nspr-4.9-2.fc16.i686 nspr-devel-4.9-2.fc16.x86_64 nspr-4.9-2.fc16.x86_64 The ls is a bit lengthy, as it also matches other things. Trimmed a bit: # ls -ld /usr/lib64/lib{nspr,plc,plds}4.so /lib64/lib{nspr,plc,plds}*4.so -rwxr-xr-x. 1 root root 243240 Mar 28 13:03 /lib64/libnspr4.so -rwxr-xr-x. 1 root root 21256 Mar 28 13:03 /lib64/libplc4.so -rwxr-xr-x. 1 root root 17096 Mar 28 13:03 /lib64/libplds4.so -rwxr-xr-x. 1 root root 243240 Mar 28 13:03 /usr/lib64/libnspr4.so -rwxr-xr-x. 1 root root 21256 Mar 28 13:03 /usr/lib64/libplc4.so -rwxr-xr-x. 1 root root 17096 Mar 28 13:03 /usr/lib64/libplds4.so
I guess this doesn't help: yum update nspr.i686 nspr.x86_64 nspr-devel.i686 nspr-devel.x86_64
I cannot reproduce your problem. I installed a fresh f16 vm, then I manually updated to the package versions that you have installed. Aug 13 21:47:02 Updated: nspr-4.9-2.fc16.x86_64 Aug 13 21:47:59 Installed: nspr-4.9-2.fc16.i686 Aug 13 21:47:59 Installed: nspr-devel-4.9-2.fc16.x86_64 Then I ran yum update nspr\* This succeeded, and I now have: Aug 13 21:48:30 Updated: nspr-4.9.1-2.fc16.x86_64 Aug 13 21:48:31 Updated: nspr-devel-4.9.1-2.fc16.x86_64 Aug 13 21:48:32 Updated: nspr-4.9.1-2.fc16.i686
(the log entries are from /var/log/yum.log)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.