[
https://jira.codehaus.org/browse/MRPM-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297840#comment-297840
]
Mike Drob commented on MRPM-107:
--------------------------------
Looks like rpmbuild on Ubuntu automatically converts the architecture string to
lowercase. See example -
{noformat}
mike@ubuntu:/tmp$ uname -a
Linux ubuntu 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
mike@ubuntu:/tmp$ rpmbuild --version
RPM version 4.9.0
mike@ubuntu:/tmp$ cat rpm-mixed.spec
Name: rpm-mixed
Version: 1
Release: 1
Summary: Minimal SPEC File
License: Public Domain
%description
%files
%attr(755,myuser,mygroup) "/foo"
%clean
mike@ubuntu:/tmp$ ls -l /tmp/buildroot
-rw-rw-r-- 1 mike mike 0 2012-05-03 23:39 /tmp/buildroot/foo
mike@ubuntu:/tmp$ rpmbuild -vv -bb --buildroot /tmp/buildroot --define '_topdir
/tmp' --target ARCH rpm-mixed.spec
Building target platforms: ARCH
Building for target ARCH
Processing files: rpm-mixed-1-1.arch
unknown, 0: Warning: using regular magic file `/etc/magic'
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /tmp/buildroot
Wrote: /tmp/RPMS/arch/rpm-mixed-1-1.arch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.Q3pYFS
+ umask 022
+ cd /tmp/BUILD
+ exit 0
{noformat}
After changing {{someArch}} to {{somearch}} in the pom.xml, the next error I
got was:
{noformat}
[INFO] Building: rpm-3/pom.xml
[INFO] ..FAILED (5.1 s)
[INFO] The post-build script did not succeed. spec version
{noformat}
I checked the verify.groovy script, and for some reason it was expecting the
version to be {{1.2}}, but I couldn't find anything that would have set it to
that. There was no explicit version set in the plugin configuration, so it
defaulted to the version of the pom, which was {{1.0}} in this case - correct
behavior according to the documentation.
I'm not sure if there is a workaround for the lowercase architecture issue.
I'll try to check if RedHat exhibits the same behavior. This might end up being
something that needs to be pushed upstream. Alternatively, I'm not sure how
many rpm compatible systems exist that have uppercase characters in their
architectures.
Unfortunately, I can't duplicate the Mac OS bug, as I don't have access to that
hardware.
> Get "The packaging for this project did not assign a file to the build
> artifact" on Mac
> ---------------------------------------------------------------------------------------
>
> Key: MRPM-107
> URL: https://jira.codehaus.org/browse/MRPM-107
> Project: Mojo RPM Plugin
> Issue Type: Bug
> Components: rpm
> Affects Versions: 2.1-alpha-1
> Environment: Mac OS 10.7.3, Mac Ports rpm
> Reporter: Anders Hammar
>
> When doing "mvn clean install" on IT rpm-3 (for example) I get an error from
> Maven saying:
> The packaging for this project did not assign a file to the build artifact
> I think the problem is that the plugin thinks the naming of the rpm file is
> something different that it is on my Mac and Maven notices that the specified
> artifact file doesn't exist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
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
