public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Kanagarajan, Vijaikumar" <Vijaikumar_Kanagarajan@mentor.com>,
	isar-users <isar-users@googlegroups.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2] dpkg-base: Remove newly deployed debs from buildchroots
Date: Wed, 28 Oct 2020 14:52:26 +0100	[thread overview]
Message-ID: <03c83ddc-c901-1816-11d3-3552b9867495@siemens.com> (raw)
In-Reply-To: <390b8f4d4ad647fcb6dac505845d485b@svr-orw-mbx-01.mgc.mentorg.com>

On 28.10.20 14:39, Kanagarajan, Vijaikumar wrote:
> Hello Jan,
> 
> -----Original Message-----
> From: isar-users@googlegroups.com [mailto:isar-users@googlegroups.com] On Behalf Of Jan Kiszka
> Sent: 22 September 2020 00:48
> To: isar-users <isar-users@googlegroups.com>; Baurzhan Ismagulov <ibr@ilbers.de>
> Subject: Re: [PATCH v2] dpkg-base: Remove newly deployed debs from buildchroots
> 
> On 24.08.20 09:16, [ext] Jan Kiszka wrote:
>> 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?
> 
> I have a  similar condition now. We build openssl with a patch downstream. Looks like with this patch now, in our setup openssl is removed from buildchrootdir, which inturn removes
> devscripts(contains mk-build-deps). This causes other recipe builds to fail. Please see the log below.
> 

I've proposed
https://groups.google.com/d/msgid/isar-users/76603767-1d25-c347-f7b1-84d4c106e771%40siemens.com
to address that scenario. We are using that in one internal layer already.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2020-10-28 13:52 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
2020-09-21 19:17     ` Jan Kiszka
2020-10-28 13:39       ` Kanagarajan, Vijaikumar
2020-10-28 13:52         ` Jan Kiszka [this message]
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=03c83ddc-c901-1816-11d3-3552b9867495@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Vijaikumar_Kanagarajan@mentor.com \
    --cc=ibr@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