Bug #13740 Max RPM's don't include new perror binary which has NDB support
Submitted: 4 Oct 2005 12:53 Modified: 20 Oct 2005 7:07
Reporter: Harrison Fisk Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:4.1.14 OS:Linux (Redhat EL 4)
Assigned to: Lenz Grimmer CPU Architecture:Any

[4 Oct 2005 12:53] Harrison Fisk
If you install NDB through the RPM's by using the max release, it will not replace the perror utility.  This will cause the --ndb option to perror not to work.

How to repeat:
1.  Install ndb through the rpm method (max, all ndb rpms)
2.  Run perror --ndb 0
3.  Notice it doesn't work as it should (you can test with -max tarball instead)

Suggested fix:
Include the appropriate perror binary in either the -max or in the ndb client tools rpm.
[13 Oct 2005 20:01] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[13 Oct 2005 20:37] Lenz Grimmer
This should now be fixed for all upcoming releases (4.1.16 and 5.0.15) - the perror binary included in the Server RPM now includes support for the NDB error codes by default. I could not add two separate binaries, as this would have caused a file name clash (there can only be one "perror" binary in the file list).
[20 Oct 2005 7:07] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented in 4.1.16 and 5.0.15 changelogs; closed.