MySQL Community 5.1.15_beta installs a program into /usr/bin/test, overwriting the 'test' program from coreutils often called by shell scripts. In my case, I noticed this because 'acroread' started spitting out errors relating to various checksums: SHA test passed! MD5 test passed! MD2 test passed! ... where's your certs dir? It seems like a bad idea to allow something to be installed over anything from coreutils. Suggested fix would be to either: 1. rename the program that MySQL installs (to mysql-test, for example) 2. not install that program Reproducible: Always Steps to Reproduce: 1. install coreutils 2. install mysql-community-5.1.15_beta Actual Results: /usr/bin/test is overwritten Expected Results: /usr/bin/test is not overwritten
# grep -C4 dev-db/mysql-community /usr/portage/profiles/package.mask # Upstream discontinued the split of -community and -enterprise specific # tarballs of source. You must move to dev-db/mysql as the -community split has # security vulnerabilities only fixed in the main package. # To be removed 2010/07/01. dev-db/mysql-community Also, FEATURES="protect-owned" has been a default for a while (or use collision-protect there instead).
(In reply to comment #1) > # grep -C4 dev-db/mysql-community /usr/portage/profiles/package.mask > # Upstream discontinued the split of -community and -enterprise specific > # tarballs of source. You must move to dev-db/mysql as the -community split has > # security vulnerabilities only fixed in the main package. > # To be removed 2010/07/01. > dev-db/mysql-community Interesting. I'd only switched to '-community' on account of: $ grep -C2 dev-db/mysql-5.1 /usr/portage/profiles/package.mask # Luca Longinotti <chtekk@gentoo.org> (12 Jan 2007) # Mask MySQL 5.1.* and the alpha versions >=dev-db/mysql-5.1 >=virtual/mysql-5.1 And I installed -community prior to the mask you mention being in place. (but only now noticed the overwritten file) > Also, FEATURES="protect-owned" has been a default for a while (or use > collision-protect there instead). Not in paludis, apparently. Feel free to INVALID or WONTFIX this, unless there's a problem with the >=5.1 mask I mentioned. (Seems wrong that there's no MySQL >= 5.1 in gentoo.)
Actually, 5.1 mask was dropped earlier today.
(In reply to comment #2) There's dev-db/mysql-5.1.44 in ~arch; don't use this completely unmaintained -community thing. The 5.1.x -community stuff has been last touched back in 2007 (!!!) per changelog.
(In reply to comment #4) > (In reply to comment #2) > > There's dev-db/mysql-5.1.44 in ~arch; don't use this completely unmaintained > -community thing. The 5.1.x -community stuff has been last touched back in 2007 > (!!!) per changelog. Sorry if I was unclear. I'd only switched to '-community' since it wasn't repo-masked when I installed it (or didn't have as-threatening wording in its mask) and am now switching back to dev-db/mysql (since it was unmasked today). The current '-community' mask properly warns against using it. (In reply to comment #3) Thanks. It seems this was mostly a case of bad timing. (Installed pre-community-mask, but prior to today's 5.1 unmasking.)
So I guess we are done with this bug. Reopen if needed
