dnf replacing yum and dnf-yum

[Ralf Corsepius]

On 04/07/2015 05:07 PM, Kevin Fenzi wrote:
> On Tue, 7 Apr 2015 08:38:57 -0500
> Bruno Wolff III <bruno at wolff.to> wrote:
>
>> On Tue, Apr 07, 2015 at 10:22:25 -0300,
>>    Paulo César Pereira de Andrade
>> <paulo.cesar.pereira.de.andrade at gmail.com> wrote:
>>>
>>>   I had also switched back to yum in rawhide due to --skip-broken,
>>> and
>>> in a few updates not even needing it (I would first see what is
>>> broken, and if not something "vital", use --skip-broken), while dnf
>>> would just fail with cryptic messages. I can keep up if kde or gnome
>>> is broken, or some other stuff that does not prevent boot and a
>>> functional system.
>>
>> dnf really does need --skip-broken like support if it is to replace
>> yum. yum can be a lot faster than the needed work around to get dnf
>> to work equivalently. I am considering going back to yum in rawhide
>> rather than continuig to test dnf in rawhide because of this issue.
>
> dnf's default behavior is like yum with --skip-broken already.

WHAT?

--skip-broken is a band-aid to work around packaging mistakes and bugs 
and NOT be the default.

IMO, this kind of behavior is not helpful and therefore should be reverted.

> If thats not working and you need to find out more, add '--best' to see
> things without 'skip-broken'.
>
> If that still doesn't work, please file a bug. ;)

Ralf