| Bug #58283 | RPMs of "cluster" are lacking the InnoDB plugin | ||
|---|---|---|---|
| Submitted: | 18 Nov 2010 11:09 | Modified: | 17 Dec 2010 3:36 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
| Version: | 6.3.39, 7.0.20, 7.1.9 | OS: | Linux (RPM packages) |
| Assigned to: | Joerg Bruehe | CPU Architecture: | Any |
[29 Nov 2010 11:38]
Joerg Bruehe
Approved by Kent via IRC on Nov 19. Used in the build of Cluster-7.1.9a, and will be used in all subsequent cluster builds of 6.1, 7., 7.1, and up.
[16 Dec 2010 19:51]
Jon Stephens
Changed category so this will show up in my work queue instead of Paul's.
[17 Dec 2010 2:46]
Jon Stephens
See also BUG#54912.
[17 Dec 2010 3:22]
Jon Stephens
Documented in the NDB-7.1.9a changelog as follows:
The InnoDB plugin was not included in MySQL Cluster RPM packages.
Closed.
[17 Dec 2010 3:35]
Jon Stephens
Reverted category to Packaging.
Description: Detected during the build of Cluster-7.1.9: The InnoDB plugin is created, and its ".so" files are in the tar.gz packages (especially for Linux), but they are not included in the RPM packages. Rather, they are reported as "unpackaged files". How to repeat: Check a "server" RPM of 7.1.9 or another affected version, or check its table of contents ("rpm -ql" output). Suggested fix: Include the InnoDB plugin in the cluster RPMs, unconditionally.