Bug 728634 - Fedora 15 MySQL RPMs strip out my_net_read
Summary: Fedora 15 MySQL RPMs strip out my_net_read
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Tom Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-05 21:10 UTC by Andrew Hutchings
Modified: 2013-07-03 03:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-05 23:57:02 UTC


Attachments (Terms of Use)

Description Andrew Hutchings 2011-08-05 21:10:02 UTC
Description of problem:
In bug #722966 there is a review for the possibility to get mydumper in Fedora/RedHat.

In the Fedora 15 .spec file I notice a changelog entry which hides functions which are not part of the API.  Unfortunately this hides my_net_read which is required by mydumper.  This means that mydumper will compile in everything except Fedora 15.

Can you please add my_net_read into your libmysql.version file?

Version-Release number of selected component (if applicable):
5.5.8-1 onwards

Additional info:
See https://bugs.launchpad.net/mydumper/+bug/803982 and RedHat Bug #722966 for more information

Comment 1 Tom Lane 2011-08-05 21:40:30 UTC
The point of hiding the not-officially-exported functions is to make sure that applications won't break if/when mysql changes or removes such functions.  It seems to me that mydumper is coding extremely unsafely if they depend on direct access to this function.  I think the appropriate course here would be for them to persuade mysql upstream to add this function to the documented API.  If it were documented I'd of course add it to the exported symbol list.

Comment 2 Andrew Hutchings 2011-08-05 23:57:02 UTC
ok, I understand your point of view.  There is another way but it will take a few months for me to develop.  Thanks anyway.


Note You need to log in before you can comment on or make changes to this bug.