On Thu, 2014-11-13 at 16:10 +0100, Miroslav Suchý wrote: > On 11/07/2014 05:09 PM, James Antill wrote: > > It's inside yum, after the transaction runs, in a function called > > verifyTransaction(). > > The two main parts of it are making sure that each transaction member > > that was supposed to be installed was actually installed (and dito. for > > those that were supposed to be removed), and installing/removing the > > yumdb information. > > OK. Sounds good to me for testing purposes to make sure that code is all > right. > But why we have this in production code?
I thought it's that RPM does not guarantee that the transaction will go as planned. E.g. a scriptlet (%preun I think?) can fail and cause the old package not to be removed, resulting in a duplicate being present once the transaction is finished. This way yum has a chance to report that something went terribly wrong. Lubo _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
