-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin doesn't work anymore with Fedora 41 #89
Comments
Looks like the timestamp is missing which would make sense if the history is not being parsed, and is similar to what happened with the difference between RHEL 5,6,7 and the move to dnf in RHEL8. Which version of the plugin are you running? |
After checking the version again - I was running 2.4.4, even though I thought I am running 2.5.2. I had to disable 2.4.4 and activate 2.5.2
But I did an update today.
This would work now:
but it has the big caveat, that if someone add options or whatever to the update-command the check would break again. Reading the documentation the command for security-updates should be now something like this:
Since I just did updates I cannot check it though, but it doesn't throw any errors. The documentation for that part is here: https://dnf5.readthedocs.io/en/latest/commands/check-upgrade.8.html |
Btw. there is an issue for having dnf5 machine-readable output but since it just closed for 2 weeks now, it didn't land yet in Fedora I guess: rpm-software-management/dnf5#867 |
When I use the plugin with Fedora41 the cache-file plugins_yum.cache looks like this:
And apparently that cannot be parsed.
And since they switched to dnf5 the command
/usr/bin/yum -C --noplugins --quiet --security list updates
doesn't work anymore.I am not 100% sure but I guess it needs to look something like this:
/usr/bin/yum check-update -C --quiet --security list
The
history
-works now different:/usr/bin/yum -C --quiet --noplugins history list
But I tried changing the commands in the plugin on the F41-machine and the error persists. Maybe because there is no update-history anymore?
The text was updated successfully, but these errors were encountered: