livna.org + YUM

ryedunn · 09-11-2006, 10:26 PM

I installed FC5 and tried adding livna.org as stated here: http://www.gagme.com/greg/linux/fc5-tips.php

after doing so yum wouldnt work (python errors) and after a few hours of attempting to fix it I thought a reinstall would just be easier. During this time I did read that if you have an improper repository things can really go bad.

So how can I be sure this wont happen again? Im much further along and a reinstall isnt an option anymore.

Cant a brotha just get some tunes?

i386 FC5

jens · 09-11-2006, 10:55 PM

He's making a very huge mistake in this tip:

Quote:

Add support for other repositories
Fedora comes with a ton of software but there are still plenty of packages of interest to most users that are not included for a variety of reasons. This is where you find the MP3 plug-in and a ton of other packages. Yum is now the preferred update format, however the handy RHN icon on the GNOME task bar that I like (but nobody else does) still seems to be tied to the old RHN method using up2date.

Before you add repositories it's probably a good idea to make sure your system is fully updated first. It's still early but right now the Livna and freshrpms repositories seems to be the most useful. The easiest way to get started is to install the freshrpms-release packages:

# rpm -ihv http://rpm.livna.org/fedora/5/i386/l...5-8.noarch.rpm
# rpm -ihv http://ayo.freshrpms.net/fedora/linu....fc.noarch.rpm

You can browse the packages available there at http://rpm.livna.org/fedora/5/i386/ and http://bordeaux.freshrpms.net/. To automatically install/update the Macromedia Flash plug-in copy This File to your /etc/yum.repos.d directory.

Never combine Livna with rpmforge(FreshRPMS, Dag, Dries, ...).
With this setup it's not surprising that you ran in trouble(they're simply not compatible).

I personally prefer RPMForge over Livna.
The repos I use are:
*core
*updates
*extras
*freshrpms
*dries

You can find an example of a simular setup here:
http://stanton-finley.net/fedora_cor...notes.html#Yum
Livna gets installed(for the 3D drivers), but not enabled. This allows you to use Livna packages without breaking your system.

If you use Livna for udpating, you can't use anthing else (core,updates,extras,livna).

Jongi · 09-12-2006, 02:30 AM

Quote:

If you use Livna for udpating, you can't use anthing else (core,updates,extras,livna).

This is not true. I have been using livna as an update repo for well over 3 months with those repos you list without issue.

jens · 09-12-2006, 05:41 AM

Quote:

Originally Posted by Jongi

This is not true. I have been using livna as an update repo for well over 3 months with those repos you list without issue.

Please read again.
Their's no problem with livna and extras (livna even started out of it). Their are problems between rpmforge(FreshRPMS, Dag, Dries, ...) and Livna.

You'll find a warning on any guide or howto:

Stanton Finley:

Quote:

Special warning regarding mixing incompatible repositories for software installation and updates:

...

As you continue please keep the following in mind: You should not use the livna.org repository in conjunction with the dag/freshrpms/dries/newrpms (RPMforge) collection of rpms in your configuration files for automatic updates. Use one group or the other but not both. These two groups are mutually incompatible and can cause errors in your installation if used together for automatic updates. Regardless of which group you choose you should also avoid using the ATrpms repository in your yum or apt configuration files for these reasons. Some additional information can be found here.

With this being said please note that it is nonetheless possible to obtain single RPM packaged applications from incompatible third party repositories in cases where such packages do not create errors when installed with yum. More specifically it is possible to configure other repositories with their enable flags set to "0" (off) so that the yum "--enablerepo" command must be used when one of those packages is desired.

I myself subscribe to the RPMforge collection as you can see in my repository selection instructions below. The dag/freshrpms/dries/newrpms/PlanetCCRMA (RPMforge) repositories have provided me with all of the programs I have needed as additions to the Fedora base.

To configure your Fedora Core 5 yum application to use the RPMForge repositories proceed as follows:

It's going in the right direction though. The extras repo(excluding Livna) should not give you troubles anymore (even though it did still gave me a few dubble packages).

Good luck with your system though, you'll need it.

odcheck · 09-12-2006, 05:55 AM

Stanton Finley is not the great champion but its true thats erros can occure if
you mix too many repos. So just use the ones that are "supported..." by Fedora Release Notes.

but sometimes try a little

Code:

yum install blahfassel --exclude-repo=whatever

If you're running in trouble

PS: I like the hints described by S.F.

jens · 09-12-2006, 06:57 AM

Quote:

Originally Posted by odcheck

Stanton Finley is not the great champion but its true thats erros can occure if
you mix too many repos. So just use the ones that are "supported..." by Fedora Release Notes.

You will not run in trouble using only one of them. They're all build against the fedora tree. It's combining non-official repos that can cause trouble. Extras and RPMForge are already working (see the FreshRPMS mailing list) on this. Why the Livna addon isn't following yet, remains unclear for me (and annoying for everyone)

Quote:

Originally Posted by odcheck

but sometimes try a little

Code:

yum install blahfassel --exclude-repo=whatever

If you're running in trouble

PS: I like the hints described by S.F.

IMO it makes more sense to do the opposite (and avoiding trouble)

Disabling either Livna or RPMforge and using "--include-repo=whatever" for installing something from the other one...

ryedunn · 09-12-2006, 08:58 PM

Jens,
SMP support, ATI 3D drivers, & VLAN all running within 10 minutes! Thank you!