FS#47055 - [yubikey-neo-manager] neoman cannot run (missing dependencies)

Attached to Project: Community Packages
Opened by Dan Andresan (forumache) - Friday, 13 November 2015, 07:32 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 18 November 2015, 16:40 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Cannot run neoman (Yubikey Neo Manager) using latest yubikey-neo-manager 1.4.0-1

Additional info:
* package version(s)
yubikey-neo-manager 1.4.0-1
* config and/or log files etc.


Steps to reproduce:
pacman -S yubikey-neo-manager

dan@archie ~ % neoman
Traceback (most recent call last):
File "/usr/bin/neoman", line 5, in <module>
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Seems like dependencies are not fulfilled.
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 18 November 2015, 16:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with yubikey-neo-manager 1.4.0-2 (and python2-pyside-1.2.4-2).
Comment by Doug Newgard (Scimmia) - Friday, 13 November 2015, 15:27 GMT
Install python2-setuptools
Comment by Dan Andresan (forumache) - Saturday, 14 November 2015, 06:22 GMT
Thanks Doug for your suggestion, but I installed python2-setuptools before raising the bug. Although the package should require it. But still didn't help. The error changed to:
pkg_resources.DistributionNotFound: The 'PySide' distribution was not found and is required by yubikey-neo-manager

All python2 pyside packages are installed and still the error appears.
pyside-tools-common-0.2.15-2 python2-pyside-tools-0.2.15-2 python2-pyside-1.2.4-1 python-pyside-common-1.2.4-1

As regard to Severity it is my understanding and I might be wrong that this is evaluated in package context. The package is not usable (at all), so that's why I raised this bug with severity critical. Of course the impact in Arch community context is very low, because few people have a YubiKey Neo.

Thank you,
Dan.
Comment by Doug Newgard (Scimmia) - Saturday, 14 November 2015, 06:29 GMT
So python2-setuptools did help, there's just other problems as well.

For the severity, "Critical" means the entire system crashes, won't boot, or has a major security flaw. High would be used when a package is totally non-functional, but a simply missing dep doesn't rise to that level. This PySide problem might, though.
Comment by Doug Newgard (Scimmia) - Saturday, 14 November 2015, 06:52 GMT
If I remove PySide fromm /usr/lib/python2.7/site-packages/yubikey_neo_manager-1.4.0-py2.7.egg-info/requires.txt, everything seems to work, so it's non a functional problem, just a faulty check somewhere. Hmm...
Comment by Doug Newgard (Scimmia) - Saturday, 14 November 2015, 06:58 GMT
Got it. The problem is that there is no egg-info for PySide. That's a separate bug in that package.
Comment by Christian Hesse (eworm) - Sunday, 15 November 2015, 21:14 GMT
Solved the dependency issue in yubikey-neo-manager 1.4.0-2.

I noted the egg-info problem on #archlinux-tu channel, but nothing changed since then. Did anybody open a bug report for that?
Comment by Doug Newgard (Scimmia) - Sunday, 15 November 2015, 23:11 GMT
I haven't. As a workaround, deleting that line in requires.txt would get things running again without any side effects AFAIK. Pacman does the the dep checks already.
Comment by Christian Hesse (eworm) - Monday, 16 November 2015, 08:03 GMT
https://bugs.archlinux.org/task/47080
Comment by Christian Hesse (eworm) - Wednesday, 18 November 2015, 16:39 GMT
PySide is fixed with python2-pyside-1.2.4-2.

Loading...