Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor Suggested Change To Installing Documentation #2094

Open
EvilSupahFly opened this issue Jun 24, 2023 · 5 comments
Open

Minor Suggested Change To Installing Documentation #2094

EvilSupahFly opened this issue Jun 24, 2023 · 5 comments

Comments

@EvilSupahFly
Copy link

EvilSupahFly commented Jun 24, 2023

Since Ubuntu 20.04, on Ubuntu and anything derived from it, the use of apt-key has been deprecated. Officially, users should manage keyring files in /etc/apt/trusted.gpg.d instead. Although apt-key still technically works as of "Jammy" - with some comnplaints - there's no guarantee it will continue to do so as Debian claimed it would be given the Red Shirt treatment in April of 2022.

There is a work-around published on Ask Ubuntu, if anybody wants to know the long way around, but I think it would be easier (and faster) to follow in the footsteps of Wine HQ, as their documentation has been updated accordingly.

It's not super urgent, but it's probably better to address this before apt-key is removed from production entirely and you get a slew of tickets for it.

Screenshot of terminal complaining about use of legacy key storage.

@ajh123
Copy link

ajh123 commented Jul 10, 2023

The main README states ..

PLEASE NOTE: Overviewer is currently unmaintained. PRs will not be merged and issues will not be addressed. The website and repository will remain online and accessible.

Instead please use the new working (“successor”) version of Overviewer supporting 1.20 worlds and textures.
https://github.com/GregoryAM-SP/The-Minecraft-Overviewer

@Gregory-AM
Copy link

Sadly, at the moment, I have not implemented any fixes towards Linux or Mac Machines.

I'm unsure as to this issue, or anything related to it as I'm a Windows Programmer.
But, since I do have a Chromebook, I will attempt to see what this issue may be, and see if there is anything I can do to fix it.

@EvilSupahFly
Copy link
Author

EvilSupahFly commented Jul 18, 2023

Sadly, at the moment, I have not implemented any fixes towards Linux or Mac Machines.

I'm unsure as to this issue, or anything related to it as I'm a Windows Programmer. But, since I do have a Chromebook, I will attempt to see what this issue may be, and see if there is anything I can do to fix it.

For testing purposes, I would suggest a VM, like Oracle's since Google locks down Chrome OS implementations, unless you're handy enough to bypass those measures, which is often more work than it's worth for what you get back in functionality.

@ajh123
Copy link

ajh123 commented Jul 18, 2023

Sadly, at the moment, I have not implemented any fixes towards Linux or Mac Machines.
I'm unsure as to this issue, or anything related to it as I'm a Windows Programmer. But, since I do have a Chromebook, I will attempt to see what this issue may be, and see if there is anything I can do to fix it.

For testing purposes, I would suggest a VM, like Oracle's since Google locks down Chrome OS implementations, unless you're handy enough to bypass those measures, which is often more work than it's worth for what you get back in functionality.

Or as I suggested in #2087 use Windows Subsystem for Linux

@Gregory-AM
Copy link

Gregory-AM commented Jul 19, 2023

@ajh123, Agreed. I can do this, the reason I wanted a second SSD was specifically for a Linux install since it's a good OS to use for development.

But, I'll be checking out the option to have a VM / Subsystem on Windows using the methods you've mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants