|
||||||||
|
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-79) BuildArch is not inc... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-79) BuildArch is no... Nicolas A. Barriga (JIRA)
- [mojo-dev] [jira] (MRPM-79) BuildArch is no... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-79) BuildArch is no... Justin Plock (JIRA)
- [mojo-dev] [jira] (MRPM-79) BuildArch is no... Justin Plock (JIRA)

Standard RPM practice is to autodetect the architecture itself. As soon as an architecture specific file is inserted into the RPM, the RPM automatically takes on that architecture.
I have had problems in the past where inserting the architecture manually with BuildArch then breaks an RPM build on RHEL5.
In theory, we'd need to verify first whether this is an RPM problem/bug rather than a plugin bug.