Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Sep 27, 2017 at 08:45:31AM +0000, Görz, Eric wrote: > Dear list, > > yesterday i installed drbd9 on a fresh Proxmox 5 installation with this repo: > > deb http://packages.linbit.com/proxmox/ proxmox-5 drbd-9.0 > > Today i encounter the following error while updating: > > root at XXXX:~# apt update > Ign:1 http://ftp.de.debian.org/debian stretch InRelease > Ign:2 http://packages.linbit.com/proxmox proxmox-5 InRelease > Hit:3 http://ftp.de.debian.org/debian stretch Release > Hit:4 http://packages.linbit.com/proxmox proxmox-5 Release > Get:5 http://packages.linbit.com/proxmox proxmox-5 Release.gpg [195 B] > Get:7 http://security.debian.org stretch/updates InRelease [62.9 kB] > Ign:5 http://packages.linbit.com/proxmox proxmox-5 Release.gpg > Reading package lists... Done > W: GPG error: http://packages.linbit.com/proxmox proxmox-5 Release: The following signatures were invalid: BADSIG 53B3B037282B6E23 LINBIT Package and Repository Signing Key (2017) > E: The repository 'http://packages.linbit.com/proxmox proxmox-5 Release' 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. > > I've already reinstalled the key. Seems there is something broken? Hm, strange, I don't get that: root at pve2:~# apt update Ign:1 http://ftp.at.debian.org/debian stretch InRelease Hit:2 http://ftp.at.debian.org/debian stretch Release Ign:3 http://packages.linbit.com/proxmox proxmox-5 InRelease Get:4 http://security.debian.org stretch/updates InRelease [62.9 kB] Hit:6 http://packages.linbit.com/proxmox proxmox-5 Release Hit:8 http://download.proxmox.com/debian stretch InRelease Get:9 http://security.debian.org stretch/updates/main amd64 Packages [174 kB] Fetched 237 kB in 2s (86.8 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done Do you, or anyone else reading this, still get that error? Regards, rck