On Wed, 2007-02-14 at 15:49 +0200, Panu Matilainen wrote: > On Wed, 14 Feb 2007, Tim Lauridsen wrote: > > Update of /home/groups/yum/cvs//yum-utils > > In directory login1.linux.duke.edu:/tmp/cvs-serv12173 > > > > Modified Files: > > yum-utils.spec > > Log Message: > > added versionlock.list to versionlock plugin to avoid at lot of bugzilla > > reports > > where people have installed all plugins and then yum,pirut etc. are failing > > because the versionlock.list file dont exist. > > Mm.. please revert this. The plugin is disabled by default nowadays (yes I > know it caused a bunch of bugzilla entries back then :) so this doesn't > help anything. I *want* the versionlock plugin in enabled state to cause > full stop until properly configured by administor. If somebody wants > version locking, they're unlikely to want "all updates allowed" policy by > default, so having a default just doesn't make any sense.
It still causes a flood of reports. On the order of one every week or two. If having a default versionlock.list is taboo, then the error case really needs to be handled with something other than a traceback. Because traceback ==> bug to many many people.[1] Jeremy [1] This is partially influenced because apps install traceback handlers to actually give you a nice interface to save and report a bug when you get a traceback. But that's because using a traceback to communicate an error case is roughly the same as calling abort() from a C library _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
