From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/buildbot/files/
Date: Thu, 26 Jul 2018 18:14:58 +0000 (UTC) [thread overview]
Message-ID: <1532628889.d32fc9a088a1abd9c6f9462822c3f5aac80f061f.dolsen@gentoo> (raw)
commit: d32fc9a088a1abd9c6f9462822c3f5aac80f061f
Author: Brian Dolbec dolsen <dolsen <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 26 18:14:24 2018 +0000
Commit: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Thu Jul 26 18:14:49 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d32fc9a0
dev-util/buildbot: Fix missed checkconfig section bug 661618
Adds RUNTIME_PYTHON default setting to the init.d script
Gentoo-bug: https://bugs.gentoo.org/661618
Package-Manager: Portage-2.3.40, Repoman-2.3.9
dev-util/buildbot/files/buildmaster.initd | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-util/buildbot/files/buildmaster.initd b/dev-util/buildbot/files/buildmaster.initd
index 933c6e2b4e5..b75ae34830d 100644
--- a/dev-util/buildbot/files/buildmaster.initd
+++ b/dev-util/buildbot/files/buildmaster.initd
@@ -32,6 +32,9 @@ checkconfig() {
eerror "${BUILDMASTER_PATH} does not contain buildbot.tac"
return 1
fi
+ if [ ! -e "${RUNTIME_PYTHON}" ]; then
+ RUNTIME_PYTHON="/usr/bin/python"
+ fi
}
start() {
next reply other threads:[~2018-07-26 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 18:14 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 14:35 [gentoo-commits] repo/gentoo:master commit in: dev-util/buildbot/files/ David Seifert
2022-02-07 20:47 Arthur Zamarin
2020-09-20 14:41 Conrad Kostecki
2020-06-15 16:39 Aaron Bauman
2019-02-27 5:35 Aaron Bauman
2017-11-04 7:25 Michael Palimaka
2016-08-10 17:18 Brian Dolbec
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=1532628889.d32fc9a088a1abd9c6f9462822c3f5aac80f061f.dolsen@gentoo \
--to=dolsen@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