Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dietpi-wireguard.list / Wireguard previously installed breaks APT (and dietpi-software) #2545

Closed
FabioEight opened this issue Feb 13, 2019 · 1 comment
Labels
Bug 🐞 Solution available 🥂 Definite solution has been done
Milestone

Comments

@FabioEight
Copy link

  • DietPi version | 6.21.1

  • Distro version | 9.6

  • Kernel version | Linux DietPi 4.14.79-v7+ Letsencrypt supports Free Noip.com Dynamic DNS #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

  • SBC device | RPi 3B+

  • Power supply used | 5V 2.5A

  • Was the software title installed freshly or updated/migrated? Fresh

  • Can this issue be replicated on a fresh installation of DietPi? Probably

  • 4dbf4340-cc8a-4b55-b691-377e8007f2bb

Steps to reproduce

  1. Install WireGuard
  2. Set WireGuard according to your needs, etc.
  3. Uninstall WireGuard
  4. apt-get update

Expected behaviour

  • apt-get update should complete accordingly.

Actual behaviour

  • GPG keys errors, breaking dietpi-software and apt-get upgrade:

Example:

W: GPG error: https://cdn-aws.deb.debian.org/debian sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 04EE7237B7D453EC
W: The repository 'https://deb.debian.org/debian sid InRelease' is not signed.

Extra details

Workaround:

root@DietPi:~# apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:2 https://archive.raspberrypi.org/debian stretch InRelease
Get:3 https://cdn-aws.deb.debian.org/debian sid InRelease [243 kB]
Ign:3 https://cdn-aws.deb.debian.org/debian sid InRelease
Fetched 243 kB in 3s (74.2 kB/s)
Reading package lists... Done
W: GPG error: https://cdn-aws.deb.debian.org/debian sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 04EE7237B7D453EC
W: The repository 'https://deb.debian.org/debian sid InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@DietPi:~# cat /etc/apt/sources.list && ls /etc/apt/sources.list.d/
deb http://raspbian.raspberrypi.org/raspbian stretch main contrib non-free rpi
dietpi-wireguard.list  raspi.list
root@DietPi:~# cat /etc/apt/sources.list.d/dietpi-wireguard.list
deb https://deb.debian.org/debian/ sid main
root@DietPi:~# rm  /etc/apt/sources.list.d/dietpi-wireguard.list
root@DietPi:~# apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:2 https://archive.raspberrypi.org/debian stretch InRelease
Reading package lists... Done

Since Wireguard has been uninstalled on my system, I think it should remove also the "dietpi-wireguard.list" which is breaking apt.
Now everything seems to be nominal.

@MichaIng
Copy link
Owner

MichaIng commented Feb 13, 2019

@XRay437
Thanks very much for your report.

Actually interesting that this missing key error does not appear on initial install of WireGuard... Thinking about it, addition a Debian repo to a Raspbian system should require to add the Debian keyring, however it seems not in this case, perhaps not as long as preferences limit it's use to the WireGuard package, not sure.

Since Wireguard has been uninstalled on my system, I think it should remove also the "dietpi-wireguard.list" which is breaking apt.

Jep that was intended but prevented by typo. Just fixed it, many thanks: Fourdee@770deb5
Changelog: Fourdee@484f347

@MichaIng MichaIng added Bug 🐞 Solution available 🥂 Definite solution has been done labels Feb 13, 2019
@MichaIng MichaIng added this to the v6.22 milestone Feb 13, 2019
@MichaIng MichaIng mentioned this issue Mar 3, 2019
@MichaIng MichaIng mentioned this issue Mar 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐞 Solution available 🥂 Definite solution has been done
Projects
None yet
Development

No branches or pull requests

2 participants