public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] dpkg-base: Remove newly deployed debs from buildchroots
Date: Mon, 24 Aug 2020 09:16:47 +0200	[thread overview]
Message-ID: <da12c272-d901-8ba5-b8c3-91707c01eb5e@siemens.com> (raw)
In-Reply-To: <20200823160636.GA11779@yssyq.m.ilbers.de>

On 23.08.20 18:06, Baurzhan Ismagulov wrote:
> Hello Jan,
> 
> On Tue, Aug 11, 2020 at 09:05:59AM +0200, Jan Kiszka wrote:
>> This ensures clean reinstallation after partial rebuilds.
>>
>> A typical error pattern so far was that firmware packages pulled by the
>> buildchroot-target were not updated there on rebuilds, causing the old
>> firmware being deployed into the image.
> 
> With this applied, we encounter random build failures downstream, e.g.:
> 
> 1. ERROR: mc:pixi-cdl100-buster:desktop-shortcuts-1.0-r0 do_install_builddeps: Execution of 'build/tmp/work/debian-buster-armhf/desktop-shortcuts/1.0-r0/temp/run.do_install_builddeps.19582' failed with exit code 1:
>    mk-build-deps: You must have equivs installed to use this program.
>    WARNING: exit code 1 from a shell command.
> 
> 2. Exception: bb.process.ExecutionError: Execution of 'build/tmp/work/debian-buster-armhf/desktop-shortcuts/1.0-r0/temp/run.dpkg_runbuild.16998' failed with exit code 2:
>    dpkg-buildpackage: info: source package desktop-shortcuts
>    dpkg-buildpackage: info: source version 1.0
>    dpkg-buildpackage: info: source distribution UNRELEASED
>    dpkg-buildpackage: info: source changed by isar-users <isar-users@googlegroups.com>
>    dpkg-architecture: warning: specified GNU system type arm-linux-gnueabihf does not match CC system type x86_64-linux-gnu, try setting a correct CC environment variable
>     dpkg-source -I --before-build .
>    dpkg-buildpackage: info: host architecture armhf
>     fakeroot debian/rules clean
>    dh clean
>    make: dh: Command not found
> 
> Seems we have a race, possibly related to removing packages. What I don't
> understand is how it could affect equivs or debhelper -- we don't do anything
> with them. Ideas?

Which packages are you (re-)building? Debian packages? Or just custom
dependencies of that desktop-shortcuts package?

In theory, do_deploy_deb should be locked against do_install_builddeps.
Anything that the latter needs should be available after the former.
Maybe you are missing a build dependency in desktop-shortcuts? Try build
that only over a clean buildchroot, that will tell you.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2020-08-24  7:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  7:05 Jan Kiszka
2020-08-11  7:47 ` Harald Seiler
2020-08-17 12:50 ` Henning Schild
2020-08-17 15:38   ` Jan Kiszka
2020-08-17 17:21     ` Henning Schild
2020-08-18  5:53       ` Jan Kiszka
2020-08-17 19:27 ` Baurzhan Ismagulov
2020-08-18  5:57   ` Jan Kiszka
2020-08-23 16:30     ` Baurzhan Ismagulov
2020-08-24  7:17       ` Jan Kiszka
2020-08-23 16:06 ` Baurzhan Ismagulov
2020-08-24  7:16   ` Jan Kiszka [this message]
2020-09-21 19:17     ` Jan Kiszka
2020-10-28 13:39       ` Kanagarajan, Vijaikumar
2020-10-28 13:52         ` Jan Kiszka
2020-10-28 14:20           ` Kanagarajan, Vijaikumar

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=da12c272-d901-8ba5-b8c3-91707c01eb5e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --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