From: Alexander Smirnov <asmirnov@ilbers.de>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] acquire database lock when calling reprepro
Date: Wed, 22 Aug 2018 14:58:48 +0300 [thread overview]
Message-ID: <78647c3f-1b7e-8bc2-5fc9-e8b30769a1f1@ilbers.de> (raw)
In-Reply-To: <1534937676-7628-1-git-send-email-Cedric_Hombourger@mentor.com>
Hi,
On 22.08.2018 14:34, Cedric Hombourger wrote:
> As bitbake performs multi-threaded builds, packages may be built
> while others get deployed. A lock was already acquired within
> dpkg_runbuild but accesses to the isar-apt database were not
> protected from do_deploy_deb. Move the lock from the buildchroot
> to the isar-apt repository and acquire the (same) lock from
> dpkg_runbuild, repo_clean and do_deploy_deb.
>
Have you observed any issues with current implementation? IIRC reprepro
has it's own built-in lock file.
Alex
> Cedric Hombourger (1):
> dpkg: acquire lock when calling reprepro
>
> meta/classes/dpkg-base.bbclass | 8 ++++++--
> meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
> meta/recipes-kernel/linux/files/build-kernel.sh | 2 +-
> 3 files changed, 8 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2018-08-22 11:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 11:34 Cedric Hombourger
2018-08-22 11:34 ` [PATCH 1/1] dpkg: acquire " Cedric Hombourger
2018-08-22 12:20 ` Jan Kiszka
2018-08-22 12:48 ` Hombourger, Cedric
2018-08-22 13:41 ` Henning Schild
2018-08-22 13:47 ` Hombourger, Cedric
2018-08-22 13:48 ` Jan Kiszka
2018-08-26 6:21 ` [PATCH v3 1/3] dpkg: move installation of dependencies into dpkg_prepare Cedric Hombourger
2018-08-26 6:21 ` [PATCH v3 2/3] linux: leverage dpkg_prepare to install build dependencies Cedric Hombourger
2018-08-26 6:21 ` [PATCH v3 3/3] dpkg+linux: use Isar's lock via do_prepare[lockfiles] instead of flock Cedric Hombourger
2018-08-28 12:12 ` [PATCH v3 1/3] dpkg: move installation of dependencies into dpkg_prepare Maxim Yu. Osipov
2018-08-31 8:10 ` Jan Kiszka
2018-08-31 8:15 ` chombourger
2018-08-31 8:21 ` Jan Kiszka
2018-08-31 8:28 ` Jan Kiszka
2018-08-31 8:33 ` chombourger
2018-08-31 8:41 ` Jan Kiszka
2018-08-31 9:05 ` Jan Kiszka
2018-09-01 6:58 ` Jan Kiszka
2018-09-01 8:44 ` Cedric Hombourger
2018-09-01 9:31 ` Jan Kiszka
2018-08-22 11:58 ` Alexander Smirnov [this message]
2018-08-22 12:07 ` [PATCH 0/1] acquire database lock when calling reprepro Hombourger, Cedric
2018-08-22 12:47 ` [PATCH v2] dpkg: acquire " Cedric Hombourger
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=78647c3f-1b7e-8bc2-5fc9-e8b30769a1f1@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=Cedric_Hombourger@mentor.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