On Thu, Aug 1, 2013 at 12:41 AM, Ales Kozumplik <akozumpl(a)redhat.com> wrote:
On 08/01/2013 02:36 AM, Ed Marshall wrote:
> Also, consider cases where repository priorities are in use; a
> lower-priority repo that's unreachable may cause unexpected/damaging
> results for the administrator in cases where there's a package version
> mismatch.
>
In cases like this it would be a good idea for the high priority repo to
set skip_if_unavailable = False.
I don't disagree with you, and I'll be making the necessary changes to make
sure I don't get bitten by a change of behavior here, regardless of what
happens.
I'm just bringing it up because I'm likely not the only one using yum
priorities, and this is a subtle side-effect of that; one that some folks
might not be aware of (and while I'm aware of it, I didn't consider the
possibility that the defaults might change out from under me ;)).
In the dnf case, it likely doesn't matter; I don't think dnf has grown
support yet for repo cost/priority yet, has it? I only commented because I
saw the BZ suggesting a similar change for yum, and wanted to warn that
changing a default like this in mid-release might catch a few people by
surprise.
(I was a little concerned to see that change show up mid-release for dnf,
to be honest, but at least dnf's adoption is limited to the curious right
now.)
--
Ed Marshall <esm(a)logic.net>
Felix qui potuit rerum cognoscere causas.
http://esm.logic.net/