From: "Louis Sautier" <sbraz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/nagiosplugin/
Date: Sat, 9 Nov 2019 12:28:55 +0000 (UTC) [thread overview]
Message-ID: <1573302523.83d87e81ebf904182907dfa8b2be20b908f271a9.sbraz@gentoo> (raw)
commit: 83d87e81ebf904182907dfa8b2be20b908f271a9
Author: Louis Sautier <sbraz <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 9 00:52:43 2019 +0000
Commit: Louis Sautier <sbraz <AT> gentoo <DOT> org>
CommitDate: Sat Nov 9 12:28:43 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83d87e81
dev-python/nagiosplugin: update upstream info
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Louis Sautier <sbraz <AT> gentoo.org>
dev-python/nagiosplugin/metadata.xml | 4 ++--
dev-python/nagiosplugin/nagiosplugin-1.2.4.ebuild | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-python/nagiosplugin/metadata.xml b/dev-python/nagiosplugin/metadata.xml
index 56b0f256a4b..7f6a93a5502 100644
--- a/dev-python/nagiosplugin/metadata.xml
+++ b/dev-python/nagiosplugin/metadata.xml
@@ -7,7 +7,7 @@
</maintainer>
<upstream>
<remote-id type="pypi">nagiosplugin</remote-id>
- <remote-id type="bitbucket">flyingcircus/nagiosplugin</remote-id>
- <bugs-to>https://bitbucket.org/flyingcircus/nagiosplugin/issues</bugs-to>
+ <remote-id type="github">mpounsett/nagiosplugin</remote-id>
+ <bugs-to>https://github.com/mpounsett/nagiosplugin/issues</bugs-to>
</upstream>
</pkgmetadata>
diff --git a/dev-python/nagiosplugin/nagiosplugin-1.2.4.ebuild b/dev-python/nagiosplugin/nagiosplugin-1.2.4.ebuild
index db0af6ad3e5..3d5a2c4be07 100644
--- a/dev-python/nagiosplugin/nagiosplugin-1.2.4.ebuild
+++ b/dev-python/nagiosplugin/nagiosplugin-1.2.4.ebuild
@@ -8,7 +8,7 @@ PYTHON_COMPAT=( pypy{,3} python{2_7,3_{5,6,7}} )
inherit distutils-r1
DESCRIPTION="A class library for writing nagios-compatible plugins"
-HOMEPAGE="https://bitbucket.org/flyingcircus/nagiosplugin/ https://pypi.org/project/nagiosplugin/"
+HOMEPAGE="https://github.com/mpounsett/nagiosplugin https://nagiosplugin.readthedocs.io"
SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
KEYWORDS="~amd64 ~x86"
next reply other threads:[~2019-11-09 12:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 12:28 Louis Sautier [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-21 5:38 [gentoo-commits] repo/gentoo:master commit in: dev-python/nagiosplugin/ Michał Górny
2024-06-02 3:44 Louis Sautier
2023-06-09 18:09 Arthur Zamarin
2023-02-15 17:29 Michał Górny
2023-02-15 17:29 Michał Górny
2022-06-04 19:57 Michał Górny
2022-05-16 13:20 Michał Górny
2022-02-08 9:42 Michał Górny
2021-07-15 22:41 Louis Sautier
2020-09-04 22:14 Louis Sautier
2020-04-20 21:33 Louis Sautier
2020-03-28 9:20 Michał Górny
2019-11-10 2:30 Louis Sautier
2019-11-10 2:30 Louis Sautier
2019-11-09 12:28 Louis Sautier
2018-07-21 15:47 Louis Sautier
2018-07-21 15:47 Louis Sautier
2018-06-18 10:34 Louis Sautier
2018-05-26 12:53 David Seifert
2016-03-12 21:48 Patrice Clement
2015-12-29 0:14 Patrice Clement
2015-12-21 23:43 Patrice Clement
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=1573302523.83d87e81ebf904182907dfa8b2be20b908f271a9.sbraz@gentoo \
--to=sbraz@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