I can confirm this.

Using the example1.pom (with a gpg key test-key with passphrase: secretpwd) the build fails with:

[INFO] Processing files: mrpm-146-77-1.superD.noarch
[WARNING] warning: File listed twice: /opt/foo/lib/commons-io-2.4.jar
[INFO] Provides: mrpm-146 = 77-1.superD osgi(org.apache.commons.io) = 2.4.0
[INFO] Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
[INFO] Checking for unpackaged file(s): /usr/lib/rpm/check-files [...]/src/MRPM-146/target/rpm/mrpm-146/buildroot
[INFO] Wrote: [...]/src/MRPM-146/target/rpm/mrpm-146/RPMS/noarch/mrpm-146-77-1.superD.noarch.rpm
[INFO] Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.toeGgm
[WARNING] + umask 022
[WARNING] + cd [...]/src/MRPM-146/target/rpm/mrpm-146/BUILD
[WARNING] + /usr/bin/rm -rf [...]/src/MRPM-146/target/rpm/mrpm-146/buildroot
[WARNING] + exit 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.880s
[INFO] Finished at: Wed Sep 25 09:20:09 CEST 2013
[INFO] Final Memory: 11M/302M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "rpm" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-3:rpm (build-rpm) on project mrpm-146: Unable to sign RPM: [...]/src/MRPM-146/target/rpm/mrpm-146/RPMS/noarch/mrpm-146-77-1.%{dist}.noarch.rpm is not a valid rpm file or cannot be read -> [Help 1]

Changing %{dist} to test from the line:

<release>1.%{dist}</release>

And the build succeeds as expected.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to