From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/openfire/
Date: Sun, 23 Jun 2019 17:25:06 +0000 (UTC) [thread overview]
Message-ID: <1561310363.58445a9bcfd0a8ea1a0a61a6137f41ee75316fab.mjo@gentoo> (raw)
commit: 58445a9bcfd0a8ea1a0a61a6137f41ee75316fab
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 23 17:19:23 2019 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Jun 23 17:19:23 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58445a9b
net-im/openfire: fixup CONFIG_PROTECT handling in latest revision.
My -r2 accidentally clobbers the existing value of CONFIG_PROTECT
instead of appending to it. Oops. Fix it in place.
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
net-im/openfire/openfire-4.2.3-r2.ebuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/net-im/openfire/openfire-4.2.3-r2.ebuild b/net-im/openfire/openfire-4.2.3-r2.ebuild
index d504e403aba..dc79cda8b4b 100644
--- a/net-im/openfire/openfire-4.2.3-r2.ebuild
+++ b/net-im/openfire/openfire-4.2.3-r2.ebuild
@@ -41,8 +41,7 @@ src_compile() {
src_install() {
#Protect ssl key on upgrade
dodir /etc/env.d/
- echo 'CONFIG_PROTECT="/opt/openfire/resources/security/"' > "${D}"/etc/env.d/98openfire
- echo 'CONFIG_PROTECT="/opt/openfire/conf/"' > "${D}"/etc/env.d/98openfire
+ echo 'CONFIG_PROTECT="/opt/openfire/conf/ /opt/openfire/resources/security/"' > "${D}"/etc/env.d/98openfire
newinitd "${FILESDIR}"/openfire-initd openfire
newconfd "${FILESDIR}"/openfire-confd openfire
next reply other threads:[~2019-06-23 17:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 17:25 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-23 17:15 [gentoo-commits] repo/gentoo:master commit in: net-im/openfire/ Michael Orlitzky
2019-02-16 9:45 Pacho Ramos
2019-02-15 18:40 Mikle Kolyada
2019-02-15 18:40 Mikle Kolyada
2019-02-15 0:18 Thomas Deutschmann
2019-01-13 21:36 Sergei Trofimovich
2018-09-22 17:29 Sergei Trofimovich
2018-03-23 20:48 Sergei Trofimovich
2018-02-19 8:02 Sergei Trofimovich
2017-06-30 21:05 Sergei Trofimovich
2017-06-30 21:01 Sergei Trofimovich
2017-05-04 22:28 Sergei Trofimovich
2017-02-25 9:33 Sergei Trofimovich
2017-02-19 10:59 Sergei Trofimovich
2017-01-01 7:21 Sergei Trofimovich
2016-12-30 10:27 Sergei Trofimovich
2016-12-29 10:45 Agostino Sarubbo
2016-12-24 9:24 Aaron Bauman
2016-12-21 21:44 Sergei Trofimovich
2016-12-01 22:44 Sergei Trofimovich
2016-08-26 15:45 Sergei Trofimovich
2016-07-29 7:22 Sergei Trofimovich
2016-07-28 15:23 Agostino Sarubbo
2016-07-09 17:46 Agostino Sarubbo
2016-06-19 13:53 Sergei Trofimovich
2016-03-22 8:50 Sergei Trofimovich
2016-02-06 10:36 Sergei Trofimovich
2015-11-18 21:07 Sergei Trofimovich
2015-11-01 13:27 Mikle Kolyada
2015-10-27 12:18 Agostino Sarubbo
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=1561310363.58445a9bcfd0a8ea1a0a61a6137f41ee75316fab.mjo@gentoo \
--to=mjo@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