MIME-Version: 1.0
From: Carl Chave <online@chave.us>
Date: Thu, 13 Feb 2020 22:55:37 -0500
Message-ID: <CAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug@mail.gmail.com>
Subject: APK Package Name Issue on armel port
To: ~alpine/apk-tools@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

I have a running armel port of an alpine base system on an old
Dell/Kace M300 SBC appliance. It seems to be running very well except
that I can't install any packages with apk and I'm completely out of
ideas on how to fix it.

I _think_ there's something going on with apk's ability to locate
packages based on their short names.  For example, on a working system
I can do:

sodco:/home/sodface# apk list file
file-5.38-r0 x86_64 {file} (BSD-2-Clause) [installed]
file-5.37-r1 x86_64 {file} (BSD-2-Clause)

and get results.  On the armel system, the same command produces no output
m300-01:/home/sodface# apk list file
m300-01:/home/sodface#

However if I add a wildcard  I get results:
m300-01:/home/sodface# apk list file*
file-5.37-r1 armel {file} (BSD-2-Clause)
file-dev-5.37-r1 armel {file} (BSD-2-Clause)
file-doc-5.37-r1 noarch {file} (BSD-2-Clause)

apk update seems to be aware of all the packages:
m300-01:/home/sodface# apk update
OK: 317 distinct packages available

I see the same sort of thing with other apk operations, like fetch and
list.  So when I try to apk add a package it always comes back with
unsatisfiable constraints that the package is missing and displays the
package short name.

Any help would be very much appreciated.

Carl