public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v7 0/5] Fix usage of additional apt keys and repos
Date: Tue, 19 Mar 2019 22:58:19 +0100	[thread overview]
Message-ID: <ae4300b0-85cb-a7af-6e1a-feb9302b61db@ilbers.de> (raw)
In-Reply-To: <20190319133523.32456-1-andreas.reichel.ext@siemens.com>

Hi Andreas,

CI build ('scripts/ci_build.sh -q') failed. See
http://isar-build.org:8080/job/isar_mosipov_next/165/console

We may create project for you on isar-build.org so you can run CI build 
on isar-build.org before submitting patches to the mailing list.
We just need your github repo name (like
https://github.com/henning-schild-work/isar/)

Thanks,
Maxim.

On 3/19/19 2:35 PM, Andreas J. Reichel wrote:
> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> 
> Diff to v6: There was a call to 'apt-key update' that was always
> executed. But apt-key needs gnupg, which is only installed if we install
> apt-keys. Second, this call is deprecated anyway, so it does not make
> sense and we don't need it. Removed it.
> 
> Sorry for this.
> 
> 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/conf/bitbake.conf                        |  1 +
>   .../isar-bootstrap/isar-bootstrap.inc         | 62 +++++++++++++------
>   4 files changed, 45 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

  parent reply	other threads:[~2019-03-19 21:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 13:35 Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-19 13:36 ` [PATCH v7 0/5] Fix usage of additional apt keys and repos Andreas Reichel
2019-03-19 14:26   ` Maxim Yu. Osipov
2019-03-19 15:39     ` Andreas Reichel
2019-03-19 21:58 ` Maxim Yu. Osipov [this message]
2019-03-20  6:26   ` Jan Kiszka
2019-03-20  6:48     ` Maxim Yu. Osipov
2019-03-20  7:12       ` Jan Kiszka
2019-03-20  7:55         ` Maxim Yu. Osipov
2019-03-20  8:22           ` Jan Kiszka
2019-03-20  8:53             ` Maxim Yu. Osipov
2019-03-20 10:25           ` Andreas Reichel
2019-03-20 10:32             ` Maxim Yu. Osipov
2019-03-20 11:50               ` Andreas Reichel
2019-03-20 10:37             ` Jan Kiszka
2019-03-20 11:05               ` Maxim Yu. Osipov
2019-03-20 12:39                 ` Jan Kiszka
2019-03-20  7:16     ` Claudius Heine

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=ae4300b0-85cb-a7af-6e1a-feb9302b61db@ilbers.de \
    --to=mosipov@ilbers.de \
    --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