when Doing a “yum update” this morning… I’m getting an error package: —>
Resolving Dependencies
–> Running transaction check
—> Package bind-libs.x86_64 32:9.9.4-61.el7 will be updated
—> Package bind-libs.x86_64 32:9.9.4-61.el7_5.1 will be an update
—> Package bind-libs-lite.x86_64 32:9.9.4-61.el7 will be updated
—> Package bind-libs-lite.x86_64 32:9.9.4-61.el7_5.1 will be an update
—> Package bind-license.noarch 32:9.9.4-61.el7 will be updated
—> Package bind-license.noarch 32:9.9.4-61.el7_5.1 will be an update
—> Package bind-utils.x86_64 32:9.9.4-61.el7 will be updated
—> Package bind-utils.x86_64 32:9.9.4-61.el7_5.1 will be an update
—> Package nethserver-backup-config.noarch 0:2.1.0-1.ns7 will be updated
—> Package nethserver-backup-config.noarch 0:2.2.0-1.ns7 will be an update
–> Processing Dependency: perl-Proc-ProcessTable for package: nethserver-backup-config-2.2.0-1.ns7.noarch
–> Processing Dependency: perl(Proc::ProcessTable) for package: nethserver-backup-config-2.2.0-1.ns7.noarch
—> Package nethserver-backup-data.noarch 0:1.3.5-1.ns7 will be updated
—> Package nethserver-backup-data.noarch 0:1.4.0-1.ns7 will be an update
–> Processing Dependency: sshpass for package: nethserver-backup-data-1.4.0-1.ns7.noarch
–> Processing Dependency: restic for package: nethserver-backup-data-1.4.0-1.ns7.noarch
—> Package nethserver-base.noarch 0:3.4.2-1.ns7 will be updated
—> Package nethserver-base.noarch 0:3.4.4-1.ns7 will be an update
—> Package nethserver-duc.noarch 0:1.4.3-1.ns7 will be updated
—> Package nethserver-duc.noarch 0:1.4.4-1.ns7 will be an update
—> Package nethserver-firewall-base.noarch 0:3.4.1-1.ns7 will be updated
—> Package nethserver-firewall-base.noarch 0:3.4.2-1.ns7 will be an update
—> Package nethserver-firewall-base-ui.noarch 0:3.4.1-1.ns7 will be updated
—> Package nethserver-firewall-base-ui.noarch 0:3.4.2-1.ns7 will be an update
—> Package nethserver-httpd-admin.noarch 0:2.3.3-1.ns7 will be updated
—> Package nethserver-httpd-admin.noarch 0:2.3.4-1.ns7 will be an update
—> Package nethserver-mail-server.noarch 0:1.12.3-1.ns7 will be updated
—> Package nethserver-mail-server.noarch 0:1.12.4-1.ns7 will be an update
—> Package webtop5-zpush.noarch 0:1.1.3-1.ns7 will be updated
—> Package webtop5-zpush.noarch 0:1.1.4-1.ns7 will be an update
–> Running transaction check
—> Package nethserver-backup-config.noarch 0:2.2.0-1.ns7 will be an update
–> Processing Dependency: perl-Proc-ProcessTable for package: nethserver-backup-config-2.2.0-1.ns7.noarch
–> Processing Dependency: perl(Proc::ProcessTable) for package: nethserver-backup-config-2.2.0-1.ns7.noarch
—> Package restic.x86_64 0:0.9.1-1.ns7 will be installed
—> Package sshpass.x86_64 0:1.06-2.el7 will be installed
–> Finished Dependency Resolution
Error: Package: nethserver-backup-config-2.2.0-1.ns7.noarch (nethserver-updates)
Requires: perl(Proc::ProcessTable)
Error: Package: nethserver-backup-config-2.2.0-1.ns7.noarch (nethserver-updates)
Requires: perl-Proc-ProcessTable
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
When I tried the command line above… I’m getting this message …
One of the configured repositories failed (Unknown),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
Thanks…
I ran “yum update --skip-broken” and update the other packages… then re-run ‘yum update’… now I get the following:
Resolving Dependencies
→ Running transaction check
—> Package nethserver-backup-config.noarch 0:2.1.0-1.ns7 will be updated
—> Package nethserver-backup-config.noarch 0:2.2.0-1.ns7 will be an update
→ Processing Dependency: perl-Proc-ProcessTable for package: nethserver-backup-config-2.2.0-1.ns7.noarch
→ Processing Dependency: perl(Proc::ProcessTable) for package: nethserver-backup-config-2.2.0-1.ns7.noarch
—> Package nethserver-backup-data.noarch 0:1.3.5-1.ns7 will be updated
—> Package nethserver-backup-data.noarch 0:1.4.0-1.ns7 will be an update
→ Processing Dependency: sshpass for package: nethserver-backup-data-1.4.0-1.ns7.noarch
→ Processing Dependency: restic for package: nethserver-backup-data-1.4.0-1.ns7.noarch
→ Running transaction check
—> Package nethserver-backup-config.noarch 0:2.2.0-1.ns7 will be an update
→ Processing Dependency: perl-Proc-ProcessTable for package: nethserver-backup-config-2.2.0-1.ns7.noarch
→ Processing Dependency: perl(Proc::ProcessTable) for package: nethserver-backup-config-2.2.0-1.ns7.noarch
—> Package restic.x86_64 0:0.9.1-1.ns7 will be installed
—> Package sshpass.x86_64 0:1.06-2.el7 will be installed
→ Finished Dependency Resolution
Error: Package: nethserver-backup-config-2.2.0-1.ns7.noarch (nethserver-updates)
Requires: perl(Proc::ProcessTable)
Error: Package: nethserver-backup-config-2.2.0-1.ns7.noarch (nethserver-updates)
Requires: perl-Proc-ProcessTable
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
editing /etc/yum.repos.d/epel.repo to baseurl http://*** and comment off metalink https://****
and ran ‘yum --enablerepo=epel update’ then the update went through ok…
I reset back to normal , commenting off baseurl and set back to metalink https://**** for now…
Thank you for all the comment and help… Truly appreciate you all…