make fails

[aboettger]

[aboettger:~/src/fpm] master ± make
rm -rf .yardoc sh notify-failure.sh rspec /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require': cannot load such file -- insist (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire' from /home/aboettger/src/fpm/spec/spec_setup.rb:2:in <top (required)>' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /home/aboettger/src/fpm/spec/fpm/command_spec.rb:1:in<top (required)>' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:inblock in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:inload_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:inrun' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' make: *\ [test] Error 1

[vStone]

Insist is part of the development requirements. Try using bundle exec make

[aboettger]

[aboettger:~/src/fpm] master ± bundle exec make rm -rf .yardoc sh notify-failure.sh rspec Skipping CPAN#input tests because 'cpanm' isn't in your PATH {:level=>:warn} Skipping OS X pkg tests requiring 'pkgbuild', which requires a Darwin platform. {:level=>:warn} Skipping Python#input tests because 'python' and/or 'easy_install' isn't in your PATH {:level=>:warn} Skipping RPM#output tests because 'rpmbuild' isn't in your PATH {:level=>:warn} Created package {:path=>"/tmp/studtmp-843e28f0-4ddf-4a10-9202-ccd61d8614db/example_1.0_amd64.deb"} .PATH: /tmp/studtmp-3b864073-feed-493b-8634-37346799caed WD: /home/aboettger/src/fpm Created package {:path=>"example_1.0_amd64.deb"} Created package {:path=>"example_1.0_amd64.deb"} ["example_1.0_amd64.deb"] ..........Debian tools (dpkg/apt) don't do well with packages that use capital letters in the name. In some cases it will automatically downcase them, in others it will not. It is confusing. Best to not use any capital letters at all. I have downcased the package name for you just to be safe. {:oldname=>"Capitalized_Name_With_Underscores", :fixedname=>"capitalized_name_with_underscores", :level=>:warn} Debian tools (dpkg/apt) don't do well with packages that use capital letters in the name. In some cases it will automatically downcase them, in others it will not. It is confusing. Best to not use any capital letters at all. I have downcased the package name for you just to be safe. {:oldname=>"Capitalized_Name_With_Underscores", :fixedname=>"capitalized_name_with_underscores", :level=>:warn} .Debian tools (dpkg/apt) don't do well with packages that use capital letters in the name. In some cases it will automatically downcase them, in others it will not. It is confusing. Best to not use any capital letters at all. I have downcased the package name for you just to be safe. {:oldname=>"Capitalized_Name_With_Underscores", :fixedname=>"capitalized_name_with_underscores", :level=>:warn} Debian tools (dpkg/apt) don't do well with packages that use capital letters in the name. In some cases it will automatically downcase them, in others it will not. It is confusing. Best to not use any capital letters at all. I have downcased the package name for you just to be safe. {:oldname=>"Capitalized_Name_With_Underscores", :fixedname=>"capitalized_name_with_underscores", :level=>:warn} .Downcasing provides 'Some-SILLY_name' because deb packages don't work so good with uppercase names {:level=>:warn} Downcasing provides 'Some-SILLY_name' because deb packages don't work so good with uppercase names {:level=>:warn} Replacing 'provides' underscores with dashes in 'some-silly_name' because debs don't like underscores {:level=>:warn} Replacing 'provides' underscores with dashes in 'some-silly_name' because debs don't like underscores {:level=>:warn} epoch in Version is set {:epoch=>"5", :level=>:warn} epoch in Version is set {:epoch=>"5", :level=>:warn} ...............epoch in Version is set {:epoch=>"5", :level=>:warn} epoch in Version is set {:epoch=>"5", :level=>:warn} ....F......................no value for epoch is set, defaulting to nil {:level=>:warn} no value for epoch is set, defaulting to nil {:level=>:warn} ...no value for epoch is set, defaulting to nil {:level=>:warn} no value for epoch is set, defaulting to nil {:level=>:warn} .no value for epoch is set, defaulting to nil {:level=>:warn} no value for epoch is set, defaulting to nil {:level=>:warn} ...................................

Failures:

1) FPM::Package::Deb#output with lintian when run against lintian should return no errors Failure/Error: expect($?).to eq(0), lintian_output E: name: changelog-file-missing-in-native-package E: name: control-file-has-bad-permissions conffiles 0664 != 0644 W: name: unknown-section default W: name: non-standard-dir-perm etc/ 0775 != 0755 W: name: non-standard-dir-perm etc/init.d/ 0775 != 0755 W: name: non-standard-file-perm etc/init.d/test 0664 != 0644 W: name: script-in-etc-init.d-not-registered-via-update-rc.d etc/init.d/test W: name: init.d-script-missing-lsb-section etc/init.d/test W: name: init.d-script-does-not-source-init-functions etc/init.d/test

./spec/fpm/package/deb_spec.rb:345:in `block (4 levels) in <top (required)>'

Finished in 5.41 seconds 94 examples, 1 failure

Failed examples:

rspec ./spec/fpm/package/deb_spec.rb:343 # FPM::Package::Deb#output with lintian when run against lintian should return no errors make: *\ [test] Error 1

[vStone]

This is just one bug that is still present, I fixed that in another pull requests. The rspec tests are unrelated to the make :)