Looks like an expired key on http://repo.aptly.info/dists/nightly/InRelease

EXPKEYSIG ED75B5A4483DA07C Andrey Smirnov <me@smira.ru>

 

Harry

Rename / delete userpatches directory and run the script again.

 

https://github.com/armbian/build/issues/1847

new key is available since 4 days ( see https://github.com/aptly-dev/aptly/issues/911 ) at 
https://www.aptly.info/pubkey.txt

 

Now how to get it into the build-system?

 

@Igor the right way  wouldnt be?:

wget https://www.aptly.info/pubkey.txt

gpg --import ./pubkey.txt

gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key ED75B5A4483DA07C: public key "Andrey Smirnov <me@smira.ru>" imported
gpg: Total number processed: 1
gpg:               imported: 1

 

1 minute ago, guidol said:

Now how to get it into the build-system?

It will get automatically when key servers are synced - key has same ID. I think this error bumps out only when building docker image since we had only one keyserver there. 

 

 

Just now, Igor said:

I think this error bumps out only when building docker image since we had only one keyserver there. 

I also got this message today while building a image - without docker - 

Its was a dev bullseye image for the NPi Neo with the option CREATE_PATCHES

3 minutes ago, guidol said:

I also got this message today while building a image - without docker - 

Its was a dev bullseye image for the NPi Neo with the option CREATE_PATCHES

But you were able to build image?

23 minutes ago, Igor said:

But you were able to build image?

yes - it did built

I encountered this running apt-get update, not during a build.

 

Tried several fixes without success.

Eventually fixed it using info from the bug report for the last time it occurred in 2018.

here

sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-keys ED75B5A4483DA07C

Harry