public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-antivirus/fangfrisch/
Date: Fri, 14 May 2021 11:19:52 +0000 (UTC)	[thread overview]
Message-ID: <1620991172.e4c081a48e3e1e58966d95ea0196bfb95539f385.sam@gentoo> (raw)

commit:     e4c081a48e3e1e58966d95ea0196bfb95539f385
Author:     Ralph Seichter <github <AT> seichter <DOT> de>
AuthorDate: Fri May 14 10:36:35 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri May 14 11:19:32 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4c081a4

app-antivirus/fangfrisch: Remove obsolete ebuild

Package-Manager: Portage-3.0.18, Repoman-3.0.2
Signed-off-by: Ralph Seichter <gentoo <AT> seichter.de>
Closes: https://github.com/gentoo/gentoo/pull/20801
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-antivirus/fangfrisch/Manifest                |  1 -
 app-antivirus/fangfrisch/fangfrisch-1.3.0.ebuild | 69 ------------------------
 2 files changed, 70 deletions(-)

diff --git a/app-antivirus/fangfrisch/Manifest b/app-antivirus/fangfrisch/Manifest
index 348557001ab..b37f9e780ea 100644
--- a/app-antivirus/fangfrisch/Manifest
+++ b/app-antivirus/fangfrisch/Manifest
@@ -1,2 +1 @@
-DIST fangfrisch-1.3.0.tar.gz 114361 BLAKE2B eca124f02f814d2915c4dbba45b6e4dc620e250730a32b34d3f5f5eaa33945e697d2d887f29251f1f8a3b1813476a54092091235a786e84695a3bc1cadebad28 SHA512 9c138737908a02efa5c9b4c6792a31e2a4908f8ab27e8cecab78612f812ab151afef75a405f47695779a949485aa88a3a5830efd02344ec334e6f37425cffe49
 DIST fangfrisch-1.4.0.tar.gz 115303 BLAKE2B 6dea9305ad22e8beff0fc04219d24da995c36e0838e1be8b98d12b11db1f68d7ca4f6084d15270c09e8a4b8d94a7bdfe1b9bb336abef1767b1ded2d1751fa22b SHA512 5fca7b7e8d24daadfb450851c70391fce94943a718bbed4fc76efe08a730cce313d92e7d9a6a8324a0b0039871f8c77f1fcd3744c569826cc0d2e7a7fd4e9b32

diff --git a/app-antivirus/fangfrisch/fangfrisch-1.3.0.ebuild b/app-antivirus/fangfrisch/fangfrisch-1.3.0.ebuild
deleted file mode 100644
index f70138cc4b3..00000000000
--- a/app-antivirus/fangfrisch/fangfrisch-1.3.0.ebuild
+++ /dev/null
@@ -1,69 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-DISTUTILS_USE_SETUPTOOLS=rdepend
-PYTHON_COMPAT=( python3_{7,8,9} )
-
-inherit distutils-r1 readme.gentoo-r1
-
-DESCRIPTION="Update and verify unofficial Clam Anti-Virus signatures"
-HOMEPAGE="https://github.com/rseichter/fangfrisch https://pypi.org/project/fangfrisch/"
-SRC_URI="https://github.com/rseichter/fangfrisch/archive/${PV}.tar.gz -> ${P}.tar.gz"
-
-MY_CONF="/etc/${PN}.conf"
-MY_DBDIR="/var/lib/${PN}"
-DISABLE_AUTOFORMATTING=1
-DOC_CONTENTS="See https://rseichter.github.io/fangfrisch/ for the official
-documentation.
-
-### Fresh installations:
-
-Modify ${MY_CONF} according to your preferences.
-Assuming you place the database into ${MY_DBDIR}
-(recommended), execute the following commands in a root shell:
-
-mkdir -m 0770 ${MY_DBDIR}
-chgrp clamav ${MY_DBDIR}
-sudo -u clamav -- fangfrisch -c ${MY_CONF} initdb
-
-You can now enable /etc/cron.d/${PN} for periodic updates.
-
-### Alternative: Updating from release 1.0.1:
-
-Either create a fresh database or manually delete all existing
-database tables, then run the initdb command as shown above."
-
-LICENSE="GPL-3+"
-SLOT="0"
-KEYWORDS="amd64 x86"
-
-DEPEND=">=dev-python/requests-2.22.0[${PYTHON_USEDEP}]
-	>=dev-python/sqlalchemy-1.3.11[${PYTHON_USEDEP}]"
-RDEPEND="${DEPEND}"
-
-python_prepare_all() {
-	sed -i -e '/SQLAlchemy/d' setup.py || die
-	# Due to the nature of Fangfrisch, most tests require network
-	# connectivity. Upstream CI reports show that the tests are
-	# successful, so instead of a pick-and-choose approach, the
-	# complete tests directory is removed in this ebuild.
-	if [ -d tests ]; then
-		rm -r tests || die
-	fi
-	distutils-r1_python_prepare_all
-}
-
-python_install_all() {
-	insinto /etc
-	doins "${FILESDIR}/${PN}.conf"
-	insinto /etc/cron.d
-	newins "${FILESDIR}/${PN}.cron" ${PN}
-	distutils-r1_python_install_all
-	readme.gentoo_create_doc
-}
-
-pkg_postinst() {
-	FORCE_PRINT_ELOG=1 readme.gentoo_print_elog
-}


             reply	other threads:[~2021-05-14 11:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 11:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-31 15:05 [gentoo-commits] repo/gentoo:master commit in: app-antivirus/fangfrisch/ Petr Vaněk
2024-08-31 14:49 Petr Vaněk
2024-04-21 12:34 Sam James
2024-03-21  2:41 Sam James
2023-06-10  7:08 Sam James
2023-05-03 15:51 Arthur Zamarin
2023-05-03  7:49 Sam James
2023-05-01 12:34 Michał Górny
2023-02-16  3:58 Sam James
2022-06-07  5:22 Joonas Niilola
2021-12-09  6:52 Ionen Wolkens
2021-12-01 17:45 Joonas Niilola
2021-12-01 17:45 Joonas Niilola
2021-10-20  3:07 Sam James
2021-10-20  3:07 Sam James
2021-10-20  3:07 Sam James
2021-05-14  9:30 Agostino Sarubbo
2021-02-12 15:10 Sam James
2021-02-12 15:10 Sam James
2021-02-11  8:13 Sam James
2021-02-11  8:13 Sam James
2021-02-11  8:11 Sam James
2020-12-15  4:09 Sam James
2020-05-19  6:01 Michał Górny
2020-05-18 21:13 Agostino Sarubbo
2020-05-18 21:10 Agostino Sarubbo
2020-05-15 20:13 Andreas K. Hüttel
2020-04-06  8:08 Andreas K. Hüttel

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=1620991172.e4c081a48e3e1e58966d95ea0196bfb95539f385.sam@gentoo \
    --to=sam@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