Debian: Updating package with PPA fails with error “gpg: no valid OpenPGP data found”

audaciousdebianpackage-managementppa

My operating system is Debian 9.1 with Cinnamon 3.2.7. I installed Audacious (version 3.7.2) from the Package Manager and want to update to the latest released. Per these instructions, I attempted to update by entering the following commands:

sudo add-apt-repository ppa:nilarimogard/webupd8   
sudo apt update   
sudo apt install audacious

After a prompt to press Enter, I received the following output:

gpg: keybox '/tmp/tmpseyl6p36/pubring.gpg' created  
gpg: /tmp/tmpseyl6p36/trustdb.gpg: trustdb created  
gpg: key 531EE72F4C9D234C: public key "Launchpad webupd8" imported  
gpg: no ultimately trusted keys found  
gpg: Total number processed: 1  
gpg:               imported: 1  
gpg: no valid OpenPGP data found.  
Exception in thread Thread-1:  
Traceback (most recent call last):  
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner  
    self.run()  
  File "/usr/lib/python3.5/threading.py", line 862, in run  
    self._target(*self._args, **self._kwargs)  
  File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 688, in addkey_func  
    func(**kwargs)  
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 386, in add_key  
    return apsk.add_ppa_signing_key()  
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 273, in add_ppa_signing_key  
    cleanup(tmp_keyring_dir)  
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 234, in cleanup  
    shutil.rmtree(tmp_keyring_dir)  
  File "/usr/lib/python3.5/shutil.py", line 480, in rmtree  
    _rmtree_safe_fd(fd, path, onerror)  
  File "/usr/lib/python3.5/shutil.py", line 438, in _rmtree_safe_fd  
    onerror(os.unlink, fullname, sys.exc_info())  
  File "/usr/lib/python3.5/shutil.py", line 436, in _rmtree_safe_fd  
    os.unlink(name, dir_fd=topfd)  
FileNotFoundError: [Errno 2] No such file or directory: 'S.gpg-agent.browser'

Then, when I attempted to run the update step (sudo apt-get install --only-upgrade audacious), I received more errors:

Ign:1 http://deb.debian.org/debian stretch InRelease  
Ign:2 http://www.scootersoftware.com bcompare4 InRelease                         
Ign:3 http://ftp.us.debian.org/debian stretch InRelease                          
Hit:4 http://deb.debian.org/debian stretch Release                               
Hit:5 http://www.scootersoftware.com bcompare4 Release                           
Hit:6 http://ftp.us.debian.org/debian stretch-updates InRelease                  
Hit:7 http://security.debian.org/debian-security stretch/updates InRelease       
Hit:8 http://ftp.us.debian.org/debian stretch Release                            
Ign:11 http://ppa.launchpad.net/alexanderk23/ppa/ubuntu artful InRelease         
Ign:13 http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu disco InRelease     
Err:14 http://ppa.launchpad.net/alexanderk23/ppa/ubuntu artful Release  
  404  Not Found  
Err:15 http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu disco Release  
  404  Not Found  
Reading package lists... Done  
E: The repository 'http://ppa.launchpad.net/alexanderk23/ppa/ubuntu artful 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.  
E: The repository 'http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu disco 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.

Finally, when I ran the install step (sudo apt install audacious), it said the latest was already installed. It must not have accepted the PPA.

Reading package lists... Done  
Building dependency tree         
Reading state information... Done  
audacious is already the newest version (3.7.2-1+b1).  
0 upgraded, 0 newly installed, 0 to remove and 241 not upgraded.

After browsing online, I entered the following commands to undo my changes:

sudo add-apt-repository --remove ppa:nilarimogard/webupd8  
sudo apt update  
sudo apt-key del 531EE72F4C9D234C  
sudo apt update

What additional commands do I need to run in order to get the PPA to add properly?

Best Answer

This doesn’t answer your question as stated, but it will give you a packaged version of Audacious 3.10 on Debian 9. Here’s how to rebuild the current Buster package on Debian 9:

enable Stretch backports, which we’ll need

