public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v3 2/3] sbuild: Set high prio for the packages from isar-apt repo
Date: Mon, 31 Oct 2022 07:06:43 +0100	[thread overview]
Message-ID: <20221031060644.20150-3-ubely@ilbers.de> (raw)
In-Reply-To: <20221031060644.20150-1-ubely@ilbers.de>

This sets high priority for `isar-apt` repo during sbuild session.
So, even if some dependency in other repos has higher version than
one we previously built and placed in isar-apt, the second one wil
be selected.

This repeats the behaviour that is implemented in rootfs.bbclass
via `rootfs_configure_isar_apt` that is disabled for sbuild chroot.

We can't simply enable this task for sbuild while we don't want to
have `/etc/apt/sources.list.d/isar-apt.list` file in sbuild chroot
while it's handled via sbuild by `--extra-repository` option

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/classes/dpkg.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index dfa097f8..c7e7dd34 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -91,6 +91,7 @@ dpkg_runbuild() {
         --host=${PACKAGE_ARCH} --build=${SBUILD_HOST_ARCH} ${profiles} \
         --no-run-lintian --no-run-piuparts --no-run-autopkgtest --resolve-alternatives \
         --no-apt-update \
+        --chroot-setup-commands="echo \"Package: *\nPin: release n=${DEBDISTRONAME}\nPin-Priority: 1000\" > /etc/apt/preferences.d/isar-apt" \
         --chroot-setup-commands="rm -f /var/log/dpkg.log" \
         --chroot-setup-commands="cp -n --no-preserve=owner ${ext_deb_dir}/*.deb -t ${deb_dir}/ || :" \
         --finished-build-commands="rm -f ${deb_dir}/sbuild-build-depends-main-dummy_*.deb" \
-- 
2.20.1


  parent reply	other threads:[~2022-10-31  6:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  6:06 [PATCH v3 0/3] Don't update apt database on every package build Uladzimir Bely
2022-10-31  6:06 ` [PATCH v3 1/3] sbuild: " Uladzimir Bely
2022-10-31  6:06 ` Uladzimir Bely [this message]
2023-01-11 14:36   ` [PATCH v3 2/3] sbuild: Set high prio for the packages from isar-apt repo Jan Kiszka
2023-01-11 14:52     ` Jan Kiszka
2023-01-11 17:34       ` Jan Kiszka
2023-01-12  7:46         ` Uladzimir Bely
2022-10-31  6:06 ` [PATCH v3 3/3] sbuild: Allow downgrades when installing dependencies Uladzimir Bely
2022-11-15  7:49 ` [PATCH v3 0/3] Don't update apt database on every package build 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=20221031060644.20150-3-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --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