I suggest creating a new overlay for masking ebuilds masked for the sole purpose of complying with a portage freeze. This will allow users who don't want the freeze to unmask these packages, but to keep unstable packages frozen. Reproducible: Always Steps to Reproduce: N/A Actual Results: N/A Expected Results: N/A Portage 2.0.47-r8 (default-1.0, gcc-2.95.3, glibc-2.2.5-r2,2.2.5-r7) ================================================================= System uname: 2.4.19-rmap14a i686 Celeron (Coppermine) GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode jpeg libg++ mikmod mmx mpeg ncurses pdflib quicktime spell truetype xml2 xmms xv arts berkdb bonobo cdr esd gdbm gif gnome-libs gpm gtkhtml guile imlib java kde libwww motif mozilla mysql nas nls opengl pam perl png postgres python qt readline scanner sdl slang ssl svga tcltk tcpd tetex tiff X gtk gnome alsa pda oggvorbis ipv6" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-O2 -mcpu=i686 -pipe" CXXFLAGS="-O2 -mcpu=i686 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
freeze only affects stable packages now ... we continue to add unstable *** This bug has been marked as a duplicate of 8397 ***