From: kotajacob <kotajacob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] PolyMC package removal
Date: Tue, 18 Oct 2022 22:59:26 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40028@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
New issue by kotajacob on void-packages repository
https://github.com/void-linux/void-packages/issues/40028
Description:
There's been a [recent storm in the minecraft launcher](https://www.pcgamer.com/minecraft-launcher-project-spins-out-of-control-after-dev-hijacks-it-to-fight-leftist-queer-ideology/) world. PolyMC, a very popular launcher which we package, has been hijacked by a (previously mostly inactive) maintainer who has banned all other maintainers in a supposed act of "purging leftist queer ideology".
The other maintainers, and [many others in the community](https://twitter.com/modrinth/status/1582093129641234432?cxt=HHwWgMDQnbbU3PQrAAAA) are urging everyone whom had PolyMC installed to remove it immediately as it may be used to spread malware in the very near future.
The maintainers who were banned have forked the project and it now exists as PrismLauncher here: https://github.com/PrismLauncher/PrismLauncher
The code is basically the same as PolyMC, but with a few additional fixes already merged and of course the name change and original maintainers being restored. I'm perfectly happy to submit any package updates, but I wasn't sure if we should put in a package removal PR for polymc followed by a package creation for prism? Or if we should simply update the download URLs in polymc to point towards prism?
next reply other threads:[~2022-10-18 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 20:59 kotajacob [this message]
2022-10-18 21:11 ` classabbyamp
2022-10-18 21:12 ` classabbyamp
2022-10-18 21:17 ` kotajacob
2022-10-18 21:17 ` [ISSUE] [CLOSED] " kotajacob
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-40028@inbox.vuxu.org \
--to=kotajacob@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).