public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/gramps/
Date: Mon, 11 Apr 2022 11:16:33 +0000 (UTC)	[thread overview]
Message-ID: <1649675620.5db0167787d646153c68cf2e8734fe2a7d6094ba.marecki@gentoo> (raw)

commit:     5db0167787d646153c68cf2e8734fe2a7d6094ba
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 11 11:13:40 2022 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Apr 11 11:13:40 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5db01677

app-misc/gramps: drop 5.1.4

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 app-misc/gramps/Manifest            |   1 -
 app-misc/gramps/gramps-5.1.4.ebuild | 112 ------------------------------------
 2 files changed, 113 deletions(-)

diff --git a/app-misc/gramps/Manifest b/app-misc/gramps/Manifest
index 637148df657e..c250581b7256 100644
--- a/app-misc/gramps/Manifest
+++ b/app-misc/gramps/Manifest
@@ -1,2 +1 @@
-DIST gramps-5.1.4.tar.gz 17425713 BLAKE2B 9b3761906b70ed6b85112e502290013cf421669418355ed0dc54d00adbcc2af4cd74c596bacaad50cdac6457e7a3b7675d4afb7b471fd471af8b7a6adae3ad82 SHA512 f43fc250142968331db1875260577e022898cff2d1453ee6b74be760d798b75cfdf93492d8d823dbb094da2ddd96a4f249e813c603e7cd9d0585641424284734
 DIST gramps-5.1.5.tar.gz 17425167 BLAKE2B f07fcb84c28f1def84c5568da6ac38a78def8657a0ee010163cb7e0899dd94ebb1c851e2c9d207fd9725754363ac7243a66f0de6e0d9708270d2d43c90485212 SHA512 8e36e8da7cfb41cc0c77881993cfc212a15bf9775dad3c8be131889b70360117e023b6837b91dad28fc03198080290a08c8089856c753246ff14c7fc3bca38be

