On Thu, Feb 20, 2020 21:34:44 -0500, Danny Lee wrote:
Ok, so in the future I will use the commands you showed me:
$ sudo dnf repoquery --whatprovides 'file'
So, it's available on F31. It isn't on F32+, though:
$ sudo dnf --releasever 32 repoquery --whatprovides ‘file'
And then look up the 'whatprovides' file in:
https://koji.fedoraproject.org/koji
https://bodhi.fedoraproject.org/
Make sure those look good and I'll report that.
Yes, that is the general way to find broken dependency errors.
Note that it isn't only a file, it is a general "capability" that rpms
provide. Files are one type of capability. Here, for example, we see
what Python modules python3-nest provides:
$ rpm -q --provides python3-nest
python-nest = 2.18.0-7.fc31
python3-nest = 2.18.0-7.fc31
python3-nest(x86-64) = 2.18.0-7.fc31
python3.7dist(connplotter) = 0.7a0
python3.7dist(pynest) = nest-2.18
python3.7dist(topology) = nest-2.18
python3dist(connplotter) = 0.7a0
python3dist(pynest) = nest-2.18
python3dist(topology) = nest-2.18
So, we could run:
$ sudo dnf repoquery --whatprovides 'python3dist(topology)'
python3-nest-0:2.18.0-2.fc31.x86_64
python3-nest-0:2.18.0-7.fc31.x86_64
However, looking at the error report in root log I saw a second
error, I was
wondering if its valid or if the first error is the one to tackle first?
[root log -
https://kojipkgs.fedoraproject.org//work/tasks/3367/41683367/root.log]
DEBUG util.py:596: 2020-02-20 08:56:36,338: The exact error message is:
DEBUG util.py:596: 2020-02-20 08:56:36,338:
DEBUG util.py:596: 2020-02-20 08:56:36,338: Non interactive installation failed:
DEBUG util.py:596: 2020-02-20 08:56:36,338: Problem 1: conflicting requests
DEBUG util.py:596: 2020-02-20 08:56:36,338: - nothing provides libcgns.so.3.4 needed by
paraview-5.6.0-14.fc32.i686
DEBUG util.py:596: 2020-02-20 08:56:36,338: - nothing provides libcgns.so.3.4()(64bit)
needed by paraview-5.6.0-14.fc32.x86_64
DEBUG util.py:596: 2020-02-20 08:56:36,339: Problem 2: conflicting
requests
DEBUG util.py:596: 2020-02-20 08:56:36,339: - package gnome-boxes-3.35.90-2.fc32.x86_64
requires libvirt-daemon-kvm, but none of the providers can be installed
DEBUG util.py:596: 2020-02-20 08:56:36,339: - package
libvirt-daemon-kvm-6.0.0-1.fc32.x86_64 requires libvirt-daemon-driver-storage =
6.0.0-1.fc32, but none of the providers can be installed
DEBUG util.py:596: 2020-02-20 08:56:36,339: - package
libvirt-daemon-driver-storage-6.0.0-1.fc32.x86_64 requires
libvirt-daemon-driver-storage-rbd = 6.0.0-1.fc32, but none of the providers can be
installed
DEBUG util.py:596: 2020-02-20 08:56:36,339: - package
libvirt-daemon-driver-storage-rbd-6.0.0-1.fc32.x86_64 requires librados.so.2()(64bit), but
none of the providers can be installed
DEBUG util.py:596: 2020-02-20 08:56:36,339: - package
libvirt-daemon-driver-storage-rbd-6.0.0-1.fc32.x86_64 requires
librados.so.2(LIBRADOS_14.2.0)(64bit), but none of the providers can be installed
DEBUG util.py:596: 2020-02-20 08:56:36,339: - nothing provides libfmt.so.5()(64bit)
needed by librados2-2:15.1.0-1.fc33.x86_64.
DEBUG util.py:596: 2020-02-20 08:56:36,339:
DEBUG util.py:596: 2020-02-20 08:56:36,340: The installer will now terminate.
AH! This would affect anything that pulls in the workstation, since that
includes gnome-boxes. Kevin filed a bug and a new build seems to have
fixed this already. So, the next compose shouldn't have this error, at
least:
https://bugzilla.redhat.com/show_bug.cgi?id=1805422
Finally, when you say to comment on the ticket - you mean the issue
#1023,
right? I posted a comment at the bottom of this URLhttps://pagure.io/releng/
failed-composes/issue/1023
Yes, the idea is to keep the releng folks in the loop as to why the
compose is failing and that we're aware of it.
Is there a bug report to file anywhere?
These are all bugs that should be filed against the individual packages.
The individual maintainers should be fixing them. Where possible, we can
help with pull requests and so on.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London