From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: virtualbox 6.1.34 is broken with Windows guests (please downgrade)
Date: Tue, 19 Jul 2022 02:21:43 +0200 [thread overview]
Message-ID: <20220719002143.P-X2_2gajH28WfTardqq8S8lGgNpI7RKHD6n0Lp8Ldg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38116@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/38116#issuecomment-1188462453
Comment:
> > ... no issue ... (after aplying the `-ffreestanding` patch).
>
> So, should others apply this patch now too (those who have this problem)?
No, the package should have that patch applied. We just don't know what's wrong in your case.
> `xbps-pkgdb -a` reports nothing.
I was asking for the report with virtualbox 6.1.34.
>
> still, there is a ticket and other complaints on the Internet
Yes, there's a ticket reports that problem, but we built with the patch addressed it. If I'm not broke, I could recover my glibc machine to test it :(
next prev parent reply other threads:[~2022-07-19 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 21:11 [ISSUE] " AngryPhantom
2022-07-18 0:53 ` sgn
2022-07-18 0:57 ` sgn
2022-07-18 1:04 ` slender100
2022-07-18 1:17 ` sgn
2022-07-18 8:18 ` AngryPhantom
2022-07-18 8:19 ` AngryPhantom
2022-07-18 11:32 ` dmarto
2022-07-18 12:57 ` sgn
2022-07-18 13:40 ` dmarto
2022-07-18 15:45 ` AngryPhantom
2022-07-19 0:21 ` sgn [this message]
2022-07-20 16:40 ` [ISSUE] [CLOSED] " AngryPhantom
2022-07-20 16:40 ` AngryPhantom
2022-09-06 8:27 ` alekspickle
2022-09-06 8:28 ` alekspickle
2022-09-06 8:29 ` alekspickle
2022-09-06 10:18 ` AngryPhantom
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=20220719002143.P-X2_2gajH28WfTardqq8S8lGgNpI7RKHD6n0Lp8Ldg@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).