On 10/20/2015 07:47 AM, Rick Stevens wrote:
On 10/19/2015 04:41 PM, jd1008 wrote:
>
>
> On 10/19/2015 05:38 PM, Ed Greshko wrote:
>> On 10/20/2015 07:27 AM, Neal Becker wrote:
>>> dnf
>>> Traceback (most recent call last):
>>> File "/bin/dnf", line 35, in <module>
>>> from dnf.cli import main
>>> File "/usr/lib/python2.7/site-packages/dnf/__init__.py", line
31, in
>>> <module>
>>> import dnf.base
>>> File "/usr/lib/python2.7/site-packages/dnf/base.py", line 26,
in
>>> <module>
>>> from dnf.comps import CompsQuery
>>> File "/usr/lib/python2.7/site-packages/dnf/comps.py", line 29,
in
>>> <module>
>>> import dnf.util
>>> File "/usr/lib/python2.7/site-packages/dnf/util.py", line 31,
in
>>> <module>
>>> import librepo
>>> File "/usr/lib64/python2.7/site-packages/librepo/__init__.py",
>>> line 1001,
>>> in <module>
>>> import librepo._librepo
>>> ImportError: libidn.so.11: cannot open shared object file: No such
>>> file or
>>> directory
>>>
>> No problem here on a fully updated F22 system. You didn't mention
>> what you were running....
>>
>> But at the end we see "libidn.so.11: cannot open shared object file".
>> Is it really missing?
>>
>> [egreshko@meimei ~]$ locate libidn.so.11
>> /usr/lib/libidn.so.11
>> /usr/lib/libidn.so.11.6.15
>> /usr/lib64/libidn.so.11
>> /usr/lib64/libidn.so.11.6.15
>>
>> The package libidn provides this....
>>
>>
> run
> sudo dnf install libidn-1.32-1.fc22.x86_64
The problem was dnf couldn't run because libidn wasn't there. :-)
Fortunately, he could download it from somewhere else and used rpm to
install it.
If one has it installed, another option would be to use "pkcon" to install
packages. This is the command line interface for "PackageKit".
--
In reality, some people should stick to running Windows and others should stay away from
computers altogether.