Re: [PATCH] sbuild: Don't update apt database on every package build

[Jan Kiszka <jan.kiszka@siemens.com>]

On 26.10.22 09:06, Uladzimir Bely wrote:
> In mail from вторник, 25 октября 2022 г. 16:37:51 +03 user Jan Kiszka wrote:
>> On 25.10.22 11:00, Uladzimir Bely wrote:
>>> In mail from понедельник, 24 октября 2022 г. 17:14:52 +03 user Jan Kiszka
>>>
>>> wrote:
>>>> On 24.10.22 15:10, Uladzimir Bely wrote:
>>>>> By default, sbuild updates apt database beforethe build. It may cause
>>>>> an inconsistency between apt databases for different packages built at
>>>>> the different time if external (Debian) mirrors has updated recently.
>>>>>
>>>>> With new changes, sbuild will rely on global apt state that was got
>>>>> during debootstrap stage.
>>>>>
>>>>> Local `isar-apt` repo will still be automatically updated while it is
>>>>> passed via `--extra-repository=` argument.
>>>>
>>>> Will that also ensure upgrades, e.g. from essential debian packages to
>>>> self-built ones hosted in isar-apt? We had a few of such cases in the
>>>> past already in downstream layers, and I recall permitting upgrades to
>>>> the old buildchroot for that.
>>>
>>> I'm afraid I don't exactly get you question...
>>>
>>> Do you mean, it may happen that Isay may update 'isar-apt' repository, but
>>> won't even try to install "newer" (custom) package from isar-apt as an
>>> upgrade of some Debian package installed at debootstrap stage?
>>
>> Actually, part of my former problems were downgrades, not upgrades, see
>> [1] and [2]. Those are possible as well because anything coming from
>> isar-apt has higher prior than other repo. Now I was only wondering if
>> that behavior is still given, with all those switches applied and
>> schroot in between us and the actual apt calls.
> 
> It seems sbuild man pages say nothing about "--allow-downgrades". So, I'm not 
> sure if it's used.
> 
> Anyway, now I guess that setting `--no-apt-upgrade` and `--no-apt-distupgrade` 
> in the v1 of patch is wrong. Most probably, such configuration won't allow 
> even upgrades from debian packages to isar-apt ones.
> 
> Also, you are saying, "isar-apt has higher prior than other repo". Where is it 
> configured? I thought, `isar-apt` is just one of sources from "apt" and if 
> Debian has newer package version than we compiled by hand, these newer 
> dependencies are to be installed...

https://github.com/ilbers/isar/blob/18db2a59f22ec3c376a1518627250d14683338fa/meta/classes/rootfs.bbclass#L93

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux