James P. Kinney III wrote:
This is a failure of the packager not your access. There is a file thatboth packages "share" and one package is trying to update the other's file. That is a no-no! I recommend NOT using sos and to use sysreport instead as that really _does_ contain the /usr/sbin/sysreport binary.You can either exclude the sos package (yum -y --exclude=sos update) or remove the sos package (yum remove sos) or you can download manually and install manually with rpm (rpm -Uvh sysreport*.rpm sos*.rpm - this willlikely fail so a retry with "rpm -Uvh sysreport*.rpm ; rpm -Uvhsos*.rpm" will split it up. If it _still_ fails you need to decide which package to keep. Read the info on each before the deletion with rpm - qpi sysreport*.rpm, - the flag -qpi means query package info from the listedrpm file. leave off the "p" and the *.rpm to get the data from the installed sysreport package. rpm -ql foo will show all files installed by the package foo.)
The sos package obsoletes the sysreport package and has a symlink for / usr/sbin/sysreport pointing to /usr/sbin/sosreport. It is actually recommended to use the sos package and *not* use the sysreport package anymore. You should not have both sos and sysreport installed and running 'yum update' should have installed sos and removed the obsoleted sysreport.
If you're not to afraid to execute terminal commands as root, please check the output of 'rpm -q sos sysreport' and I'll see what we can do.
Nils Breunese.
On Wed, 2008-01-02 at 10:06 -0500, Ronnie Miller wrote:When I try to use the graphical "Software Updater", I'm getting the following error message: [('file /usr/sbin/sysreport conflicts between attempted installs ofsos-1.7-9.1.el5 and sysreport-1.4.3-13.el5', (6, '/usr/sbin/ sysreport', 0L)), ('file /usr/share/sysreport/functions conflicts between attemptedinstalls of sos-1.7-9.1.el5 and sysreport-1.4.3-13.el5', (6, '/usr/share/sysreport/functions', 0L))]Everything downloads completely before this comes up. Blame it on my lack of understanding of Fedora, but I'm stumped. Updates were working, even after we implemented proxy authentication, but now it's not. Any ideas?