Summary: | >=dev-db/mysql-4.1 is "masked for testing"? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Masover <ninja> |
Component: | [OLD] Server | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | k, kwach, michael.postmann, steve |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Masover
2005-08-18 10:10:27 UTC
>Why is it in "dev-db"? That makes no sense. Or would you put Apache in "dev-www"? historical reason like quite all in actual civilities sometime good sometime not. All db stuff stay there. > >Why is mysql-4.1 masked at all? We've only had it for two years... Quoting from my message on gentoo-server today |We are still working on some inter-application issues. |MySQL 4.1 , 5.0 ebuilds are maintained at the same way of the stable 4.0 |ones, it should be safe to use them alone. |If you want to procede this way two edits in /etc/portage are needed: | |/etc/portage/package.unmask:=dev-db/mysql-4.1* |/etc/portage/package.keywords:dev-db/mysql ~ARCH > >Why is the latest ebuild for MySQL 4.1.13? 4.1.13a is out... But this is >really minor, compared to: Quoting MySQL Changelog: |Security improvement: Applied a patch that addresses a zlib data |vulnerability that could result in a buffer overflow and code execution. |(CAN-2005-2096) (Bug #11844). Shortly after MySQL 4.1.13 was released, a |second potential zlib security flaw was discovered and fixed - the issue |is tracked by the Mitre CVE ID (CAN-2005-1849). A patch for this flaw |was applied on top of the 4.1.13 sources and published as 4.1.13a. The |affected binaries have been rebuilt. see bug #99922 to see why we don't need to apply this > >Why, in the name of all that is holy, is >=dev-db/mysql-4.1 hard masked? It is >"masked for testing" since Nov. 2004. Surely 10 months of testing on a >one-year-old product is enough to at least remove the hard mask, so that those >of us willing to risk it can grab it with ~arch? At the moment it's more tested against a stable tree, with only the minimal changes in /etc/portage/package.unmask /etc/portage/package.keywords . *** Bug 103933 has been marked as a duplicate of this bug. *** Francesco, Hi. "At the moment it's more tested against a stable tree, with only the minimal changes in /etc/portage/package.unmask /etc/portage/package.keywords ." Can you please clarify? Has it been tested extensively against the stable tree ? If we were to put it in ~x86, would that not increase the number of testers, especially since the call for testers went out in May 17th ? Will test on my system and report. Aniruddha: The MySQL-4.1 p.mask is going to be removed at the same time that PHP5 comes properly to ~arch (deadline is this Thursday). *** Bug 104990 has been marked as a duplicate of this bug. *** *** Bug 104715 has been marked as a duplicate of this bug. *** |