From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: "Larson, Chris" <Chris_Larson@mentor.com>
Subject: Re: [PATCH] buildchroot: Lock-protect apt/dpkg operations
Date: Thu, 15 Feb 2018 12:39:09 +0300 [thread overview]
Message-ID: <952f8111-21b0-6472-e063-de90ccd4f232@ilbers.de> (raw)
In-Reply-To: <92b096db-6db3-401c-0bba-09a31cff2376@siemens.com>
On 02/14/2018 10:42 PM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> When running multiple build targets in parallel, they will compete for
> access on the package database while the related commands do not wait
> but fail immediately.
Applied to next, thanks!
Alex
prev parent reply other threads:[~2018-02-15 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 19:42 Jan Kiszka
2018-02-15 8:16 ` Alexander Smirnov
2018-02-15 8:46 ` Jan Kiszka
2018-02-15 9:39 ` Alexander Smirnov [this message]
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=952f8111-21b0-6472-e063-de90ccd4f232@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=Chris_Larson@mentor.com \
--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