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: Sun, 13 Mar 2016 03:05:10 +0000 (UTC) [thread overview]
Message-ID: <1457838293.5c96bff6d9fcbcd80e34207662f9c77454283066.np-hardass@gentoo> (raw)
commit: 5c96bff6d9fcbcd80e34207662f9c77454283066
Author: NP-Hardass <NP-Hardass <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 13 03:04:29 2016 +0000
Commit: NP Hardass <np-hardass <AT> gentoo <DOT> org>
CommitDate: Sun Mar 13 03:04:53 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5c96bff6
app-emulation/wine: Exclude staging patch that breaks -nls, Bug #577198
Package-Manager: portage-2.2.26
app-emulation/wine/wine-1.9.5.ebuild | 3 +++
1 file changed, 3 insertions(+)
diff --git a/app-emulation/wine/wine-1.9.5.ebuild b/app-emulation/wine/wine-1.9.5.ebuild
index b29387c..e7a9349 100644
--- a/app-emulation/wine/wine-1.9.5.ebuild
+++ b/app-emulation/wine/wine-1.9.5.ebuild
@@ -255,6 +255,9 @@ src_prepare() {
local STAGING_EXCLUDE=""
use pipelight || STAGING_EXCLUDE="${STAGING_EXCLUDE} -W Pipelight"
+ #577198 1.9.5 only
+ STAGING_EXCLUDE="${STAGING_EXCLUDE} -W makefiles-Disabled_Rules"
+
# Launch wine-staging patcher in a subshell, using epatch as a backend, and gitapply.sh as a backend for binary patches
ebegin "Running Wine-Staging patch installer"
(
next reply other threads:[~2016-03-13 3:05 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 3:05 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 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-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=1457838293.5c96bff6d9fcbcd80e34207662f9c77454283066.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