public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] buildchroot: allow unauthenticated sources when installing dependencies
Date: Mon, 5 Feb 2018 08:02:40 +0100	[thread overview]
Message-ID: <a86f4d0c-d2e1-6f28-3c8d-0192952c0008@siemens.com> (raw)
In-Reply-To: <7087B498BB31B32A.276abe84-d62a-44b2-a65b-abc241cae647@mail.outlook.com>

On 2018-02-04 16:42, Hombourger, Cedric wrote:
> Hi Jan,
> 
> Do you have any build deps pulling from the unauthenticated repo? There
> are no issues with packages to be installed into the image (or
> buildchroot when pulled explicitly) ; only with dependencies
> 

Yes, I do (jailhouse kernel driver depending on custom kernel-headers).
The difference is that I have Alex' "build.sh: Force 'yes' for apt"
patch applied.

Please make sure to check the list for pending patching and clarify in
the cover letter e.g. how yours relate to them. Also your reproducible
build series seems to have some overlap.

Thanks,
Jan

> 
> 
> On Sun, Feb 4, 2018 at 1:04 PM +0100, "Jan Kiszka"
> <jan.kiszka@siemens.com <mailto:jan.kiszka@siemens.com>> wrote:
> 
>     On 2018-02-04 10:40, Cedric_Hombourger@mentor.com wrote:
>     > From: Cedric Hombourger > > While multistrap would accept unauthenticated sources (with a
>     warning), > mk-build-deps (called while building custom packages)
>     would not. > Strangely, I was already doing that successfully,
>     without the change below. Jan > Signed-off-by: Cedric Hombourger >
>     --- > meta/recipes-devtools/buildchroot/files/build.sh | 3 +++ > 1
>     file changed, 3 insertions(+) > > diff --git
>     a/meta/recipes-devtools/buildchroot/files/build.sh
>     b/meta/recipes-devtools/buildchroot/files/build.sh > index
>     760ebc8..b6075b3 100644 > ---
>     a/meta/recipes-devtools/buildchroot/files/build.sh > +++
>     b/meta/recipes-devtools/buildchroot/files/build.sh > @@ -9,6 +9,9 @@
>     cd $1 > # Install command to be used by mk-build-deps >
>     install_cmd="apt-get -o Debug::pkgProblemResolver=yes
>     --no-install-recommends -y" > > +# Allow unauthenticated feeds >
>     +install_cmd="${install_cmd} --allow-unauthenticated" > + > #
>     Install all build deps > mk-build-deps -t "${install_cmd}" -i -r
>     debian/control > > -- Siemens AG, Corporate Technology, CT RDA IOT
>     SES-DE Corporate Competence Center Embedded Linux
> 


-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2018-02-05  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  9:40 [PATCH 0/1] buildchroot: allow unauthenticated sources for mk-build-deps Cedric_Hombourger
2018-02-04  9:40 ` [PATCH 1/1] buildchroot: allow unauthenticated sources when installing dependencies Cedric_Hombourger
2018-02-04 12:04   ` Jan Kiszka
2018-02-04 15:42     ` Hombourger, Cedric
2018-02-05  7:02       ` Jan Kiszka [this message]

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=a86f4d0c-d2e1-6f28-3c8d-0192952c0008@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Cedric_Hombourger@mentor.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