[PATCH] dpkg-base: Take isar.lock while cleaning deb packages

[PATCH] dpkg-base: Take isar.lock while cleaning deb packages

[Jan Kiszka]

From: Jan Kiszka <jan.kiszka@siemens.com>

Noticed while trying "bitbake a b -c clean":

The lock file '/build/tmp/deploy/isar-apt/iot2050-debian-arm64/db/iot2050-debian/lockfile' already exists. There might be another instance with the
same database dir running. To avoid locking overhead, only one process
can access the database at the same time. Do not delete the lock file unless
you are sure no other version is still running!

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/classes/dpkg-base.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
index 86933c57..8e4ee814 100644
--- a/meta/classes/dpkg-base.bbclass
+++ b/meta/classes/dpkg-base.bbclass
@@ -283,6 +283,8 @@ deb_clean() {
         done
     fi
 }
+# the clean function modifies isar-apt
+do_clean[lockfiles] = "${REPO_ISAR_DIR}/isar.lock"
 
 do_deploy_deb() {
     deb_clean
-- 
2.34.1

Re: [PATCH] dpkg-base: Take isar.lock while cleaning deb packages

[Anton Mikanovich]

04.05.2022 08:15, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Noticed while trying "bitbake a b -c clean":
>
> The lock file '/build/tmp/deploy/isar-apt/iot2050-debian-arm64/db/iot2050-debian/lockfile' already exists. There might be another instance with the
> same database dir running. To avoid locking overhead, only one process
> can access the database at the same time. Do not delete the lock file unless
> you are sure no other version is still running!
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Applied to next, thanks.