public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCHv3] dpkg-base: derive "Package" and "Architecture" from .deb in cleanup
Date: Tue, 16 Apr 2019 20:20:09 +0200	[thread overview]
Message-ID: <20190416182009.GA2115@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20190412141001.062bfe7a@md1za8fc.ad001.siemens.net>

On Fri, Apr 12, 2019 at 02:10:01PM +0200, Henning Schild wrote:
> I think we are still talking about writing style and wording of the
> commit message. No finger pointing was ever intended or even remotely
> thought about. I just said "you" to the anonymous reader of the commit
> message.

Ok, thanks for clarification. Yes, I'm talking about the wording that doesn't
leave room for misinterpretation.


> Did you succeed?

I've encountered qemu issues and haven't looked further, sorry. I need to solve
that first.


> We lock it for writes and assume that reads will happen after the repo
> is complete. Because an image depends on all recipes to deploy.
> In a multiconfig setup a writer (recipe deploy/clean) can remove
> packages that a reader (image bootstrap) needs.
> i.e. all arm64 recipes have deployed their debs and arm64 image
> bootstrap starts, during that bootstrap an x86 recipe deploy removes
> an "all" deb that the bootstrap needs ... deb missing ... press the
> jenkins build button again better luck next time

Thanks, now I get it. Readers must be also serialized against writers.


With kind regards,
Baurzhan.

  reply	other threads:[~2019-04-16 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 15:56 Henning Schild
2019-02-21 15:59 ` Henning Schild
2019-03-27 15:45 ` Henning Schild
2019-03-28 11:03 ` Baurzhan Ismagulov
2019-03-28 17:50   ` Henning Schild
2019-04-02 15:31     ` Baurzhan Ismagulov
2019-04-12 12:10       ` Henning Schild
2019-04-16 18:20         ` Baurzhan Ismagulov [this message]
2019-04-17  6:14           ` Baurzhan Ismagulov
2019-04-17 12:14     ` Baurzhan Ismagulov
2019-05-20 10:27 ` Henning Schild
2019-05-20 13:48 ` Maxim Yu. Osipov

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=20190416182009.GA2115@yssyq.m.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