On dl., juny 01 2020, fsmithred wrote:

> On 6/1/20 8:52 AM, Olaf Meeuwissen wrote:
>> Hi all,
>>
>> Olaf Meeuwissen writes:
>>
>>> Hi all,
>>>
>>> During today's `apt update`, I suddenly see
>>>
>>> E: Repository 'http://deb.devuan.org/merged beowulf
>>> InRelease' changed its 'Suite' value from 'testing-security'
>>> to 'stable'
>>
>> Oops, forgot to zap '-security' in the line above. Sorry.
>>
>>> N: This must be accepted explicitly before updates for this
>>> repository can be applied. See apt-secure(8) manpage for
>>> details.
>>>
>>> errors. Analogously for beowulf-security and beowulf-updates.
>>>
>>> While I welcome a release of beowulf, I haven't seen any
>>> announcement of
>>> it. Neither on this list nor the dng one and the website
>>> still mentions
>>> "testing Beowulf beta".
>>>
>>> Confused,
>>
>> Nevertheless, still confused,
>> --
>
> As it turns out, the most difficult part of getting Beowulf
> ready for
> release is the announcement. You can accept the change. If your
> system is
> up to date, there won't be any new packages for you.
>
> It'll all be official in a day or two. Sorry for the confusion.
>

/me nods

It was also a trade-off between a better coordinated thing and
(human) resource availability to ensure that things go well.
FWIW: pkginfo.devuan.org does reflect the change :-).
--
Evilham