Closed nekohayo closed 3 years ago
could this be related to #163?
I doubt it, though I don't know how dnf versionlock works "behind the scenes"; or at least, I'm pretty sure that if dnfdragora was to try to apply a versionlocked update, it would fail.
Certainly we don't have implemented anything to manage a command like that. However to understand if the problems is related to issue #163 you could change ui.py applying the patch here
I've applied the patch and dragora still wants to update the versionlocked packages.
thanks that means we need something more to understand that a package has been locked by version, maybe first we need to check it in dnfdaemon @Conan-Kudo ?
dnf lists the locked packages in /etc/dnf/plugins/versionlock.list.
Could you please add an example of versionlock.list content? I'm still conviced it should be implemented in dnf-daemon but as i did for protected packages i could do something like that too and cached somehow... and removed them from update list
A question, is there a way for by-passing it (e.g. dnf force or something like that)? otherwise i need to implement also that...
This will be fixed in the next dnfdaemon release, since plugins will be loaded by default.
I use "dnf versionlock" to keep Firefox from being upgraded along the rest, and when you run "dnf upgrade" it doesn't even show up (it says "Nothing to do.") which is the expected behavior. However, in DNFdragora it does show up as an upgradeable package, and I'm not sure it should...