With the release of seamonkey-2.0 all older versions have been discontinued. This means there will be no more security-fixes for any version older than 2.x. One big change in the 2.x series is that it no longer ships with any pkg-config files so any software which could use seamonkey-1.1.x as a replacement of xulrunner cannot be compiled against seamonkey-2.x. In order to remove the package mask of seamonkey-2.x all packages which depend on seamonkey need this dependency to be removed (see URL for a list of affected packages). Reproducible: Always Steps to Reproduce:
Further explanation: I'm planing to remove seamonkey-1* as soon as seamonkey-2 has a stable version in tree. That's why I already request seamonkey dependency removal from stable versions of packages.
This now becomes even more urgent. Upstream officially discontinued seamonkey-1 and also wrote about known unfixed security vulnerabilities. See this news post for reference: http://www.seamonkey-project.org/news#2010-03-16
This is fixed. bug #300418 needs just all arched to have ponyprog stabilized before it can be closed... seamonkey-2 has been unleashed into ~arch...
As of a sync at 1200hrs PDT (2000hrs GMT), this is still hard-masked for ~amd64: localhost ~ # ls /usr/portage/www-client/seamonkey/ ChangeLog files/ seamonkey-1.1.18.ebuild Manifest metadata.xml seamonkey-2.0.4.ebuild localhost ~ # emerge -pv =www-client/seamonkey-2.0.4 These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "=www-client/seamonkey-2.0.4" have been masked. !!! One of the following masked packages is required to complete your request: - www-client/seamonkey-2.0.4 (masked by: package.mask, ~amd64 keyword) /usr/portage/profiles/package.mask: # Jory A. Pratt <anarchy@gentoo.org> (24 Sep 2009) # Much testing needed, not ready for mainline by any means. ...
* gentoo-x86/profiles/package.mask: unleash seamonkey-2 into ~arch (hopefully this time for real...) Please wait a while and sync again...
