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: dev-libs/pugixml/
Date: Sat,  4 Nov 2023 13:35:09 +0000 (UTC)	[thread overview]
Message-ID: <1699104872.8519dd63a304fa3dad66b4e651452847178e13a1.sam@gentoo> (raw)

commit:     8519dd63a304fa3dad66b4e651452847178e13a1
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov  4 13:34:32 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov  4 13:34:32 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8519dd63

dev-libs/pugixml: Stabilize 1.14 amd64, #916838

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

 dev-libs/pugixml/pugixml-1.14.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/pugixml/pugixml-1.14.ebuild b/dev-libs/pugixml/pugixml-1.14.ebuild
index 3d321663dc6e..8f14b3fcb0a9 100644
--- a/dev-libs/pugixml/pugixml-1.14.ebuild
+++ b/dev-libs/pugixml/pugixml-1.14.ebuild
@@ -12,7 +12,7 @@ else
 	# Use non-release tarball for tests
 	# TODO: ask upstream to include tests in release tarballs?
 	SRC_URI="https://github.com/zeux/${PN}/archive/refs/tags/v${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="~amd64 ~arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux"
+	KEYWORDS="amd64 ~arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux"
 fi
 
 DESCRIPTION="Light-weight, simple, and fast XML parser for C++ with XPath support"


             reply	other threads:[~2023-11-04 13:35 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 13:35 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-04 16:13 [gentoo-commits] repo/gentoo:master commit in: dev-libs/pugixml/ Arthur Zamarin
2023-11-04 13:35 Sam James
2023-11-04 13:35 Sam James
2023-11-04 12:25 Sam James
2023-11-04 12:25 Sam James
2023-10-03 23:38 Sam James
2022-12-18 12:13 Sam James
2022-11-12 16:09 Arthur Zamarin
2022-11-12 16:06 Arthur Zamarin
2022-11-12 16:06 Arthur Zamarin
2022-11-03  6:15 Sam James
2022-09-10 11:33 Sam James
2022-09-10 11:33 Sam James
2022-09-05  3:56 Sam James
2022-09-03  5:27 Sam James
2022-02-28  7:06 Yixun Lan
2022-02-09  7:04 Sam James
2021-04-19 20:54 Sam James
2021-02-15  6:05 Sam James
2021-01-22  1:49 Sam James
2021-01-21 21:09 Sam James
2021-01-20  0:04 Sam James
2021-01-19  2:45 Sam James
2021-01-19  2:20 Sam James
2020-12-22 19:21 Sam James
2020-12-19 20:16 Sam James
2020-12-15  7:00 Sam James
2020-12-05 16:26 Sam James
2020-11-26 18:34 Sam James
2020-11-26 18:34 Sam James
2020-10-07  7:09 Agostino Sarubbo
2020-10-07  6:54 Agostino Sarubbo
2020-10-07  6:53 Agostino Sarubbo
2020-10-07  6:50 Agostino Sarubbo
2020-10-07  6:42 Agostino Sarubbo
2020-01-16 15:45 Tim Harder
2019-02-12 21:03 Sergei Trofimovich
2019-02-10  7:41 Mikle Kolyada
2019-02-09 18:36 Thomas Deutschmann
2019-02-08 20:35 Sergei Trofimovich
2019-02-08 19:53 Sergei Trofimovich
2019-01-09  0:17 Craig Andrews
2018-12-29 19:14 Tim Harder
2018-10-23 20:36 Sergei Trofimovich
2018-10-23 20:36 Sergei Trofimovich
2018-09-17 20:18 Sergei Trofimovich
2018-09-15 12:10 Sergei Trofimovich
2018-09-11 20:40 Matt Turner
2018-09-11 20:40 Matt Turner
2018-09-09 15:45 Mikle Kolyada
2018-04-09 15:01 Lars Wendler
2017-08-23 12:49 Tim Harder
2017-07-02 14:49 Sergei Trofimovich
2017-04-12 10:43 Tim Harder
2017-01-10 15:23 Agostino Sarubbo
2017-01-10  3:46 Aaron Bauman
2017-01-07 19:32 Tim Harder
2016-11-26 21:02 Lars Wendler
2016-11-26 21:02 Lars Wendler
2016-02-26 17:11 Markus Meier
2015-10-21 10:05 Lars Wendler

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=1699104872.8519dd63a304fa3dad66b4e651452847178e13a1.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