From: "Matthew Marlow (mattm)" <mattm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in net-analyzer/zabbix: zabbix-2.2.0.ebuild ChangeLog
Date: Sat, 16 Nov 2013 00:37:43 +0000 (UTC) [thread overview]
Message-ID: <20131116003743.B1BBD2004B@flycatcher.gentoo.org> (raw)
mattm 13/11/16 00:37:43
Modified: zabbix-2.2.0.ebuild ChangeLog
Log:
Zabbix-2.2.0 no longer happy with old zbx282 patch.
(Portage version: 2.1.12.2/cvs/Linux x86_64, signed Manifest commit with key 786037A7)
Revision Changes Path
1.2 net-analyzer/zabbix/zabbix-2.2.0.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild?r1=1.1&r2=1.2
Index: zabbix-2.2.0.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- zabbix-2.2.0.ebuild 15 Nov 2013 20:46:37 -0000 1.1
+++ zabbix-2.2.0.ebuild 16 Nov 2013 00:37:43 -0000 1.2
@@ -1,6 +1,6 @@
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild,v 1.1 2013/11/15 20:46:37 mattm Exp $
+# $Header: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/zabbix-2.2.0.ebuild,v 1.2 2013/11/16 00:37:43 mattm Exp $
EAPI="5"
@@ -69,7 +69,7 @@
}
src_prepare() {
- epatch "${FILESDIR}/2.0/patches/zbx282.patch"
+# Add any patches here
eautoreconf
}
1.142 net-analyzer/zabbix/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/ChangeLog?rev=1.142&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/ChangeLog?rev=1.142&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/net-analyzer/zabbix/ChangeLog?r1=1.141&r2=1.142
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/ChangeLog,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -r1.141 -r1.142
--- ChangeLog 15 Nov 2013 20:46:37 -0000 1.141
+++ ChangeLog 16 Nov 2013 00:37:43 -0000 1.142
@@ -1,6 +1,9 @@
# ChangeLog for net-analyzer/zabbix
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/ChangeLog,v 1.141 2013/11/15 20:46:37 mattm Exp $
+# $Header: /var/cvsroot/gentoo-x86/net-analyzer/zabbix/ChangeLog,v 1.142 2013/11/16 00:37:43 mattm Exp $
+
+ 16 Nov 2013; Matthew Marlowe <mattm@gentoo.org> zabbix-2.2.0.ebuild:
+ Zabbix-2.2.0 no longer happy with old zbx282 patch.
*zabbix-2.2.0 (15 Nov 2013)
next reply other threads:[~2013-11-16 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 0:37 Matthew Marlow (mattm) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-15 20:46 [gentoo-commits] gentoo-x86 commit in net-analyzer/zabbix: zabbix-2.2.0.ebuild ChangeLog Matthew Marlow (mattm)
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=20131116003743.B1BBD2004B@flycatcher.gentoo.org \
--to=mattm@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