dnf configuration error?

nhchauvnu · 11-10-2019, 07:13 AM

Hi,

I successfully installed Fedora 31 on my laptop. After few days of using, I did something wrong with pip:

pip list | awk '{ printf("pip install %s --upgrade --ignore-installed\n", $1);}' | bash

After that I run 'dnf' and got this error:

===
/usr/local/lib/python3.7/site-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI.

Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

warnings.warn(warning_msg)
Traceback (most recent call last):
File "/usr/bin/dnf", line 57, in <module>
from dnf.cli import main
File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in <module>
import dnf.base
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 90, in <module>
class Base(object):
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 501, in Base
_TS_FLAGS_TO_RPM = {'noscripts': rpm.RPMTRANS_FLAG_NOSCRIPTS,
AttributeError: module 'rpm' has no attribute 'RPMTRANS_FLAG_NOSCRIPTS'
===

Now dnf stopped working. Please help me to fix this error. Thanks a lot!!

jsbjsb001 · 11-10-2019, 07:34 AM

Quote:

Originally Posted by nhchauvnu

Hi,

I successfully installed Fedora 31 on my laptop. After few days of using, I did something wrong with pip:

pip list | awk '{ printf("pip install %s --upgrade --ignore-installed\n", $1);}' | bash

After that I run 'dnf' and got this error:

===
/usr/local/lib/python3.7/site-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI.

Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

warnings.warn(warning_msg)
Traceback (most recent call last):
File "/usr/bin/dnf", line 57, in <module>
from dnf.cli import main
File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in <module>
import dnf.base
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 90, in <module>
class Base(object):
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 501, in Base
_TS_FLAGS_TO_RPM = {'noscripts': rpm.RPMTRANS_FLAG_NOSCRIPTS,
AttributeError: module 'rpm' has no attribute 'RPMTRANS_FLAG_NOSCRIPTS'
===

Now dnf stopped working. Please help me to fix this error. Thanks a lot!!

It's clearly a problem with dnf's Python 3 scripts.

You could try manually downloading the python3-rpm package, then using the rpm command to install it. You'll have to open this link in your browser, go to one of the mirror's and hunt down the package called "python3-rpm" that matches your machine's architecture.

nhchauvnu · 11-10-2019, 07:43 AM

Quote:

Originally Posted by jsbjsb001

It's clearly a problem with dnf's Python 3 scripts.

You could try manually downloading the python3-rpm package, then using the rpm command to install it. You'll have to open this link in your browser, go to one of the mirror's and hunt down the package called "python3-rpm" that matches your machine's architecture.

Thank you, I downloaded python3-rpm and reinstall it. However dnf still report the same errors.

rpm --reinstall -vh python3-rpm-4.15.0-6.fc31.x86_64.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1: python3-rpm-4.15.0-6.fc31 ################################# [ 50%]
Cleaning up / removing...
2: python3-rpm-4.15.0-6.fc31 ################################# [100%]

Any more action to take?

jsbjsb001 · 11-10-2019, 07:47 AM

You could also try reinstalling dnf itself and/or python 3 from the package(s) in the same Fedora online repo too. To be clear: these problems only started to happen when you ran the pip install command, correct?

PS: You should use CODE tags when posting command output.

nhchauvnu · 11-10-2019, 07:55 AM

Quote:

Originally Posted by jsbjsb001

You could also try reinstalling dnf itself and/or python 3 from the package(s) in the same Fedora online repo too. To be clear: these problems only started to happen when you ran the pip install command, correct?

PS: You should use CODE tags when posting command output.

Yes, the problems only started after I run pip install. I installed all packages you recommend:

Code:

rpm --reinstall -vh dnf-4.2.9-5.fc31.noarch.rpm python3-3.7.5-1.fc31.x86_64.rpm python3-dnf-4.2.9-5.fc31.noarch.rpm
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:python3-3.7.5-1.fc31             ################################# [ 17%]
   2:python3-dnf-4.2.9-5.fc31         ################################# [ 33%]
   3:dnf-4.2.9-5.fc31                 ################################# [ 50%]
Cleaning up / removing...
   4:dnf-4.2.9-5.fc31                 ################################# [ 67%]
   5:python3-dnf-4.2.9-5.fc31         ################################# [ 83%]
   6:python3-3.7.5-1.fc31             ################################# [100%]

but the errors remain. Perhaps something is wrong in Python configuration as it said "/usr/local/lib/python3.7/site-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI." I actually removed the PyPI.

jsbjsb001 · 11-10-2019, 08:04 AM

No, it appears to be a problem with the python scripts - I suspect whatever you installed with pip has overwritten the scripts dnf is complaining about.

In any case, try doing the same for the python3-dnf package - as upon checking that's what contains the /usr/lib/python3.7/site-packages/dnf/base.py file.

nhchauvnu · 11-10-2019, 08:06 AM

Quote:

Originally Posted by jsbjsb001

No, it appears to be a problem with the python scripts - I suspect whatever you installed with pip has overwritten the scripts dnf is complaining about.

In any case, try doing the same for the python3-dnf package - as upon checking that's what contains the /usr/lib/python3.7/site-packages/dnf/base.py file.

Yes, I already did that but dnf is still error

jsbjsb001 · 11-10-2019, 08:20 AM

Sorry, I missed you'd already installed the python3-dnf package above. Are you sure it did actually reinstall it? I think to be sure about that, you could try forcing a complete uninstall of the python3-dnf, then installing it fresh. After you've done that, you could also try restarting the system. Although since the scripts dnf is complaining about are in that package, and given what you've said, not sure why it's still complaining anyway.

Also, are you still getting exactly the same error messages from dnf as you posted in post #1?

nhchauvnu · 11-10-2019, 08:25 AM

Quote:

Originally Posted by jsbjsb001

Sorry, I missed you'd already installed the python3-dnf package above. Are you sure it did actually reinstall it? I think to be sure about that, you could try forcing a complete uninstall of the python3-dnf, then installing it fresh. After you've done that, you could also try restarting the system. Although since the scripts dnf is complaining about are in that package, and given what you've said, not sure why it's still complaining anyway.

Also, are you still getting exactly the same error messages from dnf as you posted in post #1?

Yes I got the exactly same error:

Code:

dnf
/usr/local/lib/python3.7/site-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI.

Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

  warnings.warn(warning_msg)
Traceback (most recent call last):
  File "/usr/bin/dnf", line 57, in <module>
    from dnf.cli import main
  File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in <module>
    import dnf.base
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 90, in <module>
    class Base(object):
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 501, in Base
    _TS_FLAGS_TO_RPM = {'noscripts': rpm.RPMTRANS_FLAG_NOSCRIPTS,
AttributeError: module 'rpm' has no attribute 'RPMTRANS_FLAG_NOSCRIPTS'

To remove the python3-dnf, I have to remove some dependencies including anaconda-core:

Code:

rpm -e python3-dnf
error: Failed dependencies:
	python3-dnf >= 4.2.1 is needed by (installed) python3-dnf-plugins-extras-common-4.0.5-3.fc31.noarch
	python3-dnf >= 3.6.0 is needed by (installed) anaconda-core-31.22.6-2.fc31.x86_64
	python3-dnf >= 4.2.8 is needed by (installed) python3-dnf-plugins-core-4.0.9-1.fc31.noarch
	python3-dnf is needed by (installed) python3-libreport-2.10.1-2.fc31.x86_64
	python3-dnf = 4.2.9-5.fc31 is needed by (installed) dnf-4.2.9-5.fc31.noarch

It is dangerous to do that, isn't it?

jsbjsb001 · 11-10-2019, 08:30 AM

Yes, don't remove the dependencies rpm is complaining about, you can try the --force option. Then install the python3-dnf package.

nhchauvnu · 11-10-2019, 08:42 AM

Quote:

Originally Posted by jsbjsb001

Yes, don't remove the dependencies rpm is complaining about, you can try the --force option. Then install the python3-dnf package.

I use --force option, but the error is still the same:

Code:

# rpm --install --force -vh dnf-4.2.9-5.fc31.noarch.rpm python3-3.7.5-1.fc31.x86_64.rpm python3-dnf-4.2.9-5.fc31.noarch.rpm python3-rpm-4.15.0-6.fc31.x86_64.rpm
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:python3-3.7.5-1.fc31             ################################# [ 25%]
   2:python3-rpm-4.15.0-6.fc31        ################################# [ 50%]
   3:python3-dnf-4.2.9-5.fc31         ################################# [ 75%]
   4:dnf-4.2.9-5.fc31                 ################################# [100%]

# dnf
/usr/local/lib/python3.7/site-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI.

Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

  warnings.warn(warning_msg)
Traceback (most recent call last):
  File "/usr/bin/dnf", line 57, in <module>
    from dnf.cli import main
  File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in <module>
    import dnf.base
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 90, in <module>
    class Base(object):
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 501, in Base
    _TS_FLAGS_TO_RPM = {'noscripts': rpm.RPMTRANS_FLAG_NOSCRIPTS,
AttributeError: module 'rpm' has no attribute 'RPMTRANS_FLAG_NOSCRIPTS'

jsbjsb001 · 11-10-2019, 08:55 AM

I meant to force an uninstall of the python3-dnf package, then install it fresh, rather than forcing a reinstall. The point was so we know that the original scripts dnf is complaining about have for certain been reinstalled. I should have said the --nodeps option instead of the --force option, sorry about that.

So,

Code:

rpm -e --nodeps python3-dnf

then,

Code:

rpm --install python3-dnf

to reinstall the python3-dnf package.

If you still get the same errors from dnf, then try restarting your system, then see if dnf still gives the same errors. If so, then you could try repeating the above for the dnf package (and possibly the python3 package as well) as well. If that still doesn't fix dnf, then I'm not sure what else to suggest. So in that case, it might be best to backup anything important you have on the system, and just reinstall the whole system and start again. And be more careful using pip next time. Unless you can remember exactly what pip changed, and can restore it back to what it was before you ran pip.

nhchauvnu · 11-12-2019, 06:49 PM

Quote:

Originally Posted by jsbjsb001

I meant to force an uninstall of the python3-dnf package, then install it fresh, rather than forcing a reinstall. The point was so we know that the original scripts dnf is complaining about have for certain been reinstalled. I should have said the --nodeps option instead of the --force option, sorry about that.

So,

Code:

rpm -e --nodeps python3-dnf

then,

Code:

rpm --install python3-dnf

to reinstall the python3-dnf package.

If you still get the same errors from dnf, then try restarting your system, then see if dnf still gives the same errors. If so, then you could try repeating the above for the dnf package (and possibly the python3 package as well) as well. If that still doesn't fix dnf, then I'm not sure what else to suggest. So in that case, it might be best to backup anything important you have on the system, and just reinstall the whole system and start again. And be more careful using pip next time. Unless you can remember exactly what pip changed, and can restore it back to what it was before you ran pip.

Thank you very much for your help. I tried all possibilities but not succeeded. I reinstalled my computer. However I will install a small virtual machine and reproduce this error to see if any solution exists.