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-pda/libimobiledevice/
Date: Sun, 26 Mar 2023 18:15:33 +0000 (UTC)	[thread overview]
Message-ID: <1679854522.c09e735ada6cdccf51702a93e4d0687b52b17f65.sam@gentoo> (raw)

commit:     c09e735ada6cdccf51702a93e4d0687b52b17f65
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 26 18:15:22 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 26 18:15:22 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c09e735a

app-pda/libimobiledevice: Stabilize 1.3.0-r2 ppc, #903113

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

 app-pda/libimobiledevice/libimobiledevice-1.3.0-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-pda/libimobiledevice/libimobiledevice-1.3.0-r2.ebuild b/app-pda/libimobiledevice/libimobiledevice-1.3.0-r2.ebuild
index 2d351c5cba7b..f151f7623dc5 100644
--- a/app-pda/libimobiledevice/libimobiledevice-1.3.0-r2.ebuild
+++ b/app-pda/libimobiledevice/libimobiledevice-1.3.0-r2.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/libimobiledevice/libimobiledevice/releases/download/
 # While COPYING* doesn't mention 'or any later version', all the headers do, hence use +
 LICENSE="GPL-2+ LGPL-2.1+"
 SLOT="0/1.0-6" # based on SONAME of libimobiledevice-1.0.so
-KEYWORDS="amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv x86"
+KEYWORDS="amd64 ~arm ~arm64 ~loong ppc ~ppc64 ~riscv x86"
 IUSE="doc gnutls python static-libs"
 REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
 


             reply	other threads:[~2023-03-26 18:15 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 18:15 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-08 12:05 [gentoo-commits] repo/gentoo:master commit in: app-pda/libimobiledevice/ Petr Vaněk
2024-07-15  4:35 Sam James
2024-07-15  4:35 Sam James
2024-07-15  4:35 Sam James
2024-05-28 22:28 Ionen Wolkens
2024-04-04 16:23 Arthur Zamarin
2024-04-04 16:23 Arthur Zamarin
2024-03-21 17:00 Arthur Zamarin
2024-03-14  2:50 Yixun Lan
2024-03-13 19:38 Arthur Zamarin
2024-03-13 15:05 Arthur Zamarin
2024-03-13 15:05 Arthur Zamarin
2024-03-13 14:56 Matthew Smith
2024-03-10 17:10 Michał Górny
2024-03-10 16:46 Michał Górny
2024-03-10 16:46 Michał Górny
2024-03-10 16:46 Michał Górny
2023-12-25  8:37 Sam James
2023-10-23 14:05 Arthur Zamarin
2023-10-21 22:48 Sam James
2023-10-21 22:48 Sam James
2023-10-08 15:30 Matthew Smith
2023-08-13  1:09 Sam James
2023-03-26 18:15 Sam James
2023-03-26 18:15 Sam James
2022-12-08 18:53 Matthew Smith
2022-11-16  5:57 WANG Xuerui
2022-07-29  8:04 Matthew Smith
2022-07-25 18:50 Matthew Smith
2021-12-25 12:29 Georgy Yakovlev
2021-08-23 22:59 Marek Szuba
2021-05-31 23:47 Sam James
2021-05-02 18:12 Mikle Kolyada
2020-12-20 19:28 Sam James
2020-12-20 19:07 Thomas Deutschmann
2020-12-17 16:41 Agostino Sarubbo
2020-12-17  8:58 Sam James
2020-07-20 12:51 Jason A. Donenfeld
2020-07-18 10:57 Mart Raudsepp
2020-07-16 12:59 Joonas Niilola
2020-07-16 12:59 Joonas Niilola
2020-05-10 13:20 Andreas Sturmlechner
2020-05-10 12:40 Andreas Sturmlechner
2020-05-09  7:48 Agostino Sarubbo
2020-05-09  7:40 Agostino Sarubbo
2020-05-08 17:11 Agostino Sarubbo
2020-03-23 23:37 James Le Cuirot
2020-03-05 16:21 Michał Górny
2020-02-10 21:00 Michał Górny
2018-07-02 18:57 Pacho Ramos
2018-07-02  0:49 Thomas Deutschmann
2018-07-01  9:24 Sergei Trofimovich
2018-06-28  8:15 Agostino Sarubbo
2018-06-27 17:49 Pacho Ramos
2018-05-27 18:02 Pacho Ramos
2018-05-27 18:02 Pacho Ramos
2017-06-19 16:16 Alexis Ballier
2017-05-20 23:46 Michael Weber
2016-09-17  8:27 Pacho Ramos
2016-09-17  8:27 Pacho Ramos
2016-01-25  2:21 Mike Gilbert
2015-12-21 15:43 Ian Stakenvicius

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=1679854522.c09e735ada6cdccf51702a93e4d0687b52b17f65.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