public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/yaz/
Date: Sun, 25 Aug 2024 15:24:46 +0000 (UTC)	[thread overview]
Message-ID: <1724599460.7d85baef513ca2c4bc5e595a9f0cf7a44e8b3ca9.dilfridge@gentoo> (raw)

commit:     7d85baef513ca2c4bc5e595a9f0cf7a44e8b3ca9
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 25 15:19:37 2024 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sun Aug 25 15:24:20 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d85baef

dev-libs/yaz: remove ~mips, library and leaf package

Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 dev-libs/yaz/yaz-5.32.0.ebuild | 2 +-
 dev-libs/yaz/yaz-5.34.0.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-libs/yaz/yaz-5.32.0.ebuild b/dev-libs/yaz/yaz-5.32.0.ebuild
index 1b8c5ff2c9e8..2fa26dc6c553 100644
--- a/dev-libs/yaz/yaz-5.32.0.ebuild
+++ b/dev-libs/yaz/yaz-5.32.0.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == *9999 ]]; then
 	EGIT_REPO_URI="https://github.com/indexdata/yaz.git"
 else
 	SRC_URI="https://ftp.indexdata.com/pub/${PN}/${P}.tar.gz"
-	KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~s390 ~sparc x86"
+	KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~ppc ppc64 ~s390 ~sparc x86"
 fi
 
 LICENSE="BSD GPL-2"

diff --git a/dev-libs/yaz/yaz-5.34.0.ebuild b/dev-libs/yaz/yaz-5.34.0.ebuild
index 1e2b41c93c32..454bdf1effa7 100644
--- a/dev-libs/yaz/yaz-5.34.0.ebuild
+++ b/dev-libs/yaz/yaz-5.34.0.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == *9999 ]]; then
 	EGIT_REPO_URI="https://github.com/indexdata/yaz.git"
 else
 	SRC_URI="https://ftp.indexdata.com/pub/${PN}/${P}.tar.gz"
-	KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~s390 ~sparc x86"
+	KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~ppc ppc64 ~s390 ~sparc x86"
 fi
 
 LICENSE="BSD GPL-2"


             reply	other threads:[~2024-08-25 15:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-25 15:24 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08  7:20 [gentoo-commits] repo/gentoo:master commit in: dev-libs/yaz/ Arthur Zamarin
2025-03-08  7:20 Arthur Zamarin
2025-01-02  0:14 Conrad Kostecki
2024-10-31 23:32 Andreas K. Hüttel
2024-02-17 14:48 Sam James
2024-02-14 19:47 Arthur Zamarin
2024-02-14 19:42 Sam James
2024-02-14 16:48 Sam James
2024-01-30  6:58 Sam James
2022-12-18 20:07 Arthur Zamarin
2022-12-18 12:28 Sam James
2022-12-18 11:55 Sam James
2022-12-18 11:34 Sam James
2022-11-24 18:14 Conrad Kostecki
2022-08-26 12:04 Sam James
2022-06-12  7:33 Joonas Niilola
2022-02-19 12:38 Arthur Zamarin
2022-02-19 10:34 Arthur Zamarin
2021-08-16  3:15 Sam James
2021-08-16  3:15 Sam James
2021-08-16  2:43 Sam James
2021-07-25 21:46 Andreas K. Hüttel
2020-02-18 20:06 Andreas Sturmlechner
2016-11-05 17:21 Pacho Ramos
2016-11-05 17:16 Pacho Ramos
2016-10-01 14:12 Jeroen Roovers
2016-08-30 20:29 Markus Meier
2016-07-04 11:36 Tobias Klausmann
2016-07-03 18:45 Andreas Hüttel
2016-06-28  6:00 Michał Górny
2016-06-26 12:21 Anthony G. Basile

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=1724599460.7d85baef513ca2c4bc5e595a9f0cf7a44e8b3ca9.dilfridge@gentoo \
    --to=dilfridge@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