Closed BMurri closed 1 year ago
As a temporary workaround you can disable the wslutilities repo in /etc/pacman.conf
#[wslutilities]
#Server = https://pkg.wslutiliti.es/arch/
afaik there are not that often updates to packages from that repo, correct me if I am wrong but I need pacman working.
Thanks for the report, I will update it tonight.
As temporary
sudo vim /etc/pacman.conf
SigLevel = Never
#LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
The key for the Arch Linux is updated.
You should do the following as root:
pacman-key -d A2861ABFD897DD37
#download the new key
wget https://pkg.wslutiliti.es/public.key
pacman-key --add public.key
#locally sign the new key
pacman-key --lsign-key 2D4C887EB08424F157151C493DD50AA7E055D853
NOTE: This will also affect Debian related builds. I will try to update that tomorrow since it's already 3am in the morning.
@patrick330602 Thank you
Thanks @patrick330602 for getting to this so fast. Will you let us know when the debian builds are updated?
Thanks @patrick330602 for getting to this so fast. Will you let us know when the debian builds are updated?
@willgladstone yep, I will also post updates on Mastodon at https://fosstodon.org/@wslutilities, on Twitter at https://twitter.com/wslutilities and directly on Blog at https://blog.wslutiliti.es
Debian and Kali builds are also updated: https://blog.wslutiliti.es/2023/06/16/key-update/index.html
Windows Version
Windows 11
Windows Build Number
22621
WSL Version
WSL 2
Distro Version
ManjaroLinux 23.0.0
WSL Utilities Version
unknown
Describe the bug
The
WSL Utilities Package Signing Key <contact@wslutiliti.es>
signing key has expired.Steps to Reproduce
sudo pacman -Syu
followed by theEnter
keySee the following error message x2 followed by the subsequent error message
Expected behavior
updating the packages on my system would succeed.
Additional context
running
pacman-key -l
produces the following:Code of Conduct