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.) Hannes _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
