All, Rich Freeman asked, in another thread, for specific examples of old package.mask entries that just have "masked for testing" as the description.
Here is what I found with a quick look through package.mask. These should be cleaned up by either 1) removing the mask or 2) booting the affected packages or versions from the tree. # Sergei Trofimovich <sly...@gentoo.org> (05 Jan 2013) # Masked for testing. Is not compatible with cvsps-2 (bug #450424). # But can be used on it's own! Try 'cvsps --fast-export'. >=dev-vcs/cvsps-3 # Tim Harder <radher...@gentoo.org> (27 Nov 2012) # Masked for testing =media-libs/libsfml-2* # Markos Chandras <hwoar...@gentoo.org> (03 Nov 2012) # Masked for testing app-benchmarks/ltp # Robin H. Johnson <robb...@gentoo.org> (08 Oct 2012) # Masked for testing =sys-libs/db-6.0* =sys-libs/db-5.3* =sys-libs/db-5.2* =sys-libs/db-5.1* =sys-libs/db-5.0* # Ultrabug <ultra...@gentoo.org> (16 May 2012) # Masked for testing >=sys-cluster/corosync-2.0.0 # MATSUU Takuto <mat...@gentoo.org> (27 Oct 2011) # Mask for testing >=sys-devel/distcc-3.2_rc1 # Christian Faulhammer <fa...@gentoo.org> (12 Mar 2011) # Mask for testing >=www-apps/joomla-1.6.0 # Michael Sterrett <mr_bon...@gentoo.org> (20 Jan 2010) # testing mask for upcoming exult release >=games-engines/exult-1.3 # Vlastimil Babka <cas...@gentoo.org> (20 May 2008) # Masked for testing app-arch/rpm5 Thanks, William
signature.asc
Description: Digital signature
