apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).

Discussion in 'ISPConfig 3 Priority Support' started by werd, Jan 14, 2026.

  1. werd

    werd New Member HowtoForge Supporter

    I am getting the following warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
    What are the steps to get this resolved?
    Thank you,
    Howard
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You get this error when you do what?
     
  3. werd

    werd New Member HowtoForge Supporter

    root@server1:~# sudo apt-get update
    Get:1 http://dl.hhvm.com/debian jessie InRelease [2411 B]
    Hit:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
    Hit:3 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
    Hit:4 http://archive.ubuntu.com/ubuntu noble InRelease
    Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease
    Hit:7 http://archive.ubuntu.com/ubuntu noble-backports InRelease
    Hit:8 http://security.ubuntu.com/ubuntu noble-security InRelease
    Err:1 http://dl.hhvm.com/debian jessie InRelease
    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4112585D386EB94
    Hit:10 https://deb.goaccess.io noble InRelease
    Hit:11 https://ppa.launchpadcontent.net/ondrej/php/ubuntu noble InRelease
    Ign:6 https://www.rhsupplyco.com/apt stable InRelease
    Err:12 https://www.rhsupplyco.com/apt stable Release
    404 Not Found [IP: 104.21.76.128 443]
    Hit:9 https://rspamd.com/apt-stable noble InRelease
    Reading package lists... Done
    W: GPG error: http://dl.hhvm.com/debian jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4112585D386EB94
    E: The repository 'http://dl.hhvm.com/debian jessie InRelease' is not signed.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
    E: The repository 'https://rhsupplyco.com/apt stable Release' does not have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
     
  4. remkoh

    remkoh Well-Known Member HowtoForge Supporter

    This is not how you got the info message (not an error).

    You did something afterwards to get it.
    Probably when trying to fix the hhvm.com repository signature.

    There also appears to be an issue with the rhsypplyco.com repository.
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    What OS is that? What all is added to /etc/apt/sources.list and /etc/apt/sources.list.d/* ?
    My guess is some repository there has outdated repository key. If that is the case, download and install the current key from that repository.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    The output looks a bit strange to me. Is this an Ubuntu 24.04 system? But you have a Debian Jesse HHVM repo enabled there? And what is https://www.rhsupplyco.com/apt repo?
     
  7. werd

    werd New Member HowtoForge Supporter

    I installed them by mistake. What is the best way to remove them?
     
  8. werd

    werd New Member HowtoForge Supporter

    : The repository 'https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu noble Release' does not have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
    ubuntu@ubuntu:~$ sudo apt-get update
    Ign:1 cdrom://Ubuntu 24.04.3 LTS _Noble Numbat_ - Release amd64 (20250805.1) noble InRelease
    Hit:2 cdrom://Ubuntu 24.04.3 LTS _Noble Numbat_ - Release amd64 (20250805.1) noble Release
    Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
    Hit:5 http://archive.ubuntu.com/ubuntu noble InRelease
    Hit:6 http://archive.ubuntu.com/ubuntu noble-updates InRelease
    Hit:7 http://archive.ubuntu.com/ubuntu noble-backports InRelease
    Ign:8 https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu noble InRelease
    Err:9 https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu noble Release
    404 Not Found [IP: 185.125.190.80 443]
    Reading package lists... Done
    E: The repository 'https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu noble Release' does not have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
    ubuntu@ubuntu:~$ sudo apt-get install unetbootin
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    E: Unable to locate package unetbootin
    ubuntu@ubuntu:~$

    Thoughts?
     
  9. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    It might be best to start again from an empty system and not install extra repositories. Especially not repositories that are not meant for Ubuntu 24.04.
    If you still want to remove them, depends on how you installed the extra repositories. If you used command add-apt-repository then use the same command with --remove added.
    Another way is removing the lines from /etc/apt/sources.list or the corresponding directory from /etc/apt/sources.list.d/ . But this has complications if something is already installed from those repositories. You should apt purge those installed packages first.
     
  10. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Why do you need unetbootin on an ISPConfig system? Is this an ISPConfig installation at all?
    If unetbootin is supposed to come from gezakovacs/ppa, it is not installed because that repository does not have a release file and thus repository is disabled.
    If you want to run ISPConfig, start from an empty system, use ISPConfig autoinstall.sh and do not add stuff that is not mentioned in the installation instructions. https://www.ispconfig.org/documentation/
    Install these extra stuffs on your workstation or some other host that is not for ISPConfig.
     

Share This Page