On Sat, 2010-08-07 at 18:55 +0200, Hannes Frederic Sowa wrote: > Hi! > > I wondered why exceptions from plugins are currently not handled > more gracefully. While developing a plugin for yum I had some > exceptions thrown from my plugin. This led to some inconsistency > in my yumdb-history.sqlite: > > tid|name|epoch|version|release|arch|pkgtupid|state|done|nevra > 52|VirtualBox-3.2|0|3.2.6_63112_fedora13|1|x86_64|2439|Updated|FALSE|VirtualBox-3.2-0:3.2.6_63112_fedora13-1.x86_64 > 62|VirtualBox-3.2|0|3.2.6_63112_fedora13|1|x86_64|2439|Updated|FALSE|VirtualBox-3.2-0:3.2.6_63112_fedora13-1.x86_64 > > Especially the transaction data from /var/lib/yum/yumdb is missing. > Otherwise, if plugins should disrupt yum, how should I deal with that > inconsistencies? Is there a tool to synchronize rpmdb and yumdb and > spits out a warning if packages are missing? > > (I'm currently working on a yum-auditing tool to gather the data of > package-changes in a central database.) That's cool. there are now history plugin hooks that might help you - they're in yum 3.2.28. also - ultimately if something aborts the whole process then yum plugins can kill things off. suggestions? -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
