From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 42342@debbugs.gnu.org
Subject: bug#42342: Wine64 segfaults (5.12/staging)
Date: Tue, 28 Jul 2020 18:53:20 +0200 [thread overview]
Message-ID: <87ft9bzim7.fsf@nckx> (raw)
In-Reply-To: <dd6d9d2a043c5c40a3edebc9c797d5c5b4721bdb.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Leo Prikler 写道：
> I'll use inferiors as a local workaround for the time being and
> wait
> for the problem to be fixed upstream. I'll also look into 5.9
> to 5.11
> and perhaps provide a proper downgrade patch later on.
I admit to being a bit confused. IIRC on #guix you reported that
wine-staging was broken, not wine64-staging. If you only want to
downgrade the latter, that's all right by me, but I consider that
one of the risks of using the staging branch to begin with.
Is there a reason you rely on staging, and the 64-bit version to
boot?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-07-28 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:53 bug#42342: Wine64 segfaults (5.12/staging) Leo Prikler
2020-07-13 12:24 ` Leo Prikler
2020-07-28 16:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-07-28 17:36 ` Leo Prikler
2020-07-28 10:01 ` Pierre Neidhardt
2020-07-28 15:58 ` Pierre Neidhardt
2020-07-28 16:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 16:28 ` Pierre Neidhardt
2020-07-28 16:41 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-29 10:33 ` Pierre Neidhardt
2020-07-30 14:54 ` Jakub Kądziołka
2020-07-31 12:37 ` pelzflorian (Florian Pelz)
2020-08-09 13:38 ` Pierre Neidhardt
2020-08-09 14:03 ` Pierre Neidhardt
2020-08-09 15:03 ` Jakub Kądziołka
2021-05-11 15:40 ` Leo Prikler
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=87ft9bzim7.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=42342@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.