public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v5] dpkg: Restore support for replacing pre-installed packages in sbuild-chroot
Date: Thu, 18 Jan 2024 09:28:28 +0300	[thread overview]
Message-ID: <028f69ac16ec3769875a03d6ec5d062271e3752c.camel@ilbers.de> (raw)
In-Reply-To: <a8fd25cf-b4d3-4d0b-8e2b-fd5de8d0c200@siemens.com>

On Tue, 2024-01-16 at 09:22 +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> During the migration to sbuild, support for using self-built packages
> in
> the build environment was lost if those were already part of the
> sbuild-chroot. This restores it by adding --apt-distupgrade to the
> sbuild call. But that is not enough because sbuild will only upgrade
> packages from already configured sources, not those specified via
> --extra-repository. We therefore have to switch back to configuring
> isar-apt during sbuild-chroot creation.
> 
> As rootfs_configure_isar_apt configures the isar repo under
> /isar-apt, we bind-mount the one in /home/builder/${PN} to that
> folder.
> Another difference is that we now need to run apt-get update
> explicitly,
> but only for isar-apt.
> 
> And because the sbuild-chroots are now left behind with isar-apt
> configured, the configuration in imager_run can be removed (credits
> to
> Srinuvasan Arjunan).
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Changes in v5:
>  - also use dpkg_schroot_create_configs for apt_fetch and apt_unpack
>    (while I wasn't able to reproduce the issue, I think this should
>    resolve the CI problems)
> 

Unfortunately, the picture in full CI didn't change. Even worse, one
more job (NoCrossTest.test_nocross has failed with the similar error.

tmp/work/debian-bullseye-amd64/hello/1.0-
r0/temp/log.do_apt_unpack.1785250:
```
DEBUG: Executing shell function do_apt_unpack
cp: cannot stat '/downloads/deb-src/debian-bullseye/hello/hello_2.10-
2+isar.debian.tar.xz': No such file or directory
cp: cannot stat '/downloads/deb-src/debian-bullseye/hello/hello_2.10-
2+isar.dsc': No such file or directory
```

I'm continuing debugging the issue.

  reply	other threads:[~2024-01-18  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  8:22 Jan Kiszka
2024-01-18  6:28 ` Uladzimir Bely [this message]
2024-01-18  6:34   ` Uladzimir Bely
2024-01-18  6:59     ` Jan Kiszka
2024-01-18  7:39       ` Uladzimir Bely
2024-01-18  7:54         ` Jan Kiszka
2024-01-18 10:28         ` Jan Kiszka

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=028f69ac16ec3769875a03d6ec5d062271e3752c.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --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