public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/3] Fixes usage of additional apt keys
Date: Wed, 27 Feb 2019 17:15:56 +0100	[thread overview]
Message-ID: <20190227171556.53293b32@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190227151856.11594-1-andreas.reichel.ext@siemens.com>

Could you send a list of changes next time, or reply to the reviews.

Otherwise there is no way to tell what you did in response to the
review, which comments you skipped etc.

Henning

Am Wed, 27 Feb 2019 16:18:53 +0100
schrieb "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>:

> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> 
> If the user does not want to replace the bootstrap source together
> with the key, additional keys did not work.
> 
> This is solved by not replacing the keyring but to add keys to
> /ect/apt/trusted.gpg.d/isar.gpg, where debootstrap and any apt call
> can find it.
> 
> Furthermore, the code to add keys is simplified a lot by 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 (3):
>   Fix and simplify apt keyring generation
>   Use all source lists in target root apt
>   Separate apt-key entries from default keyring
> 
>  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         | 39
> +++++++++---------- 4 files changed, 33 insertions(+), 26 deletions(-)
> 


  parent reply	other threads:[~2019-02-27 16:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 15:18 Andreas J. Reichel
2019-02-27 15:18 ` [PATCH v2 1/3] Fix and simplify apt keyring generation Andreas J. Reichel
2019-02-27 16:12   ` Henning Schild
2019-03-01  9:09     ` Andreas Reichel
2019-03-01 10:18       ` Henning Schild
2019-03-06 16:29         ` Andreas Reichel
2019-03-01  9:16     ` Andreas Reichel
2019-03-01 10:11       ` Henning Schild
2019-03-01 10:22     ` Henning Schild
2019-03-06 16:29       ` Andreas Reichel
2019-02-27 15:18 ` [PATCH v2 2/3] Use all source lists in target root apt Andreas J. Reichel
2019-02-27 15:18 ` [PATCH v2 3/3] Separate apt-key entries from default keyring Andreas J. Reichel
2019-02-27 16:14   ` Henning Schild
2019-03-01  9:08     ` Andreas Reichel
2019-02-27 16:15 ` Henning Schild [this message]
2019-03-01  9:17   ` [PATCH v2 0/3] Fixes usage of additional apt keys 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=20190227171556.53293b32@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=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