Github messages for voidlinux
 help / color / mirror / Atom feed
From: TrueTechie <TrueTechie@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] PolyMC Depends On Old Version of Java
Date: Sat, 13 Aug 2022 13:23:43 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38645@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

New issue by TrueTechie on void-packages repository

https://github.com/void-linux/void-packages/issues/38645

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.17_1 x86_64 GenuineIntel uptodate FFFFF

### Package(s) Affected

PolyMC-1.4.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The package recommends a version of Java compatible with the latest version of Minecraft on installation. After this, when launching a profile with the latest version of Minecraft, there is no error or need to manually install a later version of Java via `xbps`

### Actual behaviour

The package recommends Java version 11, far from the necessary versions 17 or 18 for running a modern version of Minecraft. I'll see about creating a PR to change this.

### Steps to reproduce

1. Install the package
2. Start the application
3. Set a Java runtime (default being 11)
4. Set up a Minecraft profile and launch
5. Note the launch fails requesting Java version 17 or 18

             reply	other threads:[~2022-08-13 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 11:23 TrueTechie [this message]
2022-08-13 16:56 ` classabbyamp
2022-08-13 16:56 ` [ISSUE] [CLOSED] " classabbyamp

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-38645@inbox.vuxu.org \
    --to=truetechie@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).