rpm4/rpm5 incompat: rpm5 firing on provides

[Jeffrey Johnson]

On Oct 30, 2012, at 11:14 AM, Elan Ruusamäe wrote:

> On 30.10.2012 16:58, Jeffrey Johnson wrote:
>>> >so, it's already side effect of the uwanted trigger. indeed, the trigger could be fixed not to give error on missing files it tries to move
>>> >
>> You might state what you expect to happen instead of just listing
>> certain commands under the pretense rpm4/rpm5 incompatibilities
>> in the future.
> i am not sure what to expect, is the direction to fix all packages (how to find them), or keep legacy behaviour for some time. that's why i wrote to list

There is no known need "to fix all packages".

Virtual packages (which are nothing more than Provides: will never work correctly
with triggers if you change from using Providename -> NVRA (which was suggested).

>> You have two packages installed and you do not know how to "fix" that
>> condition. And so you start claiming incompatibilities as if that were
>> the root cause of your woes (which it isn't afaict).
> never said i can't fix *that* problem.


> You never asked what the incompatibilities might be either, or even if "different"
might be a better vocabulary than incompatible with …. *what* (your expectations at a minimum).