public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCHv3 8/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed
Date: Fri, 15 Nov 2019 07:07:18 +0100	[thread overview]
Message-ID: <20191115060717.hft22zhbunl5u4ek@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20191114224525.697987ee@md1za8fc.ad001.siemens.net>

On Thu, Nov 14, 2019 at 10:45:25PM +0100, Henning Schild wrote:
> The key problem is that ci_build.sh has too many knobs and does not
> test the repo build in all its beauty. In fact this fix should have
> come with a test that shows the problem it fixed in the first place.

Indeed, we only test "-r -s" after signing was implemented.


> So i guess my fix will come with another change that simplifies the
> build script and reduces the number of knobs. Maybe in the end just one,
> fast|full.

I support this as long as we don't lose tested configurations.


> Where full would do the offline build signed, unsigned, with other keys and
> without, and with+out any other variation i find on the way.

I think we could do that with one amd64 configuration, each in a separate build
directory, keeping the built artifacts.


With kind regards,
Baurzhan.

  reply	other threads:[~2019-11-15  6:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 18:55 [PATCHv3 0/9] a few cleanups a bug and a feature Henning Schild
2019-11-07 18:55 ` [PATCHv3 1/9] rootfs: fix incorrect feature name in comment Henning Schild
2019-11-07 18:55 ` [PATCHv3 2/9] base_apt_helper: change variable names to increase readability Henning Schild
2019-11-07 18:55 ` [PATCHv3 3/9] rootfs: rename ROOTFS_INSTALL_COMMAND lock to "isar-apt-lock" Henning Schild
2019-11-07 18:55 ` [PATCHv3 4/9] dpkg-base: remove pointless ";" s at end of line Henning Schild
2019-11-07 18:55 ` [PATCHv3 5/9] dpkg-base: fix indentation from tabs to spaces Henning Schild
2019-11-07 18:56 ` [PATCHv3 6/9] base: implement BB_NO_NETWORK for apt-get Henning Schild
2019-11-07 18:56 ` [PATCHv3 7/9] meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK Henning Schild
2019-11-07 18:56 ` [PATCHv3 8/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed Henning Schild
2019-11-14 20:11   ` Jan Kiszka
2019-11-14 21:45     ` Henning Schild
2019-11-15  6:07       ` Baurzhan Ismagulov [this message]
2019-11-07 18:56 ` [PATCHv3 9/9] meta: dpkg-gbp: remove unneeded proxy export Henning Schild
2019-11-12 16:39 ` [PATCHv3 0/9] a few cleanups a bug and a feature Baurzhan Ismagulov

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=20191115060717.hft22zhbunl5u4ek@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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