Re: An apt repository has changed its key
Bob Bernstein wrote: ... it looks like you are mixing Ubuntu and Debian? songbird
Re: An apt repository has changed its key
On 25.11.2020 00:56, Bob Bernstein wrote: On Wed, 25 Nov 2020, Alexander V. Makartsev wrote: URL doesn't open for me either. It looks like this ppa was removed and "now been folded into Ubuntu itself". [1] [1] https://launchpad.net/~wireguard Ah...thanks for finding the way into that rabbit-hole. Do you think it is permitted for a debian install to point its apt-get at a Ubuntu repository? There is no need for that rather dangerous action, because "wireguard" is available at least in Debian "buster-backports" repository. [1] [1] https://packages.debian.org/search?suite=all&searchon=names&keywords=wireguard -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: An apt repository has changed its key
On Tue, 24 Nov 2020 15:11:05 -0500 (EST) Bob Bernstein wrote: > > It is permitted! You get to keep any broken bits, of course! > > Hrrmm...I read your observation as a cautionary tale. And rightly so. Fortunately, there may be a better solution. Wireguard is available in buster backports, bullseye, and testing. https://packages.debian.org/search?searchon=names§ion=all&suite=all&arch=any&exact=0&keywords=wireguard You may wish to enable backports: https://backports.debian.org/Instructions/ -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: An apt repository has changed its key
Bob, quite a few times Ive installed Debian on Ubuntu ☺ Keep an eye on gcc and the versions of its libraries. Especially when building from source. Ubuntu is usually in advance of Debian in that respect. Bob are you the same BB I knew at UIC? I live down the road these days. On Tue, Nov 24, 2020, 2:11 PM Bob Bernstein wrote: > On Tue, 24 Nov 2020, Brian wrote: > > > It is permitted! You get to keep any broken bits, of course! > > Hrrmm...I read your observation as a cautionary tale. Perhaps > I need to investigate this a bit further, with, for example, the > vendor of the application that requires that "Wireguard" stuff. > > Thank you men of Debian! > > > -- > A person of great honour in Ireland (who was pleased to > stoop so low as to look into my mind) used to tell me that > my mind was like a conjured spirit, that would do mischief > if I did not give it employment. > Jonathan Swift > >
Re: An apt repository has changed its key
On Tue, 24 Nov 2020, Brian wrote: It is permitted! You get to keep any broken bits, of course! Hrrmm...I read your observation as a cautionary tale. Perhaps I need to investigate this a bit further, with, for example, the vendor of the application that requires that "Wireguard" stuff. Thank you men of Debian! -- A person of great honour in Ireland (who was pleased to stoop so low as to look into my mind) used to tell me that my mind was like a conjured spirit, that would do mischief if I did not give it employment. Jonathan Swift
Re: An apt repository has changed its key
On Tue 24 Nov 2020 at 14:56:46 -0500, Bob Bernstein wrote: > Do you think it is permitted for a debian install to point its apt-get at a > Ubuntu repository? It is permitted! You get to keep any broken bits, of course! -- Brian.
Re: An apt repository has changed its key
On Wed, 25 Nov 2020, Alexander V. Makartsev wrote: URL doesn't open for me either. It looks like this ppa was removed and "now been folded into Ubuntu itself". [1] [1] https://launchpad.net/~wireguard Ah...thanks for finding the way into that rabbit-hole. Do you think it is permitted for a debian install to point its apt-get at a Ubuntu repository? -- A person of great honour in Ireland (who was pleased to stoop so low as to look into my mind) used to tell me that my mind was like a conjured spirit, that would do mischief if I did not give it employment. Jonathan Swift
Re: An apt repository has changed its key
On 25.11.2020 00:19, Bob Bernstein wrote: At least, that's my diagnosis. Here's the pertinent line from an entry in my /etc/apt/sources.list.d/: deb http://ppa.launchpad.net/wireguard/wireguard/ubuntu focal main Here's the output of 'apt-get update': --snip-- 0% [Working] 0% [Connecting to debian.map.fastlydns.net (2a04:4e4 Err:1 http://ppa.launchpad.net/wireguard/wireguard/ubuntu focal InRelease 403 Forbidden [IP: 91.189.95.83 80] 0% [Connecting to debian.map.fastlydns.net (2a04:4e4 Hit:2 http://security.debian.org buster/updates InRelease 0% [Waiting for headers] Hit:3 http://deb.debian.org/debian buster InRelease [...] E: Failed to fetch http://ppa.launchpad.net/wireguard/wireguard/ubuntu/dists/focal/InRelease 403 Forbidden [IP: 91.189.95.83 80] E: The repository 'http://ppa.launchpad.net/wireguard/wireguard/ubuntu focal InRelease' is no longer 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. --snip-- That apt repo line, above, has worked for months. Iirc, this is not my first rodeo with this problem. I forget how I remedied it. I believe apt provides a nice solution for this, that will allow me to get the new key onto my machine? Thank you. URL doesn't open for me either. It looks like this ppa was removed and "now been folded into Ubuntu itself". [1] [1] https://launchpad.net/~wireguard -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: An apt repository has changed its key
On 11/24/2020 8:19 PM, Bob Bernstein wrote: At least, that's my diagnosis. Here's the pertinent line from an entry in my /etc/apt/sources.list.d/: deb http://ppa.launchpad.net/wireguard/wireguard/ubuntu focal main Here's the output of 'apt-get update': --snip-- 0% [Working] 0% [Connecting to debian.map.fastlydns.net (2a04:4e4 Err:1 http://ppa.launchpad.net/wireguard/wireguard/ubuntu focal InRelease 403 Forbidden [IP: 91.189.95.83 80] 0% [Connecting to debian.map.fastlydns.net (2a04:4e4 Hit:2 http://security.debian.org buster/updates InRelease 0% [Waiting for headers] Hit:3 http://deb.debian.org/debian buster InRelease [...] E: Failed to fetch http://ppa.launchpad.net/wireguard/wireguard/ubuntu/dists/focal/InRelease 403 Forbidden [IP: 91.189.95.83 80] Looks like the above IP is being blocked. -- John Doe
