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/dcraw/
Date: Sun, 28 Apr 2019 13:03:42 +0000 (UTC)	[thread overview]
Message-ID: <1556456613.c929a8780407e04347cfe7c80b6216a75338a289.slyfox@gentoo> (raw)

commit:     c929a8780407e04347cfe7c80b6216a75338a289
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 28 08:39:47 2019 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Apr 28 13:03:33 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c929a878

media-gfx/dcraw: stable 9.28.0-r1 for ppc64, bug #681082

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

 media-gfx/dcraw/dcraw-9.28.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-gfx/dcraw/dcraw-9.28.0-r1.ebuild b/media-gfx/dcraw/dcraw-9.28.0-r1.ebuild
index b711bc3baee..8765b91f901 100644
--- a/media-gfx/dcraw/dcraw-9.28.0-r1.ebuild
+++ b/media-gfx/dcraw/dcraw-9.28.0-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://www.cybercom.net/~dcoffin/dcraw/archive/${P}.tar.gz
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~hppa ia64 ~ppc ~ppc64 sparc ~x86 ~amd64-linux ~x86-linux ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~hppa ia64 ~ppc ppc64 sparc ~x86 ~amd64-linux ~x86-linux ~x86-solaris"
 LANGS=" ca cs de da eo es fr hu it nl pl pt ru sv zh_CN zh_TW"
 IUSE="nls gimp jpeg jpeg2k lcms"
 


             reply	other threads:[~2019-04-28 13:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 13:03 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-07 12:42 [gentoo-commits] repo/gentoo:master commit in: media-gfx/dcraw/ Arthur Zamarin
2024-01-07  6:49 Joonas Niilola
2024-01-07  6:48 Joonas Niilola
2024-01-07  6:28 Sam James
2021-04-13  0:26 Sam James
2020-11-08 12:02 Sam James
2020-07-23  5:15 Kent Fredric
2019-08-28  8:19 David Seifert
2019-07-04  3:27 Tim Harder
2019-06-05  7:12 Agostino Sarubbo
2019-05-20 17:22 Aaron Bauman
2019-05-11 12:10 Mikle Kolyada
2019-05-08 19:21 Mikle Kolyada
2019-05-07 21:47 Matt Turner
2019-05-03  7:11 Sergei Trofimovich
2019-04-27 20:50 Sergei Trofimovich
2019-04-26 20:35 Sergei Trofimovich
2019-04-25 22:32 Pacho Ramos
2019-04-11 14:09 Pacho Ramos
2019-04-11 13:56 Pacho Ramos
2019-03-10 21:09 Aaron Bauman
2019-01-30 13:20 Tobias Klausmann
2018-12-09 23:51 Thomas Deutschmann
2018-12-08 11:56 Mikle Kolyada
2018-12-08  9:44 Sergei Trofimovich
2018-12-08  9:36 Sergei Trofimovich
2018-12-05 20:02 Sergei Trofimovich
2018-12-04 11:56 Agostino Sarubbo
2018-12-01 15:05 Sergei Trofimovich
2018-07-01  4:45 Tim Harder
2018-01-07 13:59 Ulrich Müller
2017-08-31 12:02 Tim Harder
2017-01-17 17:08 Markus Meier
2017-01-17 14:24 Agostino Sarubbo
2017-01-14 12:32 Jeroen Roovers
2017-01-11 10:35 Agostino Sarubbo
2017-01-03 10:38 Agostino Sarubbo
2016-11-29 17:32 Markus Meier
2016-11-25 18:54 Agostino Sarubbo
2016-11-25 18:27 Agostino Sarubbo
2016-11-23 17:59 Tobias Klausmann
2016-11-12 23:37 David Seifert
2016-05-24  4:36 Tim Harder

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=1556456613.c929a8780407e04347cfe7c80b6216a75338a289.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