[mc-4.8.18 has been broken since release, so I locked 4.8.17]
# grep RETT /etc/os-release
PRETTY_NAME="Fedora 26 (Twenty Six)"
# dnf versionlock list
Last metadata expiration check: 1:33:30 ago on Thu Mar 23 16:44:17 2017 EDT.
mc-1:4.8.17-2.fc25.*
# dnf list mc
Last metadata expiration check: 1:33:33 ago on Thu Mar 23 16:44:17 2017 EDT.
Installed Packages
mc.x86_64 1:4.8.17-2.fc25 @System
# dnf check-update mc
Last metadata expiration check: 1:33:35 ago on Thu Mar 23 16:44:17 2017 EDT.
#
# dnf versionlock delete mc
Last metadata expiration check: 1:41:52 ago on Thu Mar 23 16:44:17 2017 EDT.
Deleting versionlock for: mc-1:4.8.17-2.fc25.*
# dnf list mc
Last metadata expiration check: 1:41:58 ago on Thu Mar 23 16:44:17 2017 EDT.
Installed Packages
mc.x86_64 1:4.8.17-2.fc25 @System
Available Packages
mc.x86_64 1:4.8.18-4.fc26 fedora
# dnf check-update mc
Last metadata expiration check: 1:42:08 ago on Thu Mar 23 16:44:17 2017 EDT.
mc.x86_64 1:4.8.18-4.fc26 fedora
#
How is one expected to discover via dnf when (18 day old) 4.8.19 finally becomes
available and time to delete the lock has arrived? Is this a bug in the
versionlock plugin? DNF itself? Expected behavior?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
