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: sys-apps/osinfo-db-tools/
Date: Sat,  6 Jan 2024 08:11:06 +0000 (UTC)	[thread overview]
Message-ID: <1704528616.3538acf3f865d0e78ece294bc1d7c36ed7da2500.sam@gentoo> (raw)

commit:     3538acf3f865d0e78ece294bc1d7c36ed7da2500
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan  6 08:10:16 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan  6 08:10:16 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3538acf3

sys-apps/osinfo-db-tools: Stabilize 1.11.0 arm64, #921404

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

 sys-apps/osinfo-db-tools/osinfo-db-tools-1.11.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/osinfo-db-tools/osinfo-db-tools-1.11.0.ebuild b/sys-apps/osinfo-db-tools/osinfo-db-tools-1.11.0.ebuild
index 9c6490a11d17..9efc2ffd8ea5 100644
--- a/sys-apps/osinfo-db-tools/osinfo-db-tools-1.11.0.ebuild
+++ b/sys-apps/osinfo-db-tools/osinfo-db-tools-1.11.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://releases.pagure.org/libosinfo/${P}.tar.xz"
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ~ppc ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 ~arm arm64 ~ia64 ~loong ~ppc ppc64 ~riscv ~sparc ~x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2024-01-06  8:11 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06  8:11 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-11 21:27 [gentoo-commits] repo/gentoo:master commit in: sys-apps/osinfo-db-tools/ Mart Raudsepp
2024-01-06  8:11 Sam James
2024-01-04 18:11 Arthur Zamarin
2023-12-03  7:01 Sam James
2022-12-04 15:59 WANG Xuerui
2022-10-15 15:01 Sam James
2022-03-18 19:24 Matt Turner
2022-02-15 20:36 Matt Turner
2021-12-17  1:22 Matt Turner
2021-04-15 15:36 Matt Turner
2021-04-15  5:25 Sam James
2021-04-15  1:33 Sam James
2021-04-14 18:51 Mikle Kolyada
2021-03-13  3:51 Matt Turner
2020-11-07 19:54 Mart Raudsepp
2020-08-30 18:28 Sam James
2020-08-30 18:09 Sam James
2020-08-30 15:17 Thomas Deutschmann
2020-07-26 19:03 Mart Raudsepp
2020-03-12 14:11 Mart Raudsepp
2020-03-12 14:05 Mart Raudsepp
2020-03-03 12:39 Agostino Sarubbo
2020-03-03 11:46 Agostino Sarubbo
2020-02-23 19:32 Mart Raudsepp
2020-02-23 18:10 Mart Raudsepp
2019-12-23 22:23 Mart Raudsepp
2019-12-09  0:10 Aaron Bauman
2019-12-08 11:52 Mikle Kolyada
2019-12-08 11:41 Mikle Kolyada
2019-05-22 21:20 Aaron Bauman
2019-04-09 21:15 Mikle Kolyada
2019-04-02  1:37 Thomas Deutschmann
2019-03-31  7:36 Mart Raudsepp
2019-02-19 21:39 Mart Raudsepp
2018-12-02 17:27 Mart Raudsepp
2018-12-02 14:29 Mikle Kolyada
2018-12-02 10:12 Mikle Kolyada
2018-07-09 10:08 Mart Raudsepp
2017-11-06 21:20 Sergei Trofimovich
2017-07-14 13:22 Alexis Ballier
2017-07-01 10:35 Sergei Trofimovich
2017-05-09  7:49 Tobias Klausmann
2017-04-27 10:36 Agostino Sarubbo
2017-04-23 21:23 Agostino Sarubbo
2017-03-31 10:08 Michael Weber
2017-03-31  9:30 Michael Weber
2017-03-31  9:30 Michael Weber
2017-03-28 19:38 Mart Raudsepp

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=1704528616.3538acf3f865d0e78ece294bc1d7c36ed7da2500.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