From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/podofo-build/
Date: Mon, 25 Sep 2023 02:43:40 +0000 (UTC) [thread overview]
Message-ID: <1695609817.cb3d7bd0062b63524abc89cbf7d9655ba6375e34.zmedico@gentoo> (raw)
commit: cb3d7bd0062b63524abc89cbf7d9655ba6375e34
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun Sep 24 06:31:02 2023 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Mon Sep 25 02:43:37 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cb3d7bd0
virtual/podofo-build: drop 0.10.1-r1
This virtual package was only ever used by calibre, and only in order to
depend on the union of podofo itself plus boost, see bug 503802 for
details.
Since podofo 0.10.1 does not use boost at all, the virtual package is
obsoleted by this podofo update. The one package that depends on it,
requires the old podofo (and will be version bumped to depend
exclusively on the new podofo, *without* the virtual package).
Closes: https://github.com/gentoo/gentoo/pull/32989
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
virtual/podofo-build/podofo-build-0.10.1-r1.ebuild | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/virtual/podofo-build/podofo-build-0.10.1-r1.ebuild b/virtual/podofo-build/podofo-build-0.10.1-r1.ebuild
deleted file mode 100644
index fd4a0606200b..000000000000
--- a/virtual/podofo-build/podofo-build-0.10.1-r1.ebuild
+++ /dev/null
@@ -1,15 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DESCRIPTION="Virtual package for building against PoDoFo"
-
-SLOT="0/2"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
-IUSE="fontconfig idn jpeg png test tiff +tools"
-RESTRICT="!test? ( test )"
-
-RDEPEND="
- app-text/podofo:0/2[fontconfig=,idn=,jpeg=,png=,test=,tiff=,tools=]
-"
next reply other threads:[~2023-09-25 2:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 2:43 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 8:37 [gentoo-commits] repo/gentoo:master commit in: virtual/podofo-build/ Joonas Niilola
2023-09-21 6:17 Zac Medico
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2022-12-26 17:55 Zac Medico
2022-07-15 9:09 Sam James
2022-02-26 19:52 Zac Medico
2021-05-13 15:19 David Seifert
2021-01-09 10:36 Sam James
2020-07-28 21:25 Sergei Trofimovich
2020-06-06 0:51 Zac Medico
2019-06-28 20:49 Sergei Trofimovich
2019-05-20 10:58 Mikle Kolyada
2019-05-19 13:14 Thomas Deutschmann
2019-05-12 22:03 Sergei Trofimovich
2018-07-26 17:21 Zac Medico
2017-11-23 20:50 Zac Medico
2017-11-14 2:04 Zac Medico
2017-07-03 23:17 Zac Medico
2017-05-21 22:58 Zac Medico
2017-05-18 6:43 Zac Medico
2017-05-18 5:01 Michael Weber
2017-05-16 13:05 Agostino Sarubbo
2017-05-16 8:01 Agostino Sarubbo
2017-05-16 5:00 Jeroen Roovers
2017-05-15 14:17 Agostino Sarubbo
2017-05-12 10:06 Zac Medico
2017-05-12 10:02 Zac Medico
2017-05-12 9:56 Zac Medico
2017-05-10 20:07 Zac Medico
2017-05-01 19:09 Zac Medico
2017-02-07 17:39 Zac Medico
2016-07-25 6:19 Zac Medico
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=1695609817.cb3d7bd0062b63524abc89cbf7d9655ba6375e34.zmedico@gentoo \
--to=zmedico@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