Relicensing of MySQL Man Pages Just a Bug
An anonymous reader writes "As reported earlier on Slashdot it appeared the license covering the MySQL man pages was changed from the GPL to something less good. However, as speculated, this appears to be a bug."
The build system was grabbing the wrong files, oops. The fix should be coming shortly: "Once the fixes have been made to the build system, we will rebuild the latest 5.1, 5.5, 5.6 releases plus the latest 5.7 milestone and make those available publicly asap."
For what its worth, I'll continue using MSDN for my professional manual pages and welcome anyone with open arms to use too.
Anyone with open arms? Do MSDN users usually slit their wrists?
Less good?
I think I'm just going to stop reading Slashdot before it turns me in to a retard.
Duh? You know, maybe the MariaDB people should actually investigate things before making massive conclusion jumps? Sowing FUD against Oracle and MySQL for their benefit seems to be more important than getting the truth.
... because someone noticed it. <_<
A feeling of having made the same mistake before: Deja Foobar
It appears the My Clean PC spam/virus has struck slashdor!
Have gnu, will travel.
I know Oracle is a supposed to be super evil lawyer driven blah blah blah... but just so we get the story straight, Monty sells MySql to Sun, Oracle buys Sun, Monty wants MySql back as MariaDb. At this point, Monty and the MySql community have cried wolf one to many fucking times. I really just don't care anymore.
What would happen if the build system picked up some docs on constructing an atom bomb? Could it stop by and pick some up from the NSA? And maybe a six pack and and a carton of Lucky Strikes?
“He’s not deformed, he’s just drunk!”
BULLSHIT!
Why is it possible for an automated process to insert the wrong license? Because the change is being planned or at least prepared for. This could have been a trial balloon.
That people were entertaining notions otherwise was asinine, regardless of it involving Oracle. This might have actually been something to worry about if the documents weren't already dual licensed. This sort of mistake has been made time and time again, and will continue to be made time and time again.
Seriously, a "bug" changes the license on files? A "bug?"
Please! Spare me! A license is a legal document.
They hoped it would not have been noticed and when it was, "oops!"
Sorry, Larry is a dirt bag, always has been, always will be.
This has happened before, I can remember at least 3 other times. I wrote about one case in 2005 (http://theconsultantcto.com/opensource) and right after my article had its 15 minutes of fame, they rewrote the license.
They'll just keep doing this until finally no one notices and voila, your presumed OSS licensed software ain't yours to do with as you will.
after "accidentially" removing the tz-update tool and then reinstating it with a "sorry, was an accident"
squash the bug... it's located between the chair and the keyboard on station #...