6 ms·
This looks like a great place to tell you about the burning white hot rage I have for Debian after my difficulties with MySQL this past weekend. I was working
by ocdtrekkie 9y ago
This looks like a great place to tell you about the burning white hot rage I have for Debian after my difficulties with MySQL this past weekend.
I was working on script that builds a LEMP stack with Vagrant on a Debian box. And when the script was upgraded to use Debian Stretch, everything we did to customize MySQL configuration broke, and I spent many hours of anguish not knowing why.
Until I stumbled onto the fact that Debian decided that in version 9, they'd start installing MariaDB when you typed "apt-get install mysql-server". I cannot fully explain the anger I have for this dark pattern: When I say "install x", you should either install x or say you don't have it, not install a competitor you think is close enough.
- liveoneggs 9y agoI agree. The MySQL -> MariaDB stuff is bonkers. I would like to read the discussion of it on the lists but can't be bothered to look for it.
- RealSpamapS 9y agoIt was a multi-year effort including us asking specifically for the policy to be spelled out at why there could be only one. IMO the Debian security team wrote a policy specifically to target Oracle in this specific instance, as a result. Digging it out is painful, as it all happened back in 2016, but you can start here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316
- liveoneggs 9y agoI also hold the opinion that MariaDB's failure to simply rename key "mysql" files/dirs to "mariadb" was intentionally confusing and an effort to steal market share. Percona has been a much better citizen with its fork.
- torstenvl 9y agoIt frankly ought to be a crime. Maybe someone can prosecute the responsible Debian maintained under an "exceeds authority" theory of the Computer Fraud and Abuse Act?
- torstenvl 9y agoI'm always amazed at what gets downvoted. Does anyone want to explain why they think it's acceptable to install software on someone's computer without their affirmative and informed consent? Or articulate a legal argument as to why exceeding granted authority on a computer system isn't a violation of the CFAA? 18 U.S.C. § 1030(a)(5) makes it a crime to "knowingly cause[] the transmission of a program, ... code, or command, and as a result of such conduct, intentionally cause[] ['any impairment to the ... availability of ... a program...'] without authorization, to a ['computer ... which is used in or affecting interstate or foreign commerce or communication']." The argument that Debian has "authorization" to install MariaDB simply because it's in the documentation that it will do so when told to install MySQL seems pretty thin.
- j605 9y agoI think you would need to read the GPL to figure out that Debian can do this and you have no recourse (no warranty clause is pretty clear on this).
- torstenvl 9y agoExplain to me why you think the GPL matters here. Last I checked, the GPL pertains to the program (i.e., apt-get). That is not where the problem is. Additionally, contracts are not carte blanche to violate criminal law. To the extent that a contract provision would purport to allow violating a criminal law, it would be unenforceable.
- ocdtrekkie 9y agoI am steaming mad at the Debian release team and think they made an amazingly, amazingly poor decision. I do not think they should go to jail for it. (That being said, I wouldn't mind if Oracle cease-and-desisted them for installing someone else's software using their trademark as the package name.)
- astrodust 9y agoThe way MySQL was being handled as a hybrid of open-source and closed-source for tests was causing a lot of trouble for organizations like Debian that wanted to ship truly open-source software. MariaDB was, at the time, a pretty close fork with the right license model so it was a good drop-in substitute. These situations are rare, but it's not without precedent.
- ocdtrekkie 9y agoTo be clear: I have no issue with Debian shipping MariaDB. I have an issue with Debian pretending MariaDB is MySQL. If I run "apt-get install mysql-server" and get something other than MySQL, we now have a trust issue: The Debian repository cannot be trusted.
- astrodust 9y agoFedora made the same decision, so I don't know if you can blame Debian per-se. This was a community wide problem.
- Conan_Kudo 9y agoNot exactly. Fedora maintains MySQL as "community-mysql"[1], and MariaDB uses the "mariadb"[2] package. [1]: https://apps.fedoraproject.org/packages/community-mysql https://apps.fedoraproject.org/packages/community-mysql [2]: https://apps.fedoraproject.org/packages/mariadb https://apps.fedoraproject.org/packages/mariadb
- astrodust 9y ago`dnf install mysql` gives you MariaDB by default.
- kasabali 9y agoMySQL is not available in Debian repository since MariaDB has replaced it. mysql-server package installs mariadb so that they can handle upgrades gracefully in a way that won't leave existing users in cold. They would choose to do it the way you said but then the people who are upgrading their systems would be annoyed instead of you. Tough choice but either way it's a minor annoyance to be honest. Addition: Also it's not as if it isn't very clear what you're installing: $ apt install mysql-server .... The following NEW packages will be installed: default-mysql-server galera-3 libdbd-mysql-perl libhtml-template-perl libterm-readkey-perl mariadb-client-10.1 mariadb-client-core-10.1 mariadb-common mariadb-server-10.1 mariadb-server-core-10.1 mysql-server .... $ man mysql MYSQL(1) MariaDB Database System MYSQL(1) NAME mysql - the MariaDB command-line tool .... It is not aim of distribution maintainers to hide facts or make you use counterfeit programs, they just want to help users with transition.
- 0x0 9y agoWhen you upgrade to a new major release of Debian, you should take a look at the release notes. The mysql->mariadb migration has its own chapter: https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql https://www.debian.org/releases/stable/amd64/release-notes/c... I guess the fact that mariadb now owns the "mysql-server" package name is a side-effect of how apt manages upgrades and migrations. It's probably the best way to ensure existing users end up with a supported mysql-ish server after the upgrade, instead of being silently stranded on an obsolete debian8 package without receiving security updates.
- ocdtrekkie 9y agoWhy does upgrading Debian need to replace my other software? If I have... Gimp installed, and I upgrade Windows from 7 to 10, I'd be understandably annoyed if Microsoft took the opportunity to replace Gimp with Adobe Photoshop. (And I'd be confused too, since neither Gimp nor Photoshop are Microsoft's. Yet here Debian has replaced software they don't own with other software they don't own, all without my permission.) mysql-server doesn't belong to MariaDB, they can't "own" it. Doesn't Oracle hold a trademark on it?
- mprev 9y agoDebian is an operating system that comes with its own curated library of software. To answer why it upgrades user software when you update the underlying operating system, you need to look at how that software is compiled in a Linux distribution. Whereas Windows apps tend to standalone, bringing with them any libraries they need, Debian tends to have one copy of each library, runtime, and so on. If you upgrade Debian, you upgrade way more than just the kernel, the gnu tools etc. You also upgrade, for example, the Python, the windowing system, the networking stack. Apps that rely on these must also be upgraded in order to work with the new versions of whatever other packages they rely on. It’s a domino effect and it keeps on knocking right up to GIMP or, in this case, MySQL. My answer doesn’t explain why this particular choice was made but I hope it shows how Debian can do that sort of thing whereas Windows wouldn’t.
- jrq 9y agoI don't think this is entirely debian maintainers fault. Package names aren't functions, so the string doesn't necessarily map to the thing you want. Left-pad is the modern analog to what I mean here. Mariadb probably put in for the package name, tbh I can't be bothered to go find out, but I'd bet anything debian team didn't just arbitrarily make that call for users and ship it. 100% guarantee that. I know your feeling though, that's the sort of thing that should be printing a warning or something when it happens.
- ocdtrekkie 9y agoUpon later research, I am not sure of the value of your guarantee: https://www.debian.org/News/2017/20170617 https://www.debian.org/News/2017/20170617 In "Stretch", the default MySQL variant is now MariaDB. The replacement of packages for MySQL 5.5 or 5.6 by the MariaDB 10.1 variant will happen automatically upon upgrade.
- jrq 9y agoSo then it wasn't unannounced... Seems to me this is a non issue then. I guess not everybody reads those, and I've already conceded that its something that ought to warrant a warning prompt or something. But they didn't just change it for no reason.
- kasabali 9y agoWarning prompt is right at the command line tool: $ mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 32 Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1 Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others. $ mysql --version mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (i686) using readline 5.2 It is pretty clear to anybody ever run the tool that it is MariaDB.
- rlpb 9y agoDebian MySQL maintainer here. We wanted to maintain both MySQL and MariaDB in Debian stable. However the Debian release team forced the removal of MySQL on the basis that MariaDB only would suffice. We disagreed with this but they overruled us. mysql-server in Debian stable became a transitional package in Debian stable (only; this doesn't affect testing or unstable) in order to make the upgrade work correctly. It does force users with MySQL server to crossgrade to MariaDB server, and does lead to "mysql-server" being a misnomer in Debian stable. "default-mysql-server" being MariaDB is also misleading, IMHO, but it's the best we could come up with because there isn't any other collective term that covers both MySQL and MariaDB. We didn't want this, but it was forced upon us by the Debian release team. Sorry for the trouble. As others have said, we did our best to explain this in the release notes. We continue to maintain both MySQL and MariaDB in Debian unstable, which remains free of this mess.
- ocdtrekkie 9y agoI totally understand the pain of being overruled by bad decisions, and another person here had also indicated a bit earlier that this was the case. If I could still edit the comment, I would revise "burning white hot rage I have for Debian" to "burning white hot rage I have for the Debian release team". Alas I cannot. :(
- rlpb 9y ago> I would revise "burning white hot rage I have for Debian" to "burning white hot rage I have for the Debian release team". Debian, as a project, appointed the release team and granted them the authority to make this decision. Therefore, IMHO, it's perfectly fair to attribute "Debian" to the decision. As long as you understand that it's not the Debian MySQL/MariaDB maintainers :)
- tzs 9y agoI can see what the Debian release team was trying to do...but doesn't Debian also have a legal team? Did the release team consult with the legal team about having a package named "mysql-server" that uses a trademark owned by Oracle and installs software that is a competitor to the Oracle software the trademark refers to? Oracle is litigious. This seems to be deep into "poke the bear" territory.
- saidmasoud 9y agoFWIW, this is also the case on RHEL-based systems.
- Conan_Kudo 9y agoAs far as I know, no one has stepped up to maintain MySQL for RHEL/CentOS. RHEL/CentOS 7 shipped with MariaDB. There's nothing stopping _anyone_ from volunteering to maintain "community-mysql" for RHEL/CentOS in EPEL.
- edwinyzh 9y agoUnbelievable! I must say. Is Ubuntu (which is based on Debian) affected by this issue?
- deleted 9y ago[deleted]