public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/libvirt-glib/
Date: Sun,  9 Jun 2024 03:31:24 +0000 (UTC)	[thread overview]
Message-ID: <1717903665.446a1d4c9f939371ed43f660285683c3c12e6c3e.ionen@gentoo> (raw)

commit:     446a1d4c9f939371ed43f660285683c3c12e6c3e
Author:     Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Sat Jun  8 20:45:56 2024 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sun Jun  9 03:27:45 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=446a1d4c

app-emulation/libvirt-glib: Stabilize 5.0.0 x86, #930933

Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 app-emulation/libvirt-glib/libvirt-glib-5.0.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/libvirt-glib/libvirt-glib-5.0.0.ebuild b/app-emulation/libvirt-glib/libvirt-glib-5.0.0.ebuild
index 1d45b4004f35..f40d082947f0 100644
--- a/app-emulation/libvirt-glib/libvirt-glib-5.0.0.ebuild
+++ b/app-emulation/libvirt-glib/libvirt-glib-5.0.0.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://libvirt.org/ https://gitlab.com/libvirt/libvirt-glib/"
 SRC_URI="https://libvirt.org/sources/glib/${P}.tar.xz"
 LICENSE="LGPL-2.1+"
 SLOT="0"
-KEYWORDS="amd64 arm64 ~ppc64 ~x86"
+KEYWORDS="amd64 arm64 ~ppc64 x86"
 IUSE="gtk-doc +introspection test +vala"
 RESTRICT="!test? ( test )"
 REQUIRED_USE="vala? ( introspection )"


             reply	other threads:[~2024-06-09  3:31 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09  3:31 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17  5:01 [gentoo-commits] repo/gentoo:master commit in: app-emulation/libvirt-glib/ Sam James
2024-07-03 21:21 Matthias Maier
2024-06-09  3:31 Ionen Wolkens
2024-06-09  3:31 Ionen Wolkens
2024-06-08  9:55 Arthur Zamarin
2024-01-22  5:29 Sam James
2024-01-04 18:11 Arthur Zamarin
2023-12-03  7:01 Sam James
2023-12-03  7:01 Sam James
2022-08-19  2:40 Sam James
2022-03-25  1:48 Sam James
2022-01-04 16:33 Matthias Maier
2021-09-19 20:40 Mart Raudsepp
2021-05-17  7:49 Agostino Sarubbo
2021-05-17  7:47 Agostino Sarubbo
2021-03-25  2:34 Matt Turner
2021-03-25  2:34 Matt Turner
2020-06-05  7:21 Mart Raudsepp
2020-02-03 15:24 Agostino Sarubbo
2020-02-03 12:38 Agostino Sarubbo
2019-12-31 22:01 Matthias Maier
2019-12-28 22:11 Georgy Yakovlev
2019-03-29 23:27 Mart Raudsepp
2019-02-15 22:38 Mart Raudsepp
2019-01-02 10:02 Mikle Kolyada
2018-12-29 19:12 Thomas Deutschmann
2018-11-04  5:13 Matthias Maier
2017-03-04 21:27 Matthias Maier
2017-03-04 21:27 Matthias Maier
2016-12-01 16:52 Matthias Maier
2016-11-18 20:42 Matthias Maier
2016-11-18 20:42 Matthias Maier
2016-10-04  7:19 Matthias Maier
2016-02-28 11:09 Pacho Ramos
2016-02-28 11:09 Pacho Ramos
2016-02-28  6:15 Matthias Maier
2016-02-28  6:15 Matthias Maier
2016-02-25 23:02 Andreas Hüttel
2015-12-27 13:07 Matthias Maier
2015-12-22 16:13 Matthias Maier
2015-09-07 16:24 Mikle Kolyada
2015-08-16 20:56 Mikle Kolyada
2015-08-14  4:15 Matthias Maier

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=1717903665.446a1d4c9f939371ed43f660285683c3c12e6c3e.ionen@gentoo \
    --to=ionen@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