The MySQL build team has a script that updates the license header in files that require it. Since the "different license" is actually the license of the documentation, from which the man pages are generated, it is possible that the script failed to update the licence text in the man pages.

Source: Ex-Oracle MySQL engineer.

Applying Hanlon's razor:

Never attribute to malice that which is adequately explained by stupidity.

I've always liked Hanlon's razor, I think it's woefully forgotten in the tech community who often reach for the pitchforks without thinking.

Witty. Now please demonstrate how it looks applied to this case.

Replace "malice" with "conspiracy to eradicate open-source MySQL" and "stupidity" with "bugs in the packaging code".

Good, good, almost there. Now elaborate on "bugs in the packaging code" part.

What does "the wrong set of copyright headers" do in a vicinity of the packaging pipeline and how it came to exist in the first place. It's easy to throw around flashy one-liners. It's a bit more work to actually try and read into the facts presented.

As has already been stated on this same page, there's a community edition and a commercial edition. They're likely part of the same packaging pipeline.

Do not be condescending on Hacker News when someone is responding to your question. It's easy to jump to conclusions. It's a bit more to actually try and understand what happened - that is the point of Hanlon's Razor. This may have been intentional, yes. But it may also have been a bug.

> Do not be condescending on Hacker News when someone is responding to your question.

Do not dispense unsolicited advice on the Internets. That wasn't a reply. It was a highbrow remark that was as generic as it was barely applicable. A proper reply was the sibling comment that pointed at two editions.

The context was implied and definitely applicable. This is now becoming pedantic so let's invoke Godwin's law and stop valuable electrons being pushed around for no reason.

The nazis did it.

Everyone happy now? :)

it's even more work to edit your package management system to include a set of documents that have nothing to do with the anything released ever before it. I would love to the commit comment.

The non-community release, maybe?