Re: Possible update of libnss3
On Fri, Oct 01, 2010 at 12:06:56AM +0200, Julien Cristau wrote:
> On Wed, Sep 29, 2010 at 09:37:24 +0200, Mike Hommey wrote:
> > We thus have several options:
> > - apply the 3 mentioned changes to 3.12.6 and update through t-p-u.
> > - apply the 3 mentioned changes and the upstream workaround for #592315
> > to 3.12.7 and update through standard testing migration.
> > - upload 3.12.8 to unstable with the upstream workaround for #592315
> > and update through standard testing migration.
> > Note that 3.12.7 and 3.12.8 need the latest nspr in unstable to go with
> > them.
> > What would be your preferred course of action?
> I'm kind of uneasy about the ssl false start stuff in 3.12.8. Then
> again the 3.12.6 -> 3.12.7 diffstat looks scary already, I'm not getting
> through all of that tonight.
The ssl false start stuff is only enabled if you set the
SSL_ENABLE_FALSE_START flag. AFAIK, only iceweasel/firefox 4.0 does so.
(FWIW, 3.12.7 has been in the archive from day 1 of the freeze, it could
have gone in earlier)
> 3.12.8 seems to drop a function from the exported jar.h header, where
> does that come from? [Reading further, the function was actually
> removed in 3.12.7, but its prototype was kept in the header. Still
> seems weird.]
The function was actually not exported (nss uses a symbols script, check
the various .def files in the tree), so it can't have been used by rdeps.