[Yum-devel] [PATCH] Fix problems with obsoletes and requires

[James Bowes]

On Wed, Nov 14, 2007 at 12:11:41PM +0100, Florian Festi wrote:
> Hi!
>
> It turns out that calling YumBase.update() from the depsolver in not save - 
> as Seth already suspected. Problem is that the whole TsInfo infrastructure 
> doesn't return reliable values of what has been added to the transaction or 
> not.
>
> The current code relies on the list of transaction members that is returned 
> by YumBase.update(). As a work around this patch switches to monitoring the 
> size of tsInfo. (Test case is in my gold branch)
>
> The big scale solution would be to fix the TransactionData class. But it is 
> unclear to me what these methods should return at all. For setting the 
> dependencies it would be good if they would return the txmbrs that actually 
> are in the tsInfo (should addUpdate return two?). This could do comparably 
> easy if .add() would just return the txmbr so .add*() could pass them out.
>
> For methods like update() (and the calling depsolving code) a list of the 
> new txmbrs would be needed. But may be this should be solved completely 
> different.

This one (with tests) also won't apply. Do you mind resolving the
conflicts?

-James
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum-devel/attachments/20071116/df0b6c48/attachment.pgp