echo deb http://deb.debian.org/debian stretch-backports main | sudo tee /etc/apt/sources.list.d/stretch-backports.list
sudo apt update

install some useful tools we’ll need
```
sudo apt install devscripts
```
switch to a temporary directory
```
cd /tmp
```

download the source packages

dget -xu http://deb.debian.org/debian/pool/main/a/audacious/audacious_3.10-1.dsc
dget -xu http://deb.debian.org/debian/pool/main/a/audacious-plugins/audacious-plugins_3.10-1.dsc

start building Audacious
```
cd audacious-3.10
```
build a meta-package with the build-dependencies (this will allow us to clean up later)
```
mk-build-deps debian/control
```

install it then move it out of the way

sudo apt install ./audacious-build-deps_3.10-1_all.deb
mv audacious-build-deps_3.10-1_all.deb ..

now build Audacious
```
dpkg-buildpackage -us -uc
```

install packages we’ll need to build the Audacious plugins (we can’t install Audacious on its own without those)

cd ..
sudo dpkg -i audacious-dev_3.10-1_amd64.deb libaudcore5_3.10-1_amd64.deb libaudgui5_3.10-1_amd64.deb libaudtag3_3.10-1_amd64.deb

same process to build the plugins (with an upgrade of debhelper to the Stretch backports version, required here)

cd audacious-plugins-3.10
mk-build-deps debian/control
sudo apt install -t stretch-backports debhelper
sudo apt install ./audacious-plugins-build-deps_3.10-1_amd64.deb
mv audacious-plugins-build-deps_3.10-1_amd64.deb ..
dpkg-buildpackage -us -uc

The build is complicated by the inter-dependencies between Audacious and its plugins, which is why you need to build Audacious first, the install its libraries and development package, then build the plugins. Once all that’s done you can install Audacious itself using the resulting package:

cd ..
sudo dpkg -i audacious_3.10-1_amd64.deb audacious-plugins_3.10-1_amd64.deb audacious-plugins-data_3.10-1_all.deb

To clean up the packages using during the build:

sudo apt purge audacious-dev build-essential debhelper devscripts gcc gcc-6 audacious-build-deps audacious-plugins-build-deps
sudo apt --purge autoremove

Related Solutions

Linux – Some packages in mint not updating

If you have added ppa directly with apt-add-repository command then it might setup the ppa for maya ie(Mint). I would ask you to check that out in software sources. (Search for software sources app in mint menu). There under the tab 'Other software'. Select the ppa you have installed.Click edit and change the option under 'Distribution' from 'maya' to 'precise'. Then save it run run update manager again.

If the above said option fails: It would of better if you could check which packages are being held back. If the package belongs to the ppa then nothing much can be done other than to disable that ppa. For that I would recommend ppa-purge or y ppa manager.

Regarding your doubt of Ign and Hits while updating software database, it's quite normal. And most of the ignored ones are translation packages. So dont worry. Only thing which you should worry is if at the end of update process it throws out error saying some packages couldn't be updated.

Debian – Understanding Apt Pinning Priority Restrictions

I don't understand why you are doing here. Why do you have a preferences setting for stable at all if you are running a stable system? As far I know, no preferences setting is necessary for stable in that case.

You don't explicitly say whether you are running a stable system (you really should say so), but if you are not, then I really have no idea what you are doing.

And if the release is on stable, then the usual thing to do for testing and unstable is to set their preferences to less than 100. I usually use 50.

And if you want to downgrade to stable, just do the following (assuming sane settings like the ones above) to downgrade pkgname1 and pkgname2:

apt-get install pkgname1/stable pkgname2/stable

This sets the specified packages to the target release stable.

Incidentally, mixing testing and/or unstable packages with an unstable system is generally a bad idea unless you know what you are doing. Some of the time it is Ok, but most of the time you need to use backports, either from Debian, or self-made.

Best Answer

Related Solutions

Linux – Some packages in mint not updating

Debian – Understanding Apt Pinning Priority Restrictions

Related Question