From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/pnp4nagios/
Date: Sat, 23 Sep 2023 15:07:32 +0000 (UTC) [thread overview]
Message-ID: <1695481613.c6418f54821a4d5d1d73bb831c808a44486e034e.mjo@gentoo> (raw)
commit: c6418f54821a4d5d1d73bb831c808a44486e034e
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 23 14:59:30 2023 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sat Sep 23 15:06:53 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6418f54
net-analyzer/pnp4nagios: update HOMEPAGE
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
net-analyzer/pnp4nagios/metadata.xml | 2 +-
net-analyzer/pnp4nagios/pnp4nagios-0.6.26_p20230918.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/net-analyzer/pnp4nagios/metadata.xml b/net-analyzer/pnp4nagios/metadata.xml
index 938f480add62..9e00dcae8fec 100644
--- a/net-analyzer/pnp4nagios/metadata.xml
+++ b/net-analyzer/pnp4nagios/metadata.xml
@@ -18,6 +18,6 @@
<upstream>
<remote-id type="sourceforge">pnp4nagios</remote-id>
- <remote-id type="github">lingej/pnp4nagios</remote-id>
+ <remote-id type="github">ConSol-Monitoring/pnp4nagios</remote-id>
</upstream>
</pkgmetadata>
diff --git a/net-analyzer/pnp4nagios/pnp4nagios-0.6.26_p20230918.ebuild b/net-analyzer/pnp4nagios/pnp4nagios-0.6.26_p20230918.ebuild
index bc1ee5c143cc..ac57aaf8d4fc 100644
--- a/net-analyzer/pnp4nagios/pnp4nagios-0.6.26_p20230918.ebuild
+++ b/net-analyzer/pnp4nagios/pnp4nagios-0.6.26_p20230918.ebuild
@@ -4,7 +4,7 @@
EAPI=8
DESCRIPTION="A performance data analyzer for nagios"
-HOMEPAGE="http://www.pnp4nagios.org/"
+HOMEPAGE="https://github.com/ConSol-Monitoring/pnp"
GH_COMMIT="e52677d3994d35197db68120d7089906a174a3f9"
SRC_URI="https://github.com/ConSol-Monitoring/pnp/archive/${GH_COMMIT}.tar.gz -> ${P}.tar.gz"
S="${WORKDIR}/pnp-${GH_COMMIT}"
next reply other threads:[~2023-09-23 15:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 15:07 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 13:35 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/pnp4nagios/ Sam James
2023-11-04 12:25 Sam James
2023-11-04 10:49 Sam James
2023-09-23 15:07 Michael Orlitzky
2022-12-23 13:48 Arthur Zamarin
2022-12-23 13:48 Arthur Zamarin
2022-12-23 12:17 Sam James
2022-08-30 10:06 Michael Orlitzky
2022-08-29 12:38 Jakov Smolić
2022-08-12 14:27 Sam James
2022-08-03 16:12 Arthur Zamarin
2020-03-17 7:32 Matthew Thode
2020-02-17 23:37 Matthew Thode
2018-06-19 22:24 Michael Orlitzky
2018-03-19 23:24 Sergei Trofimovich
2018-03-19 22:39 Sergei Trofimovich
2017-11-29 18:52 Thomas Deutschmann
2017-11-29 13:38 Agostino Sarubbo
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2016-11-30 23:44 Patrice Clement
2016-03-15 11:08 Agostino Sarubbo
2016-02-06 23:31 Matt Thode
2016-02-01 14:45 Matt Thode
2015-12-16 22:11 Matt Thode
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=1695481613.c6418f54821a4d5d1d73bb831c808a44486e034e.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