public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "罗百科" <patrick@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/build-docbook-catalog/
Date: Sat,  9 Oct 2021 06:39:24 +0000 (UTC)	[thread overview]
Message-ID: <1633761562.940836c2dc07c9dae733ea506df9f39e7be47aec.patrick@gentoo> (raw)

commit:     940836c2dc07c9dae733ea506df9f39e7be47aec
Author:     Patrick Lauer <patrick <AT> gentoo <DOT> org>
AuthorDate: Sat Oct  9 06:39:06 2021 +0000
Commit:     罗百科 <patrick <AT> gentoo <DOT> org>
CommitDate: Sat Oct  9 06:39:22 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=940836c2

app-text/build-docbook-catalog: Create missing dir needed in pkg_postinst

Since /run might be empty (chroot etc.) or missing, opportunistically
create the directory if needed. Avoids failing randomly for no
obvious reason.

Package-Manager: Portage-3.0.28, Repoman-3.0.3
Signed-off-by: Patrick Lauer <patrick <AT> gentoo.org>

 app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild b/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
index d3143b3652b..87cfe4c3b89 100644
--- a/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
+++ b/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
@@ -33,5 +33,7 @@ src_configure() {
 pkg_postinst() {
 	# New version -> regen files
 	# See bug #816303 for rationale behind die
+	# create directory if needed
+	mkdir -p /run/lock
 	build-docbook-catalog || die "Failed to regenerate docbook catalog. Is /run mounted?"
 }


             reply	other threads:[~2021-10-09  6:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09  6:39 罗百科 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-01  3:29 [gentoo-commits] repo/gentoo:master commit in: app-text/build-docbook-catalog/ Sam James
2023-04-25  3:50 Sam James
2022-06-29 14:13 Guilherme Amadio
2022-06-13  7:07 Agostino Sarubbo
2022-04-29  8:19 Sam James
2022-04-29  8:14 Sam James
2022-01-17 23:39 Andreas K. Hüttel
2022-01-17 23:39 Andreas K. Hüttel
2021-12-26 23:38 Sam James
2021-12-26  3:58 Sam James
2021-12-26  3:58 Sam James
2021-12-22 22:40 Sam James
2021-12-17 18:30 Jakov Smolić
2021-12-17 18:30 Jakov Smolić
2021-12-17 16:50 Arthur Zamarin
2021-12-17 14:54 Arthur Zamarin
2021-12-17 14:51 Arthur Zamarin
2021-12-17 14:49 Arthur Zamarin
2021-12-17 14:44 Arthur Zamarin
2021-10-11  1:59 Sam James
2021-10-08 12:25 Mike Frysinger
2021-10-07  2:48 Sam James
2021-10-03  4:06 Mike Frysinger
2021-03-22  5:45 Mike Frysinger
2021-01-24 17:26 Sam James
2020-12-27 14:01 Fabian Groffen
2019-05-04 14:43 Andreas K. Hüttel
2018-06-06 17:58 Mike Frysinger
2018-05-21  9:51 Mikle Kolyada
2018-05-21  9:51 Mikle Kolyada
2018-05-03  7:06 Mart Raudsepp
2018-04-28 11:36 Mikle Kolyada
2018-04-20 21:27 Sergei Trofimovich
2018-04-01 18:24 Aaron Bauman
2018-04-01 11:09 Tobias Klausmann
2018-03-31 10:05 Sergei Trofimovich
2018-03-30 12:08 Sergei Trofimovich
2016-05-23 16:13 Michael Haubenwallner

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=1633761562.940836c2dc07c9dae733ea506df9f39e7be47aec.patrick@gentoo \
    --to=patrick@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