List or Count Installed RPM Packages

If you are on a RPM-based Linux platform (such as Redhat, CentOS, Fedora, ArchLinux, Scientific Linux, etc.), here are two ways to determine the list of packages installed. Using yum: yum list installed Using rpm: rpm -qa You can also easily get a count of the installed packages by piping the output to wc: yum list installed | wc -l rpm -qa | wc -l

Fedora 17 "Error: Protected multilib versions"

Getting an error like the following when installing a package or group of packages on your Fedora 17 system? Error: Protected multilib versions: XXXXXXXX.fc17.i686 != XXXXXXXX.fc17.x86_64 This is because whenever you have both 32 and 64 bit versions of a package, they must be of the same version and release. The error message is showing you that the 32 bit version-release of the package does not equal (!=) the 64 bit version-release. You either need to update the 32 bit version to match the 64 bit version, or erase the 32 bit version to get rid of this error. While

Set up local RPM Installation Repository

There are a number of ways of installing additional RPM packages from installation media. However, if your network is fast and you are installing the same packages on a number of systems, it sometimes is easier to set up a simple local package repository and use yum to install the packages from there. This post shows you how to do this. Copy the new packages, or even the contents of an entire distribution to a suitable subdirectory on a local webserver. For example, if you are using an Apache webserver on RHEL or Fedora, suitable locations would probably be /var/www/html/repos/rhel6/

Automatically Install SRPM Build Dependancies

An RPM spec file, among other things, enumerates a list of required packages under the BuildRequires tag. Every package listed must be installed on the build platform otherwise the build will fail. You can install the necessary BuildRequires packages either manually using yum or even rpm, but a easier way to do so is to use a utility called yum-builddep which is part of the familiar yum-utils package. $ sudo yum-builddep 389-ds-base- If all goes well, all the dependency packages are automatically installed for you. Unfortunately yum-builddep does not know how to handle conditional BuildRequires and will sometimes incorrectly include

Disable PackageKit Update Check after Yum

Ever get an error message like the following when you use yum to install an RPM package or a group of RPM packages, and then, within a minute or two, attempt to use yum to install another RPM package? # yum groupinstall “Development Tools” Loaded plugins: langpacks, presto, refresh-packagekit Existing lock /var/run/ another copy is running as pid 1651. Another app is currently holding the yum lock; waiting for it to exit… The other application is: PackageKit Memory : 114 M RSS (506 MB VSZ) Started: Wed Oct 26 15:11:42 2011 – 00:10 ago State : Running, pid: 1651 Another