When I want to install the 389-ds Directory into my Linux CentOS Server I am having this issue. I tried to do solve a different way and as well tried to install missing Package but unable to solve the issue and it remains the same error.
I run the Below Command:
yum install -y 389-ds openldap-clients
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
Updating certificate-based repositories.
Setting up Install Process
No package openldap-clients available.
Resolving Dependencies
--> Running transaction check
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: idm-console-framework for package: 389-ds-1.2.2-1.el6.noarch
--> Running transaction check
---> Package 389-admin.x86_64 0:1.1.35-1.el6 will be installed
--> Processing Dependency: /usr/bin/repl-monitor.pl for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: 389-ds-base for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: mod_nss for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: nss-tools for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(CGI) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSCreate) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSMigration) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSUpdate) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSUtil) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Dialog) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DialogManager) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(FileConn) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Inf) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Migration) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::LDIF) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Resource) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Setup) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(SetupLog) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: libadminutil.so.0()(64bit) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: libadmsslutil.so.0()(64bit) for package: 389-admin-1.1.35-1.el6.x86_64
---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
--> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch
---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-dsgw.x86_64 0:1.1.11-1.el6 will be installed
--> Processing Dependency: perl(CGI) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-dsgw-1.1.11-1.el6.x86_64
---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed
--> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch
--> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch
--> Running transaction check
---> Package 389-admin.x86_64 0:1.1.35-1.el6 will be installed
--> Processing Dependency: /usr/bin/repl-monitor.pl for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: 389-ds-base for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: mod_nss for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: nss-tools for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(CGI) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSCreate) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSMigration) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSUpdate) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DSUtil) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Dialog) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(DialogManager) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(FileConn) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Inf) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Migration) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::LDIF) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Resource) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(Setup) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl(SetupLog) for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.35-1.el6.x86_64
--> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.35-1.el6.x86_64
---> Package 389-adminutil.x86_64 0:1.1.19-1.el6 will be installed
---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
--> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch
---> Package 389-dsgw.x86_64 0:1.1.11-1.el6 will be installed
--> Processing Dependency: perl(CGI) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-dsgw-1.1.11-1.el6.x86_64
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-dsgw-1.1.11-1.el6.x86_64
---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed
--> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch
--> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch
--> Processing Dependency: /usr/bin/repl-monitor.pl for package: 389-admin-1.1.35-1.el6.x86_64
>......
--> Finished Dependency Resolution
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Setup)
Error: Package: 389-dsgw-1.1.11-1.el6.x86_64 (epel)
Requires: perl(CGI)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: mod_nss
Error: Package: 389-dsgw-1.1.11-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::API)
Error: Package: 389-dsgw-1.1.11-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::Utils)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(DSUpdate)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Inf)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Dialog)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(CGI)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(DSCreate)
Error: Package: 389-console-1.1.7-1.el6.noarch (epel)
Requires: jpackage-utils
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: /usr/bin/repl-monitor.pl
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::Conn)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl-Mozilla-LDAP
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(SetupLog)
Error: Package: idm-console-framework-1.1.7-2.el6.noarch (epel)
Requires: jss >= 4.2
Error: Package: idm-console-framework-1.1.7-2.el6.noarch (epel)
Requires: ldapjdk
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: 389-ds-base
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(DSMigration)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::LDIF)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Resource)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Migration)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: policycoreutils-python
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::Utils)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(DSUtil)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(DialogManager)
Error: Package: 389-dsgw-1.1.11-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::Conn)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(FileConn)
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: perl(Mozilla::LDAP::API)
Error: Package: 389-ds-1.2.2-1.el6.noarch (epel)
Requires: 389-ds-base
Error: Package: 389-admin-1.1.35-1.el6.x86_64 (epel)
Requires: nss-tools
Error: Package: 389-dsgw-1.1.11-1.el6.x86_64 (epel)
Requires: perl-Mozilla-LDAP
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
It will be great appreciated to you.
Related
Fresh install of Ubuntu 20.x, npm and node on the latest version. Getting these errors:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/#angular/compiler-cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/watchpack/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/sass/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/rollup/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules/karma/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 2602 packages from 1488 contributors and audited 2686 packages in 196.679s
63 packages are looking for funding
run npm fund for details
found 140 vulnerabilities (88 low, 5 moderate, 45 high, 2 critical)
run npm audit fix to fix them, or npm audit for details
How to fix it?
This behaviour is common when cloning a repo from github. Several packages have vulnerabilities and are not up-to-date. The 140 vulnerabilities include packages that are for production and development.
To check for vulnerabilities for production:
npm audit --production
To fix vulnerabilities for production:
npm audit fix --production
To fix every issue you can use npm audit fix, but be aware that some dependencies can be broken.
Many questions such as this one talk about this very annoying behavior on non-mac OS.
When I run npm install I want to remain aware of any warnings, but in Windows or Linux I would get this:
$ ./npm install
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules/laravel-mix/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN bootstrap#4.5.0 requires a peer of jquery#1.9.1 - 3 but none is installed. You must install peer dependencies yourself.
added 279 packages from 165 contributors, removed 4 packages, updated 2 packages and audited 1978 packages in 27.632s
Notice that most WARN are caused by fsevents which is not available outside of macOS.
Some suggest to hide every warnings with:
npm --logevel=error install
Others advise to use:
npm install --no-optional --no-shrinkwrap --no-package-lock
But all these methods does not seem right to me. I only want to execute npm install and have a configuration file that would hide all optional dependencies that are not available on my operating system.
How can I do that?
npm install --no-optional prevents this warning.
I am trying to create a react-native-cli project by command "react-native init projectname" but it is getting stuck by showing this line in command line after some time "info adding required Dev dependencies"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\jest-haste-map\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
info Adding required dev dependencies
fsevents is optional dependency and its used only if you use macOS env, and this is not error its only warning.
I'm trying to use a node package which requires a higher version of webpack than I have installed.
My packages.json file is here.
When I try to install:
npm install webpack#3.12.0
I get the following error:
$ npm install webpack#3.12.0
app#1.0.0 /home/ubuntu/workspace
└── UNMET PEER DEPENDENCY webpack#3.12.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.1.2 (node_modules/watchpack/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN eonasdan-bootstrap-datetimepicker#4.17.47 requires a peer of bootstrap#^3.3 but none was installed.
npm WARN extract-text-webpack-plugin#2.1.2 requires a peer of webpack#^2.2.0 but none was installed.
npm ERR! code 1
I had the same issue, but it was resolved by following the instructions stated by Vu Huu Cuong:
rm -rf node_modules/
npm cache clean
npm install
I'm running a VPS with cPanel / WHM 58.0 (Build 24) and Centos 6.8. I'm attempting to install the varnish cache on the server to improve response but I get this error during the install:
Loaded plugins: fastestmirror, tsflags, universal-hooks
Setting up Install Process
Loading mirror speeds from cached hostfile
* EA4: 198.245.49.52
* base: centos.serverspace.co.uk
* epel: epel.check-update.co.uk
* extras: centos.hyve.com
* updates: centos.serverspace.co.uk
Resolving Dependencies
--> Running transaction check
---> Package varnish.x86_64 0:4.1.3-1.el7 will be installed
--> Processing Dependency: varnish-libs = 4.1.3-1.el7 for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: systemd-units for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.15)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: systemd-sysv for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: jemalloc for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.4)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libpcre.so.1()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libjemalloc.so.1()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvgz.so()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnish.so()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishcompat.so()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvarnishapi.so.1()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libvcc.so()(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Running transaction check
---> Package jemalloc.x86_64 0:3.6.0-1.el6 will be installed
---> Package varnish.x86_64 0:4.1.3-1.el7 will be installed
--> Processing Dependency: systemd-units for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.15)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: systemd-sysv for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: varnish-4.1.3-1.el7.x86_64
--> Processing Dependency: libpcre.so.1()(64bit) for package: varnish-4.1.3-1.el7.x86_64
---> Package varnish-libs.x86_64 0:4.1.3-1.el7 will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: varnish-libs-4.1.3-1.el7.x86_64
--> Processing Dependency: libpcre.so.1()(64bit) for package: varnish-libs-4.1.3-1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: varnish-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: libpcre.so.1()(64bit)
Error: Package: varnish-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: libc.so.6(GLIBC_2.14)(64bit)
Error: Package: varnish-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: libc.so.6(GLIBC_2.15)(64bit)
Error: Package: varnish-libs-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: libpcre.so.1()(64bit)
Error: Package: varnish-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: systemd-sysv
Error: Package: varnish-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: systemd-units
Error: Package: varnish-libs-4.1.3-1.el7.x86_64 (varnish-4.1)
Requires: libc.so.6(GLIBC_2.14)(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Obviously a dependancy is missing but I'm at a loss to resolve it. Any suggestions would be very much appreciated.
Thanks
Kev
You are trying to install too new Varnish to too old Centos.
What repo are you installing Varnish package from?
Run yum list glibc on you machine a examine version.
As it is Centos 6.8, it would be probably 2.12-something and Varnish 4.1.x need at least 2.15 according to your dump.
You have to try either older version or Varnish, or upgrade your distro to newer version.