Installation Confusion on Fedora

JohnGraham · 02-07-2013, 06:19 AM

Hi there,

I'm usually a Debian user, totally new to Fedora. I'm trying to install tcpreplay - the website says most RPM-based distros should have it, so I tried:

Code:

# yum install tcpreplay
Loaded plugins: fastestmirror, kmod
Loading mirror speeds from cached hostfile
 * base: mirrors.vooservers.com
 * extras: centos.serverspace.co.uk
 * updates: mirror.sov.uk.goscomb.net
Setting up Install Process
No package tcpreplay available.
Nothing to do

I tried searching online, but I can't find a central place to find info about yum packages like packages.debian.org, can anyone enlighten me?

Anyway, I decided to download the RPM and try to install it:

Code:

# yum localinstall --nogpgcheck rpmforge-release-0.5.2-2.el6.rf.i686.rpm 
Loaded plugins: fastestmirror, kmod
Setting up Local Package Process
Examining rpmforge-release-0.5.2-2.el6.rf.i686.rpm: rpmforge-release-0.5.2-2.el6.rf.i686
Marking rpmforge-release-0.5.2-2.el6.rf.i686.rpm to be installed
Loading mirror speeds from cached hostfile
 * base: mirrors.vooservers.com
 * extras: centos.serverspace.co.uk
 * updates: mirror.sov.uk.goscomb.net
Resolving Dependencies
--> Running transaction check
---> Package rpmforge-release.i686 0:0.5.2-2.el6.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package
      Arch    Version            Repository                                Size
================================================================================
Installing:
 rpmforge-release
      i686    0.5.2-2.el6.rf     /rpmforge-release-0.5.2-2.el6.rf.i686     13 k

Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade       0 Package(s)

Total size: 13 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
rpmlib(FileDigests) is needed by rpmforge-release-0.5.2-2.el6.rf.i686
rpmlib(PayloadIsXz) is needed by rpmforge-release-0.5.2-2.el6.rf.i686
Complete!
(1, [u'Please report this error in http://bugs.centos.org/set_project.php?project_id=16&ref=http://bugs.centos.org/bug_report_page.php?category=yum'])

I tried "yum install rpmlib" but this gave be the same result as for tcpreplay above.

I know this is probably because of my unfamiliarity of Fedora/yum, but it's getting a bit frustrating. I'm now in the middle of "yum groupinstall development-tools" so I can build the package from source - but I'd still like to know what I should do to get this via the package manager. The information I can find on the internet seems either very disparate and/or doesn't seem to apply this/fix my problems.

I must be missing something - Fedora is too big for someone not to have had these issues before, I just can't find it! Can anyone help?

unSpawn · 02-07-2013, 08:37 AM

Since your Yum output shows repos like "centos.serverspace.co.uk" you're not running Fedora but CentOS 6. It's good to first read http://wiki.centos.org/AdditionalResources/Repositories and then fetch EPEL-release from http://fedoraproject.org/wiki/EPEL#H...ra_packages.3F after which you should be able to fidn and install tcpreplay.

JohnGraham · 02-07-2013, 09:47 AM

Quote:

Originally Posted by unSpawn

Since your Yum output shows repos like "centos.serverspace.co.uk" you're not running Fedora but CentOS 6. It's good to first read http://wiki.centos.org/AdditionalResources/Repositories and then fetch EPEL-release from http://fedoraproject.org/wiki/EPEL#H...ra_packages.3F after which you should be able to fidn and install tcpreplay.

Thanks for that, silly of me not to notice. This stuff is giving me a nightmare - first GCC started segfaulting when I tried to compile from source, and now after I updated yum it's doing the same. Have asked on the CentOS forums for some help.

DavidMcCann · 02-07-2013, 11:48 AM

Firstly, do not use extra repositories with CentOS untill you have set their priorities or the results can be nasty
http://wiki.centos.org/AdditionalResources/Repositories
http://wiki.centos.org/PackageManagement/Yum/Priorities

Secondly, you can get tcpreplay from the EPEL repository
http://fedoraproject.org/wiki/EPEL

Thirdly, when you need to find a program, these are a good place to start
http://rpm.pbone.net/
http://pkgs.org/

unSpawn · 02-07-2013, 12:00 PM

Quote:

Originally Posted by JohnGraham

Thanks for that, silly of me not to notice.

Sh*t happens ;-p

Quote:

Originally Posted by JohnGraham

This stuff is giving me a nightmare - first GCC started segfaulting when I tried to compile from source, and now after I updated yum it's doing the same.

It really shouldn't have to. While you may have get accustomed to using a different package management system your knowledge isn't wasted. The theory behind it, the fundamental principles, Standard Operational Procedures and Best Practices don't change. And just like Debian Red Hat (CentOS refers to them as "TUV") provides well-written, easily accessible documentation. There are however some reflexes you need to suppress and there's certain things you should not do unless b0rkage is your definition of "fun". For example you should not try to replace the version of Python the system comes with, you shouldn't compile applications on a production host and you shouldn't need to compile a compiler as gcc is part of the Base CentOS repository. For anything you can't find in Base and Extra http://wiki.centos.org/AdditionalResources/Repositories suggests best practices (like using yum-priorities) and the level of quality (or b0rkage ;-p) you can expect from repos like RPMForge, EPEL and others. Even if you think compiling from source is necessary it's always good to do research first because some vendors provide their own RPM packages (say Snort) and some even have their own repo (like Rsyslogd). Also note installing from source means bypassing package management system which is minimally inefficient as you have to track files and check for updates a different way, so creating packages (that's what you have your staging area machines for) is preferable. If you need help with the latter do a quick LQ search. You'll find there's a few knowledgeable members who help with building packages.