[Yum-devel] [PATCH] Use state-aware filename rpmdb index if rpm supports it

Panu Matilainen pmatilai at laiskiainen.org
Wed Aug 31 17:21:38 UTC 2011


On 08/31/2011 06:49 PM, seth vidal wrote:
> On Wed, 2011-08-31 at 11:44 +0300, Panu Matilainen wrote:
>> This fixes some cases where yum depsolver and rpm>= 4.9.0
>> disagree on dependencies on removal (including but not limited
>> to the example in BZ 729973), causing "ERROR with transaction check
>> vs depsolve" errors. The state-aware file index is currently only
>> in rpm.org HEAD but likely to get backported to 4.9.x series.
>>
>> Also it requires 'yum clean rpmdb' on first go to wipe previously cached
>> data, pointing out another problem: the state-aware files index is dynamic,
>> and should not be cached across transactions as a transaction can change
>> file states of packages that aren't included in that transaction.
>
>
>
> A couple of questions:
>
> does the state-aware file index impact:
>
> rpm -qf?
> rpm -ql?
> rpm -q --whatprovides /some/file

-qf and --whatprovides are the same for paths, and yes those are 
affected (currently only in rpm.org HEAD though). -ql still behaves the 
same as always for now, not quite sure what to do about that and some 
other quirks like ghosts yet. It might have to change as well, but some 
way of querying the entire contents without considering state needs to 
be available I suppose.

> Does the state-aware index get impacted by --nodocs/--noconf or is it
> just for multilib overlays?

It covers all "physical" files, so yes --nodocs/--noconf etc affect it 
besides multilib.

>
> I'm trying to understand the impact of this index on what rpm will
> return - inclusive of deps.

Sure, feel free to ask if there are further unclear issues.

Oh and note that the rpm side of this is nowhere near fully covered yet 
either, so for now this basically just a direction towards which rpm is 
moving.

	- Panu -


More information about the Yum-devel mailing list