public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schild, Henning" <henning.schild@siemens.com>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: sbuild: use build-depends from backports
Date: Mon, 8 Aug 2022 08:17:09 +0000	[thread overview]
Message-ID: <AM9PR10MB48695E240C20071A19207BC589639@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Hi,

In ISAR v0.9 we were able to use build dependencies from the backports repository:


  1.  Add the backports repo to DISTRO_APT_SOURCES
  2.  Write an apt preferences file to prefer the backports package and add it to DISTRO_APT_PREFERENCES

This still works for runtime dependencies, but not for build dependencies.
The sbuilder simply does not attract the package from backports as they have "NotAutomatic: yes".

Maybe we could work around by using ` --build-dep-resolver="apt"`.
But then more questions arise:
- are the DISTRO_APT_SOURCES added as -external-repository? I don't think so
- when creating the base-schroot: Is the repo considered (and are DISTRO_APT_PREFERENCES active)
- are the DISTRO_APT_PREFERENCES files added to the schroot?

Help wanted.

Felix
--
Siemens AG, Linux Expert Center
Otto-Hahn-Ring 6, 81739 München, Germany


[-- Attachment #2: Type: text/html, Size: 4980 bytes --]

             reply	other threads:[~2022-08-08  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  8:17 Moessbauer, Felix [this message]
2022-08-09 17:45 ` Anton Mikanovich

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=AM9PR10MB48695E240C20071A19207BC589639@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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