X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by lists.alpinelinux.org (Postfix) with ESMTP id 1A0DAF84D71 for ; Mon, 18 Mar 2019 01:27:06 +0000 (UTC) Received: by mail-pg1-f182.google.com with SMTP id h34so10190962pgh.11 for ; Sun, 17 Mar 2019 18:27:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chave-us.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ydl0Q5/fS6blfeYmH3ZYm3ps3lbVdD0n3/QCfnnIOlg=; b=hvPOOFaTwK0rJwK/kSZOvXmA6DJhV67XSpsgnoH8O7lBTlvScXhSchgIt4Rpn8RTv6 hKjhm3nEVbCblcKPyUaBi5FTEYi/dbpW9SBCbQ2w196TeqjNqZIlw2CZF4D9AjwXr8ku e9HS05FmkdYCNDC3uSqQwXgLoOJwVQTMHtOYXRi/V2p4mMIL1s42jAzx3rVHb3klRW25 F7dJ91b05yrBbtoZixofAoud1oem033TSb42LfRxGlBUOxrBViucggR0HDGcVlevGWSZ YRttJyl0RUG4SWEIyMLQXo1MDXQKmGnQE6IgBgij9K80lzgfrkjA12yMFq5nroCxOxYv 6sJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ydl0Q5/fS6blfeYmH3ZYm3ps3lbVdD0n3/QCfnnIOlg=; b=Z5tUAuvKUvMpS9oAnSDEw2Jil5Ge3bE6BA8yyamSHpN9wvURopjdAar+mITvL0cb/8 rPcGf6TBnY5gWz2czcU4x0l0OgT1CXi0yIy5Z72XvFE3ygFb+LRWlyP04SL9n6QJMQmq 1Ef5GdIr5daq5LdRmbX+RkM/m7U7k7uzIiFmK6JcOlRrr36Xp1Yl8X99NrB2lS0DML/c vSOGy4V3rdbZMTBZ4HVvD/ZGhMBxyzfrfoNdYiVJ+YcCrTHFsXabiA4XbEq7uceyZXiJ ubUlv4tbuZfTXZm3aCO4YVxihvMUFSvciu1oYkKB88/rcLpmkYfvHN7Db/emgJgbHKas 4doA== X-Gm-Message-State: APjAAAWJtlkpqXATumZoiv4tG0vwmXI8h5cFmQzYa9VPEbOSrodd4WYh TFsJ+H2PF8QTGjHi/xIBkfIwZOxyZPvecIy9aSGJbkpx X-Google-Smtp-Source: APXvYqyLA2yvhV+SH7ahg/0LzFHrnt05XRY/G+W6kbNUOHTC2K3u7GjgJmZpVtXsmbLF/O6c+bYgIBMxrIXYcU7cOus= X-Received: by 2002:a63:6e4c:: with SMTP id j73mr8406016pgc.276.1552872425276; Sun, 17 Mar 2019 18:27:05 -0700 (PDT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 References: In-Reply-To: From: Carl Chave Date: Sun, 17 Mar 2019 21:26:54 -0400 Message-ID: Subject: [alpine-devel] Re: Adding Local Abuild Package to Cache To: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="0000000000004a5b03058454492c" --0000000000004a5b03058454492c Content-Type: text/plain; charset="UTF-8" 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 reboot. --0000000000004a5b03058454492c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Sun, Mar 17, 2019 at 2:31 PM Carl Chave <carl@chave.us> wrote:

On Sun, Mar 17, 2019 at 10:52 AM Ca= rl Chave <carl@chave.= us> 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.=C2=A0 I added the ~/packages/t= esting repo to /etc/apk/repositories and I can apk add the packages and pul= l in dependencies successfully like a package in the official repos.
<= div>
I've tested that the application works and that the = /etc/init.d scripts will start and stop the service also.=C2=A0 The applica= tion name is added to /etc/apk/world but the packages are not added to the = local cache and not automatically loaded on reboot.=C2=A0 I have to add the= m manually again.=C2=A0 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 remo= ved from the cache.

I suspect this has something t= o do with signing and trust perhaps, though the abuild -r process signed th= e 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= !=C2=A0 Thanks,
Carl

<= div>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?=C2=A0 I deleted the= package from /etc/apk/world, deleted the local repo from /etc/apk/reposito= ries and then ran apk cache clean.=C2=A0 I then cd'd into the local pac= kages directory and installed with apk add --allow-untrusted and they were = added to the cache and were installed on reboot.=C2=A0
--0000000000004a5b03058454492c-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---