Date: Wed, 07 Apr 2010 21:21:03 +0200 From: Beat Gaetzi <beat@FreeBSD.org> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@FreeBSD.org Subject: Re: Updating security/nss Message-ID: <4BBCDB1F.4060107@FreeBSD.org> In-Reply-To: <1270408368.32902.37.camel@shumai.marcuscom.com> References: <4BB08760.3090906@FreeBSD.org> <1270408368.32902.37.camel@shumai.marcuscom.com>
index | next in thread | previous in thread | raw e-mail
Joe Marcus Clarke wrote: > On Mon, 2010-03-29 at 12:56 +0200, Beat Gaetzi wrote: >> The upcoming update of SeaMonkey to 2.0.4 requires a newer version of >> security/nss: >> http://tmp.chruetertee.ch/seamonkey-2.0.4.log >> >> I've created a patch to update NSS to 3.12.6: >> http://tmp.chruetertee.ch/nss-3126.patch >> >> With this version of NSS SeaMonkey 2.0.4 builds fine. I haven't done any >> further testing. I first want to ask if there are any plans for updating >> security/nss to a newer version? > > We do not yet have it in MC. I have no objection to this patch being > committed. I've run a test on a tinderbox with 8.0-STABLE i386 and tested the ports depending on security/nss with 3.12.6. Beside a build failure of ruby (which doesn't look related to nss) I couldn't found a problem: http://gecko.miwibox.org/index.php?action=list_buildports&build=8-FreeBSD_i386 Also the update to 3.12.6 does not include a shlib bump so I think there is no PORTREVISION bump of the depending ports needed. Does this update somehow interfere with the upcoming gnome update? Thanks, Beathome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BBCDB1F.4060107>