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've heard quite a bit about the dangers of RPM repository mixing between Fedora Extras/livna.org and others such as DAG and Freshrpms, but I haven't really heard an explanation as to why they're incompatible. Are the rpms compiled differently? What is the fundamental difference between the two categories of rpms? Thanks.
They are compatible, but can be a pain to use. For example newrpms, name their rpms slightly differently to the other repositories, so if you have the same version of a package, newrpms way of packaging things makes rpm think that their package is newer and will upgrade/install it if you are using automated tools such as apt and yum.
Maybe they are compatible, maybe not. There is no guarantee, since nobody tests all the possible permutations.
If you mix them and your personal experience is that it seems to work for you, consider yourself lucky. A different user might run into problems because he uses other packages.
Different package naming schemes can result in package or file conflicts between packages. The most often reported form of repository mixing problems.
Incompatible package names break src.rpm build requirements, i.e. when you want to rpmbuild --rebuild source packages.
Different software versions included in packages with the same name either break dependencies or lead to fully untested and unsupported installation configurations. An application built with and tested with a specific version of a library may not work as intended with a different version of the library. The newest version is not always the best version. A library in one repository may be compiled with different features than the same library in another repository. The files within packages may be placed in different locations.
Different repositories may include and apply different patches. An older package might include important patches, which would be lost if it were upgraded with a newer package from a different repository.
Some repositories upgrade packages in Fedora Core or rename FC packages to make room for different software versions. They move you farther away from the tested Fedora Core environment. Packages in FC may contain important patches not yet merged in upstream project's releases. Be sure to not upgrade without good reason.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.