Is --rpm-rpmbuild-define broken?

217 views
Skip to first unread message

s.m. koppelman

unread,
Aug 24, 2012, 3:42:58 PM8/24/12
to fpm-...@googlegroups.com
As mentioned in the earlier thread and possibly in someone's comment to issue #136:


I'm seeing the same kind of failure whenever I try to use --rpm-rpmbuild-define: The following runs fine if I simply remove the --rpm-rpmbuild-define parameter.

rvm use system
$ fpm -s dir -t rpm -n ${JOB_NAME} -v ${branch} --iteration ${BUILD_NUMBER} -a all \
  --rpm-rpmbuild-define '_rvm_ruby 1.9.3' \
  --rpm-user appuser --rpm-group appuser --prefix /var/www/apps/${JOB_NAME} \
  --template-scripts --after-install pkg/postinstall.sh .
 
/usr/lib/ruby/gems/1.8/gems/fpm-0.4.13/lib/fpm/package/deb.rb:23: warning: already initialized constant COMPRESSION_TYPES
/usr/lib/ruby/gems/1.8/gems/fpm-0.4.13/lib/fpm/package/rpm.rb:45: undefined local variable or method `attributes' for #<FPM::Command:0x7f133289e558> (NameError)
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/attribute_declaration.rb:32:in `instance_exec'
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/attribute_declaration.rb:32:in `rpm_rpmbuild_define='
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/option/parsing.rb:27:in `send'
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/option/parsing.rb:27:in `parse_options'
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:49:in `parse'
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:63:in `run'
	from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:126:in `run'
	from /usr/lib/ruby/gems/1.8/gems/fpm-0.4.13/bin/fpm:8
	from /usr/bin/fpm:19:in `load'
	from /usr/bin/fpm:19

Does it work for anyone? The Ruby in use here is 1.8.7p352 and rubygems 1.3.7 on RHEL 6.2.

Rgds, &c.

Eric Merritt

unread,
Nov 6, 2012, 4:09:59 PM11/6/12
to fpm-...@googlegroups.com
I am seeing the same exact thing. Did you ever find a fix for this?

Jordan Sissel

unread,
Mar 20, 2013, 9:03:12 PM3/20/13
to fpm-...@googlegroups.com


On Tuesday, November 6, 2012 1:09:59 PM UTC-8, Eric Merritt wrote:
I am seeing the same exact thing. Did you ever find a fix for this?


I have a fix for this based on this pull request: 

Sorry for the delay in repair! :)

-Jordan
Reply all
Reply to author
Forward
0 new messages