Warning: Key is stored in legacy trusted.gpg keyring

[kneekoo]

Describe the bug
The warnings are self-explanatory, we should store APT keys separately. The result of using the deprecated apt-key to add all PPAs into the same file (trusted.pgp) is a list of warnings in mintUpdate.

Screenshots

To Reproduce
Add a PPA, like the ones I have:
ppa:inkscape.dev/stable
ppa:libreoffice/ppa
ppa:minetestdevs/stable

Expected behavior
A clear and concise description of what you expected to happen.

Distribution:

• Linux Mint 21 Cinnamon

Software version:
mintUpdate 5.8.8

Logs:

W: http://ppa.launchpad.net/inkscape.dev/stable/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://ppa.launchpad.net/libreoffice/ppa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://ppa.launchpad.net/minetestdevs/stable/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

I used this guide to solve the issue, but this should be taken care of in mintUpdate and mintSources. Now that I think about it, mintUpdate is actually seeing the side effects of mintSources using the deprecated apt-key.

There's also a "quick and dirty" way to fix this, but it's only recommended after adding all PPAs. Otherwise it will be more complicated to deal with for the average/new user.

cd /etc/apt
sudo cp trusted.gpg trusted.gpg.d

[terr72]

This might be more related to mintupgrade, which takes care of the upgrading process.
I opened a bug report over there:
linuxmint/mintupgrade#58

It's also not just related to PPAs.
All 3rd party repositories like Google Earth, Virtualbox, WINE, Skype, ... are affected.

[kneekoo]

This might be more related to mintupgrade, which takes care of the upgrading process. I opened a bug report over there

Thanks, and technically yes. Practically it's also mintupdate's issue because this gets in the way of doing the regular updates. I'd rather see this cross-posted and hopefully get attention, than having to wait for 21.1 this Christmas.

This is one of those things that require some digging and knowing what to do and how to recover from a mistake, which is out of reach for the average users.

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[kneekoo]

Re-rested on Mint 21.3 Cinnamon with Update Manager (mintUpdate) 6.0.9, and this issue is now handled properly.