public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kristian Fiskerstrand" <k_f@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-power/apcupsd/
Date: Wed, 28 Sep 2016 21:17:31 +0000 (UTC)	[thread overview]
Message-ID: <1475097445.82a2fab3856a3dd33079e76bfc6efc8815d046f0.k_f@gentoo> (raw)

commit:     82a2fab3856a3dd33079e76bfc6efc8815d046f0
Author:     Kristian Fiskerstrand <k_f <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 28 21:17:02 2016 +0000
Commit:     Kristian Fiskerstrand <k_f <AT> gentoo <DOT> org>
CommitDate: Wed Sep 28 21:17:25 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=82a2fab3

sys-power/apcupsd: Fixup missing || die

Package-Manager: portage-2.3.1

 sys-power/apcupsd/apcupsd-3.14.14.ebuild | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/sys-power/apcupsd/apcupsd-3.14.14.ebuild b/sys-power/apcupsd/apcupsd-3.14.14.ebuild
index 22b9887..02c1086 100644
--- a/sys-power/apcupsd/apcupsd-3.14.14.ebuild
+++ b/sys-power/apcupsd/apcupsd-3.14.14.ebuild
@@ -74,12 +74,12 @@ src_compile() {
 	# the text files in the distribution, but I wouldn't count on them
 	# doing that anytime soon.
 	MANPAGER=$(type -p cat) \
-		emake || die "emake failed"
+		emake
 }
 
 src_install() {
 	emake DESTDIR="${D}" install
-	rm -f "${D}"/etc/init.d/halt
+	rm -f "${D}"/etc/init.d/halt || die
 
 	insinto /etc/apcupsd
 	newins examples/safe.apccontrol safe.apccontrol
@@ -90,7 +90,7 @@ src_install() {
 
 	dohtml -r doc/manual/*
 
-	rm "${D}"/etc/init.d/apcupsd
+	rm "${D}"/etc/init.d/apcupsd || die
 	newinitd "${FILESDIR}/${PN}.init.4" "${PN}"
 	newinitd "${FILESDIR}/${PN}.powerfail.init" "${PN}".powerfail
 
@@ -98,7 +98,7 @@ src_install() {
 	systemd_dotmpfilesd "${FILESDIR}"/${PN}-tmpfiles.conf
 
 	# remove hal settings, we don't really want to have it around still.
-	rm -r "${D}"/usr/share/hal
+	rm -r "${D}"/usr/share/hal || die
 
 	# replace it with our udev rules if we're in Linux
 	if use kernel_linux; then


             reply	other threads:[~2016-09-28 21:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 21:17 Kristian Fiskerstrand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-28  7:55 [gentoo-commits] repo/gentoo:master commit in: sys-power/apcupsd/ Sam James
2023-04-03 17:40 Jakov Smolić
2022-07-11 15:03 David Seifert
2022-01-04 10:30 David Seifert
2021-09-15  2:34 Sam James
2021-09-03  1:53 Sam James
2021-05-13 21:17 Sam James
2021-05-13 18:56 Sam James
2021-05-13 17:10 Sam James
2021-04-01 22:23 Thomas Deutschmann
2021-03-07 16:45 David Seifert
2021-03-07 11:58 David Seifert
2020-05-06 17:25 Michał Górny
2019-02-09  9:52 Andreas Sturmlechner
2018-10-01 14:04 Sergey Popov
2018-09-26 15:07 Sergey Popov
2018-08-26 20:35 Michał Górny
2018-03-14 19:19 Mikle Kolyada
2018-01-07 23:38 Mikle Kolyada
2018-01-07 14:23 Sergei Trofimovich
2017-11-26 23:26 David Seifert
2016-11-23 20:52 Kristian Fiskerstrand
2016-11-18 23:39 Kristian Fiskerstrand
2016-09-28 21:11 Kristian Fiskerstrand
2016-09-28 21:11 Kristian Fiskerstrand
2016-09-28  8:55 Kristian Fiskerstrand
2016-08-06  9:16 Pacho Ramos
2016-06-06 13:33 Agostino Sarubbo
2015-12-22 12:07 Lars Wendler

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=1475097445.82a2fab3856a3dd33079e76bfc6efc8815d046f0.k_f@gentoo \
    --to=k_f@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