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



On Sun, Feb 4, 2018 at 1:04 PM +0100, "Jan Kiszka" <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