1 1
maya.b

new build installation from github fails on download_and_verify

Recommended Posts

Hi,

 

I was just setting up a new armbian build environment following the usual github instructions on a bionic 18.04.3 system.

 

Running ./compile.sh (alone or with any configuration) generates the following error:

[ o.k. ] Checking for external GCC compilers 
[ .... ] downloading using torrent network [ gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz ]
[ error ] ERROR in function download_and_verify [ general.sh:1026 ]                                                                   [ error ] verification failed 

 

From the output/debug/output.log

Displaying message: Checking for external GCC compilers  info
Displaying message: downloading using torrent network gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz
gpg: error reading key: No public key
gpg: DBG: locking for '/media/psf/ssd1TB/armbian/cache/.gpg/gnupg_spawn_dirmngr_sentinel.lock' done via O_EXCL
gpg: connecting dirmngr at '/media/psf/ssd1TB/armbian/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: error reading key: No public key
gpg: DBG: locking for '/media/psf/ssd1TB/armbian/cache/.gpg/gnupg_spawn_dirmngr_sentinel.lock' done via O_EXCL
gpg: connecting dirmngr at '/media/psf/ssd1TB/armbian/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: assuming signed data in '/media/psf/ssd1TB/armbian/cache/toolchains/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz'
gpg: Signature made Tue 19 Nov 2013 09:00:03 AM GMT
gpg:                using RSA key D47877808F427EAF
gpg: Can't check signature: No public key
Displaying message: ERROR in function download_and_verify general.sh:1026 err
Displaying message: verification failed  err
Displaying message: Process terminated  info

 

Any suggestions?

 

M.

Share this post


Link to post
Share on other sites

Yes, same errors.

 

Have also had a quick look for public keys to add to gpg's key manager but no luck so far.

Share this post


Link to post
Share on other sites
7 minutes ago, maya.b said:

Have also had a quick look for public keys to add to gpg's key manager but no luck so far.


Try running with a parameter USE_TORRENT="no" or put that to userpatches/config-example

Share this post


Link to post
Share on other sites

Still fails on installing the toolchain with the same gpg error as above.

 

Including output/debug/output.log

Share this post


Link to post
Share on other sites

will give that a go - will take a while to setup, the vagrant option (what I used to use) is misbehaving but will start a separate thread on that.

Share this post


Link to post
Share on other sites

The vagrant issues in that thread look familiar,

 

The docker build is proceding so am guessing it's one of the dependancies that got installed in the docker container. PGP validation seems to working without issue but still going.

 

From past experience, if it's installing the toolchain without issue, it's fine.

 

Thanks!

Share this post


Link to post
Share on other sites
Just now, maya.b said:

The docker build is proceding so am guessing it's one of the dependancies that got installed in the docker container. PGP validation seems to working without issue but still going.


I will check native build later on since it should work. Is that a clean Ubuntu 18.04 build that you are using?

Share this post


Link to post
Share on other sites

Yes, the native is a clean 18.04 with kernel:

Linux 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

 

Share this post


Link to post
Share on other sites

ack! spoke to soon. closer:

Displaying message: Building deb linux-u-boot-current-nanopim4_19.11.4_arm64.deb info
dpkg-deb: error: control directory has bad permissions 700 (must be >=0755 and <=0775)
Displaying message: ERROR in function compile_uboot compilation.sh:257 err

 

Share this post


Link to post
Share on other sites

I made two tests:

 

1. Building on Ubuntu Xenial inside Docker (succeded)

2. Clean Ubuntu 18.04 mini + standard system utils, native build (succeded)

Share this post


Link to post
Share on other sites

Just created a new native VM 18.04 to build in. Works fine on the VMs local storage.

 

Same failures with a remote ext4 mount.

 

Time to buy more local storage. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
1 1