|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MRPM-107) Get "The packaging... Mike Drob (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Mike Drob (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Mike Drob (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Mike Drob (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-107) Get "The pack... Anders Hammar (JIRA)

One thing I've picked up is that the --target parameter is for some reason being hard coded to be 'noarch-apple-mac os x' - note the spaces in the target name. It is not clear as to why there is a target parameter is here at all. Rpmbuild contains it's own intelligence to figure out the target, and I've seen all sorts of weirdness occur if you try and override rpmbuild's idea of the target.