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 0/3] Don't update apt database on every package build
Date: Mon, 31 Oct 2022 07:06:41 +0100	[thread overview]
Message-ID: <20221031060644.20150-1-ubely@ilbers.de> (raw)

Here we want to avoid the default behaviour of sbuild when it tries
to update all apt sources.

To have package database consistent, we should rely on one we got
during the debootstrap. The only repo that really needs updates
is local `isar-apt` where custom build depends may be placed.

Also, `isar-apt` should have the high priority over other sources
and allow downgrades (like it was done earlier for buildchroot).

Changes since v2:
 - Allow downgrades when installing package dependencies

Changes since v1:
 - Disable only `apt update`, but leave `apt distupgrade` unchanged
(enabled by default). This allows package upgrades from isar-apt repo.
 - Added a patch that sets high priority for isar-apt.

Uladzimir Bely (3):
  sbuild: Don't update apt database on every package build
  sbuild: Set high prio for the packages from isar-apt repo
  sbuild: Allow downgrades when installing dependencies

 meta/classes/dpkg.bbclass | 3 +++
 1 file changed, 3 insertions(+)

-- 
2.20.1


             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 Uladzimir Bely [this message]
2022-10-31  6:06 ` [PATCH v3 1/3] sbuild: " Uladzimir Bely
2022-10-31  6:06 ` [PATCH v3 2/3] sbuild: Set high prio for the packages from isar-apt repo Uladzimir Bely
2023-01-11 14:36   ` 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-1-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