yum

Presto: Speed up your updates and save bandwidth

Need more help or want to ask a question? Discuss this topic here.

A little background information

Delta RPMs (DRPMs) are very similar to binary (regular) RPMs. The main difference is that DRPMs contain only the changes between two versions of an RPM package. This allows you to do full updates in a lot less time - Instead of downloading a full 10MB for an update where only 50kb of content changed, for example, you can now download only that 50kb of change and apply it to your system.

Not only will you save on bandwidth since you're only downloading in the changes in a package, but you'll also cut down on the time it takes to download and apply the packages.

Presto is a project which brings deltarpm and yum together; In other words, letting you use yum to apply DRPMs.

Installing yum-presto

The first step toward setting up Presto is installing the yum plugin:

yum -y install yum-presto

Configure the Updates repository

Next, we need to configure your updates repository to download deltarpm packages instead of the full ones. In the /etc/yum.repos.d/fedora-updates.repo file you'll find two lines that looks like this in the [updates] section:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Add a pound character to the start of the mirrorlist line so that it looks like this:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Finally, add a new line just under the "#mirrorlist=" line we just edited:

mirrorlist=http://presto-mirrors.anmar.eu.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch 

The pound sign makes Yum ignore the line that it's on, so essentially we're telling yum to ignore the base repository and any mirrors. The line which was added tells yum to use the presto-enabled mirrors instead.

 
That's it! Now run you can use yum or yumex as normal and benefit from the advantages of deltarpms.
 
Need more help or want to ask a question? Discuss this topic here.
Rating: 
Tags: 

Presto: Speed up your updates and save bandwidth

Prestro is a new project that bridges the gap between deltarpm and yum. Now only will using yum-presto save you lots of bandwidth, but it will cut down on the time it takes to perform updates!

Need more help or want to ask a question? Discuss this topic here.

A little background information

Delta RPMs (DRPMs) are very similar to binary (regular) RPMs. The main difference is that DRPMs contain only the changes between two versions of an RPM package. This allows you to do full updates in a lot less time - Instead of downloading a full 10MB for an update where only 50kb of content changed, for example, you can now download only that 50kb of change and apply it to your system.

Not only will you save on bandwidth since you're only downloading in the changes in a package, but you'll also cut down on the time it takes to download and apply the packages.

Presto is a project which brings deltarpm and yum together; In other words, letting you use yum to apply DRPMs.

Installing yum-presto

The first step toward setting up Presto is installing the yum plugin:

yum -y install yum-presto

Configure the Updates repository

Next, we need to configure your updates repository to download deltarpm packages instead of the full ones. In the /etc/yum.repos.d/fedora-updates.repo file you'll find two lines that looks like this in the [updates] section:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Add a pound character to the start of the mirrorlist line so that it looks like this:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Finally, add a new line just under the "#mirrorlist=" line we just edited:

mirrorlist=http://presto-mirrors.anmar.eu.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch 

The pound sign makes Yum ignore the line that it's on, so essentially we're telling yum to ignore the base repository and any mirrors. The line which was added tells yum to use the presto-enabled mirrors instead.

 
That's it! Now run you can use yum or yumex as normal and benefit from the advantages of deltarpms.
 
Need more help or want to ask a question? Discuss this topic here.
Rating: 
Tags: 

Presto: Speed up your updates and save bandwidth

Need more help or want to ask a question? Discuss this topic here.

A little background information

Delta RPMs (DRPMs) are very similar to binary (regular) RPMs. The main difference is that DRPMs contain only the changes between two versions of an RPM package. This allows you to do full updates in a lot less time - Instead of downloading a full 10MB for an update where only 50kb of content changed, for example, you can now download only that 50kb of change and apply it to your system.

Not only will you save on bandwidth since you're only downloading in the changes in a package, but you'll also cut down on the time it takes to download and apply the packages.

Presto is a project which brings deltarpm and yum together; In other words, letting you use yum to apply DRPMs.

Installing yum-presto

The first step toward setting up Presto is installing the yum plugin:

yum -y install yum-presto

Configure the Updates repository

Next, we need to configure your updates repository to download deltarpm packages instead of the full ones. In the /etc/yum.repos.d/fedora-updates.repo file you'll find two lines that looks like this in the [updates] section:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Add a pound character to the start of the mirrorlist line so that it looks like this:

#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fX&arch=$basearch

Finally, add a new line just under the "#mirrorlist=" line we just edited:

mirrorlist=http://presto-mirrors.anmar.eu.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch 

The pound sign makes Yum ignore the line that it's on, so essentially we're telling yum to ignore the base repository and any mirrors. The line which was added tells yum to use the presto-enabled mirrors instead.

That's it! Now run you can use yum or yumex as normal and benefit from the advantages of deltarpms.
 
Need more help or want to ask a question? Discuss this topic here.
Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as RPM Fusion and Dries (RPMForge). This guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/DVD/WMV playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

