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

Library gems (e.g. json_pure) create empty bindirs? (Amazon Linux 2013.09 conflicts) #612

Closed
astrostl opened this Issue Jan 3, 2014 · 2 comments

Comments

Projects
None yet
3 participants

astrostl commented Jan 3, 2014

# fpm -s gem -t rpm -v 1.7.7 json_pure
# rpm -i rubygem-json_pure-1.7.7-1.noarch.rpm
 file /usr/bin from install of rubygem-json_pure-1:1.7.7-1.noarch conflicts with file from package filesystem-2.4.30-3.8.amzn1.x86_64
# rpm -qpl rubygem-json_pure-1.7.7-1.noarch.rpm |grep bin
 /usr/bin

If I set --gem-bin-path to something uncovered by the 'filesystem' package (e.g. /var/emptygem), it still creates an empty dir for it, but it works around the conflict.

/me too

Owner

jordansissel commented Jan 8, 2014

Confirmed.

% rpm -qlp rubygem-json_pure-1.7.7-1.noarch.rpm | grep bin
/usr/local/bin

@gerbercj gerbercj added a commit to gerbercj/fpm that referenced this issue Feb 27, 2014

@jordansissel @gerbercj jordansissel + gerbercj Don't put gem_bin_path in packages if there's no need.
This should fix #612.
4684de1

@gerbercj gerbercj added a commit to gerbercj/fpm that referenced this issue Mar 11, 2014

@jordansissel @gerbercj jordansissel + gerbercj Don't put gem_bin_path in packages if there's no need.
This should fix #612.
bf1ab64

@gerbercj gerbercj added a commit to gerbercj/fpm that referenced this issue Apr 25, 2014

@jordansissel @gerbercj jordansissel + gerbercj Don't put gem_bin_path in packages if there's no need.
This should fix #612.
1f1476e

@prof-milki prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 18, 2014

jls Don't put gem_bin_path in packages if there's no need.
This should fix #612.
3f4d7f2

@prof-milki prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 27, 2014

@jordansissel jordansissel Don't put gem_bin_path in packages if there's no need.
This should fix #612.
1ec3891
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment