koji-1.13 cannot be resolved as a dependency in f25


I found this issue when installing fedpkg in either f25 container or
VM. There are two koji versions in f25 repos, following steps run in a
f25 container

[root@e151b05870c7 pkgs]# dnf repoquery koji
Last metadata expiration check: 0:01:39 ago on Sat Aug 12 02:25:14 2017.

and koji-1.13 is listed by resolving the dependencies

[root@e151b05870c7 pkgs]# dnf repoquery --requires --resolve fedpkg
Last metadata expiration check: 0:04:56 ago on Sat Aug 12 02:25:14 2017.

The problem is, when start to install fedpkg, koji-1.10 is resolved
rather than version 1.13

[root@e151b05870c7 pkgs]# dnf install fedpkg
Last metadata expiration check: 0:10:38 ago on Sat Aug 12 02:25:14 2017.
Dependencies resolved.
Package Arch Version
Repository Size
koji noarch 1.10.1-13.fc25
fedora 279 k

This problem does not affect fedpkg but also other packages, e.g.
bodhi-client and packagedb-cli, that has "Requires: koji" in SPEC
file. I created a fake package with only koji in Requires, this
problem can also be reproduced with it.


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

By Michael Schwendt at 08/12/2017 - 04: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.

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

By Chenxiong Qi at 08/14/2017 - 01:58

On Sat, 2017-08-12 at 10:10 +0200, Michael Schwendt wrote:
Tested `dnf install fedpkg' in Fedora 26, koji-1.13 can be resolved
from updates repository. Why does dnf behave differently?

I haven't tested it yet, because it make no sense as `dnf install
fedpkg' fails due to the conflict between python2-koji and koji-1.10.

In Fedora 25, koji-1.13 can be resolved when `dnf install koji'. So,
there is a workaround that is to install koji in advance, then fedpkg.