AIX Open Source

Hi everyone!

We recently noticed that "yum update" (haven't switched to dnf yet...) is not updating the sudo package.

We use reposync to sync the IBM repo to a server on our network, and then use that as repo server for all our AIX LPARs.

We are running sudo version 1.8.15-1noldap.ppc, while the latest seems to be 1.9.15p5-1.ppc.

Upon some investigation it seems the older versions in the repo, prior to 1.8.15-2.ppc, have an unexpected epoch number, which means they superseded newer packages without an epoch number. This is illustrated by the following (abbreviated) repoquery output:

# repoquery --nevra --show-duplicates "*sudo*"
sudo-0:1.8.15-2.ppc
sudo-0:1.8.20p2-1.ppc
…
sudo-0:1.9.14p3-1.ppc
sudo-0:1.9.15p5-1.ppc
sudo-2001030501:1.6.5p2-2.ppc
…
sudo-2008050201:1.6.9p23-2.ppc
sudo-2008050201:1.6.9p23-2noldap.ppc
sudo-2008050201:1.8.15-1noldap.ppc
sudo_ids-0:1.8.20p2-1.ppc
…
sudo_ids-0:1.9.15p5-1.ppc
sudo_noldap-0:1.9.5p2-1.ppc
sudo_noldap-0:1.9.12p2-1.ppc
...

sudo_noldap-0:1.9.15p5-1.ppc
sudo_noldap-0:1.9.15p5-1.ppc

The temporary workaround of course is to "yum downgrade -y sudo-0:1.9.15p5-1.ppc", but a subsequent "yum update" will propose upgrading back to 2008050201:1.8.15-1noldap.

Does anyone have any idea whether there is/was a valid reason for that epoch number? It looks like a mistake to me. The only permanent fix for this is likely to remove the old packages from the IBM repo?

Thanks in advance for any thoughts & advice on how to handle this!

Kind regards,

Clifford

Hi Clifford,

Now we don't have this older version of package in the repository.

You can install latest  one by giving the exact version as below.

dnf install sudo-1.9.15p5-1

Please note, now sudo build with noldap is named as sudo_noldap

Hi everyone!

We recently noticed that "yum update" (haven't switched to dnf yet...) is not updating the sudo package.

We use reposync to sync the IBM repo to a server on our network, and then use that as repo server for all our AIX LPARs.

We are running sudo version 1.8.15-1noldap.ppc, while the latest seems to be 1.9.15p5-1.ppc.

Upon some investigation it seems the older versions in the repo, prior to 1.8.15-2.ppc, have an unexpected epoch number, which means they superseded newer packages without an epoch number. This is illustrated by the following (abbreviated) repoquery output:

# repoquery --nevra --show-duplicates "*sudo*"
sudo-0:1.8.15-2.ppc
sudo-0:1.8.20p2-1.ppc
…
sudo-0:1.9.14p3-1.ppc
sudo-0:1.9.15p5-1.ppc
sudo-2001030501:1.6.5p2-2.ppc
…
sudo-2008050201:1.6.9p23-2.ppc
sudo-2008050201:1.6.9p23-2noldap.ppc
sudo-2008050201:1.8.15-1noldap.ppc
sudo_ids-0:1.8.20p2-1.ppc
…
sudo_ids-0:1.9.15p5-1.ppc
sudo_noldap-0:1.9.5p2-1.ppc
sudo_noldap-0:1.9.12p2-1.ppc
...

sudo_noldap-0:1.9.15p5-1.ppc
sudo_noldap-0:1.9.15p5-1.ppc

The temporary workaround of course is to "yum downgrade -y sudo-0:1.9.15p5-1.ppc", but a subsequent "yum update" will propose upgrading back to 2008050201:1.8.15-1noldap.

Does anyone have any idea whether there is/was a valid reason for that epoch number? It looks like a mistake to me. The only permanent fix for this is likely to remove the old packages from the IBM repo?

Thanks in advance for any thoughts & advice on how to handle this!

Kind regards,

Clifford