Yum: Failed to check for updates

Community
1

NethServer Version: 7.6.1810 (final)
Module: Software center, updates Locked on current version

Just for info:

This morning, I received an email regarding an error during checking the updates:

Failed to check for updates with the following error message:
Failed to build transaction: nethserver-subscription-3.3.0-1.ns7.noarch requires jq

In Software center, I found the following updates:

nethserver-mail-common 2.4.3 - 1.ns7
nethserver-mail-disclaimer 2.4.3 - 1.ns7
nethserver-mail-filter 2.4.3 - 1.ns7
nethserver-mail-p3scan 2.4.3 - 1.ns7
nethserver-mail-quarantine 2.4.3 - 1.ns7
nethserver-mail-server 2.4.3 - 1.ns7
nethserver-mail-smarthost 2.4.3 - 1.ns7
nethserver-subscription 3.3.0 - 1.ns7
nethserver-subscription-ui 3.3.0 - 1.ns7

On the first attempt to install the updates, I get the following error (from log):

Dec 22 21:47:13 mail pkgaction[30870]: [YumRPMCheckError] [u’ERROR with transaction check vs depsolve:’, ‘jq is needed by nethserver-subscription-3.3.0-1.ns7.noarch’]

After CLEAR YUM CACHE and Unlocked the updates for current version, on the second attempt, everything worked fine (back to Locked after the updates):

Dec 22 21:49:02 Updated: nethserver-mail-common-2.4.3-1.ns7.noarch
Dec 22 21:49:03 Updated: nethserver-mail-filter-2.4.3-1.ns7.noarch
Dec 22 21:49:03 Installed: oniguruma-5.9.5-3.el7.x86_64
Dec 22 21:49:04 Installed: jq-1.5-1.el7.x86_64
Dec 22 21:49:04 Updated: nethserver-subscription-3.3.0-1.ns7.noarch
Dec 22 21:49:04 Updated: nethserver-subscription-ui-3.3.0-1.ns7.noarch
Dec 22 21:49:05 Updated: nethserver-mail-p3scan-2.4.3-1.ns7.noarch
Dec 22 21:49:05 Updated: nethserver-mail-quarantine-2.4.3-1.ns7.noarch
Dec 22 21:49:06 Updated: nethserver-mail-disclaimer-2.4.3-1.ns7.noarch
Dec 22 21:49:06 Updated: nethserver-mail-server-2.4.3-1.ns7.noarch
Dec 22 21:49:07 Updated: nethserver-mail-smarthost-2.4.3-1.ns7.noarch

Yum%20-%20email
Yum - email.JPG850×133 26.9 KB

Yum%20-%20Software%20center
Yum - Software center.JPG1063×684 67.5 KB

2

Hi Gabriel,

Can it be the same issue:?

1 Like
3

Hi Mark,

Sorry, but I didn’t see that post.
Yes, is the same issue and how @dnutan said, “the error could happen again.”
It’s about how locked updates works with some repositories and I don’t think is a big issue.
I wrote this because I thought that if there are more documented cases, the problem can be resolved more quickly by those who are confronted with it.
That’s why I put it in Community section and I said “Just for info”.

1 Like
4

Thank you for reporting, I think everything comes from EPEL and SCLO which are not supporting minor releases when accessing the repositories.

I will try to find a workaround as soon we will be back from holidays!

2 Likes