[ 
https://jira.codehaus.org/browse/MRPM-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297888#comment-297888
 ] 

Mike Drob commented on MRPM-107:
--------------------------------

Mac OS apparently does not respect {{--target}} in the rpmbuild command:

Script:
{noformat}
#!/bin/bash

SCRATCH=/tmp/$$
trap "rm -rf $SCRATCH" exit

mkdir -p $SCRATCH/{buildroot,RPMS,BUILD}
cat > $SCRATCH/buildroot/foo.spec << SPEC
Name: rpm-minimal
Version: 1
Release: 1
Summary: Minimal SPEC File
License: Public Domain
Group: None
%description
%files
%attr(777,`whoami`,`whoami`) "/foo.spec"
SPEC

rpmbuild -vv -bb \
  --buildroot $SCRATCH/buildroot \
  --define "_topdir $SCRATCH" \
  --define "_tmppath /tmp" \
  --define "_build_name_fmt 
%%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm" \
  --target UPPERCASE \
  $SCRATCH/buildroot/foo.spec
{noformat}

Output:
{noformat}
D: pool fd:     created size 392 limit -1 flags 0
D: pool iob:    created size 48 limit -1 flags 0
D: pool mire:   created size 136 limit -1 flags 0
D: pool lua:    created size 64 limit -1 flags 0
D: pool ts:     created size 1200 limit -1 flags 0
D:     target platform: UPPERCASE
D: pool spec:   created size 600 limit -1 flags 0
D: pool h:      created size 360 limit -1 flags 0
D: pool pkg:    created size 168 limit -1 flags 0
D: pool ctx:    created size 112 limit -1 flags 0
D: pool ds:     created size 232 limit -1 flags 0
D: pool dig:    created size 408 limit -1 flags 0
Building target platforms: UPPERCASE
Processing files: rpm-minimal-1-1.i386
D: pool sx:     created size 40 limit -1 flags 0
D: pool fi:     created size 560 limit -1 flags 0
D: created directory(s) /tmp/92684/RPMS/i386 mode 0755
D: fini      100777  1 (   0,   0)         161 /foo.spec 
GZDIO:       6 writes,      412 total bytes in 0.000052 secs
D: pool tsi:    created size 48 limit -1 flags 0
D: Signature: size(920)+pad(0)
Wrote: /tmp/92684/RPMS/i386/rpm-minimal-1-1.i386.rpm
D: pool pkg:    reused 0, alloc'd 1, free'd 1 items.
D: pool spec:   reused 0, alloc'd 1, free'd 1 items.
D: pool tsi:    reused 3, alloc'd 1, free'd 1 items.
D: pool ts:     reused 0, alloc'd 2, free'd 2 items.
D: pool ds:     reused 0, alloc'd 1, free'd 1 items.
D: pool fi:     reused 0, alloc'd 1, free'd 1 items.
D: pool h:      reused 3, alloc'd 4, free'd 4 items.
D: pool lua:    reused 0, alloc'd 1, free'd 1 items.
D: pool sx:     reused 0, alloc'd 1, free'd 1 items.
D: pool mire:   reused 2, alloc'd 2, free'd 2 items.
D: pool ctx:    reused 4, alloc'd 2, free'd 2 items.
D: pool iob:    reused 3, alloc'd 2, free'd 2 items.
D: pool dig:    reused 0, alloc'd 2, free'd 2 items.
D: pool fd:     reused 6, alloc'd 4, free'd 4 items.
D: exit code: 0
{noformat}
                
> 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
>         Attachments: MRPM-107.patch
>
>
> 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


Reply via email to