Bug 1588448 - kickstart install: with explicit dnf package anaconda crashed on unresolved libyaml-0.so.2 dependecies
Summary: kickstart install: with explicit dnf package anaconda crashed on unresolved l...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libyaml
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: John Eckersberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-07 11:21 UTC by Frantisek Hanzlik
Modified: 2018-06-07 13:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-07 13:15:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
packaging.log ends with this error message (62.30 KB, text/plain)
2018-06-07 11:21 UTC, Frantisek Hanzlik
no flags Details
/tmp/anaconda.log (87.79 KB, text/plain)
2018-06-07 13:05 UTC, Frantisek Hanzlik
no flags Details

Description Frantisek Hanzlik 2018-06-07 11:21:32 UTC
Created attachment 1448690 [details]
packaging.log ends with this error message

Description of problem:
F28/x86_64 kickstart installation crashed on unresolved dependencies, when kickstart file specifies "dnf" in %packages section. Anaconda error window say:

 Problem: package dnf-2.7.5-12.fc28.noarch requires python3-dnf = 2.7.5-12.fc28, but none of the providers can be installed
  - package python3-dnf-2.7.5-12.fc28.noarch requires libmodulemd >= 1.3.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libyaml-0.so.2 needed by libmodulemd-1.3.0-2.fc28.i686
  - nothing provides libyaml-0.so.2()(64bit) needed by libmodulemd-1.3.0-2.fc28.x86_64
  - nothing provides libyaml-0.so.2 needed by libmodulemd-1.4.1-1.fc28.i686
  - nothing provides libyaml-0.so.2()(64bit) needed by libmodulemd-1.4.1-1.fc28.x86_64

and offer Quit button.


Version-Release number of selected component (if applicable):
libyaml-0.1.7-5.fc28.x86_64.rpm from fedora repo

Additional info:
without explicitly stating "dnf" in %package section installation ends successfuly, but dnf is not installed.

Comment 1 Frantisek Hanzlik 2018-06-07 13:03:41 UTC
In this case, I install from locally mirrored Fedora Everything and Fedora updates repos. And I cannot find the cause of the error:

in repository are packages:
# find . -name 'libyaml-*.rpm' -ls
97222407  100 -rw-r--r--   2 root     root       101388 Feb  3 16:36 ./Everything/x86_64/os/Packages/l/libyaml-devel-0.1.7-5.fc28.i686.rpm
97222408  100 -rw-r--r--   1 root     root       101380 Feb  3 16:36 ./Everything/x86_64/os/Packages/l/libyaml-devel-0.1.7-5.fc28.x86_64.rpm
97222406   64 -rw-r--r--   1 root     root        61668 Feb  3 16:36 ./Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.x86_64.rpm
97222405   64 -rw-r--r--   2 root     root        64112 Feb  3 16:36 ./Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.i686.rpm

and libyaml pkgs capabilities seems be sufficient:
# rpm -qp --provides Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.i686.rpm
warning: Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 9db62fb1: NOKEY
libyaml = 0.1.7-5.fc28
libyaml(x86-32) = 0.1.7-5.fc28
libyaml-0.so.2

# rpm -qp --provides Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.x86_64.rpm
warning: Everything/x86_64/os/Packages/l/libyaml-0.1.7-5.fc28.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 9db62fb1: NOKEY
libyaml = 0.1.7-5.fc28
libyaml(x86-64) = 0.1.7-5.fc28
libyaml-0.so.2()(64bit)

And when I query repodata DB with dnf (from F27/i686, thus '--forcearch=x86_64'):

# dnf --repofrompath f28,Everything/x86_64/os --repo=f28 --forcearch=x86_64 repoquery --whatprovides 'libyaml-0.so.2()(64bit)'
Added f28 repo from Everything/x86_64/os
Last metadata expiration check: 2:53:45 ago on Thu 07 Jun 2018 12:03:03 PM CEST.
libyaml-0:0.1.7-5.fc28.x86_64

# dnf --repofrompath f28,Everything/x86_64/os --repo=f28 --forcearch=x86_64 repoquery --whatprovides 'libyaml-0.so.2'
Added f28 repo from Everything/x86_64/os
Last metadata expiration check: 2:54:00 ago on Thu 07 Jun 2018 12:03:03 PM CEST.
libyaml-0:0.1.7-5.fc28.i686

then all seems good for me... weird...

Comment 2 Frantisek Hanzlik 2018-06-07 13:05:12 UTC
Created attachment 1448713 [details]
/tmp/anaconda.log

Comment 3 Frantisek Hanzlik 2018-06-07 13:15:20 UTC
excuse, my error - I had libyaml disabled ("-libyaml") in some included file (perhaps to avoid the installation of unwanted Gnome packages, as I use MATE).


Note You need to log in before you can comment on or make changes to this bug.