FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I try to update with yum or the software updater and some items fail depencency checks because of missing libraries. However, these are libraries that were from FC4 which I upgraded from.
Here is a sample error message, does anyone know what I need to do to fix this?
[('file /usr/lib/librpm-4.4.so from install of rpm-libs-4.4.2-33.fc6 conflicts with file from package librpm4.4-4.4.2-15.2_60.fc4.at', (7, '/usr/lib/librpm-4.4.so', 0L)), ('file /usr/lib/librpmbuild-4.4.so from install of rpm-libs-4.4.2-33.fc6 conflicts with file from package librpm4.4-4.4.2-15.2_60.fc4.at', (7, '/usr/lib/librpmbuild-4.4.so', 0L)), ('file /usr/lib/librpmdb-4.4.so from install of rpm-libs-4.4.2-33.fc6 conflicts with file from package librpm4.4-4.4.2-15.2_60.fc4.at', (7, '/usr/lib/librpmdb-4.4.so', 0L)), ('file /usr/lib/librpmio-4.4.so from install of rpm-libs-4.4.2-33.fc6 conflicts with file from package librpm4.4-4.4.2-15.2_60.fc4.at', (7, '/usr/lib/librpmio-4.4.so', 0L))]
Upgrading two versions (FC 4 to 6) in one step can be problematic. It’s hard enough to do a single version upgrade.
Under normal upgrading conditions, you would identify the old packages causing conflicts and attempt to delete them without deleting other essential packages.
For x86_64, the conflict is often caused by an attempt to upgrade an old i386 package that is not available as i386 in the new OS version.
Sometimes, the conflict problem is caused by there being two versions of the same package concurrently installed.
Try listing the conflicting package name to see what is installed and what is available.
...where --orphans will give you a list of old packages that are candidates for removal and --problems will identify packages with dependency problems.
Note: The system should be as up-to-date as possible before running package-cleanup.
Thanks for the responses folks, I tried all of it. However, I am still getting a number of packages some of which I don't even use from FC4 that are unable to update.
Do I attack them one at a time and remove them then install them again? If I remove rpm for instance will it cause problems. I once tried to remove cyrus but it had so many dependencies it also tried to remove I could not do it.
I want to basically remove just the problem packages without dependencies then re-install the newer ones.
I ran package-cleanup --orphans and again for --problems and it still chokes on these packages.
Seeing atrpms on the orphans list tells me that you have 3rd party packages installed.
Code:
# yum list installed | grep .at | sort
Start by disabling all 3rd party repos except for livna in yum.conf and yum.repos.d followed by removing or downgrading all installed 3rd party packages. Easy to do if you “yum install yum-allowdowngrade” first.
Then after attempting an update, pick a conflicting package and run “yum list <package>”.
Once the conflicts are resolved, you can reinclude atrpms as a repo, which I personally think is a very bad idea. Try to “shop” for your 3rd party packages somewhere else that provides stable, compatible packages.
Good news! I fixed them all. WhatsHisName, thank you. I did what you said and removed the atrpms from my repos. Then did an rpm -e {for all FC4.at packages} --nodeps
Then just did this for each one of the problem packages. I guess now I should clean the database.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.