Enabling only one Repo during update doesn't refresh the cache nor uses the system cache for the selected repo

[ledents]

When updating a package provided by a know: ex. own-repo
using

sudo dnf --disablerepo=* --enablerepo=own-repo check-update packagename

Might not see a new package is available.
Even if
sudo dnf check-update packagename would see a new version.

Executing sudo dnf --disablerepo=* --enablerepo=own-repo clean all before doesn't change the result.
It seems that the system cache for own-repo is not consulted !

[jan-kolarik]

Hello Stefan, I was trying to replicate the issue, but I was not successful. When I have the git package available for upgrade in the updates repository and I execute:

sudo dnf --disablerepo=* --enablerepo=updates check-update git

or

sudo dnf --repo=updates check-update git

Then the update is listed. Even when using --cacheonly to use only cached metadata for the updates repo. Could you provide a reproducer?

[ledents]

Hi Jan,
I have some issues to figure out what causes the issue, which I experience an all of our systems.
Could it be that the package we want to update is dependent of another package which although already installed the repo from which it comes is disabled in our dnf command ?
Could it help if I could provide an strace of both commands with and without disabling the repos (or a diff of the strace)?

[jan-kolarik]

Could it be that the package we want to update is dependent of another package which although already installed the repo from which it comes is disabled in our dnf command ?

In the check-update command, dependencies are not resolved, the packages are really filtered against enabled available repositories.

Could it help if I could provide an strace of both commands with and without disabling the repos (or a diff of the strace)?

It could help, but the better would be to provide a reproducer, like a configuration with a simplest sequence of commands which triggers the described problem. Of course, if it is possible and these are not confidential data...

Btw, does it happen even if you cleanup the local metadata before running each of the commands you mentioned?

[ledents]

Yes it happens even if I do a 'dnf clean al' with and without sudo.