Mail archive

[alpine-devel] Re: Adding Local Abuild Package to Cache

From: Carl Chave <>
Date: Sun, 17 Mar 2019 21:26:54 -0400

On Sun, Mar 17, 2019 at 2:31 PM Carl Chave <> wrote:

> On Sun, Mar 17, 2019 at 10:52 AM Carl Chave <> wrote:
>> Hello,
>> I followed the wiki to abuild a package that was not in any of the repos,
>> which resulted in a main package, and -openrc and -doc packages. I added
>> the ~/packages/testing repo to /etc/apk/repositories and I can apk add the
>> packages and pull in dependencies successfully like a package in the
>> official repos.
>> I've tested that the application works and that the /etc/init.d scripts
>> will start and stop the service also. The application name is added to
>> /etc/apk/world but the packages are not added to the local cache and not
>> automatically loaded on reboot. I have to add them manually again. If I
>> manually copy the packages to cache and reboot, they still don't load and
>> when I run an apk cache clean they get removed from the cache.
>> I suspect this has something to do with signing and trust perhaps, though
>> the abuild -r process signed the APKINDEX file in the local package repo
>> and I added my public key to /etc/apk/keys.
>> Please let me know what I'm missing! Thanks,
>> Carl
> I should add that this is the 3.9.2 armv7 image on the Raspberry Pi 3 B+
> and I'm doing an lbu commit -d prior to rebooting.

Disregard I guess? I deleted the package from /etc/apk/world, deleted the
local repo from /etc/apk/repositories and then ran apk cache clean. I then
cd'd into the local packages directory and installed with apk add
--allow-untrusted and they were added to the cache and were installed on

Received on Sun Mar 17 2019 - 21:26:54 UTC