This message is appearing when trying to build an image with manjaro-arm-tools and the same is happening when building the github-action repositories.
Does anyone know what is happening?
-> Extracting aarch64 rootfs...
-> Setting up keyrings...
==> ERROR: Aborting...
umount: /var/lib/manjaro-arm-tools/img/rootfs_aarch64/var/cache/pacman/pkg: not mounted.
Thank you very much!
The error may be in Setting up keyrings, I’m trying to fix it but so far without success, if anyone else can help I would appreciate it.
==> Creating gnome edition rootfs image for rpi4...
-> Removing old aarch64 rootfs...
-> Removing old aarch64 rootfs archive...
-> Downloading latest aarch64 rootfs archive...
/home/juliano/Works 100%[===================>] 201,14M 12,8MB/s em 15s
-> Extracting aarch64 rootfs...
-> Setting up keyrings...
error: config file /etc/pacman.d/mirrorlist could not be read: No such file or directory
error parsing '/etc/pacman.conf'
mkdir: cannot create directory '': No such file or directory
gpg: Warning: using insecure memory!
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
chmod: cannot access '/trustdb.gpg': No such file or directory
gpg: Warning: using insecure memory!
==> Generating pacman master key. This may take some time.
gpg: Warning: using insecure memory!
gpg: Generating pacman keyring master key...
gpg: directory '/root/.gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/8D5CC6837A4D9992BEBEFA777CA42BADAE151415.rev'
gpg: Done
==> Updating trust database...
gpg: Warning: using insecure memory!
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
error: config file /etc/pacman.d/mirrorlist could not be read: No such file or directory
error parsing '/etc/pacman.conf'
==> ERROR: You do not have sufficient permissions to read the pacman keyring.
==> Use 'pacman-key --init' to correct the keyring permissions.
-> Setting branch to stable...
I am not sure what you are trying to do now. If you are trying to build an image to use I tell how to do it in that link I gave above by downloading the latest good rootfs and placing it in your file system where it belongs. Then build the image but leave out the -n flag. By leaving out the -n flag it will not download The latest aarch64 rootfs archive that is bad and replace your good one you have on your system.