building RPM with --prefix trail slash fails #353

Closed
cturra opened this Issue Feb 6, 2013 · 1 comment

Projects

None yet

2 participants

@cturra
cturra commented Feb 6, 2013

when passing fpm a --prefix that includes a trail slash, the following error is returned:

error: line 34: Prefixes must not end with "/": Prefix: /some/awesome/sause/ {:level=>:error}
/usr/lib/ruby/gems/1.8/gems/fpm-0.4.29/lib/fpm/util.rb:42:in `safesystem': rpmbuild failed (exit code 1). Full command was:["rpmbuild", "-bb", "--define", "buildroot /tmp/package-rpm-build20130206-20564-112lces/BUILD", "--define", "_topdir /tmp/package-rpm-build20130206-20564-112lces", "--define", "_sourcedir /tmp/package-rpm-build20130206-20564-112lces", "--define", "_rpmdir /tmp/package-rpm-build20130206-20564-112lces/RPMS", "/tmp/package-rpm-build20130206-20564-112lces/SPECS/AwesomeSause.spec"] (FPM::Util::ProcessFailed)
    from /usr/lib/ruby/gems/1.8/gems/fpm-0.4.29/lib/fpm/package/rpm.rb:251:in `output'
    from /usr/lib/ruby/gems/1.8/gems/fpm-0.4.29/lib/fpm/command.rb:408:in `execute'
    from /usr/lib/ruby/gems/1.8/gems/clamp-0.3.1/lib/clamp/command.rb:64: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.29/bin/fpm:8
    from /usr/bin/fpm:19:in `load'
    from /usr/bin/fpm:19

i believe the spec files requires that the path does not include a trailing slash and as we discussed, this is something fpm could remove for us :)

@r4um
Collaborator
r4um commented Jul 29, 2013

Fixed since 0.4.34

@r4um r4um closed this Jul 29, 2013
@prof-milki prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 18, 2014
pranay.kanwar #353 Remove trailing slash from prefix eadd123
@prof-milki prof-milki pushed a commit to prof-milki/xpm that referenced this issue Dec 27, 2014
@r4um r4um #353 Remove trailing slash from prefix 5fade43
@r4um r4um added a commit that referenced this issue Apr 24, 2015
@r4um r4um #353 Remove trailing slash from prefix fc7b917
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment