Red Hat Bugzilla – Bug 1020239
python-augeas should require python-ctypes
Last modified: 2017-04-06 06:39:05 EDT
Description of problem:
python-augeas package needs python-ctypes to work, but looks like the ctypes package is not a dependency to python-augeas.
from augeas import Augeas
File "/usr/lib/python2.4/site-packages/augeas.py", line 42, in ?
ImportError: No module named ctypes
Version-Release number of selected component (if applicable):
rpm -q python-augeas
Steps to Reproduce:
$ from augeas import Augeas
can you think of any reason why this wouldn't count for fedora versions too?
(In reply to Greg Swift from comment #1)
> can you think of any reason why this wouldn't count for fedora versions too?
As far as i know ctypes are part of python-libs from python 2.5. So there is no need for separate python-ctypes.
python-augeas-0.4.1-5.el5 has been submitted as an update for Fedora EPEL 5.
Just went back and reviewed the packaging guidelines for python packages, and I want to make another set of changes to the spec. shouldn't change functionality. might take me a few more days to find the time though, but technically its not necessary so this can go forward. up to you.
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing python-augeas-0.4.1-5.el5'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.