public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/winetricks/
Date: Sun, 22 May 2022 20:08:55 +0000 (UTC)	[thread overview]
Message-ID: <1653250109.eccce59ea0346db8c6a6c082ca144af86e8604c9.jsmolic@gentoo> (raw)

commit:     eccce59ea0346db8c6a6c082ca144af86e8604c9
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Sun May 22 20:08:29 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Sun May 22 20:08:29 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eccce59e

app-emulation/winetricks: Stabilize 20220411 amd64, #846995

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 app-emulation/winetricks/winetricks-20220411.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/winetricks/winetricks-20220411.ebuild b/app-emulation/winetricks/winetricks-20220411.ebuild
index 244cabfaef0f..4ad5136e7b23 100644
--- a/app-emulation/winetricks/winetricks-20220411.ebuild
+++ b/app-emulation/winetricks/winetricks-20220411.ebuild
@@ -11,7 +11,7 @@ if [[ ${PV} == "99999999" ]] ; then
 	SRC_URI=""
 else
 	SRC_URI="https://github.com/Winetricks/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="~amd64 ~x86"
+	KEYWORDS="amd64 ~x86"
 fi
 
 wtg="winetricks-gentoo-2012.11.24"


             reply	other threads:[~2022-05-22 20:09 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 20:08 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-03 14:58 [gentoo-commits] repo/gentoo:master commit in: app-emulation/winetricks/ Jimi Huotari
2024-09-07 21:26 Andreas Sturmlechner
2024-09-07 21:26 Andreas Sturmlechner
2024-06-28 20:33 Jimi Huotari
2024-05-30 15:01 Arthur Zamarin
2024-05-30 15:01 Arthur Zamarin
2024-01-06  0:13 Jimi Huotari
2023-12-16 21:06 Jimi Huotari
2023-05-06  9:49 Arthur Zamarin
2023-05-06  9:49 Arthur Zamarin
2023-02-12 12:42 Jimi Huotari
2023-02-12 12:42 Jimi Huotari
2022-05-23  6:43 Agostino Sarubbo
2022-04-13 13:13 Nick Sarnie
2022-04-13 13:13 Nick Sarnie
2021-08-27 14:07 Nick Sarnie
2021-04-16 21:32 Nick Sarnie
2021-04-11 20:08 Thomas Deutschmann
2021-04-11 11:11 Sam James
2021-03-06 17:40 Nick Sarnie
2021-03-06 17:40 Nick Sarnie
2021-01-18  3:41 Nick Sarnie
2020-11-17  0:42 Nick Sarnie
2020-11-15  1:27 Sam James
2020-11-14  2:16 Thomas Deutschmann
2020-11-14  2:16 Thomas Deutschmann
2020-07-27  4:41 Sam James
2020-07-14  0:34 Nick Sarnie
2020-04-15 23:42 Nick Sarnie
2019-12-25  0:26 Nick Sarnie
2019-12-24 23:33 Nick Sarnie
2019-11-26 23:17 Nick Sarnie
2019-11-26  0:58 Thomas Deutschmann
2019-11-17 11:26 Agostino Sarubbo
2019-09-16 22:20 Nick Sarnie
2019-09-16 22:20 Nick Sarnie
2019-06-21 22:17 Nick Sarnie
2019-05-27 12:50 Nick Sarnie
2019-05-20 11:01 Mikle Kolyada
2019-05-19 15:48 Thomas Deutschmann
2019-03-10 14:45 Nick Sarnie
2019-03-10 14:45 Nick Sarnie
2019-03-10 14:45 Nick Sarnie
2019-03-10 14:45 Nick Sarnie
2019-02-06 23:13 Nick Sarnie
2019-01-27 17:19 Nick Sarnie
2018-08-30  1:34 Austin English
2018-06-03 17:12 Nick Sarnie
2018-05-16 22:08 Nick Sarnie
2018-04-30 22:31 Nick Sarnie
2018-04-30 22:31 Nick Sarnie
2018-01-22 22:51 NP Hardass
2018-01-18 13:54 Mikle Kolyada
2017-09-05 23:50 Austin English
2017-09-05 23:50 Austin English
2017-06-18  5:25 Austin English
2017-06-18  5:25 Austin English
2017-05-17  6:33 Austin English
2017-04-10 17:58 NP Hardass
2017-03-28  6:57 Austin English
2016-07-29  4:48 NP Hardass
2016-07-29  4:48 NP Hardass
2016-07-10  0:48 NP Hardass
2016-07-10  0:48 NP Hardass
2016-05-13  1:50 NP Hardass
2016-05-13  1:50 NP Hardass
2016-03-30 23:12 NP Hardass
2016-03-30 23:12 NP Hardass
2016-03-30 23:12 NP Hardass
2016-01-19  2:04 NP Hardass
2015-11-17  2:12 NP Hardass
2015-11-17  2:12 NP Hardass
2015-11-14  0:26 NP Hardass
2015-11-14  0:26 NP Hardass
2015-09-27 13:44 NP Hardass

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=1653250109.eccce59ea0346db8c6a6c082ca144af86e8604c9.jsmolic@gentoo \
    --to=jsmolic@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