From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/spice-vdagent/
Date: Mon, 12 Apr 2021 16:04:30 +0000 (UTC) [thread overview]
Message-ID: <1618243399.ac2d1c9307a6b2082cb8de3880084295adfe8364.sam@gentoo> (raw)
commit: ac2d1c9307a6b2082cb8de3880084295adfe8364
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 12 16:03:19 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 12 16:03:19 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ac2d1c93
app-emulation/spice-vdagent: Revert "Stabilize 0.21.0 amd64, #753956"
Apologies - my script chucked this into the 'success' bin after I killed the
test for hanging. Investigating.
(I am not aware of any actual runtime issues with this package, but we should
do this to be safe.)
This reverts commit 5c1fa98b7829ef8086092975d491c53c70cc14e7.
Bug: https://bugs.gentoo.org/753956
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-emulation/spice-vdagent/spice-vdagent-0.21.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-emulation/spice-vdagent/spice-vdagent-0.21.0.ebuild b/app-emulation/spice-vdagent/spice-vdagent-0.21.0.ebuild
index 8d228a8f9fa..ea8f4936384 100644
--- a/app-emulation/spice-vdagent/spice-vdagent-0.21.0.ebuild
+++ b/app-emulation/spice-vdagent/spice-vdagent-0.21.0.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.spice-space.org/download/releases/${P}.tar.bz2"
LICENSE="LGPL-2.1"
SLOT="0"
-KEYWORDS="amd64 ~x86"
+KEYWORDS="~amd64 ~x86"
IUSE="gtk selinux systemd"
CDEPEND="
next reply other threads:[~2021-04-12 16:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 16:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 11:01 [gentoo-commits] repo/gentoo:master commit in: app-emulation/spice-vdagent/ WANG Xuerui
2023-06-18 2:18 Matthias Maier
2023-06-18 2:07 Matthias Maier
2023-03-04 8:39 Joonas Niilola
2023-03-04 8:39 Joonas Niilola
2023-03-04 5:38 Arthur Zamarin
2022-06-24 9:17 Arthur Zamarin
2022-06-12 8:04 Joonas Niilola
2022-06-12 8:04 Joonas Niilola
2022-03-09 23:12 Sam James
2022-01-06 14:03 Joonas Niilola
2022-01-06 14:03 Joonas Niilola
2022-01-06 13:38 Joonas Niilola
2021-09-26 19:36 Conrad Kostecki
2021-04-04 18:35 Matthias Maier
2021-04-04 18:35 Matthias Maier
2020-10-04 15:20 Mikle Kolyada
2020-04-18 19:06 Matthias Maier
2020-04-18 18:56 Matthias Maier
2020-03-15 18:41 Agostino Sarubbo
2020-03-15 18:26 Agostino Sarubbo
2020-03-14 20:59 Matthias Maier
2020-03-14 20:57 Matthias Maier
2019-10-15 16:33 Matthias Maier
2019-10-15 16:11 Matthias Maier
2019-09-22 2:29 Matthias Maier
2019-07-28 19:39 Matthias Maier
2019-07-28 19:39 Matthias Maier
2018-05-22 23:06 Aaron Bauman
2018-03-29 15:19 Thomas Deutschmann
2018-03-27 7:42 Jeroen Roovers
2018-03-27 7:42 Jeroen Roovers
2018-03-19 19:50 Agostino Sarubbo
2018-03-19 16:09 Matthias Maier
2017-08-17 17:06 Michał Górny
2017-06-14 14:24 Matthias Maier
2017-05-11 14:24 Matthias Maier
2017-05-11 8:37 Agostino Sarubbo
2017-05-11 7:51 Agostino Sarubbo
2017-05-11 5:19 Matthias Maier
2015-11-18 21:15 Matthias Maier
2015-08-22 19:25 Matthias Maier
2015-08-14 5:24 Matthias Maier
2015-08-14 5:24 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=1618243399.ac2d1c9307a6b2082cb8de3880084295adfe8364.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