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: media-video/mjpegtools/
Date: Mon, 24 Jan 2022 03:42:54 +0000 (UTC)	[thread overview]
Message-ID: <1642995737.8611e639f7bac0cf6af7bb054cf5583fc32e9da3.sam@gentoo> (raw)

commit:     8611e639f7bac0cf6af7bb054cf5583fc32e9da3
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 24 03:42:17 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 24 03:42:17 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8611e639

media-video/mjpegtools: Stabilize 2.2.1 ppc64, #831805

Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-video/mjpegtools/mjpegtools-2.2.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-video/mjpegtools/mjpegtools-2.2.1.ebuild b/media-video/mjpegtools/mjpegtools-2.2.1.ebuild
index 58de34bc51f8..c4e8bfaa0e0a 100644
--- a/media-video/mjpegtools/mjpegtools-2.2.1.ebuild
+++ b/media-video/mjpegtools/mjpegtools-2.2.1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://sourceforge/mjpeg/${P}.tar.gz"
 LICENSE="GPL-2"
 # Compare with version in SONAME on major bumps (e.g. 2.1 -> 2.2)
 SLOT="1/2.2"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ppc ~ppc64 ~riscv ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ppc ppc64 ~riscv ~sparc x86"
 IUSE="cpu_flags_x86_mmx dv gtk png quicktime sdl sdlgfx static-libs"
 REQUIRED_USE="sdlgfx? ( sdl )"
 


             reply	other threads:[~2022-01-24  3:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24  3:42 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-27 22:00 [gentoo-commits] repo/gentoo:master commit in: media-video/mjpegtools/ Sam James
2024-03-08 14:23 Daniel Pielmeier
2023-08-12 13:34 Daniel Pielmeier
2023-08-12 13:32 Daniel Pielmeier
2022-12-07 13:52 David Seifert
2022-11-02  5:50 WANG Xuerui
2022-05-17  5:34 Sam James
2022-04-09 10:38 Daniel Pielmeier
2022-01-24 19:19 Sam James
2022-01-24  3:42 Sam James
2022-01-22 12:38 Jakov Smolić
2022-01-22 12:38 Jakov Smolić
2021-09-30 17:10 Daniel Pielmeier
2021-08-19 17:42 Daniel Pielmeier
2021-08-13 23:29 Sam James
2021-08-10  6:41 Agostino Sarubbo
2021-08-09  1:42 Sam James
2021-08-09  1:18 Sam James
2021-08-09  1:18 Sam James
2021-08-09  0:28 Sam James
2021-03-17 15:33 Daniel Pielmeier
2019-05-03  8:44 Pacho Ramos
2019-05-02 21:23 Mikle Kolyada
2019-04-01 19:58 Thomas Deutschmann
2019-03-24 20:25 Sergei Trofimovich
2019-03-24 20:12 Sergei Trofimovich
2019-03-24 19:44 Sergei Trofimovich
2019-03-24 13:08 Sergei Trofimovich
2019-03-24 10:01 Agostino Sarubbo
2018-10-07 15:50 Daniel Pielmeier
2018-08-02 18:14 Daniel Pielmeier
2018-07-30 21:50 Sergei Trofimovich
2018-06-19 14:32 Tobias Klausmann
2018-05-25 23:58 Thomas Deutschmann
2018-05-24 14:31 Agostino Sarubbo
2018-05-23  7:28 Sergei Trofimovich
2018-05-21  7:30 Sergei Trofimovich
2018-05-20 19:10 Andreas Sturmlechner
2018-05-20 19:10 Andreas Sturmlechner
2018-05-20 19:10 Andreas Sturmlechner
2018-03-28 22:41 Matt Turner
2017-11-19 11:39 Daniel Pielmeier

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=1642995737.8611e639f7bac0cf6af7bb054cf5583fc32e9da3.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