From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v6 0/5] Fix usage of additional apt keys and repos
Date: Tue, 19 Mar 2019 12:42:15 +0100 [thread overview]
Message-ID: <20190319114215.GA13118@iiotirae> (raw)
In-Reply-To: <a402e80e-bb91-9ff2-2461-502544b353c9@ilbers.de>
On Tue, Mar 19, 2019 at 12:34:11PM +0100, Maxim Yu. Osipov wrote:
> Hi Andreas,
>
> I've tried this series with apt repo caching feature - see
> https://github.com/ilbers/isar/blob/next/doc/user_manual.md#creation-of-local-apt-repo-caching-upstream-debian-packages.
>
> "fast" CI build doesn't test this feature by default.
>
> I've just launched
>
> 'bitbake -c cache_base_repo multiconfig:qemuamd64-stretch:isar-image-base'
>
> <snip>
>
> and got the error:
>
> Log data follows:
> | DEBUG: Executing shell function do_build
> | Get:1 file:/isar-apt isar InRelease
> | Ign:1 file:/isar-apt isar InRelease
> | Get:2 file:/isar-apt isar Release [3554 B]
> | Get:2 file:/isar-apt isar Release [3554 B]
> | Get:3 file:/isar-apt isar Release.gpg
> | Ign:3 file:/isar-apt isar Release.gpg
> | Reading package lists...
> | E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them
> is required for this operation
> | WARNING: exit code 255 from a shell command.
> | ERROR: Function failed: do_build (log file is located at /home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-amd64/buildchroot-target/temp/log.do_build.7187)
>
I also see this on the Siemens runner now... investigating... :(
> Regards,
> Maxim.
>
>
> On 3/19/19 11:28 AM, Andreas J. Reichel wrote:
> > From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> >
> > Diff to v5: Don't use glob star to get keyfiles, use find
> >
> > Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
> >
> > Andreas Reichel (5):
> > Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS"
> > Remove duplicate code from apt-keyring generation
> > Fix fetched key location in apt-keyring generator
> > Use apt-key to generate apt-keyring
> > If we use a custom keyring debootstrap may fall to https
> >
> > .../conf/multiconfig/qemuamd64-buster.conf | 1 -
> > .../conf/multiconfig/qemuamd64-jessie.conf | 1 -
> > meta/classes/isar-bootstrap-helper.bbclass | 2 +
> > meta/conf/bitbake.conf | 1 +
> > .../isar-bootstrap/isar-bootstrap.inc | 62 +++++++++++++------
> > 5 files changed, 47 insertions(+), 20 deletions(-)
> >
>
>
> --
> Maxim Osipov
> ilbers GmbH
> Maria-Merian-Str. 8
> 85521 Ottobrunn
> Germany
> +49 (151) 6517 6917
> mosipov@ilbers.de
> http://ilbers.de/
> Commercial register Munich, HRB 214197
> General Manager: Baurzhan Ismagulov
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
Andreas.Reichel@tngtech.com, +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
prev parent reply other threads:[~2019-03-19 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 10:28 Andreas J. Reichel
2019-03-19 10:28 ` [PATCH v6 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-19 10:28 ` [PATCH v6 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-19 10:28 ` [PATCH v6 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-19 10:28 ` [PATCH v6 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-19 10:28 ` [PATCH v6 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-19 11:34 ` [PATCH v6 0/5] Fix usage of additional apt keys and repos Maxim Yu. Osipov
2019-03-19 11:42 ` Andreas Reichel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190319114215.GA13118@iiotirae \
--to=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox