Why is it in "dev-db"? That makes no sense. Or would you put Apache in "dev-www"? Why is mysql-4.1 masked at all? We've only had it for two years... Why is the latest ebuild for MySQL 4.1.13? 4.1.13a is out... But this is really minor, compared to: 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? Reproducible: Always Steps to Reproduce: 1. emerge '>=dev-db/mysql-4.1' 2. see a bunch of "masked by: package.mask" errors 3. get mad Actual Results: "masked by: package.mask" errors Expected Results: merged successfully, or at least attempted. Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12.3 x86_64) ================================================================= System uname: 2.6.12.3 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://mirror.tds.net/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X a52 aac aalib acpi adns alsa apache2 audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdparanoia cdr crypt cups dedicated doc dvb dvd dvdr dvdread eds emul-linux-x86 encode ffmpeg flac foomaticdb ftp gdbm gif gnome gpm gstreamer gtk gtk2 imap imlib ipv6 ithreads jack jpeg kde ladcca lirc lm_sensors lzw lzw-tiff maildir matroska mikmod mmap mp3 mpeg mysql ncurses nls nocd nptl offensive ogg opengl pam pdflib perl png ppds python qt quicktime readline ruby samba sdl shorten slang socks5 speex spell ssl szip tcpd theora tiff truetype-fonts type1-fonts usb userlocales v4l vcd vhosts videos vorbis xml2 xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
>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. ***
