public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Is schroot updating external apt databases?
Date: Mon, 24 Oct 2022 10:18:30 +0200	[thread overview]
Message-ID: <Y1ZKVi4sfJX6n6Bx@ilbers.de> (raw)
In-Reply-To: <2078393.9o76ZdvQCi@hp>

On Mon, Oct 24, 2022 at 11:07:15AM +0300, Uladzimir Bely wrote:
> > Are we pulling newer packages from Debian here? This should not
> > happen, obviously. What is done to prevent this?
> 
> Yes, sbuild by default updates all the sources before package building.
> 
> It has options like `--(no-)apt-update`, `--(no-)apt-upgrade` and `--(no-)apt-
> distupgrade` and corresponding config options to tune the behaviour.
> 
> We most probably should use them, but, at the same time, still somehow update 
> 'isar-apt' part. For example, in `--chroot-setup-commands` stage

We needed this to pull locally built dependencies like libhello. Seems like a
regression, we'll check.

With kind regards,
Baurzhan

      reply	other threads:[~2022-10-24  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  6:26 Jan Kiszka
2022-10-24  8:07 ` Uladzimir Bely
2022-10-24  8:18   ` Baurzhan Ismagulov [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=Y1ZKVi4sfJX6n6Bx@ilbers.de \
    --to=ibr@radix50.net \
    --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