On Tue, Aug 18, 2015 at 07:17:56AM +, Lennart Weller wrote:
> August 11 2015 7:54 PM, "David Kalnischkies" wrote:
> > apt does not link indirectly to libnettle nor to libcurl-gnutls. The
> > optinal apt-transport-https does. That is a big difference for
> > bootstrappers as it means they can i
August 11 2015 7:54 PM, "David Kalnischkies" wrote:
> apt does not link indirectly to libnettle nor to libcurl-gnutls. The
> optinal apt-transport-https does. That is a big difference for
> bootstrappers as it means they can ignore -https for the time being
> until the base system is up and runnin
Control: tags -1 - patch
Hi,
On Fri, Jan 30, 2015 at 11:01:08AM +0100, Weller wrote:
> Replacing the hashing methods with the ones provided by libnettle, which
> apt is already indirectly linked against via libcurl-gnutls resulted in a
apt does not link indirectly to libnettle nor to libcurl-gnu
After spending some time with this issue recently I discovered the root
of the problem. Unlike I assumed before it has nothing to do with
the way the http method is structured but solely stems from the way
hashing is done in apt, sequential and in the same thread as the
download.
Replacing the has
4 matches
Mail list logo
