Re: [DNG] release status, was: Re: Devuan Beowulf 3.0.0 released.

2020-06-03 Thread d...@d404.nl
On 03-06-2020 21:51, fsmithred via Dng wrote: > On 6/3/20 3:43 PM, Gregory Nowak wrote: >> Since this topic came up, I have a couple non critical machines >> running jessie, and they still get updates. Is this a fluke, or is >> jessie still being supported. If jessie is still being supported, then

Re: [DNG] release status, was: Re: Devuan Beowulf 3.0.0 released.

2020-06-03 Thread fsmithred via Dng
On 6/3/20 3:43 PM, Gregory Nowak wrote: > > Since this topic came up, I have a couple non critical machines > running jessie, and they still get updates. Is this a fluke, or is > jessie still being supported. If jessie is still being supported, then > how long is that planned to continue as of

[DNG] release status, was: Re: Devuan Beowulf 3.0.0 released.

2020-06-03 Thread Gregory Nowak
On Wed, Jun 03, 2020 at 10:04:37AM +0100, Mark Hindley wrote: > On Wed, Jun 03, 2020 at 10:56:50AM +0200, Dario Niedermann wrote: > > * how long will Devuan 2 ASCII keep receiving security updates? > > At least as long as Debian stretch has LTS. That is TBC in 2022 according to >

Re: [DNG] Devuan Beowulf 3.0.0 released.

2020-06-03 Thread Mark Hindley
On Wed, Jun 03, 2020 at 10:56:50AM +0200, Dario Niedermann wrote: > Il 02/06/2020 alle 19:30, Mark Hindley ha scritto: > > > Devuan Developers are delighted to announce the release of Devuan > > Beowulf 3.0.0 as the project's new stable release. [...] > > Hi! Couple of questions whose answers I

Re: [DNG] Devuan Beowulf 3.0.0 released.

2020-06-03 Thread Dario Niedermann
Il 02/06/2020 alle 19:30, Mark Hindley ha scritto: Devuan Developers are delighted to announce the release of Devuan Beowulf 3.0.0 as the project's new stable release. [...] Hi! Couple of questions whose answers I couldn't find on Devuan's website: * is there a full list of packages I can

Re: [DNG] repository status problem?

2020-06-03 Thread al3xu5 / dotcommon
Mon, 1 Jun 2020 21:47:23 +0100 (BST) - Jim Jackson : > Some googling indicated that this sort of problem might be solved by doing > an > > apt update Indeed... While `apt-get update` not asked me to say Y, `apt update` did, and this solved the problem. Anyway this surprised me, both