public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tony Vroon" <chainsaw@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/munin/files/
Date: Wed, 11 Jul 2018 11:34:01 +0000 (UTC)	[thread overview]
Message-ID: <1531308834.9e9859656b5c85034a3cbba8bada4fb75756e80d.chainsaw@gentoo> (raw)

commit:     9e9859656b5c85034a3cbba8bada4fb75756e80d
Author:     Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
AuthorDate: Sun Jul  8 08:52:42 2018 +0000
Commit:     Tony Vroon <chainsaw <AT> gentoo <DOT> org>
CommitDate: Wed Jul 11 11:33:54 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9e985965

net-analyzer/munin: remove unused patches

Closes: https://github.com/gentoo/gentoo/pull/9122

 .../munin/files/munin-2.0.33-nogitversion.patch    | 11 ---------
 .../munin/files/munin-2.0.33-perl526.patch         | 26 ----------------------
 2 files changed, 37 deletions(-)

diff --git a/net-analyzer/munin/files/munin-2.0.33-nogitversion.patch b/net-analyzer/munin/files/munin-2.0.33-nogitversion.patch
deleted file mode 100644
index 6cf33538bde..00000000000
--- a/net-analyzer/munin/files/munin-2.0.33-nogitversion.patch
+++ /dev/null
@@ -1,11 +0,0 @@
---- munin-2.0.33/getversion
-+++ munin-2.0.33/getversion
-@@ -54,8 +54,6 @@
- 
- if [ -s "RELEASE" ]; then
-     cat RELEASE
--elif [ "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]; then
--    generate_version_string
- elif [ ! -z "$(generate_version_string_from_dir)" ]; then
- 	generate_version_string_from_dir
- else

diff --git a/net-analyzer/munin/files/munin-2.0.33-perl526.patch b/net-analyzer/munin/files/munin-2.0.33-perl526.patch
deleted file mode 100644
index d3cabb9906c..00000000000
--- a/net-analyzer/munin/files/munin-2.0.33-perl526.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-diff -ruN munin-2.0.33.orig/master/Build.PL munin-2.0.33/master/Build.PL
---- munin-2.0.33.orig/master/Build.PL	2017-03-03 00:02:39.000000000 -0000
-+++ munin-2.0.33/master/Build.PL	2017-08-05 15:06:55.799816839 -0000
-@@ -1,3 +1,4 @@
-+use lib q[.];
- use MasterBuilder;
- 
- use warnings;
-diff -ruN munin-2.0.33.orig/node/Build.PL munin-2.0.33/node/Build.PL
---- munin-2.0.33.orig/node/Build.PL	2017-03-03 00:02:39.000000000 -0000
-+++ munin-2.0.33/node/Build.PL	2017-08-05 15:11:07.689824612 -0000
-@@ -1,3 +1,4 @@
-+use lib q[.];
- use NodeBuilder;
- 
- use warnings;
-diff -ruN munin-2.0.33.orig/plugins/Build.PL munin-2.0.33/plugins/Build.PL
---- munin-2.0.33.orig/plugins/Build.PL	2017-03-03 00:02:39.000000000 -0000
-+++ munin-2.0.33/plugins/Build.PL	2017-08-05 15:13:57.056168401 -0000
-@@ -1,3 +1,4 @@
-+use lib q[.];
- use PluginsBuilder;
- 
- use warnings;


             reply	other threads:[~2018-07-11 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 11:34 Tony Vroon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-26 21:31 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/munin/files/ Conrad Kostecki
2021-12-04 15:23 Brian Evans
2019-07-20 19:39 Aaron Bauman
2017-10-12  9:32 Christian Ruppert
2017-01-15 10:25 David Seifert

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=1531308834.9e9859656b5c85034a3cbba8bada4fb75756e80d.chainsaw@gentoo \
    --to=chainsaw@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