From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/build-docbook-catalog:master commit in: /
Date: Tue, 5 Oct 2021 01:14:46 +0000 (UTC) [thread overview]
Message-ID: <1633396287.2b69063f19a03e9224eeaa6cecd35dd2004127c0.vapier@gentoo> (raw)
commit: 2b69063f19a03e9224eeaa6cecd35dd2004127c0
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 5 01:11:27 2021 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Oct 5 01:11:27 2021 +0000
URL: https://gitweb.gentoo.org/proj/build-docbook-catalog.git/commit/?id=2b69063f
add explicit check & error message for /run/lock
If the system is missing its lock dir, show an explicit error message
instead of confusing bash "file does not exist" errors.
Bug: https://bugs.gentoo.org/816303
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
build-docbook-catalog | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/build-docbook-catalog b/build-docbook-catalog
index 9064d72..5b6cd85 100755
--- a/build-docbook-catalog
+++ b/build-docbook-catalog
@@ -66,7 +66,12 @@ main() {
mkdir -p "${ROOT}${ROOTCONFDIR}" || error "could not create ${ROOTCONFDIR}"
fi
- local lock="${ROOT}/run/lock/build-docbook-catalog.lock"
+ local lock_dir="${ROOT}/run/lock"
+ if [[ ! -d ${lock_dir} ]] ; then
+ error "${lock_dir}: missing critical system path; please create it"
+ fi
+
+ local lock="${lock_dir}/build-docbook-catalog.lock"
(
# Lock the dir to avoid trashing other runs that might
# be running parallel.
next reply other threads:[~2021-10-05 1:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 1:14 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 3:43 [gentoo-commits] proj/build-docbook-catalog:master commit in: / Sam James
2023-04-25 3:43 Sam James
2022-01-27 20:28 Sam James
2022-01-17 23:13 Andreas K. Hüttel
2021-10-08 12:22 Mike Frysinger
2021-10-05 1:14 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-03 4:01 Mike Frysinger
2021-10-02 6:20 Mike Frysinger
2021-10-02 6:20 Mike Frysinger
2021-10-02 6:17 Mike Frysinger
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=1633396287.2b69063f19a03e9224eeaa6cecd35dd2004127c0.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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