[deb package] Ubuntu 22.04 deprecates /

[almereyda]

What is the current behavior?

When running apt update on Ubuntu 22.04, a warning is thrown:

$ apt update
...
W: https://cli-assets.heroku.com/apt/./InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details.

This error is also appears when running the Ubuntu/Debian installation script from https://devcenter.heroku.com/articles/heroku-cli#install-with-ubuntu-debian-apt-get

What is the expected behavior?

apt does not complain about anything.

Which are known workarounds?

One can manually export the GPG key from apt-key and save a dearmoured copy in /usr/share/keyrins, plus has to add the signing key via a [signed-by=/usr/share/keyrings/heroku.gpg] declaration in /etc/apt/sources.list.d/heroku.list

References:

• Ubuntu: How to Fix “Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)” – Colek Colek
• apt - Key is stored in legacy trusted.gpg keyring after Ubuntu 22.04 update - Ask Ubuntu

[NJT145]

If there is any conflict caused by the ubuntu version, you can check the version number and do whatever is necessary according to that number. take a look at here: https://linuxize.com/post/how-to-check-your-ubuntu-version/
For the convertion of deprecated version of keys to supported new one, check these:
https://askubuntu.com/questions/1407632/key-is-stored-in-legacy-trusted-gpg-keyring-etc-apt-trusted-gpg
https://itsfoss.com/key-is-stored-in-legacy-trusted-gpg/

[NJT145]

Of course, the uninstallation process for heroku should check the fixed keyring, or this will cause more troubles... Didn't check that, so do it at your own risk until a Heroku developer answers this issue.

[NJT145]

still got this warning:

W: https://cli-assets.heroku.com/channels/stable/apt/./InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

And, for the uninstall script, there is no heroku-toolbelt. So, you can better change this script to

sudo apt-get remove heroku heroku*
sudo rm /etc/apt/sources.list.d/heroku.list

[sbosio]

This is being tracked by this GUS Work Item (Heroku internal).

There's a proposed solution on #1999, but here we are required a few more changes around the uninstall script that we should incorporate before reviewing and merging.