new build installation from github fails on download_and_verify

[maya.b]

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.

[Igor]

Have you tried to start again?

[maya.b]

Yes, same errors.

 

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

[Igor]

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

[maya.b]

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

 

Including output/debug/output.log

[Igor]

OK, then I will need to recreate ... What about 

apt install dirmngr

+ run again.

[maya.b]

already installed at latest version

[Igor]

./compile docker is one possible workaround ...

[maya.b]

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.

[Igor]

1 minute ago, maya.b said:

the vagrant option

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

[maya.b]

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!

[Igor]

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?

[maya.b]

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

 

[maya.b]

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

 

[Igor]

I made two tests:

 

1. Building on Ubuntu Xenial inside Docker (succeded)

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

[maya.b]

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. 

[maya.b]

docker build on storage host slooooowly coming along ....

 

sigh.

[FrikoAnPulento]

Hello, same problem here.

I've manually downloaded files, manually uncompressed them and added .download-complete file and then run compile again.

Now it works, but would be nice to fix it.
If you need more info about the problem just ask

 

P.S. I can say that I had to download toolchains from browser, because wget got several download errors (probably due to connection issue). Could be related to the problem?
 

[balbes150]

This may be related to something, but I stopped loading rootfs caches during the build (the system has to build everything itself from packages).

[Igor]

We recently made some improvements and I hope this will not happen again.
https://github.com/armbian/build/pull/2400