From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-eselect/eselect-wine/
Date: Wed, 23 Nov 2022 20:39:10 +0000 (UTC) [thread overview]
Message-ID: <1669235901.5bf131a2a1d9365fcf992468091ce2814782dc3e.ionen@gentoo> (raw)
commit: 5bf131a2a1d9365fcf992468091ce2814782dc3e
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 23 16:10:41 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Wed Nov 23 20:38:21 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5bf131a2
app-eselect/eselect-wine: unleash eselect-wine-2
Had expected to need a 2.0.1 before this, but no issues reported
so far. Let's see how it goes.
I do imagine it may cause some confusion given portage doesn't
make emerging it pretty and need to source /etc/profile at
least once, but have no "good" solutions to these beside warnings.
(also expecting a benign tinderbox bug about symlinks which can't
be silenced currently)
Closes: https://bugs.gentoo.org/632576
Closes: https://bugs.gentoo.org/657748
Closes: https://bugs.gentoo.org/717470
Closes: https://bugs.gentoo.org/874612
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
app-eselect/eselect-wine/eselect-wine-2.0.0.ebuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/app-eselect/eselect-wine/eselect-wine-2.0.0.ebuild b/app-eselect/eselect-wine/eselect-wine-2.0.0.ebuild
index 135547b3e333..92c25353de07 100644
--- a/app-eselect/eselect-wine/eselect-wine-2.0.0.ebuild
+++ b/app-eselect/eselect-wine/eselect-wine-2.0.0.ebuild
@@ -9,8 +9,7 @@ SRC_URI="https://gitweb.gentoo.org/proj/eselect-wine.git/snapshot/${P}.tar.bz2"
LICENSE="GPL-2+"
SLOT="0"
-# rewrite that really needs testing so it doesn't break any bottles
-#KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 ~x86"
RDEPEND="app-admin/eselect"
next reply other threads:[~2022-11-23 20:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 20:39 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-21 19:40 [gentoo-commits] repo/gentoo:master commit in: app-eselect/eselect-wine/ Arthur Zamarin
2025-02-14 8:00 Ionen Wolkens
2024-07-25 21:49 Ionen Wolkens
2023-08-23 15:41 Ionen Wolkens
2023-08-23 15:41 Ionen Wolkens
2023-08-06 4:32 Ionen Wolkens
2023-07-30 19:29 Ionen Wolkens
2023-07-30 16:18 Ionen Wolkens
2023-03-03 5:26 Ionen Wolkens
2022-12-29 20:29 Ionen Wolkens
2022-12-05 20:46 Ionen Wolkens
2022-12-03 22:40 Ionen Wolkens
2022-12-03 14:08 Ionen Wolkens
2022-12-03 13:52 Ionen Wolkens
2022-12-03 1:03 Ionen Wolkens
2022-12-02 3:18 Ionen Wolkens
2022-12-02 3:18 Ionen Wolkens
2022-11-29 0:27 Ionen Wolkens
2022-11-23 20:39 Ionen Wolkens
2022-11-20 17:12 Ionen Wolkens
2022-11-17 7:53 Ionen Wolkens
2022-11-16 17:01 Ionen Wolkens
2022-11-16 15:02 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-08-11 18:41 Nick Sarnie
2022-07-24 8:26 Joonas Niilola
2021-02-07 1:43 Sam James
2017-09-29 3:07 NP Hardass
2017-09-28 22:32 NP Hardass
2017-09-15 6:10 NP Hardass
2017-09-15 6:01 NP Hardass
2017-09-13 23:54 NP Hardass
2017-08-07 14:10 NP Hardass
2017-04-12 1:37 NP Hardass
2017-04-11 6:03 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=1669235901.5bf131a2a1d9365fcf992468091ce2814782dc3e.ionen@gentoo \
--to=ionen@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