seth vidal-3 wrote: > > On Wed, 2008-07-09 at 00:23 -0700, Frédéric PICA wrote: >> Greetings, >> >> There is nobody to help me ? >> This is a big problem for me, I'm developping a package changes >> monitoring >> system that is cross distribution (for now, yum and apt based) that I >> will >> soon release on SourceForge or other. >> The apt based plugin works well but I'm still having troubles and this is >> a >> really big problem. >> >> Is there any documentation for yum developers ?? >> >> I still not understand why in the package transaction, the >> yum-metadata-parser (this is not the only one) updates attribute is empty >> while the state of the package is TS_UPDATE ! >> Is this a bug or is there something I have not understood in Yum >> transaction >> handling ?? >> >> Thanks for your help, >> Frédéric PICA > > I never saw your earlier message. In fact, I'm not sure if it made it to > the mailing list. > > What is the plugin supposed to do? Also what version of yum are you > using? If you're using 3.0.X from rhel5.0 or rhel 5.1 then update to > rhel 5.2 and yum 3.2.8 and see if the problem you're seeing no longer > exists before we chase down what's going on. > > -sv >
The plugin is supposed to put every transaction in a database, with the date, the channel of the package, the type of the package (security,bugfix,...) to have an history. He also maintain the list of currently installed packages on the system, ... I have tried new things this morning : Apparently, the problem appears only when I want to update Yum from a fresh RHEL 5.0 (3.0.1-5.el5) install to the latest available in the repositories (3.2.8-9.el5_2.1), and only yum (yum install yum). The problem disappeared when installing Yum with all of the other updates (yum update) : In this case the yum-metadata-parser updates attribute is correctly populated and none of the other installed packages have the problem. I don't know the origin of the bug and if it's corrected in later versions of yum. I've tried (from a fresh install) to update Yum and after to update all the packages and no problems appears. If you want to have a look at what's going on to see if this problem can appear in later version of Yum, I think you can reproduce the bug : From a fresh RHEL5 installation, update yum to the latest available in the repositories and look at the transaction in the posttrans plugin hook. I can do some specific test if you want, feel free to ask me. Thanks for your quick answer. PS: My first message is here https://lists.dulug.duke.edu/pipermail/yum-devel/2008-June/005315.html -- View this message in context: http://www.nabble.com/-plugin--yum-packages-transaction-tp18010946p18361307.html Sent from the YUM - Dev mailing list archive at Nabble.com. _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
