On Thu, Jun 29, 2023 at 08:30:19PM +0900, Olaf Meeuwissen wrote:
> Hi all,
>
> I got a pile of "package such-and-such migrated to excalibur" in my
> mailbox today. Yeay! So I had a go on building a container image for
> it, per

PLease don't. I was just starting to set it up. It isn't ready and won't work
(yet). I expect to have it finished over the weekend.

>
> https://git.devuan.org/paddy-hack/container-images/issues/46
>
> While my migration script needs a minor tweak, I got stuck on
>

>   Get:1 http://deb.devuan.org/merged excalibur InRelease [21.7 kB]
>   Err:1 http://deb.devuan.org/merged excalibur InRelease
>     The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B3982868D104092C

>
> My migration script grabs the devuan-archive-keyring from
>

>    https://files.devuan.org/devuan-archive-keyring.gpg

>
> and that has been working fine for all maintained releases so far.
> It looks that file needs to be updated to include a new key (or a
> key on that keyring should be used to sign the InRelease file).

You need the daedalus version (2023.05.28) of devuan-keyring which includes the
correct key.

>
> # I know the suite name says `future-do-not-use` (as of writing). Am I
> # jumping the gun and should I wait a day, or more?

Yes

Thanks for your enthusiasm though!

Mark