New answers tagged

1

I found that ${VAR:+...} will let you use "..." if the var is set, otherwise it will be empty. So using that with ${VAR:-...} gives me what I'm looking for: yum install docker${DOCKER_VERSION:+-}${DOCKER_VERSION} so if DOCKER_VERSION is set it to "1.8.2" will look like: yum install docker-1.8.2 And if it's not set, it will look like yum install ...


0

yumdownloader [options] package1 [package2...] http://linux.die.net/man/1/yumdownloader This seems to download the packages and their primary dependencies. What it does not do is download the dependencies of the dependencies. It Only downloads the top level dependencies of the package. repotrack [options] package1 [package2...] ...


0

Do you try to run the 'lsb_release -a' on the host ? It is maybe missing.


1

On CentOS, you'll need to find a yum repository that holds the package, and then add it to the system using the Puppet yumrepo resource. class aptdater { if $::osfamily == 'RedHat' { # Only install the yum repo on RH-family systems yumrepo { 'blah': ... } # Override the package to require the yum repo to be deployed first ...


2

You can install php7 for C7 (and others) as a Software Collection (scl) This installs alongside the system provided php 5 and is entirely independent of it. You can find the php7 scl on the REMI repo. You may also be interested in this Q&A on SF.


1

I don't think that is the good way. It is very ornate to configuration and to program if you have to different PHP versions on one server. It's much easier if you have a separate server. Also why do you need both? PHP 5 app are pretty much compatible to PHP 7... if they use mysql_connect instead of mysqli


13

1 is the RPM epoch number. It overrides the normal comparison order on version checking. So, if there is some odd reason why you as a packager want to mark a lower version number as an upgrade, you can tag it with an Epoch number. yum info xorg-x11-xauth Name : xorg-x11-xauth Arch : x86_64 Epoch : 1 Version : 1.0.9 Release : ...


0

You can use below command -: yum install curl-devel --skip-broken or yum install gcc* then yum install curl-devel


-1

I know it is already answered, but I found an easier solution to the above issue yum update openssl openssl-devel


0

yumrepo is provided by ansible-extras The problem is most likely that a version of this module that contains yumrepo has not yet been released. If you check the extras directory in your ansible installation you can verify this. Mine is at: /usr/local/lib/python2.7/site-packages/ansible/modules/extras/packaging/os/ ls -ltr You will see that there is no ...


1

This happens because yum could not remove the old copy of the named file, /usr/lib/python2.7/site-packages/python_augeas-0.5.0-py2.7.egg-info. This may be because the permissions are set incorrectly, or an immutable attribute is set. Check the permissions and attributes for the named file/directory, and of the containing directory, and fix any problems. ...


1

If your machine boots correctly now, I'd move the rescue kernels out of /boot into your home directory (or any other place really) and reboot, make sure it works and then remove them and then rerun yum update. You shouldn't need that many rescue kernels or any if your machine boots correctly Edit: Now, the fun part is if it doesn't boot correctly after ...



Top 50 recent answers are included