public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Andreas Reichel <andreas.reichel.ext@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 1/3] Fix and simplify apt keyring generation
Date: Fri, 1 Mar 2019 11:11:47 +0100	[thread overview]
Message-ID: <20190301111147.29051eb0@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190301091650.GA13010@iiotirae>

Am Fri, 1 Mar 2019 10:16:50 +0100
schrieb Andreas Reichel <andreas.reichel.ext@siemens.com>:

> On Wed, Feb 27, 2019 at 05:12:42PM +0100, Henning Schild wrote:
> > Am Wed, 27 Feb 2019 16:18:54 +0100
> > schrieb "[ext] Andreas J. Reichel"
> > <andreas.reichel.ext@siemens.com>: 
> > > From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> > > 
> > > +
> > > +    if [ -d ${TMPDIR}/aptkeys ]; then
> > > +        for keyfile in ${TMPDIR}/aptkeys/*
> > > +        do
> > > +            kfn="tmp/$(basename $keyfile)"
> > > +            cp $keyfile "$ROOTFSDIR/$kfn"
> > > +            sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-key add
> > > "/$kfn"  
> > 
> > Would probably be a good idea to work in /tmp/ as well and in a
> > subdir. Try naming your key "root" or "usr" ...
> >   
> I AM working in /tmp/, ... a subdir is not needed since we directly
> work with the file names.
> This is not " a key ", these are arbitrarily many keys and the name of
> the key files don't change between the host, the build and target
> chroots.

I see the "tmp/" is in $kfn, might be more readable to have in the the
cp and apt-key.

Henning

> Andreas
> 


  reply	other threads:[~2019-03-01 10:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 15:18 [PATCH v2 0/3] Fixes usage of additional apt keys 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 [this message]
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 ` [PATCH v2 0/3] Fixes usage of additional apt keys Henning Schild
2019-03-01  9:17   ` 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=20190301111147.29051eb0@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