RPM Fusion

RPM Fusion is the merger of the Livna, FreshRPMs and Dribble repositories. To install it, simply run:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

RPMForge (Dries)

Please note that RPMForge has not yet rebuild their packages for Fedora 9. For the time being, installing it is not recommended.

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora 10 - RPMforge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
RPM Fusion /etc/yum.repos.d/rpmfusion*.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as RPM Fusion and Dries (RPMForge). This guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/DVD/WMV playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

RPM Fusion

RPM Fusion is the merger of the Livna, FreshRPMs and Dribble repositories. To install it, simply run:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

RPMForge (Dries)

Please note that RPMForge has not yet rebuild their packages for Fedora 9. For the time being, installing it is not recommended.

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora 9 - i386 - RPMforge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
RPM Fusion /etc/yum.repos.d/rpmfusion*.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as RPM Fusion and Dries (RPMForge). This guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/DVD/WMV playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash). You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

RPM Fusion

RPM Fusion is the merger of the Livna, FreshRPMs and Dribble repositories. To install it, simply run:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

 

RPMForge (Dries)

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora 8 - RPMForge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
RPM Fusion /etc/yum.repos.d/rpmfusion*.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as Livna, FreshRPMs, Dries (RPMForge) and Dribble. Soon many of these will merge into one repo called RPMFusion, but until then this guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/dvd/wmv playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

Livna

Livna is my personal favourite repo because it's fast, compatible with Fedora (Extras) and contains almost everything you'll need to get started: 

Dribble

The beauty of the Dribble repo is that one command will work for all Fedora versions. Make sure you have Livna installed and run:

rpm -ivh http://dribble.org.uk/repo/dribble-release-5-3.noarch.rpm

 

FreshRPMs

To install FreshRPMs, run:

wget http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/5/freshrpms-release/\
freshrpms-release-1.1-1.fc.noarch.rpm

rpm -ihv freshrpms-release-1.1-1.fc.noarch.rpm
rm -f freshrpms-release-1.1-1.fc.noarch.rpm
exit

 

RPMForge (Dries)

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora Core 5 - i386 - RPMForge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
FreshRPMs /etc/yum.repos.d/freshrpms.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 
Dribble /etc/yum.repos.d/dribble.repo
Livna  /etc/yum.repos.d/livna.repo

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as Livna, FreshRPMs, Dries (RPMForge) and Dribble. Soon many of these will merge into one repo called RPMFusion, but until then this guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/dvd/wmv playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

Livna

Installing Livna is a matter of one simple command:

Dribble

The beauty of the Dribble repo is that one command will work for all Fedora versions. Make sure you have livna installed and run:

rpm -ivh http://dribble.org.uk/repo/dribble-release-5-3.noarch.rpm

 

FreshRPMs

To install FreshRPMs, run:

wget http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/6/freshrpms-release/\
freshrpms-release-1.1-1.fc.noarch.rpm

rpm -ihv freshrpms-release-1.1-1.fc.noarch.rpm
rm -f freshrpms-release-1.1-1.fc.noarch.rpm
exit

 

RPMForge (Dries)

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora Core 6 - i386 - RPMForge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
FreshRPMs /etc/yum.repos.d/freshrpms.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 
Dribble /etc/yum.repos.d/dribble.repo
Livna  /etc/yum.repos.d/livna.repo

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as Livna, FreshRPMs, Dries (RPMForge) and Dribble. Soon many of these will merge into one repo called RPMFusion, but until then this guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/DVD/WMV playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

Livna

Installing Livna is one command:

 

Dribble

The beauty of the Dribble repo is that one command will work for all Fedora versions. Make sure you have livna installed and run:

rpm -ivh http://dribble.org.uk/repo/dribble-release-5-3.noarch.rpm

 

FreshRPMs

To install FreshRPMs, run:

wget http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/7/freshrpms-release/\
freshrpms-release-1.1-1.fc.noarch.rpm

rpm -Uhv freshrpms-release-1.1-1.fc.noarch.rpm
rm -f freshrpms-release-1.1-1.fc.noarch.rpm

 

RPMForge (Dries)

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora 7 - i386 - RPMForge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
FreshRPMs /etc/yum.repos.d/freshrpms.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 
Dribble /etc/yum.repos.d/dribble.repo
Livna  /etc/yum.repos.d/livna.repo

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Rating: 
Tags: 

Presto!

Size of all updates downloaded from Presto-enabled repositories: 1.7M
Size of updates that would have been downloaded if Presto wasn't enabled: 31M
This is a savings of 95 percent

Updated: anaconda.i386 0:11.2.0.55-1 glibc.i686 0:2.5.90-21
Dependency Updated: anaconda-runtime.i386 0:11.2.0.55-1 glibc-common.i386 0:2.5.90-21 glibc-devel.i386 0:2.5.90-21 glibc-headers.i386 0:2.5.90-21
Complete!
Rating: