When I run sudo apt update I see this: W: https://download.docker.com/linux/ubuntu/dists/noble/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. As it’s only a warning I’m tempted to do nothing, but what do you a…

Hi, it appears to just mean that your gpg keys are not in the right place. apt-key(8) — apt — Debian testing — Debian Manpages *Recommended:* Instead of placing keys into the /etc/apt/trusted.gpg.d directory, you can place them anywhere on your filesystem by u…

[immagine] darkpixlz: rm -rf /etc/apt/trusted.gpg.d/* A word of caution to anyone visiting this in future, this is not the solution to your problem and improper handling of rm -rf commands can potentially nuke your whole system beyond repair. So please exercise caution. There is ample docume…

[immagine] itsbhanusharma: but the issue is not discourse specific In my case it arguably is Discourse specific (though not in the way you mean) as I only have the server for a Discourse installation that followed the standard installation instructions. But I’ll read the link you provided. T…

[immagine] Jonathan5: Though an idiot’s guide would be much appreciated. Take a full backup, set up a fresh instance of discourse and restore your backup there. That way you don’t need to mess with anything and in 99% of cases your issue will be gone.

I’d need an idiot’s guide for that too! For instance, I only learnt recently that a full backup includes not only the backup you get using the Discourse website but also the app.yml file.

[immagine] Jonathan5: I’d need an idiot’s guide for that too! If you’re not familiar with a shell, I would recommend downloading the backup off your current site and following standard restore procedure . However, if you’re even a little comfortable in the shell or don’t want to deal with con…

There are pretty elaborate guides already available for that: [immagine] Backup discourse from the command line Self-Hosting bookmark This guide covers how to back up and restore your Discourse site using command line tools, specifically designed for self-host…

[immagine] darkpixlz: However, if you’re even a little comfortable in the shell or don’t want to deal with configuring a temporary site then I would recommend doing a CLI restore . This look simple, thanks. I’d be using a Digital Ocean droplet so imagine would have to update the DNS “A” record…

[immagine] Jonathan5: I’d be using a Digital Ocean droplet so imagine would have to update the DNS “A” record afterwards to the new IP address. Correct, if the machine has a new public IP you need to update the A record to point to the new server. [immagine] Jonathan5: What about Amazon …

Thanks. I might do this soon then. I upgraded Ubuntu to 24.04 with Discourse in situ. It seemed to work all right, but this must just be an unforeseen consequence.

Avviso "La chiave è memorizzata nel keyring trusted.gpg legacy"

Supporto

Jonathan5 6 Marzo 2026, 11:15am 11

Grazie. Potrei farlo presto allora. Ho aggiornato Ubuntu a 24.04 con Discourse in situ. Sembrava funzionare bene, ma questa deve essere solo una conseguenza imprevista.

Argomento		Risposte	Visualizzazioni
"ignoring file '50unattended-upgrades.wcf-dist' in directory '/etc/apt/apt.conmf.d/' as it has an invalid filename extension Self-hosting	18	3566	Febbraio 20, 2017
Updating I get a "Configuring openssh-server" message about the "sshd_config" file Self-hosting	2	3250	Agosto 20, 2023
Discourse update error Self-hosting	35	2196	Gennaio 30, 2023
Trying to update Docker on DigitalOcean; stuck on Docker 19.03.13 😔 Support	17	309	Febbraio 10, 2025
Apt-get update fails inside container yarn repo not signed Bug	26	9022	Febbraio 20, 2023

Avviso "La chiave è memorizzata nel keyring trusted.gpg legacy"

Argomenti correlati