On Mon, Dec 30, 2013 at 11:04:48AM -0800, Jonathan Nieder wrote: > block 726073 by 726116 > quit > (culling cc list) > > Hi, > > Alessandro Ghedini wrote: > > On ven, dic 27, 2013 at 11:24:11 +0000, Debian Bug Tracking System wrote: > >> Processing commands for [email protected]: > > >>> affects 726073 + git src:git > >> Bug #726073 [libcurl3-nss] libcurl3-nss: tries to use libnsspem, which is > >> not provided by libnss3 > >> Added indication that 726073 affects git and src:git > > > > Care to explain how this affects git, considering that it uses > > libcurl3-gnutls? > > Time permitting, I'd like to switch git to using libcurl3-gnutls (for a > few different reasons --- sidestepping the libgmp licensing issue is > one, and the possibility of better interoperability with some broken > servers is another). Using "affects" makes it easier for me to track > this bug when working on the git package.
TBQH if ever libnss turned out to be a viable option, I'd seriously consider
switching curl to be libnss-only (like e.g. Red Hat does).
> > Also, there's not much I can do about this (except maybe dropping
> > libcurl3-nss
> > altogether), and since we have #726116 tracking this now, I'm inclined to
> > close
> > this report.
>
> Could we keep it open? It's the only report that tracks the symptom
> instead of that specific proposed fix --- e.g., if libcurl could use the
> shared nssdb instead of PEM certificates when using the NSS backend,
> that would be a fine way to solve this.
Ok, makes sense.
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
