Hi I am having difficulty installing the 'createrepo' package on opensuse SLES 15 SP4. I've ran
zypper install createrepo
But I am missing the necessary repos and cannot find the correct repos for the OS I am using. Thanks for any help!
The package is named createrepo_c and can be found in repository SLE-Module-Basesystem15-SP4-Pool. There is also python3-createrepo_c in repository SLE-Module-Desktop-Applications15-SP4-Pool.
Related
I want to install chromedriver in one of the AWS EC2 instance which is linux(Red Hat Enterprise Linux Server release 6.7 Santiago - 64 bit). While installing the chromedriver, we ran into issue due to missing packages. I could find the package here but this in turn requires many other packages. Using any other AMI is not an option.
Error is -
error while loading shared libraries libgconf-2.so.4 cannot open shared object file
I am using Ubuntu x64 and yum didn't work for me. But I found somebody mentioning simply use
$sudo apt install libgconf-2-4
worked for me to install the libgconf.
Please ask yum for the file, libgconf-2.so.4 : $ yum provides */libgconf-2.so.4
Install GConf2 : # yum install GConf2
Packages http://mirror.centos.org/centos/6.8/os/ ... and updates http://mirror.centos.org/centos/6.8/updates/
The chromedriver depends on the same packages / files as GConf2, and then some. Please see for yourself : $ ldd chromedriver , where 'chromedriver' is the unzipped executable.
EDIT :
Solution for the chromedriver issue : Install a chromedriver for RHEL 6, chromedriver-31.0.1650.63-1.el6.x86_64.rpm https://drive.google.com/file/d/0B7S255p3kFXNX1c0UWlGOWpZOHM/view?usp=sharing
Please download the package, and 1) cd Downloads/ 2) yum install chromedriver-31.0.1650.63-1.el6.x86_64.rpm ... and you have /usr/local/bin/chromedriver
P.S. : The EL6 chromedriver was built from the source package chromium-31.0.1650.63-1.el6.src.rpm
You might want to read this CentOS thread about your GLIBCXX_3.4.15. Especially apropos is this answer on the thread, especially the FAQ it references.
CentOS (which aims to be as compatible with RHEL as possible) is a curated LTS distribution (as is RHEL). You might find a version of chromedriver compiled for RHEL 6 in one of the many repositories. If not, you'll probably have to build it yourself.
I was installing libapr-util1-1.3.9-4.1.x86_64 on RHEL v6.6 and it requires libapr-1.so.0 as a dependency. I've searched a lot and couldn't find.
The only rpm I found was vulture-common-3.2-185.1.x86_64.rpm which installs a lot of other packages as well that will conflict with already installed servers and software on my machine.
Does anyone know from where I can get this rpm? Or how to select specific part from the rpm to be installed?
For me yum whatprovides 'libapr-1.so.0' shows apr-1.3.9-5.el6_2.i686 is the package, on my CentOS 6.6.
For CentOS 7.7 I had the same error when trying to configure and compile mesos.
I had to install some additional libraries:
sudo yum install -y git apache-maven python-devel java-devel zlib-devel libcurl-devel openssl-devel cyrus-sasl-devel cyrus-sasl-md5 apr-devel subversion-devel apr-util-devel
For me yum install apr , on my CentOS 7.x.
Try to search for apr-1.4.8-7.el7.x86_64.rpm and apr-util-1.5.2-6.e7.x86_64.rpm
I have downloaded the Puppet Enterprise 3.7 installer from the PuppetLabs website,
but while installing I got the below error...
./puppet-enterprise-installer
ERROR: This is a supported platform, but this is not the installer for this platform. Please use the platform specific installer
(puppet-enterprise-3.7.2-el-6-x86_64).
How can I fix this?
You can get the enterprise linux puppet installer for 3.7.2 following this link.
https://s3.amazonaws.com/pe-builds/released/3.7.2/puppet-enterprise-3.7.2-el-6-x86_64.tar.gz
Looks to me like you downloaded it for the wrong linux distribution.
Hope this helps.
** This only applies to the open source version **
Which distribution are you installing this on? The error is telling you to use the EL6 install package which is available on their yum repo. It's much easier if you just install their repo package:
rpm -Uhv http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
and then run yum install puppet facter.
Will Mercurial work on Redhat Linux? I tried, yum install mercurial, with no success. I tried downloading a tar ball from Mercurial site but it failed when I tried to install. Does Mercurial work at all on Redhat?
Here's instructions for obtaining RPM packages for Linux systems.
Here is a discussion describing many methods for obtaining Mercurial in Red Hat.
On Rhel 7.2 i performed below command and it worked like charm :)
sudo rpm -ivh https://www.mercurial-scm.org/release/centos7/RPMS/x86_64/mercurial-3.4-0.x86_64.rpm
Mercurial project provides RPM packages starting from version 3.4.
I'm trying to upgrade a package using yum on Fedora 8. The package is elfutils. Here's what I have installed locally:
$ yum info elfutils
Installed Packages
Name : elfutils
Arch : x86_64
Version: 0.130
Release: 3.fc8
Size : 436 k
Repo : installed
Summary: A collection of utilities and DSOs to handle compiled objects
There's a bug in this version, and according to the bug report, a newer version has been pushed to the Fedora 8 stable repository. But, if I try to update:
$ yum update elfutils
Setting up Update Process
Could not find update match for elfutils
No Packages marked for Update
Here are my repositories:
$ yum repolist enabled
repo id repo name status
InstallMedia Fedora 8 enabled
fedora Fedora 8 - x86_64 enabled
updates Fedora 8 - x86_64 - Updates enabled
What am I missing?
OK, I figured it out. I needed to upgrade the fedora-release package. That allowed me to see all of the updated packages. Thanks to ethyreal for pointing me to the Yum upgrade FAQ.
i know this seems silly but did you try removing it and reinstalling?
yum remove elfutils
then
yum install elfutils
alternatively you could try updating everything:
yum update
...if their is no update marked in the repository you might try:
yum upgrade
If you look at the listing of the repository packages directory at
Link to Fedora Repository
You will see that you have the latest version in that directory, which is why yum is not upgrading your package. This is the same in both the i386 and x86_64 package directories. So the reason that you are not seeing an update is that there is not a more current version in the repository yet. The notification in the bug report that a new version is in the repository is incorrect.