Trying to run /usr/bin/lddtree from pax-utils, the following Python error is shown: $ lddtree /usr/bin/nano Traceback (most recent call last): File "/bin/lddtree", line 53, in <module> from elftools.elf.elffile import ELFFile ImportError: No module named elftools.elf.elffile This is because we need to package https://github.com/eliben/pyelftools and add it as a dependency to pax-utils. (Or, if this isn't desired, split lddtree in another package).
Assigning to myself as I've started working on it, importing python-pyelftools in Cauldron and Mageia 6.
Assignee: thierry.vignaud => rverscheldeWhiteboard: (none) => MGA6TOOCC: (none) => thierry.vignaud
Fixed in Cauldron with pax-utils-1.2.2-3.mga7: http://svnweb.mageia.org/packages?view=revision&revision=1156077 Thierry, if you feel that pax-utils' dependency should be kept minimal and not require a python module, there is a Makefile option `USE_PYTHON=no` that could be defined to enforce installing lddtree.sh instead of lddtree.py. For now I kept the Python flavour which seems to be the upstream default. ---- Update candidate for Mageia 6: Advisory: ========= Updated pax-utils package fixes dependencies for lddtree utility The lddtree utility provided by pax-utils depends on a Python module, pyelftools, which was previously unpackaged. This update candidate fixes it by providing pyelftools packages for Python 2 and Python 3 and adding the corresponding dependency in pax-utils. RPMs in core/updates_testing: ============================= pax-utils-1.2.2-1.1.mga6 python2-pyelftools-0.24-1.mga6 python3-pyelftools-0.24-1.mga6 SRPMs in core/updates_testing: ============================== pax-utils-1.2.2-1.1.mga6 python-pyelftools-0.24-1.mga6
Assignee: rverschelde => qa-bugsWhiteboard: MGA6TOO => (none)QA Contact: (none) => rverscheldeVersion: Cauldron => 6
Is the python2 prefix correct here Rémi?
CC: (none) => lewyssmithKeywords: (none) => advisory
(In reply to claire robinson from comment #3) > Is the python2 prefix correct here Rémi? Yes, it's turning to be our new policy for Mageia 7, and for Mageia 6 we were in a gray area with some packages using python- as prefix, others using python2-. So I think it's fine to keep it this way to be in sync with Mageia 7+.
Probing M6/64 BEFORE potential update, normal repos: pax-utils Version : 1.2.2 Release : 1.mga6 $ urpmq -d pax-utils ... pax-utils pkgconfig run-parts setup AFTER potential update, updates_testing repos: pax-utils Version : 1.2.2 Release : 1.1.mga6 $ urpmq -d pax-utils ... pax-utils pkgconfig python|lib64python2.7-stdlib +++ python2-pyelftools +++ run-parts setup The new Python2 dependancy is evident. But what about Python3?
pax-utils only requires the Python 2 flavour, but as for all modules, we provide both the Python 2 and Python 3 flavours anyway. Mageia 6 users may find other use cases for python3-pyelftools.
Testing M6/64 BEFORE the update: installed pax-utils-1.2.2-1.mga6 # urpmi python2-pyelftools Dim pecyn o'r enw python2-pyelftools [no pkg of this name] # urpmi python3-pyelftools Dim pecyn o'r enw python3-pyelftools [no pkg of this name] DOING the update from updatesTesting, selecting : pax-utils-1.2.2-1.1.mga6 automatically pulled in : python2-pyelftools-0.24-1.mga6 which is what this update is about. No sign of python3-pyelftools-0.24-1.mga6 though. Despite which, I am OKing & validating. Rémi can undo if he thinks fit.
Whiteboard: (none) => MGA6-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2017-0091.html
Status: NEW => RESOLVEDResolution: (none) => FIXED