Du to problems with upstream's build farms new releases of seamonkey had been delayed for several months. These problems seem to be gone now and upstream just released seamonkey-2.35 a couple of days ago. seamonkey-2.33.1 has several security related bugs (the same that firefox-36 has) and thus we need new stable versions of seamonkey ASAP. Arches please test and mark stable the following packages. =www-client/seamonkey-2.35: ~alpha amd64 ~arm ~ppc ~ppc64 x86 =www-client/seamonkey-bin-2.35: amd64 x86
If the update fixes security vulnerabilities, the bug should probably be in the Gentoo Security component and assigned to security@g.o.
The security issues are the same as listed in bug 559186 and previous. We can add seamonkey to the subject there and CC arches again, if you prefer?
I'm about to stabilize these packages myself anyway. Arch teams are too slow...
commit fe43f913980775b796bba926f308d732fb96a1d2 Author: Lars Wendler <polynomial-c@gentoo.org> Date: Wed Sep 16 16:45:21 2015 www-client/seamonkey-bin: version 2.35 stable (amd64 and x86) (bug #559950) Package-Manager: portage-2.2.20.1 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> www-client/seamonkey-bin/seamonkey-bin-2.35.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 4275930ce40448ab250f64c00c0644e279a3c916 Author: Lars Wendler <polynomial-c@gentoo.org> Date: Wed Sep 16 16:42:01 2015 www-client/seamonkey: version 2.35 stable (amd64 and x86) (bug #559950). Package-Manager: portage-2.2.20.1 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> www-client/seamonkey/seamonkey-2.35.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
