Just what the title says.

Keith

There is just one that I use, Livna. I am not sure what version of Fedora you are using or planning to use, but this site should come in handy.

freshrpms and atrpms are good too.

My best suggestion is Livna ....it Supports Fedora 7, 8 and 9 .

this contains most of the 3rd party RPM .

but for some programs like dvdrip and all you have to get Freshrpms or atrpms

Livna

To install the Livna repository which can be left on by default.

su -c 'rpm -i http://rpm.livna.org/livna-release-9.rpm'




FreshRPMS

You can install the freshrpms package however it is recommended to change the enabled section to be manually enabled.

su -c 'rpm -i http://ftp.freshrpms.net/pub/freshrp....fc.noarch.rpm'

su -c 'gedit /etc/yum.repos.d/freshrpms.repo'

You will need to change the enabled=1 to enabled=0 This is how it will be installed.

[freshrpms]
name=Fedora Core $releasever - $basearch - Freshrpms
#baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/freshrpms/
mirrorlist=http://ayo.freshrpms.net/fedora/linux/$releasever/mirrors-freshrpms
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-freshrpms
gpgcheck=1

It needs to be changed to

[freshrpms]
name=Fedora Core $releasever - $basearch - Freshrpms
#baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/freshrpms/
mirrorlist=http://ayo.freshrpms.net/fedora/linux/$releasever/mirrors-freshrpms
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-freshrpms
gpgcheck=1


Atrpms

su -
cat <<EOF> /etc/yum.repos.d/atrpms.repo
[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/f$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
enabled = 0
EOF


People ... correct me if i am wrong ....

Livna is one of the recommended repositories but somewhere in the near future we should use the new RPM Fusion repository as that will have combined three repositories :

Dribble - they are already in the moving process
Freshrpms - these are some lazy guys
Livna - These guys are lazy to


If they succeed the merging of those three repositories the resulting RPM Fusion will be all you need

RPM Fusion is UP now .... Cool one ....

http://rpmfusion.org/Configuration

rpm fusion for sure.

Well, my system went broken after this fusion.
I used to have livna-repository working just fine.
From livna the system automatic update scripts (yum-updatesd) was some fusion-files installed, and now the system won't update anymore due to errors.

"Two packages porovide the same file.
This is usually due to mising packages for different software sources."

The abobe message pops up every few minutes to the desktop and it is hard to kill this deadlock. Had to kill packagekitd few times, before it believed there is no use to retry over and over again.

Well, finally when I got it killed, I could try to run yum manually and see what is the problem:
Transaction Check Error:
file /usr/lib64/libavutil.so.49 from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package libavutil49-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/libavcodec.so.51 from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package libavcodec51-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/libpostproc.so.51 from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package libpostproc51-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/libswscale.so.0 from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package libswscale0-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/drawtext.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/fish.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/imlib2.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/null.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/ppm.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/vhook/watermark.so from install of ffmpeg-libs-0.4.9-0.48.20080908.fc9.x86_64 conflicts with file from package ffmpeg-0.4.9-23_r8743.fc6.at.x86_64
file /usr/lib64/libmpeg2convert.so.0.0.0 from install of libmpeg2-0.5.1-3.fc9.x86_64 conflicts with file from package libmpeg2convert0-0.4.1-3.fc6.at.x86_64
file /usr/lib64/libmpeg2.so.0 from install of libmpeg2-0.5.1-3.fc9.x86_64 conflicts with file from package libmpeg2_0-0.4.1-3.fc6.at.x86_64
file /usr/lib64/libmp3lame.so.0.0.0 from install of lame-libs-3.98.2-2.fc9.x86_64 conflicts with file from package libmp3lame0-3.97-16.fc6.x86_64

Error Summary
-------------

zimon, funny you posted this. My system took a complete dump after using the fusion repo. Because of all the other problems with F9, I have installed F8 using freshrpms again. I really can not believe they are going to release F10 with all the stuff that seems broken still with F9.

If you were specifically referring to rpmfusion, it seems to work very well with Fedora 10. I have been using Fedora 10 (rawhide) for about a week now with rpmfusion as the only third party repo and so far, everything works well.

Zimon

You do notice that those are FC6 packages and support for FC6 was dropped about a year(more?) ago?

Yes, noticed after I got over packagekitd and got to work with yum.
Seems like there were also many more fc6-packages still remaining in the system. I guess I should have made a clean new install for f9, and not to try upgrade from fc6. (I did upgrade using and booting with the f9 installation DVD)

After "some" hand work, removing/replacing all remaining fc6 packages, rpmfusion seems to work now.

There still seems to be few fc7 and fc8 packages remaining. But for example, xsp.fc7 is needed by monodevelop (f9), and no f9 package is found from repositories, so I guess it needs to stay. Or redhat-lsb.fc8, which seem to be needed by many f9 packages.


For an even more unexperienced user packagekitd would have been even more pain in the ass. It just couldn't recover from the error. Had to manually kill it several times. (Something or itself restarted itself many times with different new PID when killed.)