Tag Info

New answers tagged

0

Regarding why EPEL does not contain the latest versions, taken from the EPEL Guidelines and Policies: Why not a rolling release with latest packages like what was in Fedora Extras? Why should we? That would be what Fedora Extras did and worked and works well for it -- but that's mainly because Fedora (Core) has lots of updates and a nearly ...


2

RHEL 6 was released in 2010 and one of the consequences of choosing an enterprise distribution with long term support cycles is you'll end up with seeming old versions of software, a trade-off for stability and better support for third-party software. (Note: an old version do not equate to insecure, read up on backporting of security updates.) Typically ...


0

Whay I ended up doing and worked for me: yum list installed | grep @rpmforge rpm --erase --nodeps <list obtained with first command> Then disabled rpmforge repos from the config files yum install <list obtained with first command>


0

declare -x didnt work.This worked for me. [root@host ~]# unset LD_LIBRARY_PATH If any variable is defined in /etc/ld.so.conf then remove it and run # ldconfig command to recreate ld cache. [root@host ~]# ldconfig Confirm that the Python library now links to the correct /lib64/libexpat.so.1 library. [root@host ~]# ldd ...


1

Use yum history list to see recent yum transactions. Use yum history info <ID> to view the details of a transaction. Use yum history undo last to revert the most recent transaction, or yum history undo <ID> to revert a specific transaction.


2

This is an old question, but it is still one the first results in google search, so I'd like post the solution that got my problem solved. 1) create a new file /etc/yum.repos.d/city-fan.repo 2) Paste the following contents: [CityFan] name=City Fan Repo baseurl=http://www.city-fan.org/ftp/contrib/yum-repo/rhel5/x86_64/ enabled=1 ...


2

You miss the optional repository: rhn-channel --add --channel=rhel-x86_64-server-optional-6 Once you added this channel, you will find the git-all and git-svn packages. [root@ls406135 ~]# yum install git-svn Loaded plugins: rhnplugin This system is receiving updates from RHN Classic or RHN Satellite. ... ...


1

This is a more updated answer for AWS EC2 users as of April 2015: As of Amazon Linux AMI 2015.03, Python 2.7 or Python 3 is supported directly by Amazon by default. Python 2.6, 2.7, and 3.4 can be installed simultaneously and are managed by the alternatives command. All of this is documented clearly on the top half of: ...


1

It seems there is a problem with the /usr/local/lib/python2.7/ssl.py file. Can you post an the md5sum of this file both from the failing machine and from a working one? Can you also check if the python version is the same?


0

In case you want to know which packages are excluded due to priority protections you can use yum list updates -d3


0

For keeping repos in sync, pulp can do the job for sure. Either you could put the secondary server in place and configure it as a node with the primary one as a server, then you can bind whichever repo you want to the node and preform a node sync which will then sync the full repo. This requires both servers be pulps. Second approach also using pulp is you ...


0

To see what package contains a command, you can use sudo yum search unar. If you still can't find it, it may not be present in the repos you have enabled and you might need to enable additional repos or install that package manually or build it from source - just be sure any repos you add are trustworthy.


0

I'm not sure what do do for RHEL6 without support. If you were running, CentOS6 and could make use of the EPEL repository this would be the answer: $ sudo yum install epel-release && sudo install php-pecl-ssh2 $ yum whatprovides "/usr/lib64/php/modules/ssh2.so" Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile ...


0

If you simply upgrade using rpm -U, the binaries will be upgraded, but the configuration files will remain the same. See http://stackoverflow.com/questions/14511334/rpm-upgrade-handling-of-config-files


1

I think is better if you use the whole packet name in this case yum remove rpm-4.4.2.3-36.el5_11.i386 and yum remove sssd-client-1.5.1-70.el5.i386


1

remove conflicted packages: yum remove rpm sssd-client and then install them back: yum install rpm sssd-client


0

I was in the same boat after aborting a yum update that was working on glibc. Dennis Kaarsemaker pointed me in the right direction. The OP didn't mark any of the answers as accepted. Just to corfirm which parts worked in my case: The package-cleanup --cleandupes wouldn't comply and complained about packages that were protected. The rpm --rebuilddb ...


0

They are packaged by different maintainers and may conflict in the sense that they provide the same files etc, and possibly mysql rpm:s from official repos will not consider themselves upgrades of the mysql rpm:s installed from remi. I think dump the databases, uninstall all mysql rpm:s from remi repo, disable remi repo, yum clean all, install mysql from ...


0

This will install the package ignoring dependencies but automatically looking up the download URL from your repositories. rpm -Uvh --nodeps `repoquery --location winswitch` When updating, you can do the same command before doing a "yum update" so that winswitch will be properly updated.


0

You're trying to install packages meant for EL6 onto EL7. This will not work and there is no way to make it work. They are not compatible. If you really want to run an old Varnish version, then use EL6 to begin with. The version of varnish included with EPEL for EL7 is 4.0, so it is not likely there will ever be 3.0 built for EL7.



Top 50 recent answers are included