From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: apt/preferences broken in sbuild-chroot
Date: Wed, 11 Jan 2023 10:39:57 +0100 [thread overview]
Message-ID: <53128bd8-8374-d307-8df3-aab8530d6f3e@siemens.com> (raw)
In-Reply-To: <4537384d-c014-381c-10ca-946a00a342b7@siemens.com>
On 11.01.23 10:30, Jan Kiszka wrote:
> Hi all,
>
> just noticed that the preferences are broken in our build env (current
> isar next), failing to prefer isar-apt over the rest:
>
> (isar-builder-a1d3aa19-9a79-4215-81db-e13b5c1ea3c4-23867)root@a027a964728d:/home/builder/hello-isar/hello-isar-0.3-a18c14c#
> cat /etc/apt/preferences.d/bootstrap
> (isar-builder-a1d3aa19-9a79-4215-81db-e13b5c1ea3c4-23867)root@a027a964728d:/home/builder/hello-isar/hello-isar-0.3-a18c14c#
>
..and there was no /etc/apt/preferences.d/isar-apt. That was obviously
in the devshell. Just noticed that this isar-apt file is only injected
in dpkg_runbuild, not for the devshell.
Still, I'm seeing build setup errors here as well, very likely because
of that pref not working as it should. Examining.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-01-11 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 9:30 Jan Kiszka
2023-01-11 9:39 ` 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=53128bd8-8374-d307-8df3-aab8530d6f3e@siemens.com \
--to=jan.kiszka@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