So now, when information on web site is correct please consider removing
'mirrors' workaround so it will not get propagated. And clear message will
be sent to users which address should be used.
Once removed people will be forced to clean their setup now, and new
mistakenly created setups will si
On 05/02/2016 09:15 AM, Arnt Gulbrandsen wrote:
> helle...@dyne.org writes:
>> auto.mirrors does not exist: only auto.mirror does. Unknown names point
>> to www.devuan.org.
>
> Auto.mirrors exists as of yesterday. It was on the devuan home page due
> to a typo. Nextime made the typo work, then fi
helle...@dyne.org writes:
auto.mirrors does not exist: only auto.mirror does. Unknown names point
to www.devuan.org.
Auto.mirrors exists as of yesterday. It was on the devuan home page due to
a typo. Nextime made the typo work, then fixed the typo.
Arnt
_
On 04/30/2016 08:25 PM, Don Wright wrote:
>
> I resolve them as:
> auto.mirror.devuan.org. 300 IN CNAME packages.devuan.org.
> packages.devuan.org.1800IN A 46.105.191.77
>
> auto.mirrors.devuan.org. 300IN CNAME www.devuan.org.
> www.devuan.org. 600
On Sat, 4/30/16, Don Wright wrote:
Subject: Re: [DNG] Devuan Security Repo (was Re: invalid security
certificate)
To: "dng"
Date: Saturday, April 30, 2016, 3:25 PM
Daniel Reurich wrote:
>We now have jessie-security and ascii-security repositories available on
>our mir
Daniel Reurich wrote:
>We now have jessie-security and ascii-security repositories available on
>our mirrors
>
>deb http(s)://.mirror.devuan.org/merged jessie-security main
>[contrib] [non-free]
Would someone speak to the differences between auto.mirror.devuan.org
and auto.mirrors.devuan.org? Th
On Sat, 4/30/16, Daniel Reurich wrote:
Subject: Re: [DNG] Devuan Security Repo (was Re: invalid security
certificate)
To: "dev1fanboy" , "dng@lists.dyne.org"
Date: Saturday, April 30, 2016, 6:12 AM
We now have jessie-security and ascii-security repositories avai
Joel Roth wrote:
> Daniel Reurich wrote:
> > We now have jessie-security and ascii-security repositories available on
> > our mirrors
>
> > deb http(s)://.mirror.devuan.org/merged jessie-security main
> > [contrib] [non-free]
>
> https didn't work on my system. When I went to install
> apt-transp
Daniel Reurich wrote:
> We now have jessie-security and ascii-security repositories available on
> our mirrors
Great news! Yesterday I took the opportunity to switch my
personal system from debian-jessie / sysvinit to
devuan-jessie. It went perfectly. With such a smooth
transition, I think many ot
Excellent!
On Apr 30, 2016 6:10 AM, Daniel Reurich wrote:
We now have jessie-security and ascii-security repositories available on
our mirrors
deb http(s)://.mirror.devuan.org/merged jessie-security main
[contrib] [non-free]
If you've installed from the beta image the security repo stanza should
Nice one :)
Just tested it and it's all working here, pulling about 40 updates right now :)
Cheers,
chillfan
On Saturday, April 30, 2016 12:12 PM, Daniel Reurich
wrote:
> We now have jessie-security and ascii-security repositories available on
> our mirrors
>
> deb http(s)://.mirror.devuan.o
We now have jessie-security and ascii-security repositories available on
our mirrors
deb http(s)://.mirror.devuan.org/merged jessie-security main
[contrib] [non-free]
If you've installed from the beta image the security repo stanza should
already be in your /etc/apt/sources.list
Thanks go to Fra
You'll get updates from time to time when the debian main repo gets updated.
Best to wait for devuan security mirror instead of trying to use the debian
mirror, as you can end up with packages that use systemd that way.
Cheers,
chillfan
On Saturday, April 30, 2016 8:00 AM, Herb Garcia wrote
Um. Then what source is recommended for security updates?
Sent from my Verizon 4G LTE Droid
On Apr 29, 2016 10:45 AM, hellekin wrote:
On 04/29/2016 03:27 PM, Haines Brown wrote:
>
> security.devuan.org uses an invalid security certificate.
> The certificate is only valid for the following nam
On 04/29/2016 03:27 PM, Haines Brown wrote:
>
> security.devuan.org uses an invalid security certificate.
> The certificate is only valid for the following names:
> devuan.org, www.devuan.org
> (Error code: ssl_error_bad_cert_domain)
>
> How do I resolve this?
>
Don't use security.devua
15 matches
Mail list logo