New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot build rpm if filenames contain "=" #554

Closed
ebeyrent opened this Issue Sep 16, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@ebeyrent

ebeyrent commented Sep 16, 2013

Using 0.4.31, I'm able to build an rpm from files and directories that contain an "= character in the name, such as the files required for openldap.

However, the latest version of fpm complains about these filenames:

/usr/bin/fpm -s dir -t rpm
--name fen-ldap
--version 0.5
--after-install fen-ldap_after-install.sh
--architecture all
--depends "openldap"
--depends "openldap-clients"
--depends "openldap-servers"
--depends "star"
fen-ldap_after-install.sh
etc/openldap/schema/fen.schema
etc/openldap/slapd.d/cn=config/cn=schema.ldif
etc/openldap/slapd.d/cn=config/olcDatabase={0}config.ldif
etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif
etc/openldap/slapd.d/cn=config/olcDatabase={2}bdb.ldif
etc/openldap/slapd.d/cn=config/olcDatabase={-1}frontend.ldif
etc/openldap/slapd.d/cn=config/cn=schema/cn={4}fen.ldif
etc/rsyslog.d/slapd.conf
etc/logrotate.d/slapd
/usr/lib/ruby/1.8/fileutils.rb:1262:in copy': unknown file type: cn\ (RuntimeError) from /usr/lib/ruby/1.8/fileutils.rb:452:incopy_entry'
from /usr/lib/ruby/1.8/fileutils.rb:1331:in traverse' from /usr/lib/ruby/1.8/fileutils.rb:449:incopy_entry'
from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:158:in copy' from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:119:inclone'
from /usr/lib/ruby/1.8/find.rb:39:in find' from /usr/lib/ruby/1.8/find.rb:38:incatch'
from /usr/lib/ruby/1.8/find.rb:38:in find' from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:117:inclone'
from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:67:in input' from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:66:inchdir'
from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/package/dir.rb:66:in input' from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/command.rb:294:inexecute'
from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/command.rb:293:in each' from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/lib/fpm/command.rb:293:inexecute'
from /usr/lib64/ruby/gems/1.8/gems/clamp-0.6.1/lib/clamp/command.rb:67:in run' from /usr/lib64/ruby/gems/1.8/gems/clamp-0.6.1/lib/clamp/command.rb:125:inrun'
from /usr/lib64/ruby/gems/1.8/gems/fpm-0.4.42/bin/fpm:8
from /usr/bin/fpm:23:in `load'
from /usr/bin/fpm:23
make: *** [default] Error 1

I reverted my install of fpm back to 0.4.31 and everything works as expected. Any ideas what may have changed?

@r4um

This comment has been minimized.

Contributor

r4um commented Sep 17, 2013

Looks like the dir source mapping feature causing this, added in fpm version 0.4.40.

@r4um r4um closed this in 89d3642 Dec 6, 2013

jordansissel added a commit that referenced this issue Dec 6, 2013

Merge pull request #556 from r4um/issue-554
Fixes #554 do not map existing paths with = in them

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

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

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

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

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

jls
Merge pull request jordansissel#556 from r4um/issue-554
Fixes jordansissel#554 do not map existing paths with = in them

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

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

Merge pull request jordansissel#556 from r4um/issue-554
Fixes jordansissel#554 do not map existing paths with = in them

jordansissel added a commit that referenced this issue Apr 24, 2015

Merge pull request #556 from r4um/issue-554
Fixes #554 do not map existing paths with = in them

jordansissel added a commit that referenced this issue Jun 20, 2016

Merge pull request #556 from r4um/issue-554
Fixes #554 do not map existing paths with = in them
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment