From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/5] Fix usage of additional apt keys and repos
Date: Tue, 19 Mar 2019 10:47:52 +0100 [thread overview]
Message-ID: <20190319094752.GA28015@iiotirae> (raw)
In-Reply-To: <3969feb6-c01a-d140-a30f-3755319c192f@ilbers.de>
On Mon, Mar 18, 2019 at 04:13:19PM +0100, Maxim Yu. Osipov wrote:
> Hi Andreas,
>
> I've applied your series and "fast" CI build (just call
> `./scripts/ci_build.sh -q -f' failed.
>
> See for details
> http://isar-build.org:8080/job/isar_mosipov_develop/61/console
>
> If you need an account on CI build server - just let me know.
>
Yes please.
Andreas
> Regards,
> Maxim.
>
>
>
> On 3/18/19 2:31 PM, Andreas J. Reichel wrote:
> > From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> >
> > Diff to v4:
> > * don't remove keyring deployed to target rootfs
> > so that one can do updates later
> > * keys are temporarily held in WORKDIR/aptkeys, not
> > TMPDIR/aptkeys
> > * variable renamed from APTKEYTMPDIR to APT_KEYS_DIR
> >
> > Unchanged with reason:
> > * function for retreiving override for https is unchanged,
> > since renaming this to one global function
> > "get_distro_overrides" is better done in a separate patch.
> > This patch should concentrate on getting things finally
> > working, before changing too much code that is more or less
> > a beautification.
> > * (Other comments on mailing list)
> > * HAVE_CUSTOM_APT_KEYS is used in patch 4, but introduced in
> > patch 5, which is okay here, because we check if it exists...
> >
> > What this series does:
> > * Enable/fix possibility of additional apt repos
> > * Enable/fix handling of additional apt keys
> > * Deduplicate some code
> >
> > 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
next prev parent reply other threads:[~2019-03-19 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 13:31 Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-18 13:47 ` [PATCH v5 0/5] Fix usage of additional apt keys and repos Claudius Heine
2019-03-18 15:13 ` Maxim Yu. Osipov
2019-03-19 9:47 ` Andreas Reichel [this message]
2019-03-19 10:16 ` Andreas Reichel
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=20190319094752.GA28015@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