From: xlibun <xlibun@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Missing wine-gecko for x86_64
Date: Sat, 20 Jan 2024 22:50:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48309@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
New issue by xlibun on void-packages repository
https://github.com/void-linux/void-packages/issues/48309
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.11_1 x86_64 AuthenticAMD uptodate rrmFFF
### Package(s) Affected
wine-gecko-2.47.4_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Both 64-bit and 32-bit packages are supposed to exist.
### Actual behaviour
Only 32-bit version of the package exists, resulting in wine complaining about wine-gecko missing, when 64-bit application is run, e.g. old offline java installers.
### Steps to reproduce
Run any application that needs gecko.
next reply other threads:[~2024-01-20 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 21:50 xlibun [this message]
2024-02-01 20:04 ` Luciogi
2024-02-01 20:04 ` Luciogi
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48309@inbox.vuxu.org \
--to=xlibun@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).