I have Centos 7.9 server and I'm trying to install nodejs.
curl --silent --location https://rpm.nodesource.com/setup_18.x | sudo bash -
repository is configured in the file /etc/yum.repos.d/nodesource-el7.repo
after that when typed sudo yum install nodejs its returned:
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 2:18.13.0-1nodesource will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.28)(64bit) for package: 2:nodejs-18.13.0-1nodesource.x86_64
--> Processing Dependency: libm.so.6(GLIBC_2.27)(64bit) for package: 2:nodejs-18.13.0-1nodesource.x86_64
--> Finished Dependency Resolution
Error: Package: 2:nodejs-18.13.0-1nodesource.x86_64 (nodesource)
Requires: libc.so.6(GLIBC_2.28)(64bit)
Error: Package: 2:nodejs-18.13.0-1nodesource.x86_64 (nodesource)
Requires: libm.so.6(GLIBC_2.27)(64bit)
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
mod_fcgid-2.3.9-6.el7.x86_64 has missing requires of httpd-mmn = ('0', '20120211x8664', None)
and I can't install any other version of nodejs
Related
I am trying to build a docker image through Jenkins using Centos 8 as base. My Dockerfile looks like this (only relevant lines are included):
RUN yum update -y \
&& curl -sL https://rpm.nodesource.com/setup_current.x | bash - \
&& yum install -y nodejs unzip sudo numactl-libs libnsl libaio \
Build is failing with below error:
--> Finished Dependency Resolution
[91mError: Package: 2:nodejs-18.7.0-1nodesource.x86_64 (nodesource)
Requires: libstdc++.so.6(GLIBCXX_3.4.21)(64bit)
[91mError: Package: 2:nodejs-18.7.0-1nodesource.x86_64 (nodesource)
Requires: libm.so.6(GLIBC_2.27)(64bit)
[91mError: Package: 2:nodejs-18.7.0-1nodesource.x86_64 (nodesource)
Requires: libstdc++.so.6(GLIBCXX_3.4.20)(64bit)
[91mError: Package: 2:nodejs-18.7.0-1nodesource.x86_64 (nodesource)
Requires: libc.so.6(GLIBC_2.28)(64bit)
[91mError: Package: 2:nodejs-18.7.0-1nodesource.x86_64 (nodesource)
Requires: libstdc++.so.6(CXXABI_1.3.9)(64bit)
It seems like since the node version is not specified in dockerfile, the latest node version (18.7.0) is being installed and hence some dependencies are not found. Last build (few months back) had node v17. If this is the root cause, can someone help me with suggestions on how this can be fixed.
I have deleted my phpmyadmin by mistake while updating to php version 7.3
Now when i tried to install it back using this command sudo yum install phpmyadmin it is not installing I'm getting this response:
--> Processing Dependency: php-simplexml for package: phpMyAdmin49-4.9.3-1.el7.ius.noarch
--> Processing Dependency: php-recode for package: phpMyAdmin49-4.9.3-1.el7.ius.noarch
--> Processing Dependency: php-mbstring for package: phpMyAdmin49-4.9.3-1.el7.ius.noarch
--> Running transaction check
---> Package php-mbstring.x86_64 0:7.3.17-1.el7.remi will be installed
--> Processing Dependency: libonig.so.5()(64bit) for package: php-mbstring-7.3.17-1.el7.remi.x86_64
---> Package php-recode.x86_64 0:7.3.17-1.el7.remi will be installed
--> Processing Dependency: librecode.so.0()(64bit) for package: php-recode-7.3.17-1.el7.remi.x86_64
---> Package php-xml.x86_64 0:7.3.17-1.el7.remi will be installed
---> Package phpMyAdmin49.noarch 0:4.9.3-1.el7.ius will be installed
--> Processing Dependency: php-zip for package: phpMyAdmin49-4.9.3-1.el7.ius.noarch
Package php73-common-7.3.16-1.el7.ius.x86_64 is obsoleted by php-common-7.3.17-1.el7.remi.x86_64 which is already installed
--> Running transaction check
---> Package oniguruma5.x86_64 0:6.9.4-1.el7.remi will be installed
---> Package phpMyAdmin49.noarch 0:4.9.3-1.el7.ius will be installed
--> Processing Dependency: php-zip for package: phpMyAdmin49-4.9.3-1.el7.ius.noarch
Package php73-common-7.3.16-1.el7.ius.x86_64 is obsoleted by php-common-7.3.17-1.el7.remi.x86_64 which is already installed
---> Package recode.x86_64 0:3.6-38.el7 will be installed
--> Finished Dependency Resolution
Error: Package: phpMyAdmin49-4.9.3-1.el7.ius.noarch (ius)
Requires: php-zip
Available: php-common-5.4.16-46.el7.x86_64 (base)
php-zip
Available: php-common-5.4.16-46.1.el7_7.x86_64 (updates)
php-zip
Available: php-pecl-zip-1.18.1-1.el7.remi.5.6.x86_64 (remi-php56)
php-zip = 1:1.18.1-1.el7.remi.5.6
Available: php-pecl-zip-1.18.1-1.el7.remi.7.3.x86_64 (remi-php73)
php-zip = 1:1.18.1-1.el7.remi.7.3
Available: php-pecl-zip-1.18.2-1.el7.remi.5.6.x86_64 (remi-php56)
php-zip = 1:1.18.2-1.el7.remi.5.6
Available: php-pecl-zip-1.18.2-1.el7.remi.7.3.x86_64 (remi-php73)
php-zip = 1:1.18.2-1.el7.remi.7.3
Available: php72u-common-7.2.26-1.el7.ius.x86_64 (ius)
php-zip
Available: php72u-common-7.2.27-1.el7.ius.x86_64 (ius)
php-zip
Available: php72u-common-7.2.28-1.el7.ius.x86_64 (ius)
php-zip
Available: php73-common-7.3.14-1.el7.ius.x86_64 (ius)
php-zip
Available: php73-common-7.3.15-1.el7.ius.x86_64 (ius)
php-zip
Available: php73-common-7.3.16-1.el7.ius.x86_64 (ius)
php-zip
Installed: php-common-7.3.17-1.el7.remi.x86_64 (#remi-php73)
Not found
Available: php-common-5.6.40-19.el7.remi.x86_64 (remi-php56)
Not found
Available: php-common-5.6.40-20.el7.remi.x86_64 (remi-php56)
Not found
Available: php-common-7.3.16-1.el7.remi.x86_64 (remi-php73)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
the php version was updated with no problems however the phpmyadmin it's not installing what can i do to get it back?
Don't mixed so much PHP providers, especially; don't mix "IUS" and "Remi".
If you want PHP 7.3, only keep "remi-php73", and you can take phpMyAdmin (5.0.2) from "remi"
yum-config-manager --enable remi-php73
yum-config-manager --disable remi-php56
yum-config-manager --disable ius
yum --enablerepo=remi install phpMyAdmin
As Remi said, don't mix his repository with IUS. Pick one or the other. If you decide to go with IUS, we have phpMyAdmin49 and phpMyAdmin50 packages available. Asking yum to install phpMyAdmin will likely result in it trying to install the EPEL phpMyAdmin package, which is stuck at version 4.4.x to remain compatible with stock PHP 5.4.x.
I'm try install dotnet by command for OS Amazon Linux 2 AMI
sudo yum install -y dotnet-sdk-2.1.4
And it show for me:
Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main | 2.1 kB 00:00:00
amzn-updates | 2.5 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package dotnet-sdk-2.1.4.x86_64 0:2.1.4-1 will be installed
--> Processing Dependency: dotnet-runtime-2.0.5 >= 2.0.5 for package: dotnet-sdk-2.1.4-2.1.4-1.x86_64
--> Processing Dependency: aspnetcore-store-2.0.5 >= 2.0.5 for package: dotnet-sdk-2.1.4-2.1.4-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.5.x86_64 0:2.0.5-1 will be installed
--> Processing Dependency: aspnetcore-store-2.0.3 >= 2.0.3 for package: aspnetcore-store-2.0.5-2.0.5-1.x86_64
---> Package dotnet-runtime-2.0.5.x86_64 0:2.0.5-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.5-2.0.5-1.x86_64
--> Processing Dependency: dotnet-hostfxr-2.0.5 for package: dotnet-runtime-2.0.5-2.0.5-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.3.x86_64 0:2.0.3-1 will be installed
--> Processing Dependency: aspnetcore-store-2.0.0 >= 2.0.0 for package: aspnetcore-store-2.0.3-2.0.3-1.x86_64
---> Package dotnet-hostfxr-2.0.5.x86_64 0:2.0.5-1 will be installed
--> Processing Dependency: dotnet-host >= 2.0.5 for package: dotnet-hostfxr-2.0.5-2.0.5-1.x86_64
---> Package dotnet-runtime-2.0.5.x86_64 0:2.0.5-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.5-2.0.5-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.0.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-host.x86_64 0:2.1.0-1 will be installed
---> Package dotnet-runtime-2.0.5.x86_64 0:2.0.5-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.5-2.0.5-1.x86_64
--> Finished Dependency Resolution
Error: Package: dotnet-runtime-2.0.5-2.0.5-1.x86_64 (packages-microsoft-com-prod)
Requires: openssl-libs
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I enter
sudo yum list
And i can't found openssl-libs in result.
Also i installed openssl-devel, but result is same.
Update:
I compared the used repositories to another server. There it was installed successfully.
First server repository repository: !amzn-main/latest, os version: "Amazon Linux AMI 2018.03"
Second server repository (with installed dotnet) repository: !amzn2-core/2017.12/x86_64, os version: "Amazon Linux 2 (2017.12) LTS Release Candidate"
I think yum cannot get openssl-libs from repository. How can I install this package?
I ran into a similar issue while installing Powershell. I managed to fake the installation of the latest CentOS package like this:
sudo rpm -ivh https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/openssl-libs-1.0.2k-21.el7_9.x86_64.rpm --justdb --force
The --justdb --force added it to the RPM database but without touching the filesystem.
While installing libpcap-devel on fedora 21 following error are coming :-
**yum install libpcap-devel**
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> Package libpcap-devel.x86_64 14:1.6.2-1.fc21 will be installed
--> Processing Dependency: libpcap = 14:1.6.2-1.fc21 for package: 14:libpcap-devel-1.6.2-1.fc21.x86_64
--> Running transaction check
---> Package libpcap.i686 14:1.6.2-1.fc21 will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.11) for package: 14:libpcap-1.6.2-1.fc21.i686
--> Running transaction check
---> Package glibc.i686 0:2.20-5.fc21 will be installed
--> Processing Dependency: glibc-common = 2.20-5.fc21 for package: glibc-2.20-5.fc21.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.20-5.fc21.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.20-5.fc21.i686
--> Running transaction check
---> Package glibc.i686 0:2.20-5.fc21 will be installed
--> Processing Dependency: glibc-common = 2.20-5.fc21 for package: glibc-2.20-5.fc21.i686
---> Package nss-softokn-freebl.i686 0:3.17.2-1.fc21 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.20-5.fc21.i686 (fedora)
Requires: glibc-common = 2.20-5.fc21
Installed: glibc-common-2.20-8.fc21.x86_64 (installed)
glibc-common = 2.20-8.fc21
Available: glibc-common-2.20-5.fc21.x86_64 (fedora)
glibc-common = 2.20-5.fc21
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
The kernel i am using-
uname -r
4.1.13-100.fc21.x86_64
I cannot erase glibc-common-2.20-8.fc21.x86_64 , since it is with kernel package, can someone help me in this?
I installed the wrong version of rpmforge for el7. Then I ran an update which installed this package on my system
python-crypto-2.6.1-1.el7.rf.x86_64
Notice the el7 but I am on rhel6. I then realized and removed the wrong repository and installed the right one for el6.
$ rpm -qa | grep rpmfor
rpmforge-release-0.5.2-2.el6.rf.x86_64
But the above process has broken the update process, which I know I could work around using --skip-broken option. How do I downgrade for the above mentioned package. I tried to uninstall and install it back again but I get this error:
Error: Trying to remove "c4ebpl", which is protected
It shows me some protected packages which can't be removed.
Update process using sudo yum update gives me this error:
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libgmp.so.10()(64bit)
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libc.so.6(GLIBC_2.14)(64bit)
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: python(abi) = 2.7
Installed: python-2.6.6-52.el6.x86_64 (#el66/$releasever)
python(abi) = 2.6
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libpython2.7.so.1.0()(64bit)
You could try using --skip-broken to work around the problem
Would anyone know how to downgrade to the original packages? Is there a way to do a factory reset? Or do I need to re-install linux again?
Some things I tried:
I deleted the python-crypto.x86_64 package using this command
sudo rpm --nodeps -e python-crypto.x86_64
And the update went through. So I thought I should install the python-crypto.x86_64package now as I have the right el6 rpmforge repository. So I ran this command sudo yum install python-crypto.x86_64 but I got the same error:
Resolving Dependencies
--> Running transaction check
---> Package python-crypto.x86_64 0:2.6.1-1.el7.rf will be installed
--> Processing Dependency: python(abi) = 2.7 for package: python-crypto-2.6.1-1.el7.rf.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: python-crypto-2.6.1-1.el7.rf.x86_64
--> Processing Dependency: libpython2.7.so.1.0()(64bit) for package: python-crypto-2.6.1-1.el7.rf.x86_64
--> Processing Dependency: libgmp.so.10()(64bit) for package: python-crypto-2.6.1-1.el7.rf.x86_64
--> Finished Dependency Resolution
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libgmp.so.10()(64bit)
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libc.so.6(GLIBC_2.14)(64bit)
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: python(abi) = 2.7
Installed: python-2.6.6-52.el6.x86_64 (#el66/$releasever)
python(abi) = 2.6
Error: Package: python-crypto-2.6.1-1.el7.rf.x86_64 (rpmforge)
Requires: libpython2.7.so.1.0()(64bit)
You could try using --skip-broken to work around the problem
I don't know why its trying to find the el7 package? I have these libraries in my machine.
$ rpm -qa | grep rpmfor
rpmforge-release-0.5.3-1.el7.rf.x86_64
Solution from #Michael Hapton on this link
Here is the solution. I take no credit for it.
First you need to install the correct rpmforge-release package. Download it and use rpm -U --oldpackage to install it over the wrong package.
Second, you need to clean the cached yum metadata that it had. Use yum clean all to get rid of everything.
Third, use yum distro-sync to downgrade any packages that were installed for the wrong distribution. (And note that this will also upgrade any out-of-date packages.)