public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/sshguard/
Date: Wed, 12 Jun 2019 07:26:22 +0000 (UTC)	[thread overview]
Message-ID: <1560324381.d837c89222357e775e80c4afb31df3842dff1aac.jer@gentoo> (raw)

commit:     d837c89222357e775e80c4afb31df3842dff1aac
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 12 07:26:12 2019 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Wed Jun 12 07:26:21 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d837c892

app-admin/sshguard: Old

Package-Manager: Portage-2.3.67, Repoman-2.3.14
Signed-off-by: Jeroen Roovers <jer <AT> gentoo.org>

 app-admin/sshguard/Manifest              |  1 -
 app-admin/sshguard/sshguard-2.3.0.ebuild | 40 --------------------------------
 2 files changed, 41 deletions(-)

diff --git a/app-admin/sshguard/Manifest b/app-admin/sshguard/Manifest
index b9f5b164c7e..799fe68405e 100644
--- a/app-admin/sshguard/Manifest
+++ b/app-admin/sshguard/Manifest
@@ -1,4 +1,3 @@
 DIST sshguard-2.1.0.tar.gz 1117466 BLAKE2B 1a105f346aa9b774fb0314161d779eadaab299d3b74181a449ab86534e11375e4c017c142bc621733593369bcebada9511dd40c64cb4a49cd124eb7537ae0717 SHA512 0a75e9d1a8c9c010c767a49e96e88db4a92aae8d428deebcff1ce8befa36b77cb1937f2fcb2a4e2a3e86d47896a8405265eb30ee7a603fc18a3ee117d646b119
-DIST sshguard-2.3.0.tar.gz 755702 BLAKE2B 3b2e9bea3cf65c4e9a3ab82b6f5013c167033310d6f9ffe27d1d7dc9380be2214fdfdab4892ab9f6dfaa51b1131698d729257695ddef9debbc0ad06a9f49acfd SHA512 b3df479a752e0263fc444c582dd6c89dfdd4154ab011d23d0973f16f3b3e60f21f01b53e6ed0c4b138f134cd7e3dea5e67b44901f812f3da0d1aac760eeee279
 DIST sshguard-2.3.1.tar.gz 765330 BLAKE2B d86fe596c788209cb35c699601ccb698365e0c6b497ef8184c64d879ebb821a57e5f366c3b518e6f0c6bf65952b2c675f87f029b7b8184466c7f90d6dfebaca3 SHA512 b24f5dba34bed9246665c432b379afa4f1edacb56fd41e0b254a698ded1280c33fd51fb36466ae70d44ef4a31a0a75b59fa4df97d0e8ed8d194bf8046a3ac84d
 DIST sshguard-2.4.0.tar.gz 771506 BLAKE2B 82e9caf70dc9a1ba9ef6ba1c0916424a74891c84069a4a879c9057f3baea32af68f35d8b31cacdd60d323f5ec7b02a6e12aff1ec72fc0291b74c4882cd441d93 SHA512 64293700ef85f0843c333c3a27b04c5b2f69bf8dddf46353a371d4178915deb931362b3641ded0eeb5365f30cb63ce6ce17256d8d094383d1cfe661065b9c1c6

diff --git a/app-admin/sshguard/sshguard-2.3.0.ebuild b/app-admin/sshguard/sshguard-2.3.0.ebuild
deleted file mode 100644
index 578e515dab0..00000000000
--- a/app-admin/sshguard/sshguard-2.3.0.ebuild
+++ /dev/null
@@ -1,40 +0,0 @@
-# Copyright 1999-2018 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-DESCRIPTION="protects hosts from brute force attacks against ssh"
-HOMEPAGE="https://www.sshguard.net/"
-SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
-
-LICENSE="BSD"
-SLOT="0"
-KEYWORDS="~amd64 ~arm ~x86 ~x86-fbsd"
-
-DEPEND="
-	sys-devel/flex
-"
-RDEPEND="
-	virtual/logger
-"
-DOCS=(
-	CHANGELOG.rst
-	CONTRIBUTING.rst
-	README.rst
-	examples/net.sshguard.plist
-	examples/sshguard.service
-	examples/whitelistfile.example
-)
-PATCHES=(
-	"${FILESDIR}"/${PN}-2.1.0-conf.patch
-)
-
-src_install() {
-	default
-
-	newinitd "${FILESDIR}"/${PN}.initd-r1 ${PN}
-	newconfd "${FILESDIR}"/${PN}.confd ${PN}
-
-	insinto /etc
-	newins examples/sshguard.conf.sample sshguard.conf
-}


             reply	other threads:[~2019-06-12  7:26 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  7:26 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21  0:08 [gentoo-commits] repo/gentoo:master commit in: app-admin/sshguard/ Yixun Lan
2023-09-20 16:30 Arthur Zamarin
2023-09-20 16:30 Arthur Zamarin
2023-08-09 13:03 Yixun Lan
2023-08-09 13:03 Yixun Lan
2023-06-17  6:12 Sam James
2021-12-02  0:53 Jonas Stein
2021-10-12  8:12 Yixun Lan
2021-10-12  7:10 Agostino Sarubbo
2021-10-11  5:12 Sam James
2021-08-04  7:35 Yixun Lan
2021-03-30 15:26 Yixun Lan
2021-02-16 12:26 Sam James
2021-02-16  2:38 Yixun Lan
2021-02-15 10:05 Yixun Lan
2021-02-13 16:15 Yixun Lan
2021-02-13 16:15 Yixun Lan
2021-02-04  7:58 Agostino Sarubbo
2021-02-03 23:55 Thomas Deutschmann
2020-08-01  6:37 Jeroen Roovers
2019-08-08  7:14 Jeroen Roovers
2019-08-08  7:14 Jeroen Roovers
2019-06-12  7:25 Jeroen Roovers
2019-04-23  7:12 Jeroen Roovers
2019-01-02 13:03 Jeroen Roovers
2019-01-02 13:03 Jeroen Roovers
2018-12-17 20:42 Jeroen Roovers
2018-07-16 18:15 Jeroen Roovers
2018-04-13 14:18 Jeroen Roovers
2018-03-13 19:03 Mikle Kolyada
2018-03-13 18:08 Markus Meier
2018-03-11 15:07 Thomas Deutschmann
2017-11-01  9:33 Jeroen Roovers
2017-10-11  8:33 Jeroen Roovers
2017-03-08  4:48 Jeroen Roovers
2017-03-08  4:48 Jeroen Roovers
2017-01-29 20:40 Jeroen Roovers
2017-01-29 20:40 Jeroen Roovers
2017-01-04  9:22 Jeroen Roovers
2017-01-04  8:31 Jeroen Roovers
2017-01-04  8:23 Jeroen Roovers
2017-01-04  8:23 Jeroen Roovers
2016-12-29 10:05 Agostino Sarubbo
2016-12-17 14:18 Aaron Bauman
2016-10-26  8:20 Jeroen Roovers
2016-10-26  8:20 Jeroen Roovers
2016-08-10  7:20 Jeroen Roovers
2016-05-08  7:09 Jeroen Roovers
2016-05-08  7:03 Jeroen Roovers
2015-12-16  8:19 Jeroen Roovers

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=1560324381.d837c89222357e775e80c4afb31df3842dff1aac.jer@gentoo \
    --to=jer@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