I've followed precisely the instructions in /usr/share/doc/yum-versionlock-1.1.11/README, yet yum-versionlock causes yum to die with "Error: None". Example: # repoquery --quiet --envra --pkgnarrow=installed ntfs-3g yum yum-utils 0:yum-utils-1.1.11-1.fc9.noarch 0:yum-3.2.11-1.fc9.noarch 2:ntfs-3g-1.2121-0.1.RC.fc9.i386 # cd /etc/yum/pluginconf.d # ls -l total 12 -rw-r--r-- 1 root root 143 2008-01-30 01:18 fastestmirror.conf -rw-r--r-- 1 root root 69 2008-02-19 23:33 versionlock.conf -rw-r--r-- 1 root root 33 2008-02-19 23:50 versionlock.list # cat versionlock.conf [main] enabled = 1 locklist = /etc/yum/pluginconf.d/versionlock.list # cat versionlock.list 2:ntfs-3g-1.2121-0.1.RC.fc9.i386 # yum update Loaded plugins: fastestmirror, versionlock Loading mirror speeds from cached hostfile * livna-development: mirrors.tummy.com * development: gulus.usherbrooke.ca Reading version lock configuration Error: None Am I doing something wrong, or is yum-versionlock broken?
Apparently versionlock has been broken upstream for a couple of releases now, the fix is simple: http://devel.linux.duke.edu/gitweb/?p=yum-utils.git;a=commitdiff;h=2cd3ae080486ce46e166c3d5a8ebc6b5b19dd6e2;hp=f4eefa9053ae5b13dbd5fd6bb7f555fc1e11004d ...it should also be fixed in the next yum-utils rawhide release.
Ok, thanks; I hacked up versionlock.py on my local disk until updated packages trickle down the appropriate channels. Yum now runs with no errors (and properly excludes the ntfs-3g package).
Updated to yum-versionlock-1.1.11-5.fc9.noarch today and it once again blew away my manual edit for this fix. It has not been fixed yet in rawhide.
it will be out in 1.1.12 of yum-utils. for now, closed upstream