Adam Williamson composed on 2016-02-13 10:19 (UTC+0100):
> It's possible there are simply dependency issues at present with your
> particular package set, in which case you kinda have to wait for them
> to be fixed (or fix them yourself) - report them if they're not already
> reported
That's what I thought I sorta did, except I left off the last two parameters
from the last dnf command I typed into OP:
Felix Miata composed on 2016-02-12 00:08 (UTC-0500):
...
> SOLV_1.0 not defined in file libsolv.so.0 with link time reference
> # rpm -qa | grep libsol
> libsolv-0.6.14-7.fc23.i686
> # rpm -qa | grep fc23
> dbus-python-1.2.0-12.fc23.i686
> (restore, then try again)
> # dnf update dnf pyt* perl*
Should have been:
# dnf update dnf pyt* perl* libsolv dbus-python
So, libsolv and/or dbus-python apparently was/were (a) dep(s) not recognized
as required and thus not installed/updated by 'dnf update dnf'.
> got me past the dnf problem....
(black screen/hard lockup on 4.5rc kernel, but otherwise OK)
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
test mailing list
[email protected]
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/[email protected]
