On Fri, Jun 16, 2017 at 09:00:23AM +0100, G.W. Haywood wrote: > Hi there, > > On Fri, 16 Jun 2017, Taiidan@ wrote: > > >When trying to run apt-get update with https I receive this error > > > >curl: (1) Protocol "http" not supported or disabled in libcurl > > https://curl.haxx.se/docs/faq.html#Protocol_xxx_not_supported_or_di > > Is there some compelling reason to want apt-get to use HTTPS? After > all, downloaded archives can be checked for integrity independently > of the transport mechanism. > > Your problem description is a little vague, and I'd expect Devuan's > libcurl to support HTTPS. I wonder what exactly have you done to try > to make 'apt-get update' use https. Is 'curl' itself installed, and > how was it installed? Do you know if you have installed curl/libcurl > other than from packages? If you post the output of
Hi, if you want to use apt-get via https, you should install apt-transport-https. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ]
signature.asc
Description: Digital signature
_______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
