public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "NP Hardass" <np-hardass@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine-mono/
Date: Thu, 28 Sep 2017 22:32:36 +0000 (UTC)	[thread overview]
Message-ID: <1506637944.489fae457c02827acb7bc123cb49e6484aabe64a.np-hardass@gentoo> (raw)

commit:     489fae457c02827acb7bc123cb49e6484aabe64a
Author:     NP-Hardass <NP-Hardass <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 27 19:49:13 2017 +0000
Commit:     NP Hardass <np-hardass <AT> gentoo <DOT> org>
CommitDate: Thu Sep 28 22:32:24 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=489fae45

app-emulation/wine-mono: Stable for amd64, x86

Package-Manager: Portage-2.3.10, Repoman-2.3.3

 app-emulation/wine-mono/wine-mono-4.6.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/wine-mono/wine-mono-4.6.4.ebuild b/app-emulation/wine-mono/wine-mono-4.6.4.ebuild
index 2479dca9023..a9f2ddc6bc2 100644
--- a/app-emulation/wine-mono/wine-mono-4.6.4.ebuild
+++ b/app-emulation/wine-mono/wine-mono-4.6.4.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://dl.winehq.org/wine/${PN}/${PV}/${P}.msi"
 
 LICENSE="BSD-2 GPL-2 LGPL-2.1 MIT MPL-1.1"
 SLOT="${PV}"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 x86"
 
 DEPEND="!!app-emulation/wine:0"
 


             reply	other threads:[~2017-09-28 22:32 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 22:32 NP Hardass [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07  2:49 [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine-mono/ Sam James
2024-10-07  2:44 Sam James
2024-09-12 14:40 Ionen Wolkens
2024-09-07  3:23 Ionen Wolkens
2024-07-03 16:31 Jakov Smolić
2024-07-03 16:31 Jakov Smolić
2024-06-27  6:55 Ionen Wolkens
2024-06-27  6:55 Ionen Wolkens
2024-04-23  9:33 Ionen Wolkens
2024-03-20  7:17 Ionen Wolkens
2024-02-11  3:39 Sam James
2024-02-11  3:39 Sam James
2024-02-06 13:33 Ionen Wolkens
2024-02-06  5:29 Ionen Wolkens
2024-01-27  1:00 Ionen Wolkens
2023-10-26 12:49 Sam James
2023-10-26 12:49 Sam James
2023-10-24 22:11 Ionen Wolkens
2023-10-06  9:23 Arthur Zamarin
2023-08-19  9:51 Ionen Wolkens
2023-08-06 11:51 Sam James
2023-05-19  8:17 Ionen Wolkens
2023-05-11 17:01 Ionen Wolkens
2023-04-17 20:44 Ionen Wolkens
2023-03-04 12:08 Ionen Wolkens
2023-02-26 18:35 Arthur Zamarin
2023-02-26  0:30 Sam James
2022-12-02  3:18 Ionen Wolkens
2022-12-02  3:18 Ionen Wolkens
2022-12-02  3:18 Ionen Wolkens
2022-12-02  3:18 Ionen Wolkens
2022-10-26 10:13 Ionen Wolkens
2022-09-10  9:48 Ionen Wolkens
2022-09-10  9:48 Ionen Wolkens
2022-06-04 15:25 Nick Sarnie
2022-04-11 23:22 Sam James
2022-04-09 15:01 Nick Sarnie
2022-03-12 11:51 Jakov Smolić
2022-02-13 15:06 Nick Sarnie
2021-12-05 16:08 Nick Sarnie
2021-11-23  2:51 Nick Sarnie
2021-09-26  0:35 Nick Sarnie
2021-08-01  0:25 Nick Sarnie
2021-08-01  0:25 Nick Sarnie
2021-08-01  0:09 Nick Sarnie
2021-08-01  0:09 Nick Sarnie
2021-06-05 15:57 Nick Sarnie
2021-06-05 15:57 Nick Sarnie
2021-04-11 17:16 Nick Sarnie
2021-02-28 15:39 Sam James
2021-02-28 15:39 Sam James
2021-02-13 20:03 Nick Sarnie
2020-10-11 20:21 Nick Sarnie
2020-06-20  3:36 Nick Sarnie
2020-04-25 21:32 Nick Sarnie
2020-04-13 16:53 Agostino Sarubbo
2020-04-12  7:30 Agostino Sarubbo
2019-11-16 17:13 Nick Sarnie
2019-09-28 17:26 Nick Sarnie
2019-08-17 17:19 Nick Sarnie
2019-06-22 21:55 Nick Sarnie
2019-06-04 14:45 Thomas Deutschmann
2019-05-02 22:25 Nick Sarnie
2019-04-16  1:46 Nick Sarnie
2019-03-17 14:29 Nick Sarnie
2019-03-03 11:59 Mikle Kolyada
2019-01-27 16:51 Nick Sarnie
2018-08-24  4:09 Mikle Kolyada
2018-08-02  2:44 Nick Sarnie
2018-07-09  0:41 Mikle Kolyada
2018-07-02  0:49 Thomas Deutschmann
2017-09-13 22:53 NP Hardass
2017-09-13 19:48 NP Hardass
2017-04-10 17:22 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=1506637944.489fae457c02827acb7bc123cb49e6484aabe64a.np-hardass@gentoo \
    --to=np-hardass@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