From: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: [PATCH v3 0/6] Fixes usage of additional apt keys and repos
Date: Wed, 6 Mar 2019 17:26:12 +0100 [thread overview]
Message-ID: <20190306162619.826-1-andreas.reichel.ext@siemens.com> (raw)
From: Andreas Reichel <andreas.reichel.ext@siemens.com>
Diff to v2:
* split patches in a clean way:
* only install https-support and ca-certificates if
we have provided a custom apt-key
(see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891009)
- use the existing override mechanism for this
* first improve existing isar code before adding my own
* don't include "tmp/" inside of $kfn
What this series does:
Enable the user to really ADD bootstrap repos and keys without
replacing existing ones.
The existing keyring is not replaced but keys are added to
/ect/apt/trusted.gpg.d/isar.gpg instead, where debootstrap and any apt
call can find it.
Furthermore, the code to add keys is simplified by removing duplicate
code and not manually parsing URIs and guessing about download locations
as well as not manually handling gpg and giving apt config overrides.
It is much simpler by using `apt-key` and default apt keyring paths.
Furthermore, apt-get must not use a given single source list which was
used from debootstrapping. Otherwise, additional packages are always
unauthenticated, which is a quite misleading error. Instead, apt-get
should use all source lists available in the built root.
Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
Andreas Reichel (6):
Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS"
Remove duplicate code from apt-keyring generation
Fix key filename in apt-keyring generator
Use apt-key to generate apt-keyring
Use all source lists in target root apt
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 | 17 +++++--
meta/classes/isar-image.bbclass | 1 +
.../isar-bootstrap/isar-bootstrap-host.bb | 2 +-
.../isar-bootstrap/isar-bootstrap.inc | 49 +++++++++++--------
6 files changed, 43 insertions(+), 28 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-06 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 16:26 Andreas J. Reichel [this message]
2019-03-06 16:26 ` [PATCH v3 1/6] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-06 17:18 ` Henning Schild
2019-03-07 9:15 ` Andreas Reichel
2019-03-06 16:26 ` [PATCH v3 2/6] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-06 16:26 ` [PATCH v3 3/6] Fix key filename in apt-keyring generator Andreas J. Reichel
2019-03-06 16:26 ` [PATCH v3 4/6] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-06 17:33 ` Henning Schild
2019-03-07 9:06 ` Andreas Reichel
2019-03-07 13:43 ` Henning Schild
2019-03-06 16:26 ` [PATCH v3 5/6] Use all source lists in target root apt Andreas J. Reichel
2019-03-06 17:27 ` Henning Schild
2019-03-07 9:36 ` Claudius Heine
2019-03-06 16:26 ` [PATCH v3 6/6] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-06 17:43 ` Henning Schild
2019-03-07 9:14 ` Andreas Reichel
2019-03-07 13:41 ` Henning Schild
2019-03-07 14:41 ` Henning Schild
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=20190306162619.826-1-andreas.reichel.ext@siemens.com \
--to=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/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