public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/scrot/
Date: Fri, 18 Dec 2020 10:25:25 +0000 (UTC)	[thread overview]
Message-ID: <1608287115.af68bc9b20883894a3005be930042532121e6f00.slyfox@gentoo> (raw)

commit:     af68bc9b20883894a3005be930042532121e6f00
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 18 10:18:58 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Dec 18 10:25:15 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af68bc9b

media-gfx/scrot: stable 1.4 for ppc64

stable wrt bug #760372

Package-Manager: Portage-3.0.12, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 media-gfx/scrot/scrot-1.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-gfx/scrot/scrot-1.4.ebuild b/media-gfx/scrot/scrot-1.4.ebuild
index 956e5ff60f2..0ddd01558b2 100644
--- a/media-gfx/scrot/scrot-1.4.ebuild
+++ b/media-gfx/scrot/scrot-1.4.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/resurrecting-open-source-projects/${PN}/archive/${PV
 
 LICENSE="feh LGPL-2+"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ppc ppc64 ~sparc ~x86"
 
 RDEPEND="
 	>=media-libs/giblib-1.2.3


             reply	other threads:[~2020-12-18 10:25 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 10:25 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-18  7:41 [gentoo-commits] repo/gentoo:master commit in: media-gfx/scrot/ Joonas Niilola
2024-07-18  7:41 Joonas Niilola
2023-12-18  9:01 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-12-17 19:43 Arthur Zamarin
2023-11-24 15:18 Michał Górny
2023-06-18 12:16 Joonas Niilola
2023-06-11  8:22 Joonas Niilola
2023-06-11  8:22 Joonas Niilola
2023-06-11  8:22 Joonas Niilola
2023-05-15  4:10 Sam James
2023-05-15  4:10 Sam James
2023-05-13  9:02 Arthur Zamarin
2023-05-13  8:37 Arthur Zamarin
2023-05-13  8:37 Arthur Zamarin
2023-05-13  8:37 Arthur Zamarin
2023-04-11  4:07 Sam James
2023-03-28 11:50 Ionen Wolkens
2023-03-28 11:37 Ionen Wolkens
2023-02-26 20:00 Arthur Zamarin
2023-02-25 18:29 Arthur Zamarin
2023-02-25 18:26 Arthur Zamarin
2023-02-25 18:22 Arthur Zamarin
2023-02-25 18:21 Arthur Zamarin
2023-02-25 18:15 Arthur Zamarin
2023-01-21  4:54 Sam James
2023-01-11  5:15 Sam James
2023-01-10  3:59 Sam James
2022-08-19  3:46 Sam James
2022-07-15 12:44 Sam James
2022-06-21 16:08 Jakov Smolić
2022-06-17 12:18 Jakov Smolić
2022-06-17 11:48 Jakov Smolić
2022-06-17 10:27 Arthur Zamarin
2022-06-17  6:19 Joonas Niilola
2022-06-17  6:19 Joonas Niilola
2022-02-20  1:12 Sam James
2021-12-11  1:35 Sam James
2021-12-11  1:34 Sam James
2021-12-11  1:29 Sam James
2021-09-02  8:52 Yixun Lan
2020-12-20 18:47 Sam James
2020-12-20 16:40 Thomas Deutschmann
2020-12-18 20:49 Sergei Trofimovich
2020-12-17 16:41 Agostino Sarubbo
2020-12-17  8:17 Sam James
2020-07-19 10:15 Jeroen Roovers
2020-04-29  8:22 Jeroen Roovers
2020-04-16 12:26 Jeroen Roovers
2020-04-16  4:33 Jeroen Roovers
2020-04-16  4:29 Jeroen Roovers
2020-01-01 23:54 Jeroen Roovers
2019-05-03 15:23 Pacho Ramos
2019-05-03 13:49 Mikle Kolyada
2019-04-21  2:44 Anthony G. Basile
2019-04-17 11:39 Mikle Kolyada
2019-04-08  2:18 Thomas Deutschmann
2019-04-07 10:35 Mikle Kolyada
2019-04-05 19:03 Sergei Trofimovich
2019-01-27  6:21 Benda XU
2016-03-13 16:31 Patrice Clement
2016-03-13 15:34 Patrice Clement

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=1608287115.af68bc9b20883894a3005be930042532121e6f00.slyfox@gentoo \
    --to=slyfox@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