Can't create new device aport via init command due to apkindex failure
As I mentioned in the title, I can't get past analysing the boot image, due to this happening:
(004070) [16:16:39] Which flash method does the device support?
[16:16:39] Flash method (fastboot/heimdall/0xffff/uuu/none) [fastboot] fastboot
(004070) [16:16:40] You can analyze a known working boot.img file to automatically fill out the flasher information for your deviceinfo file. Either specify the path to an image or press return to skip this step (you can do it later with 'pmbootstrap bootimg_analyze').
[16:16:40] Path /home/lilly/Downloads/twrp-3.3.1-0-fugu.img
(004070) [16:16:53] NOTE: You will be prompted for your sudo password, so we can set up a chroot to extract and analyze your boot.img file
(004070) [16:16:53] NOTE: Skipped apk version check for chroot 'native', because it is not installed yet!
(004070) [16:16:53] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/dev
(004070) [16:16:53] % sudo mount -t tmpfs -o size=1M,noexec,dev tmpfs /home/lilly/.local/var/pmbootstrap/chroot_native/dev
(004070) [16:16:53] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/dev/pts /home/lilly/.local/var/pmbootstrap/chroot_native/dev/shm
(004070) [16:16:53] % sudo mount -t tmpfs -o nodev,nosuid,noexec tmpfs /home/lilly/.local/var/pmbootstrap/chroot_native/dev/shm
(004070) [16:16:53] % sudo mknod -m 666 /home/lilly/.local/var/pmbootstrap/chroot_native/dev/null c 1 3
(004070) [16:16:53] % sudo mknod -m 666 /home/lilly/.local/var/pmbootstrap/chroot_native/dev/zero c 1 5
(004070) [16:16:53] % sudo mknod -m 666 /home/lilly/.local/var/pmbootstrap/chroot_native/dev/full c 1 7
(004070) [16:16:53] % sudo mknod -m 644 /home/lilly/.local/var/pmbootstrap/chroot_native/dev/random c 1 8
(004070) [16:16:53] % sudo mknod -m 644 /home/lilly/.local/var/pmbootstrap/chroot_native/dev/urandom c 1 9
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/proc
(004070) [16:16:54] % sudo mount --bind /proc /home/lilly/.local/var/pmbootstrap/chroot_native/proc
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/var/cache/apk
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/cache_apk_x86_64 /home/lilly/.local/var/pmbootstrap/chroot_native/var/cache/apk
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-ccache
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/cache_ccache_x86_64 /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-ccache
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/var/cache/distfiles
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/cache_distfiles /home/lilly/.local/var/pmbootstrap/chroot_native/var/cache/distfiles
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-git
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/cache_git /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-git
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-abuild-config
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/config_abuild /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-abuild-config
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/etc/apk/keys
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/config_apk_keys /home/lilly/.local/var/pmbootstrap/chroot_native/etc/apk/keys
(004070) [16:16:54] % sudo mkdir -p /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-packages
(004070) [16:16:54] % sudo mount --bind /home/lilly/.local/var/pmbootstrap/packages /home/lilly/.local/var/pmbootstrap/chroot_native/mnt/pmbootstrap-packages
(004070) [16:16:54] ERROR: Missing required key 'arch' in block {}, file: /home/lilly/.local/var/pmbootstrap/cache_apk_x86_64/APKINDEX.066df28d.tar.gz. Please try again.
Is this another upstream Alpine Linux issue or should I perform a certain workaround?
Edited by Alexey Min