Tag Info

New answers tagged

0

You need to download bash-3.2-33.el5_11.4.i386 (or find it at any other alternative location) follow by: yum remove bash yum localinstall bash


2

.. assuming the CentALT repo doesn't mysql-devel rpm, you'd need to re-install mysql-server, by un-installing the one that you already have and installing it from base before installing mysql-devel (both has to be installed from same place). yum remove mysql yum install mysql-devel


0

Your mysql version differs from the mysql-devel version you're trying to install. This is because you have installed mysql from CentALT repo according to your output. Try yum --enablerepo=CentALT install mysql-devel


0

I think the issue is Provides: plat-6 You are making it conflict with itself. EDIT: Try Conflicts: plat-6 < %{version}


1

You appear to be using a internal mirror of lstn.net / limestonenetworks.com. That mirror is probably out of sync. You should contact them and make sure they sync the mirror. As the vulnerability you are trying to patch is critical, I'd advise to use a different mirror until they have synced theirs. Until then switch to the external ones provided by the ...


-1

It seems you are using CentALT repository. Error messages say mysql rpm from CentALT is installed; it is the source of the problem. Remove the mysql rpm and disable CentALT repository; after then, try to install mysql-devel again. Or you can temporarily disable CentALT to install mysql-devel: #remove mysql from CentALT yum remove mysql #install mysql and ...


-1

Well, you are trying to install a devel package for a previous mysql version. Package mysql-devel.x86_64 0:5.1.73-3.el6_5 will be installed Requires: mysql = 5.1.73-3.el6_5 Installed: mysql-5.5.29-1.el6.x86_64


3

If you don't have a subscription anymore and that's not likely to change, and you don't care about losing Redhat's (or other vendor's for that matter) support for this box in the future, you can switch it to CentOS and have your box updated with its packages. It's not ideal, but it may still preferable to having a box you can't update anymore. You have been ...


0

If you haven't got a valid subscription you can roll your own bash package: Install fpm Download the source file (http://ftp.gnu.org/gnu/bash/bash-3.2.tar.gz) Download all patches (http://ftp.gnu.org/gnu/bash/bash-3.2-patches/) tar xzvf bash-3.2.tar.gz Apply all patches, up to the latest patch -p0 <bash32-054 ./configure --prefix=/usr make mkdir -p ...


5

Could be a false positive - Make sure the 'echo' file does not exist from an earlier test on your bad machine, then retest. Failing that, could also be a false negative - Check you can touch a file on your good machine, then retest.


0

The other option I found was to disable these properties tests completely. If you edit /etc/rkhunter.conf and look for the DISABLE_TESTS line and change it to: DISABLE_TESTS="suspscan hidden_procs deleted_files packet_cap_apps apps properties" The properties test is the one checking and returning false positives on the file hashes.


0

Upgrades from RHEL 4 to 5 are not supported; the same would apply to CentOS. You should backup the server and perform a fresh installation of your CentOS version of choice. Although anaconda provides an option for upgrading from earlier major versions of Red Hat Enterprise Linux to Red Hat Enterprise Linux 5.11, Red Hat does not currently support this. ...


0

I had the same problem. I took a stab at creating some Python code to pull together Yum Updates and advisories from the steve-meier Errata site mentioned above (I filter it based on installed packages). In case it helps, here is the source: https://github.com/wied03/centos-package-cron


0

Removing hhvm.repo from etc/yum.repos.d solved it.


2

It's been a while since this question was asked, but it looks like EPEL is now preferred to RPMForge, at least by the CentOS community. You can see here that EPEL is listed under "Community Approved Repositories": Available Repositories for CentOS - Community Approved Repositories While RPMForge is listed under "Known Problem Repositories": ...


0

Execute the following command : # rpm -qa | grep mysql It will list all installed mysql packages on your system. Eg: mysql-libs-5.1.73-3.el6_5.x86_64 now execute the command: # yum remove <name displayed in above step-1> Eg: yum remove mysql-libs-5.1.73-3.el6_5.x86_64


3

Look into the yumrepo(doc link) resource and use it to duplicate the file on your puppet master. It can be used like this: yumrepo { "cuda": baseurl => "http://repourl", descr => "cuda", enabled => 1, gpgcheck => 0 } This approach is the (IMHO) best way to do this, but there are other possible approaches. You could treat it as a ...


5

Transaction Test tells if the required package/rpm will install without any issue if it fails it will throw error. To understand it better you must understand the transaction with rpm command. In brief this is what yum does : 1: Installing the package breaks none of the already installed packages (recursively, as they may need packages of their own ...


2

It stand for download only. Same as yum --downloadonly


1

From the repo FAQ: php-* packages are standard ones: they override the default system version (still an admin choice, as you have to enable the repository to get them) only one version can be installed one repository per version (remi, remi-php55 and remi-php56) php54-php-, php55-php- and php56-php* packages are Softwares ...


1

It sounds like this customer should either have their own organisation inside the satellite (and you could then give them org admin rights if you so desired), OR you should clone the channels you need, and then, when they say go, you go into each cloned channel and update it (can't quite think of the terminology right now, but its next to the 'sync' button. ...


2

I have been experiencing exactly the same issue. I tried following the accepted answer above and found I couldn't remove very much because of preexisting dependencies. In the end, I installed yum-utils and ran the following: package-cleanup --dupes This sorted everything out straight away. I was then able to yum update to update Apache, which is what I ...


0

EPEL is not compatible with Amazon Linux. It used to be, back in the very early days when Amazon Linux looked more like CentOS, but it is too different now.


1

# yum install yum-priorities Need to add a priority to all the repos set up. Go to /etc/yum.repos.d and edit all the files and add priority The lower the number the more important it is – so the EPEL ones are the lowest. Example: [epel] name=Extra Packages for Enterprise Linux 6 - $basearch ...


1

In my case I had used yum remove mysql mysql-server. My VPS is using centos release 6.5. I simply ran cpanel upcp script: root@server [~]# /scripts/upcp It has worked for me.



Top 50 recent answers are included