:: [DNG] sources.list targets (was: Re…
Pàgina inicial
Delete this message
Reply to this message
Autor: Joel Roth
Data:  
A: dng
Assumptes vells: Re: [DNG] Devuan Security Repo (was Re: invalid security certificate)
Assumpte: [DNG] sources.list targets (was: Re: Devuan Security Repo (was Re: invalid security certificate)
Joel Roth wrote:
> Joel Roth wrote:
> > Daniel Reurich wrote:
> > > We now have jessie-security and ascii-security repositories available on
> > > our mirrors
> >
> > > deb http(s)://<CC|auto>.mirror.devuan.org/merged jessie-security main
> > > [contrib] [non-free]
> >
> > https didn't work on my system. When I went to install
> > apt-transport-https, I got the warning:
> >
> > WARNING: The following packages cannot be authenticated!
> > apt-transport-https
> >
> > Was able to resolve it by converting sources.list
> > from packages.devuan.org to auto.mirror.devuan.org.
>
> Not quite. Still having a certificate problem.
>
> Err https://auto.mirror.devuan.org jessie-security/contrib amd64 Packages
> SSL: certificate subject name (packages.devuan.org) does not match target host name 'auto.mirror.devuan.org'



Hi,

The devuan.org website gives these targets:

deb http://auto.mirrors.devuan.org/merged jessie main
deb http://auto.mirrors.devuan.org/merged jessie-updates main
deb http://auto.mirrors.devuan.org/merged jessie-security main

However, apt-get update returns several errors:

    Ign http://auto.mirrors.devuan.org jessie InRelease
    Ign http://auto.mirrors.devuan.org jessie-updates InRelease
    Ign http://auto.mirrors.devuan.org jessie-security InRelease
    Ign http://auto.mirrors.devuan.org jessie Release.gpg
    Ign http://auto.mirrors.devuan.org jessie-updates Release.gpg
    Ign http://auto.mirrors.devuan.org jessie-security Release.gpg
    Ign http://auto.mirrors.devuan.org jessie Release
    Ign http://auto.mirrors.devuan.org jessie-updates Release
    Ign http://auto.mirrors.devuan.org jessie-security Release
    Err http://auto.mirrors.devuan.org jessie/main amd64 Packages
      404  Not Found [IP: 46.105.191.76 80]
    Ign http://auto.mirrors.devuan.org jessie/main Translation-en_US
    Ign http://auto.mirrors.devuan.org jessie/main Translation-en
    Err http://auto.mirrors.devuan.org jessie-updates/main amd64 Packages
      404  Not Found [IP: 46.105.191.76 80]
    Ign http://auto.mirrors.devuan.org jessie-updates/main Translation-en_US
    Ign http://auto.mirrors.devuan.org jessie-updates/main Translation-en
    Err http://auto.mirrors.devuan.org jessie-security/main amd64 Packages
      404  Not Found [IP: 46.105.191.76 80]
    Ign http://auto.mirrors.devuan.org jessie-security/main Translation-en_US
    Ign http://auto.mirrors.devuan.org jessie-security/main Translation-en
    W: Failed to fetch http://auto.mirrors.devuan.org/merged/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: 46.105.191.76 80]


    W: Failed to fetch http://auto.mirrors.devuan.org/merged/dists/jessie-updates/main/binary-amd64/Packages  404  Not Found [IP: 46.105.191.76 80]


    W: Failed to fetch http://auto.mirrors.devuan.org/merged/dists/jessie-security/main/binary-amd64/Packages  404  Not Found [IP: 46.105.191.76 80]


I went back to my previous settings using auto.mirror.devuan.org
And was able to apt-get update without errors.

What is the difference between these two hosts? Should
devuan.org be updated? I think this is important.


Regards,

Joel

--
Joel Roth