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-text/podofo/
Date: Fri, 15 Dec 2023 04:40:53 +0000 (UTC)	[thread overview]
Message-ID: <1702615210.3eab26b9f07bf88b38e42bf743767ccc1f3c79a5.sam@gentoo> (raw)

commit:     3eab26b9f07bf88b38e42bf743767ccc1f3c79a5
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 15 04:39:57 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Dec 15 04:40:10 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3eab26b9

Revert "app-text/podofo: Stabilize 0.10.1-r1 amd64, #919929"

This reverts commit fbdfa6af172b014ca50334a35396fb0b5e77421a.

Bug: https://bugs.gentoo.org/919929
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-text/podofo/podofo-0.10.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-text/podofo/podofo-0.10.1-r1.ebuild b/app-text/podofo/podofo-0.10.1-r1.ebuild
index 703873f384e4..bc45d82bde0f 100644
--- a/app-text/podofo/podofo-0.10.1-r1.ebuild
+++ b/app-text/podofo/podofo-0.10.1-r1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/podofo/podofo/archive/refs/tags/${PV}.tar.gz -> ${P}
 
 LICENSE="LGPL-2+ tools? ( GPL-2+ )"
 SLOT="0/2"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ppc64 ~x86"
 IUSE="idn jpeg tiff png fontconfig test tools"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2023-12-15  4:40 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  4:40 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22  6:59 [gentoo-commits] repo/gentoo:master commit in: app-text/podofo/ Viorel Munteanu
2024-01-05 18:16 Arthur Zamarin
2024-01-05 18:16 Arthur Zamarin
2024-01-05  8:13 Sam James
2023-12-21  0:07 Ionen Wolkens
2023-12-15  6:31 Sam James
2023-12-15  5:15 Sam James
2023-12-15  4:40 Sam James
2023-12-15  4:39 Sam James
2023-12-15  4:39 Sam James
2023-12-05  5:57 Zac Medico
2023-10-29  3:36 Sam James
2023-09-25  2:43 Zac Medico
2023-09-25  2:43 Zac Medico
2023-09-22  8:24 Joonas Niilola
2023-09-22  8:24 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 18:15 Zac Medico
2022-12-26 17:55 Zac Medico
2022-10-17 22:19 Sam James
2022-09-05 19:18 Zac Medico
2022-02-27 16:57 Sam James
2022-02-27 16:51 Zac Medico
2022-02-26 19:52 Zac Medico
2021-06-18 21:07 David Seifert
2021-05-02 19:31 Mikle Kolyada
2021-05-02 15:07 Mikle Kolyada
2021-03-25 23:31 Conrad Kostecki
2020-12-03 22:58 Marek Szuba
2020-08-01  7:55 Sergei Trofimovich
2020-07-28 22:05 Zac Medico
2020-07-28 21:25 Sergei Trofimovich
2020-07-18  0:29 Sam James
2020-07-17 23:25 Sam James
2020-07-17 12:09 Sam James
2020-07-17 10:25 Sam James
2020-06-29  4:41 Zac Medico
2020-06-29  4:38 Zac Medico
2020-06-10  6:31 Zac Medico
2020-06-06  0:27 Zac Medico
2020-02-18 20:06 Andreas Sturmlechner
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
2019-01-06 10:04 Zac Medico
2018-07-26 17:21 Zac Medico
2017-11-12  6:12 Zac Medico
2017-10-16  8:36 Zac Medico
2017-07-03 23:17 Zac Medico
2017-06-10 19:25 Zac Medico
2017-05-23 16:49 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:11 Zac Medico
2017-05-01 17:10 Zac Medico
2017-02-07 17:39 Zac Medico
2016-07-24  0:23 Zac Medico
2016-05-11 22:42 Anthony G. Basile
2015-09-13 23:40 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=1702615210.3eab26b9f07bf88b38e42bf743767ccc1f3c79a5.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