Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

RPM build choking on != dependency #243

Closed
tateeskew opened this Issue Aug 1, 2012 · 1 comment

Comments

Projects
None yet
2 participants

When trying to build an rpm from a python module (python-ssh), the rpmbuild blows up when encountering != in the dependecies list.

$ fpm -s python -t rpm -e ssh==1.7.14

------- removed for brevity -------
Copying ssh.egg-info to /tmp/package-python-staging20120801-6873-uzisfl/usr/lib/python2.7/dist-packages/ssh-1.7.14.egg-info
running install_scripts
error: line 40: Dependency tokens must begin with alpha-numeric, '_' or '/': Requires: python-pycrypto != 2.4
/var/lib/gems/1.8/gems/fpm-0.4.10/lib/fpm/util.rb:33:in safesystem': rpmbuild failed (exit code 1). Full command was:["rpmbuild", "-bb", "--define", "buildroot /tmp/package-rpm-build20120801-6873-px26v4/BUILD", "--define", "_topdir /tmp/package-rpm-build20120801-6873-px26v4", "--define", "_sourcedir /tmp/package-rpm-build20120801-6873-px26v4", "--define", "_rpmdir /tmp/package-rpm-build20120801-6873-px26v4/RPMS", "/tmp/package-rpm-build20120801-6873-px26v4/SPECS/python-ssh.spec"] (FPM::Util::ProcessFailed) from /var/lib/gems/1.8/gems/fpm-0.4.10/lib/fpm/package/rpm.rb:197:inoutput'
from /var/lib/gems/1.8/gems/fpm-0.4.10/lib/fpm/command.rb:329:in execute' from /var/lib/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:64:inrun'
from /var/lib/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:126:in run' from /var/lib/gems/1.8/gems/fpm-0.4.10/bin/fpm:8 from /usr/local/bin/fpm:19:inload'
from /usr/local/bin/fpm:19

If I remove the line with Requires: python-pycrypto != 2.4 on it, the RPM builds correctly.
Perhaps this problem lies within the lib/fpm/package/rpm.rb or python.rb code. Looking through the past issues, it looks as though this was fixed in various other bits of code for deb packages and gems.

Owner

jordansissel commented Mar 5, 2013

This is fixed I think! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment