How to force reload an unsigned repository in Ubuntu and avoid the "GPG error, see apt-secure (8)"

GPG error or apt-secure (8)

Although Flatpak packages are gaining popularity with each passing day, I would dare to say that most of us continue to prefer repository software regardless of distribution. For that reason it is easy for, for example, in Ubuntu to add a repository to have the latest version of OBS Studio with its most up-to-date dependencies. But what if we do it and see the text "GPG error"? It is something that has a solution.

When we see the GPG error or ask us to see the apt-secure (8) manual page, what is happening is that we are trying to use an unsigned repository, or it is simply not available for our version of Debian / Ubuntu. This can happen, for example, if we are on a system that no longer receives or is not yet supported, such as Ubuntu 22.04 Jammy Jellifish that is in development right now. Keep in mind that by forcing the recharge, we will be skipping a security notice, so you have to be careful with this. Even if we use official sources, such as OBS or Pipewire, something could stop working. It's not a new bug, but we had nothing on it here at LxA.

Avoid the GPG error by editing the sources.list file

Doing so is pretty straightforward. Here we are going to use the Pipewire repository as an example, with which it is said that the problem of Kooha that freezes in the latest versions is solved (it was not my case in Jammy Jellyfish ...). For force reload, we would do the following:

  1. We have to add the repository in the sources.list file that is in / etc / apt, so the fastest way is to open a terminal and write:
sudo nano /etc/apt/sources.list
  1. We enter the password of our user.
  2. Now, at the end we will add the repository and mark it as trusted. In the case of Pipewire and for Ubuntu 21.10, or 22.04, since there is no "jammy" option, we would add the following:
deb [trusted=yes] http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu/ hirsute main
  1. Once the above is added, we press Ctrl + O to save, Enter to confirm and Ctrl + X to exit.

From what we have entered, "[trusted = yes]" is what marks it as trustworthy, then the URL of the repository goes and "hirsute" would be the version mark, 21.10 in the case of Ubuntu. As we have explained, it also works in Ubuntu 22.04, where it gives an error simply because it is not yet available for the version that will be released next April.

And that would be all. It's a simple process that can save us a lot of headaches, but we should not rule out the possibility that it gives us another. Personally, I would only recommend it for software that we need and is not available by other means, but that is the explanation.


The content of the article adheres to our principles of editorial ethics. To report an error click here!.

Be the first to comment

Leave a Comment

Your email address will not be published.

*

*

  1. Responsible for the data: AB Internet Networks 2008 SL
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

bool (true)