SUSE artificially uses 2 classes of update candidates, those obsoleting a package (ClassB) and those providing and obsoleting it (ClassA).
This may lead to situations where it needs 2 update steps to install the best candidate. A first step to install the best ClassA candidate. A second step to install an even better ClassB candidate (now as no more ClassA candidates are available).
Not sure if this "feature" is actually needed somewhere, it's in the way if the 1st update step (often a dup) fails because the final update candidate is needed immediately.
As libsolv allows to disable this behavior and to treat all candidates the same. So zypp should provide means to set this option to try to fix those failing dup scenarios.
SUSE artificially uses 2 classes of update candidates, those obsoleting a package (ClassB) and those providing and obsoleting it (ClassA).
This may lead to situations where it needs 2 update steps to install the best candidate. A first step to install the best ClassA candidate. A second step to install an even better ClassB candidate (now as no more ClassA candidates are available).
Not sure if this "feature" is actually needed somewhere, it's in the way if the 1st update step (often a dup) fails because the final update candidate is needed immediately.
As libsolv allows to disable this behavior and to treat all candidates the same. So zypp should provide means to set this option to try to fix those failing dup scenarios.