On 2017-08-22 16:22, Richard W.M. Jones wrote:
I don't know what component to file this bug under ...
When running ‘fedora-review -b 1477363’, it fails to test build the
package in mock. The errors in root.log are peculiar:
DEBUG util.py:450: Package ocaml-4.04.2-4.fc27.x86_64 is already installed, skipping.
DEBUG util.py:450: Error:
DEBUG util.py:450: Problem 1: cannot install both ocaml-runtime-4.05.0-2.fc27.x86_64 and ocaml-runtime-4.04.2-4.fc27.x86_64
DEBUG util.py:450: - package ocaml-4.05.0-2.fc27.x86_64 requires ocaml-runtime = 4.05.0-2.fc27, but none of the providers can be installed
Installing the higher version would be correct here, but ...
DEBUG util.py:450: - package ocaml-cmdliner-1.0.2-1.fc27.x86_64 requires ocaml(Array) = 83626447aa49c1fc006c752026de61fb, but none of the providers can be installed
... this dependency is wrong. But on the other hand mock is supposed
to be *building* ocaml-cmdliner at this point, so there shouldn't even
be a binary package of this.
DEBUG util.py:450: - cannot install the best candidate for the job
DEBUG util.py:450: - problem with installed package ocaml-cmdliner-1.0.2-1.fc27.x86_64
DEBUG util.py:450: Problem 2: cannot install both ocaml-runtime-4.05.0-2.fc27.x86_64 and ocaml-runtime-4.04.2-4.fc27.x86_64
DEBUG util.py:450: - package ocaml-cmdliner-1.0.2-1.fc27.x86_64 requires ocaml(Array) = 83626447aa49c1fc006c752026de61fb, but none of the providers can be installed
DEBUG util.py:450: - package ocaml-ocamlbuild-0.11.0-9.fc27.x86_64 requires ocaml(Pervasives) = 07ea9e20ae94d62c35cfecbe7d66d3ea, but none of the providers can be installed
ocaml(Pervasives) = 07ea... is provided by
ocaml-runtime-4.05.0-2.fc27.x86_64
DEBUG util.py:450: - package ocaml-cmdliner-devel-1.0.2-1.fc27.x86_64 requires ocaml-cmdliner = 1.0.2-1.fc27, but none of the providers can be installed
DEBUG util.py:450: - cannot install the best candidate for the job
DEBUG util.py:450: - problem with installed package ocaml-cmdliner-devel-1.0.2-1.fc27.x86_64
It seems as if a binary ocaml-cmdliner with incorrect dependencies is
appearing from somewhere ...
It might be in the dnf cache from a previous run. I recommend running
mock --scrub all (which will delete the buildroot and caches) and trying
again.
Michael
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
