public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: [PATCH v4 0/6] Fixes usage of additional apt keys and repos
Date: Thu,  7 Mar 2019 15:22:58 +0100	[thread overview]
Message-ID: <20190307142304.14508-1-andreas.reichel.ext@siemens.com> (raw)

From: Andreas Reichel <andreas.reichel.ext@siemens.com>

Diff to v3:
	* Remove apt-get update in target root file systems,
	  and use the isar-apt again as the only apt source, to support
	  consistent target root file systems without intermediate
	  updates.
	* Add the keyring in the right place (isar-bootstrap function
	  in isar-bootstrap.inc, which needs Claudius' flock patch
	  to fix the reversed double-ticks usage, which breaks
	  everything
	* only add gnupg if we add apt-keys
	* better commit message for revert commit
	* include Claudius' patch to make it clear that it should
	  be merged before
	* isar keyring file is specified in bitbake.conf, where
	  it should be to be available to all image generation
	  steps

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.

The patch of Claudius is included here because it is not yet merged
but required (fix of awful flock usage).

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

Claudius Heine (1):
  meta: refactored flock usage

 .../conf/multiconfig/qemuamd64-buster.conf    |  1 -
 .../conf/multiconfig/qemuamd64-jessie.conf    |  1 -
 meta/classes/buildchroot.bbclass              |  6 +-
 meta/classes/isar-bootstrap-helper.bbclass    |  2 +
 meta/classes/isar-image.bbclass               |  1 +
 meta/classes/wic-img.bbclass                  |  6 +-
 meta/conf/bitbake.conf                        |  1 +
 .../isar-bootstrap/isar-bootstrap.inc         | 76 +++++++++++++------
 8 files changed, 65 insertions(+), 29 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-03-07 14:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:22 Andreas J. Reichel [this message]
2019-03-07 14:22 ` [PATCH v4 1/6] meta: refactored flock usage Andreas J. Reichel
2019-03-07 14:23 ` [PATCH v4 2/6] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-07 14:23 ` [PATCH v4 3/6] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-07 14:46   ` Henning Schild
2019-03-18 10:14     ` Andreas Reichel
2019-03-07 14:23 ` [PATCH v4 4/6] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-07 14:23 ` [PATCH v4 5/6] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-07 14:51   ` Henning Schild
2019-03-18 12:57     ` Andreas Reichel
2019-03-07 14:58   ` Claudius Heine
2019-03-18 10:21     ` Andreas Reichel
2019-03-18 11:48       ` Claudius Heine
2019-03-18 11:49         ` Andreas Reichel
2019-03-18 11:53         ` Andreas Reichel
2019-03-07 14:23 ` [PATCH v4 6/6] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-07 14:54   ` Henning Schild
2019-03-18 10:09     ` 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=20190307142304.14508-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