public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/ejabberd/files/, net-im/ejabberd/
Date: Thu, 30 Apr 2020 09:44:35 +0000 (UTC)	[thread overview]
Message-ID: <1588239865.fdfa70080cd3916f32561b479da795248eddf738.hanno@gentoo> (raw)

commit:     fdfa70080cd3916f32561b479da795248eddf738
Author:     Hanno Böck <hanno <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 30 09:44:25 2020 +0000
Commit:     Hanno Böck <hanno <AT> gentoo <DOT> org>
CommitDate: Thu Apr 30 09:44:25 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fdfa7008

net-im/ejabberd: Remove duplicate patch

Both patch files for old and new version were identical.

Signed-off-by: Hanno Böck <hanno <AT> gentoo.org>
Package-Manager: Portage-2.3.99, Repoman-2.3.22

 net-im/ejabberd/ejabberd-20.03.ebuild                     |  2 +-
 .../ejabberd-19.08-0002-Dont-overwrite-service-file.patch | 15 ---------------
 2 files changed, 1 insertion(+), 16 deletions(-)

diff --git a/net-im/ejabberd/ejabberd-20.03.ebuild b/net-im/ejabberd/ejabberd-20.03.ebuild
index aadecdb23d9..7ed076748bb 100644
--- a/net-im/ejabberd/ejabberd-20.03.ebuild
+++ b/net-im/ejabberd/ejabberd-20.03.ebuild
@@ -61,7 +61,7 @@ RDEPEND="${DEPEND}
 
 DOCS=( CHANGELOG.md README.md )
 PATCHES=( "${FILESDIR}/${PN}-19.08-ejabberdctl.patch"
-	"${FILESDIR}/${PN}-19.08-0002-Dont-overwrite-service-file.patch")
+	"${FILESDIR}/${PN}-17.04-0002-Dont-overwrite-service-file.patch")
 
 EJABBERD_CERT="${EPREFIX}/etc/ssl/ejabberd/server.pem"
 # Paths in net-im/jabber-base

diff --git a/net-im/ejabberd/files/ejabberd-19.08-0002-Dont-overwrite-service-file.patch b/net-im/ejabberd/files/ejabberd-19.08-0002-Dont-overwrite-service-file.patch
deleted file mode 100644
index 2bea750ef04..00000000000
--- a/net-im/ejabberd/files/ejabberd-19.08-0002-Dont-overwrite-service-file.patch
+++ /dev/null
@@ -1,15 +0,0 @@
-diff --git a/Makefile.in b/Makefile.in
-index a0b4553d..4675b88a 100644
---- a/Makefile.in
-+++ b/Makefile.in
-@@ -204,8 +204,8 @@ install: all copy-files
- 	chmod 755 ejabberd.init
- 	#
- 	# Service script
--	$(SED) -e "s*@ctlscriptpath@*$(SBINDIR)*g" ejabberd.service.template \
--		> ejabberd.service
-+	[ -f ejabberd.service ] || $(SED) -e "s*@ctlscriptpath@*$(SBINDIR)*g" \
-+		ejabberd.service.template > ejabberd.service
- 	chmod 644 ejabberd.service
- 	#
- 	# Spool directory


             reply	other threads:[~2020-04-30  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  9:44 Hanno Böck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-28 20:58 [gentoo-commits] repo/gentoo:master commit in: net-im/ejabberd/files/, net-im/ejabberd/ Florian Schmaus
2022-05-18  7:13 Florian Schmaus
2021-12-10 13:06 Florian Schmaus
2020-04-30  8:16 Hanno Böck
2019-02-24 10:53 Pacho Ramos
2017-05-28 13:30 Amadeusz Piotr Żołnowski
2017-05-28 13:30 Amadeusz Piotr Żołnowski
2017-05-27 20:55 Amadeusz Piotr Żołnowski
2017-04-01 19:46 Amadeusz Piotr Żołnowski
2016-08-21 10:49 Amadeusz Piotr Żołnowski
2016-02-15 21:49 Amadeusz Piotr Żołnowski

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=1588239865.fdfa70080cd3916f32561b479da795248eddf738.hanno@gentoo \
    --to=hanno@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