Bug #37409 rpmbuild fails if explicit build type not specified
Submitted: 14 Jun 2008 10:32 Modified: 23 Nov 2010 12:57
Reporter: Domas Mituzas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:5.0.62 OS:Linux (RHEL)
Assigned to: Joerg Bruehe CPU Architecture:Any

[14 Jun 2008 10:32] Domas Mituzas 
Description:
it is not documented anywhere that source RPM packages need specification of build type, and there're no working defaults. 

How to repeat:
Installing MySQL-enterprise-gpl-5.0.62-0.rhel5.src.rpm
warning: user mysqldev does not exist - using root
warning: group mysqldev does not exist - using root
warning: user mysqldev does not exist - using root
warning: group mysqldev does not exist - using root
error: parse error in expression
error: /usr/src/redhat/SPECS/mysql-5.0.62.rhel5.spec:92: parseExpressionBoolean returns -1
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)

Suggested fix:
if no build type defined, default to the package location-specific specification (enterprise_gpl on enterprise, etc)
[12 Aug 2010 11:36] Joerg Bruehe 
Grabbing this ...

Recently, Jonathan has done a big cleanup on the spec files.
The result is in the 5.5 sources and was used to build the 5.5.5 RPMs.

As part of this cleanup, he ensured there are defaults - if no options are given to the build, "generic" (any Linux) RPMs with the "community" feature set will be created,

I don't know what exactly is meant by "location-specific", so if you have different proposals, please specify them.
[12 Sep 2010 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[13 Oct 2010 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[14 Nov 2010 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[23 Nov 2010 12:57] Joerg Bruehe 
There have been no replies to my note of August 12 for more than three months now.

The associated support issue also doesn't include any hint of a missing part.

Based on this, I think Jonathan's cleanup solves the request, so I close this bug.
[14 Dec 2011 15:22] Ali Jawad 
Bug still exists on 

[root@SQL-Node-100-90 SPECS]# rpmbuild -ba mysql-7.1.17.rhel5.spec
error: parse error in expression
error: /usr/src/redhat/SPECS/mysql-7.1.17.rhel5.spec:264: parseExpressionBoolean returns -1
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)