So, I've been tearing apart mysql-connector-odbc-5.1.11-1.fc18.x86_64
And I've tracked down some horrible breakage there that needs to be fixed upstream.
Given the state of mysql in the distro, and the pending move to mariadb, I'm wondering where the best place to report this bug would be. I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com.
On 5/19/2013 18:00, Sam Varshavchik wrote:
So, I've been tearing apart mysql-connector-odbc-5.1.11-1.fc18.x86_64
And I've tracked down some horrible breakage there that needs to be fixed upstream.
Given the state of mysql in the distro, and the pending move to mariadb, I'm wondering where the best place to report this bug would be. I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com.
http://bugs.mysql.com/ is relevant I suppose?
staticsafe writes:
On 5/19/2013 18:00, Sam Varshavchik wrote:
So, I've been tearing apart mysql-connector-odbc-5.1.11-1.fc18.x86_64
And I've tracked down some horrible breakage there that needs to be fixed upstream.
Given the state of mysql in the distro, and the pending move to mariadb, I'm wondering where the best place to report this bug would be. I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com.
http://bugs.mysql.com/ is relevant I suppose?
Yeah, and I found my bug:
http://bugs.mysql.com/bug.php?id=61991
Reported two years ago. Even though someone kindly provided a patch, it still hasn't been applied.
And some wonder why mysql is stagnating.
On Sun, May 19, 2013 at 7:00 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
Given the state of mysql in the distro, and the pending move to mariadb, I'm wondering where the best place to report this bug would be. I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com.
huh? http://bugs.mysql.com/search.php?cmd=display&status=Active&os=0&...
I was able to create an account, and bug reports are there for all to see. Are you sure you havent fallen victim to the MDB camps FUD campaign?
FC
Are you sure you havent fallen victim to the MDB camps FUD campaign?
Did you read his later message? he found the bug already reported 18 months ago complete with proposed patch, verified status and S2 (serious) severity ... and yet not fixed...
OP you might be better off filing a bug against either MySQL and F18 in bugzilla.redhat.com and let the maintainers decide what to do about it there ... if if you can test against community-mysql in F19 verify it there and again file in bugzilla.redhat.com ... at least there's some chance then of a Fedora patch being applied even if it's not fixed upstream after all this time ...
With the pending migration to MariaDB it might be worth double checking if the bug exists there and filing a bug with them - at least there's a reasonable chance of it getting fixed within a timespan less than 2 years that way ;)
Am 20.05.2013 12:35, schrieb James Hogarth:
Did you read his later message? he found the bug already reported 18 months ago complete with proposed patch, verified status and S2 (serious) severity ... and yet not fixed...
and how does this match his "I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com" while type "mysql bugreport" would be enough to get to http://bugs.mysql.com/?
if i would get a dollar for each Fedora bugreport closed by the bugzapper at EOL i would be a rich man..........
Fernando Cassia writes:
On Sun, May 19, 2013 at 7:00 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
Given the state of mysql in the distro, and the pending move to mariadb,
I'm
wondering where the best place to report this bug would be. I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com.
huh? http://bugs.mysql.com/search.php? cmd=display&status=Active&os=0&bug_age=0&order_by=date&direction=ASC&limic=10&reorder_by=date
I was able to create an account, and bug reports are there for all to see. Are you sure you havent fallen victim to the MDB camps FUD campaign?
Nope.
I have a challenge for you:
Start with any links you can find in the mysql packages' documentation. Or, just start with the home page, mysql.com, and tell me how you can find bugs.mysql.com, just by following the links.
Around 11:48am on Monday, May 20, 2013 (UK time), Sam Varshavchik scrawled:
I have a challenge for you:
Start with any links you can find in the mysql packages' documentation. Or, just start with the home page, mysql.com, and tell me how you can find bugs.mysql.com, just by following the links.
Because I was bored I tried this. The contact us link on the main page took me to a FAQ link. The first question in the FAQ links to bugs.mysql.com.
I agree it would be even better if the FAQ link was on the main page, but it doesn't seem to shabby to me.
Steve
Reindl Harald writes:
Am 20.05.2013 12:35, schrieb James Hogarth:
Did you read his later message? he found the bug already reported 18 months ago complete with proposed patch, verified status and S2 (serious) severity ... and yet not fixed...
and how does this match his "I find nothing but Oracle's bureaucratease, when I try to dig around mysql.com" while type "mysql bugreport" would be enough to get to http://bugs.mysql.com/?
Can you go to mysql.com, type "mysql bugreport" in the search box on the top, and see what you find.
I wouldn't expect a need to use Google to figure out where to report mysql bugs, when mysql's home page, presumably, exists, and that's where one would logically expect to look, first. Maybe if I didn't know what mysql's homepage was, perhaps, then I can understand using Google. But not when, allegedly, mysql has a home page that I can look at.
By comparison, if I go to www.postgresql.org, I immediately see a fscking "Report a Bug" link right on the home page. Was that too hard?
The closest thing on www.mysql.com is the "Contact Us" link. That leads to Oracle's sales department. An even tinier link, at the bottom, called "Support" leads to a gateway for paid Oracle technical support.
And even if one would like to make an argument that using Google would not be unreasonable here, it's still reasonable to expect that the best place to find the relevant link would be the home page, but after looking around www.mysql.com, you can't blame someone for getting the impression that it's going to be a waste of time.
Furthermore, the fact that the bug remains unfixed, even with a supplied patch, isn't a good sign.