From: "NP Hardass" <np-hardass@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine/
Date: Mon, 13 Mar 2017 04:52:07 +0000 (UTC) [thread overview]
Message-ID: <1489380719.9d5e1e9d261d887b283d71b98f09d1ddb128df12.np-hardass@gentoo> (raw)
commit: 9d5e1e9d261d887b283d71b98f09d1ddb128df12
Author: NP-Hardass <NP-Hardass <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 13 04:35:57 2017 +0000
Commit: NP Hardass <np-hardass <AT> gentoo <DOT> org>
CommitDate: Mon Mar 13 04:51:59 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d5e1e9d
app-emulation/wine: Stabilize 2.0
Package-Manager: Portage-2.3.3, Repoman-2.3.1
app-emulation/wine/wine-2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-emulation/wine/wine-2.0.ebuild b/app-emulation/wine/wine-2.0.ebuild
index e037d416acf..b383399ced7 100644
--- a/app-emulation/wine/wine-2.0.ebuild
+++ b/app-emulation/wine/wine-2.0.ebuild
@@ -17,7 +17,7 @@ if [[ ${PV} == "9999" ]] ; then
else
MAJOR_V=$(get_version_component_range 1-2)
SRC_URI="https://dl.winehq.org/wine/source/${MAJOR_V}/${P}.tar.bz2"
- KEYWORDS="-* ~amd64 ~x86 ~x86-fbsd"
+ KEYWORDS="-* amd64 x86 ~x86-fbsd"
fi
VANILLA_GV="2.47"
next reply other threads:[~2017-03-13 4:52 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 4:52 NP Hardass [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-05 18:39 [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine/ Ulrich Müller
2017-08-23 17:10 Michał Górny
2017-04-29 20:52 NP Hardass
2017-03-23 9:24 NP Hardass
2017-03-23 9:24 NP Hardass
2017-03-23 9:24 NP Hardass
2017-03-23 9:24 NP Hardass
2017-03-13 4:52 NP Hardass
2017-03-13 0:47 NP Hardass
2017-03-12 21:26 NP Hardass
2017-01-25 23:02 NP Hardass
2017-01-19 0:09 NP Hardass
2017-01-09 18:52 NP Hardass
2017-01-09 18:50 NP Hardass
2017-01-09 18:09 NP Hardass
2017-01-02 17:36 Lars Wendler
2016-12-31 2:23 NP Hardass
2016-12-31 2:23 NP Hardass
2016-12-31 2:23 NP Hardass
2016-12-30 22:43 NP Hardass
2016-11-29 21:23 Austin English
2016-10-03 16:38 NP Hardass
2016-09-20 16:05 NP Hardass
2016-09-19 21:18 NP Hardass
2016-09-12 2:01 NP Hardass
2016-09-06 21:31 NP Hardass
2016-09-06 21:31 NP Hardass
2016-09-06 21:31 NP Hardass
2016-09-05 3:31 NP Hardass
2016-08-24 19:07 NP Hardass
2016-08-24 19:07 NP Hardass
2016-08-24 19:07 NP Hardass
2016-08-11 4:29 NP Hardass
2016-08-11 4:29 NP Hardass
2016-08-11 4:29 NP Hardass
2016-07-24 23:27 NP Hardass
2016-07-24 23:27 NP Hardass
2016-07-19 4:47 NP Hardass
2016-07-11 17:49 NP Hardass
2016-07-10 21:58 NP Hardass
2016-07-10 17:42 NP Hardass
2016-07-10 13:10 NP Hardass
2016-06-26 3:45 Austin English
2016-06-07 17:13 NP Hardass
2016-06-07 3:20 Austin English
2016-06-06 19:28 Pacho Ramos
2016-06-01 5:32 NP Hardass
2016-06-01 5:32 NP Hardass
2016-05-13 1:50 NP Hardass
2016-05-13 1:50 NP Hardass
2016-05-13 1:50 NP Hardass
2016-04-24 22:11 NP Hardass
2016-04-22 4:48 NP Hardass
2016-04-22 4:48 NP Hardass
2016-04-22 4:48 NP Hardass
2016-04-22 4:48 NP Hardass
2016-04-19 17:08 NP Hardass
2016-04-19 17:08 NP Hardass
2016-04-19 17:08 NP Hardass
2016-04-10 22:55 NP Hardass
2016-04-09 18:15 NP Hardass
2016-04-09 18:15 NP Hardass
2016-04-09 6:01 NP Hardass
2016-04-09 6:01 NP Hardass
2016-03-13 3:05 NP Hardass
2016-03-12 21:36 NP Hardass
2016-03-11 21:20 NP Hardass
2016-03-06 2:57 NP Hardass
2016-03-06 2:57 NP Hardass
2016-01-30 5:34 NP Hardass
2016-01-24 9:22 NP Hardass
2016-01-19 2:04 NP Hardass
2016-01-19 2:04 NP Hardass
2016-01-19 2:04 NP Hardass
2015-12-31 23:37 NP Hardass
2015-11-17 17:56 NP Hardass
2015-11-16 7:58 NP Hardass
2015-11-15 22:12 NP Hardass
2015-11-15 19:38 NP Hardass
2015-11-14 0:26 NP Hardass
2015-09-09 0:23 NP Hardass
2015-09-08 22:17 NP Hardass
2015-08-31 0:16 Alexandre Rostovtsev
2015-08-26 4:44 Alexandre Rostovtsev
2015-08-26 4:44 Alexandre Rostovtsev
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=1489380719.9d5e1e9d261d887b283d71b98f09d1ddb128df12.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