From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Brian Munyao Longwe <blongwe@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Help! apt-get update fails, key deprecated....
Date: Wed, 1 May 2024 07:42:24 +0200 [thread overview]
Message-ID: <CAJUtOOh4cNyeB75=gj=S4320jAwUn0CHg8Fx-h2RdR2pWpEO6w@mail.gmail.com> (raw)
In-Reply-To: <CAHSdPfaJ-ZnQuCU27p8ob5MQ-z3feY8xP8EVfFtA23Fs5e2fyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
Thanks for letting us know, Brian. Also, for joining our new chat on Zulip.
The old one, on Matrix, is not used anymore. So we encourage anyone here to
join the current one:
https://chat.libreqos.io/join/fvu3cerayyaumo377xwvpev6/
Also, I kudos to you for finding out how to fix it on your own!
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Wed, May 1, 2024 at 4:06 AM Brian Munyao Longwe via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Hey guys - noticed some performance related problems and upon digging
> deeper found that my Libreqos is way out of date. I upgraded to 1.4 but
> apt-get update has not been working due to deprecated keys.
>
>
> W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
> W: http://stats.libreqos.io/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
> W: Failed to fetch https://repos.influxdata.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
> W: Some index files failed to download. They have been ignored, or old ones used instead.
>
> I must admit I am a total dummy on how to switch to the new gpg key
> method. Can some please give me (clear) steps to follow to get this done?
> Would also be nice to have the documentation updated so that newbies don't
> fall down this hole.
>
>
> Thanks!
>
>
> Brian
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 4190 bytes --]
prev parent reply other threads:[~2024-05-01 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 2:06 Brian Munyao Longwe
2024-05-01 5:42 ` Frantisek Borsik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJUtOOh4cNyeB75=gj=S4320jAwUn0CHg8Fx-h2RdR2pWpEO6w@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=blongwe@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox