Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: An attempt to update in rawhide an installed squid-3.4.9-3.fc22.x86_64 tp the current squid-3.5.2-3.fc23 results in the following errors: Running transaction test Transaction check error: file /usr/share/squid/errors/zh-cn from install of squid-7:3.5.2-3.fc23.x86_64 conflicts with file from package squid-7:3.4.9-3.fc22.x86_64 file /usr/share/squid/errors/zh-tw from install of squid-7:3.5.2-3.fc23.x86_64 conflicts with file from package squid-7:3.4.9-3.fc22.x86_64 What gives? That looks quite strange but I did not try to examine how these packages are put together. Version-Release number of selected component (if applicable): squid-3.5.2-3.fc23 How reproducible: On every try in the situation described. Additional info: An obvious workaround: 'yum remove squid; yum install squid' does not have any issues. As it happened I did not have any installed packages which depend on squid.
I don't see a reason why yum shouldn't cope with the upgrade, let's see what they have.
I see very similar error when upgrading from F21 to F22. # rpm -qf /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info python-psutil-2.1.3-1.fc21.x86_64 # rpm -q yum yum-3.4.3-153.fc21.noarch # yum --releasever=22 --disableplugin=presto --enablerepo=updates-testing distro-sync .... Running transaction check Running transaction test Transaction check error: file /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info from install of python-psutil-2.1.3-1.fc22.x86_64 conflicts with file from package python-psutil-2.1.3-1.fc21.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This error is from rpm. Maybe to do with the downgrade? Do you have multiple arches installed?
(In reply to James Antill from comment #4) > This error is from rpm. Maybe to do with the downgrade? Do you have multiple > arches installed? The originally reported error showed up when attempting to update packages on a rawhide installation and 3.4.9-3.fc22 to 3.5.2-3.fc23 hardly looks like a downgrade. As it happens this test rig has on it only x86_64 and noarch packages installed (although "production" machines are more often than not multiarch). Another incident noted in a comment #2 does not look like a downgrade either. OTOH I do not recall seeing anyting similar since the time of the report. Back in March I did not noticed anything "obvious" in packages in question which would explain an observed behaviour but I did not delve deeply into details. Still looking again it appears that /usr/share/squid/errors/zh-{cn,tw} in 3.4.9-3 are directories while in 3.5.2-3.fc23 they were both replaced by symlinks. Would that cause the reported trouble?
(In reply to Michal Jaegermann from comment #5) > (In reply to James Antill from comment #4) > > This error is from rpm. Maybe to do with the downgrade? Do you have multiple > > arches installed? > > The originally reported error showed up when attempting to update packages > on a rawhide installation and 3.4.9-3.fc22 to 3.5.2-3.fc23 hardly looks like > a downgrade. As it happens this test rig has on it only x86_64 and noarch > packages installed (although "production" machines are more often than not > multiarch). > Another incident noted in a comment #2 does not look like a downgrade > either. OTOH I do not recall seeing anyting similar since the time of the > report. > > Back in March I did not noticed anything "obvious" in packages in question > which would explain an observed behaviour but I did not delve deeply into > details. Still looking again it appears that > /usr/share/squid/errors/zh-{cn,tw} in 3.4.9-3 are directories while in > 3.5.2-3.fc23 they were both replaced by symlinks. Would that cause the > reported trouble? Yes, that causes the trouble. *** This bug has been marked as a duplicate of bug 447156 ***
The issue in #2 does not seem to be neither symlinks nor directories.
Where did you get the package python-psutil-2.1.3-1.fc21.x86_64, it is not in f21 repositories nor in koji? I built it from python-psutil-2.1.3-1.fc22.src.rpm. Then I was able to reproduce the problem. The root cause was that /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info was a directory in my python-psutil-2.1.3-1.fc21.x86_64: # rpm -qlp python-psutil-2.1.3-1.fc21.x86_64.rpm ... drwxr-xr-x 2 root root 0 Sep 22 09:40 /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info ... But /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info was a file in python-psutil-2.1.3-1.fc22.x86_64.rpm from fc22 repository: # rpm -qlvp python-psutil-2.1.3-1.fc22.x86_64.rpm ... -rw-r--r-- 1 root root 19361 Jan 6 2015 /usr/lib64/python2.7/site-packages/psutil-2.1.3-py2.7.egg-info ... So the problem was replacing a directory with a file.
(In reply to Ľuboš Kardoš from comment #8) > So the problem was replacing a directory with a file. OK.