DevHeads.net

Reply to comment

Re: koji-1.13 cannot be resolved as a dependency in f25

By Michael Schwendt at 08/12/2017 - 03:10

Your analysis is incomplete. It's not sufficient to claim there is an
issue. "Requires: koji" is non-versioned, so the depsolver behaviour is
implementation dependent. It may pull in _either_ build of the koji package
to satisfy the dependencies. There is no rule [yet] that would pull in the
latest EVR of a package already when installing it for the first time. Yum
hasn't done it, with its author refusing to change that behaviour, and DNF
probably mimics that behaviour. A subsequent "dnf update" may update koji
immediately. Have you tested that?

Further, it is absolutely normal that some packages exist in the repos
with multiple builds. For example, the initial release in the [fedora]
repo, an update in the [updates] repo, and for several years in the past,
older repository maintenance tools have kept multiple builds in the repos.
That could become the default again in the future.

And finally, it could be that there's a real issue that would require a
detailed look at the packages, which may cause dnf to not choose the
latest koji for the initial transaction set.

Reply