diff --git a/app-misc/gramps/gramps-5.1.4.ebuild b/app-misc/gramps/gramps-5.1.4.ebuild
deleted file mode 100644
index fb62bc7dbe1d..000000000000
--- a/app-misc/gramps/gramps-5.1.4.ebuild
+++ /dev/null
@@ -1,112 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-PYTHON_COMPAT=( python3_{8..9} )
-PYTHON_REQ_USE="sqlite"
-
-DISTUTILS_SINGLE_IMPL=1
-DISTUTILS_USE_SETUPTOOLS=no
-inherit distutils-r1 xdg-utils
-
-DESCRIPTION="Community genealogy program aiming to be both intuitive and feature-complete"
-HOMEPAGE="https://gramps-project.org/"
-SRC_URI="https://github.com/gramps-project/${PN}/archive/v${PV}.tar.gz
-	-> ${P}.tar.gz"
-
-LICENSE="GPL-2+"
-SLOT="0"
-KEYWORDS="amd64 x86"
-IUSE="berkdb exif geo postscript +rcs +reports spell test"
-RESTRICT="!test? ( test )"
-
-RDEPEND="
-	$(python_gen_cond_dep '
-		dev-python/pycairo[${PYTHON_USEDEP}]
-		>=dev-python/pygobject-3.12:3[cairo,${PYTHON_USEDEP}]
-		dev-python/pyicu[${PYTHON_USEDEP}]
-		berkdb? ( dev-python/bsddb3[${PYTHON_USEDEP}] )
-		exif? ( >=media-libs/gexiv2-0.5[${PYTHON_USEDEP},introspection] )
-	')
-	gnome-base/librsvg:2
-	>x11-libs/gtk+-3.14.8:3[introspection]
-	x11-libs/pango[introspection]
-	x11-misc/xdg-utils
-	reports? ( media-gfx/graphviz[postscript?] )
-	geo? ( >=sci-geosciences/osm-gps-map-1.1.0 )
-	spell? ( app-text/gtkspell:3[introspection] )
-	rcs? ( dev-vcs/rcs )
-"
-BDEPEND="test? ( ${RDEPEND}
-	$(python_gen_cond_dep '
-		dev-python/jsonschema[${PYTHON_USEDEP}]
-		dev-python/lxml[${PYTHON_USEDEP}]
-	')
-)"
-
-PATCHES=(
-	"${FILESDIR}"/${PN}-5.1.3-test_locale.patch
-)
-
-python_prepare_all() {
-	# Install documentation to the proper location. This can't be done
-	# easily with a patch because we substitute in the ${PF} variable,
-	# and that changes with every revision.
-	sed -i "s:share/doc/gramps:share/doc/${PF}:g" setup.py || die
-	distutils-r1_python_prepare_all
-}
-
-python_configure_all() {
-	DISTUTILS_ARGS=(
-		--resourcepath=/usr/share
-		--no-compress-manpages
-	)
-}
-
-python_test() {
-	# Gramps builds just fine out of tree but it confuses its test suite.
-	# The following might be an ugly hack but at least it lets the tests
-	# run properly until either I or upstream have come up with something
-	# better. FIXME: test this when a new release comes out.
-	rm -rf "${S}/build" && ln -s "${BUILD_DIR}" "${S}"/build || \
-		die "Failed to symlink build directory to source directory"
-
-	# Set a sane default locale for the tests which do not explicitly set one.
-	local -x LC_ALL=C.UTF-8
-
-	# Note that as of 5.1.3, test failures do not actually propagate back
-	# to this function. For now this is fortunate because the test suite
-	# does not handle the absence of bsddb3 well, in the long run however
-	# this should be fixed.
-	esetup.py test || die
-}
-
-# Ugly hack to work around Bug #717922
-python_install() {
-	local DISTUTILS_ARGS=(
-		--resourcepath=/usr/share
-		--no-compress-manpages
-		build
-	)
-	distutils-r1_python_install
-	echo -n "${EPREFIX}/usr/share" > "${D}$(python_get_sitedir)/gramps/gen/utils/resource-path" || die
-}
-
-pkg_postinst() {
-	xdg_desktop_database_update
-	xdg_icon_cache_update
-	xdg_mimeinfo_database_update
-
-	if use berkdb; then
-		ewarn "The BSDDB back-end in ${PN} has got known stability and data-corruption issues. It has been deprecated since version 5.1.0 and might be removed in 5.2.0."
-		ewarn "If you have any family trees in this format you are highly advised to convert them to SQLite, as described here:"
-		ewarn
-		ewarn "https://gramps-project.org/wiki/index.php/Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Converting_a_BSDDB_Family_Tree_to_SQLite"
-	fi
-}
-
-pkg_postrm() {
-	xdg_desktop_database_update
-	xdg_icon_cache_update
-	xdg_mimeinfo_database_update
-}


             reply	other threads:[~2022-04-11 11:16 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 11:16 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-06  8:26 [gentoo-commits] repo/gentoo:master commit in: app-misc/gramps/ Sam James
2024-09-06 10:12 Petr Vaněk
2024-09-05 13:27 Petr Vaněk
2024-05-28 13:19 Sam James
2024-04-08 13:15 Marek Szuba
2023-10-24 23:16 Marek Szuba
2023-10-23 23:08 Sam James
2023-09-08  9:56 Marek Szuba
2023-09-07  8:38 Marek Szuba
2023-09-07  8:38 Marek Szuba
2023-08-22 21:35 Marek Szuba
2023-08-22 11:16 Sam James
2023-07-10 23:04 Marek Szuba
2023-07-08 23:39 Marek Szuba
2023-05-01 13:43 Sam James
2023-02-27  0:23 Marek Szuba
2022-05-18 23:18 Marek Szuba
2022-04-11  6:50 Agostino Sarubbo
2022-04-10  9:05 Agostino Sarubbo
2022-02-07 19:39 Marek Szuba
2021-09-13 17:11 Marek Szuba
2021-09-11  6:42 Agostino Sarubbo
2021-09-11  6:02 Sam James
2021-07-28 18:41 Marek Szuba
2021-05-15 14:22 Marek Szuba
2021-04-29  1:52 Sam James
2021-02-15 12:39 Marek Szuba
2020-11-13 14:30 Sam James
2020-08-24 17:19 Marek Szuba
2020-07-29 11:33 Marek Szuba
2020-07-14 20:56 Marek Szuba
2020-04-22 23:48 Marek Szuba
2020-04-21 22:21 Marek Szuba
2020-04-21 12:31 Marek Szuba
2020-03-04 10:00 Marek Szuba
2020-02-12 18:22 Agostino Sarubbo
2020-02-12 14:20 Agostino Sarubbo
2020-01-13 14:49 Marek Szuba
2020-01-13 14:49 Marek Szuba
2020-01-13 14:49 Marek Szuba
2019-10-29 15:54 Marek Szuba
2019-08-09 15:11 Marek Szuba
2019-07-18  7:26 Agostino Sarubbo
2019-07-15 14:17 Agostino Sarubbo
2019-07-15 11:46 Marek Szuba
2019-01-09 14:38 Marek Szuba
2018-10-11 14:37 Marek Szuba
2018-10-11 14:37 Marek Szuba
2018-07-01  9:45 Mikle Kolyada
2018-06-30 10:04 Pacho Ramos
2018-06-27 17:20 Pacho Ramos
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2017-06-04 10:42 Agostino Sarubbo
2017-06-02 20:02 Agostino Sarubbo
2017-04-28  4:03 Michael Orlitzky
2017-04-28  4:03 Michael Orlitzky
2017-01-15 19:54 Göktürk Yüksek
2016-12-29 11:41 Agostino Sarubbo
2016-12-29 11:36 Agostino Sarubbo
2016-11-16  9:33 Marek Szuba
2016-11-13 15:02 Marek Szuba
2016-10-20 23:55 David Seifert
2016-09-23  7:37 Marek Szuba
2016-09-23  6:57 Marek Szuba
2016-07-07 19:48 Austin English
2016-05-28  9:32 Pacho Ramos

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=1649675620.5db0167787d646153c68cf2e8734fe2a7d6094ba.marecki@gentoo \
    --to=marecki@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