Date: Fri, 14 Feb 2020 10:52:15 +0200
From: Timo Teras <timo.teras@iki.fi>
To: Carl Chave <online@chave.us>
Cc: ~alpine/apk-tools@lists.alpinelinux.org
Subject: Re: APK Package Name Issue on armel port
Message-ID: <20200214105215.6873e402@vostro.wlan>
In-Reply-To: <CAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug@mail.gmail.com>
References: <CAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 13 Feb 2020 22:55:37 -0500
Carl Chave <online@chave.us> wrote:

> 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)

This sounds weird. What is apk-tools version, and Alpine branch (edge
or some stable)?

> apk update seems to be aware of all the packages:
> m300-01:/home/sodface# apk update
> OK: 317 distinct packages available

This indicates that no remote repositories are configured, and the
package count is pretty low. Perhaps you are missing some repositories
from etc/apk/repositories config?

> 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.

Yeah, sounds like you are missing repositories.

Timo