Source: horizon Severity: minor Tags: patch User: [email protected] Usertags: buildpath X-Debbugs-Cc: [email protected]
A .lock file that is intended to be removed in debian/rules may still get installed if the package build is performed in a non-default path. Patch attached which uses a path-independent match to remove the .lock file. Build paths are currently normalized on buildd.debian.org and reproducible builds infrastructure, as well as most high-level package building tooling, so marking this as minor severity. live well, vagrant
From 0d86e7f8954c319041856ed13b6d0286eeadd430 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian <[email protected]> Date: Thu, 1 Oct 2026 13:09:15 -0700 Subject: [PATCH] debian/rules: Remove secret_key_store lock file in a path-independent way. The match with "_build*" is actually derived from the build path (typically /build/reproducible-path/PACKAGE-VERSION in Debian) and can fail to match if built in a different path. https://reproducible-builds.org/docs/build-path/ --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index b0936a63b..4837684ca 100755 --- a/debian/rules +++ b/debian/rules @@ -99,7 +99,7 @@ override_dh_auto_install: find . -name __pycache__ -prune -exec rm -rf {} +; ## Delete not needed files - rm -f $(CURDIR)/debian/tmp/usr/lib/python3/dist-packages/openstack_dashboard/local/_build*.lock + rm -f $(CURDIR)/debian/tmp/usr/lib/python3/dist-packages/openstack_dashboard/local/*secret_key_store.lock dh_install dh_missing --fail-missing -- 2.47.3
signature.asc
Description: PGP signature
