Date: Wed, 28 Dec 2011 23:18:07 +0100 From: Florian Smeets <flo@FreeBSD.org> To: "Mikhail T." <mi+thun@aldan.algebra.com> Cc: gecko@FreeBSD.org Subject: Re: New nss and firefox Message-ID: <4EFB959F.1030501@FreeBSD.org> In-Reply-To: <4EFB3B18.3050001@aldan.algebra.com> References: <4EF7C66F.9090005@aldan.algebra.com> <4EF81D1C.3090405@FreeBSD.org> <4EF9BC57.8050605@aldan.algebra.com> <4EFAD049.7000406@freebsd.org> <4EFB3B18.3050001@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 28.12.11 16:51, Mikhail T. wrote: > On 28.12.2011 03:16, Florian Smeets wrote: >> The ports slush is still not completley lifted. We are still in a >> partial ports thaw. > Well, the update right now will not even touch anything "major" -- > firefox builds with its own. And the new version is completely compatible. >> What is it that you need so urgently? We could update only the >> certdata.txt in security/ca_root_nss, but there should really be a good >> reason for it. > Ideally, all ports would be up-to-date with the upstream releases. The > closer to ideal the better, is not it? :) > > In this particular case, the latest nss is required for firefox to build > with "system nss" -- something we must go back to doing ASAP in my > strongly-held opinion. > JFYI, i updated the version in ports to nss-3.12.11.with.ckbi.1.88.tar.gz Cheers, Florian [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk77laAACgkQapo8P8lCvwme6wCg0GgWw1tAp/GQjA2hSGtgExLZ RlgAn3seUKN86uFuZO03KJs89bmfNkOb =VfrQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFB959F.1030501>
