MIME-Version: 1.0
References: <CAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug@mail.gmail.com>
 <20200214105215.6873e402@vostro.wlan>
In-Reply-To: <20200214105215.6873e402@vostro.wlan>
From: Carl Chave <online@chave.us>
Date: Sun, 16 Feb 2020 14:01:03 -0500
Message-ID: <CAGP1gyOakdw54WaRNVrJFWwr4vcv410c-hUr_k4J4su6CnRBBg@mail.gmail.com>
Subject: Re: APK Package Name Issue on armel port
To: Timo Teras <timo.teras@iki.fi>
Cc: ~alpine/apk-tools@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

Timo,

I'll try to keep this short but I'm out of ideas and hoping you might
see where I'm going wrong.

-- used aports/abuild and bootstrap.sh on alpine x86_64 to cross
compile an armel base package set, all but kernel and initramfs
-- compiled kernel separately with appended .dtb for the armel board
-- modified the genrootfs.sh script to build root file system image
with just alpine-base
-- added kernel modules to root file system
-- boot armel board from included uboot with root= kernel argument (no
initramfs)

All of the above seems to work just fine.  I get no errors during
boot, I can login, network is good etc.  The only issue so far is with
apk always returning unsatisfiable constraints missing (alpine-base)
and alpine-base is the only entry in world.  My public key is in
/etc/apk/keys and I don't see anything that would indicate trust is an
issue.  I rebuilt the whole repo again last night and the problem
remains.

So I decided to take the same armel repo and modified the
alpine-chroot script to use it to build an armel chroot on my Fedora
machine with QEMU static.  This worked fine and apk worked as expected
in the chroot!  I diff'd the /lib/apk/db/installed file between the
armel board load and the chroot and they were identical.  I even moved
the file between machines just to see and either file works in the
chroot but neither works on the armel board load.  apk still complains
of unsatisfiable constraints.

Next I tar'd up the chroot on the fedora machine, wiped the armel
board / partition and restored it with the chroot image.  Did a few
changes in etc for securetty, inittab, fstab, shadow and symlinks in
/etc/runlevels but that's it.  Rebooted, everything came up fine but
apk remains broken the same as it was.

Can you think of anything that I'm doing wrong that would break or
confuse apk?  A kernel config option?  Lack of initramfs? Tar option?
Timestamps? Locale? Timezone? fstab mount option? I ran strace at one
point but didn't see anything obviously different between a working
system and the non-working system.  I couldn't get ltrace to compile.

I just don't know how to proceed from here.

Thanks,
Carl