You are not logged in.
Pages: 1
I've been struggling to install. sway for a minute. I was having a freezing issue with sway before and following a fix in the github for the same issue, I uninstalled sway and tried to reinstall sway from aur (vs community sway that I had) and wlroots. I kept getting
an error trying to install wlroots-git though that libseat and logind-provider weren't valid options. I tried messing around with that for an hour or so and gave up. I uninstalled all of that mess and went back to install everything using pacman. wlroots installed fine.
but sway, swaylock, and swayidle give me:
error: sway: signature from "Brett Cornwall <brett@i--b.com>" is unkown trustI don't know how to fix this.
Last edited by TheJaava (2021-08-02 10:38:44)
Offline
That was just asked here:
https://bbs.archlinux.org/viewtopic.php?id=268496
Bug report: https://bugs.archlinux.org/task/71704
As a workaround you could manually verify the signatures of these packages in the cache, then copy the packages (without signatures) to /tmp and use pacman -U to install.
For example:
pacman-key --verify /var/cache/pacman/pkg/swaybg-1.1-1-x86_64.pkg.tar.zst.sigLast edited by progandy (2021-08-02 09:30:34)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
thanks for pointing me to that.
pacman-key --verify /var/cache/pacman/pkg/swaybg-1.1-1-x86_64.pkg.tar.zst.sig
I tried this workaround. It gave me this error:
==> ERROR: The signature identified by /var/cache/pacman/pkg/swayidle-1.6-1-x86_64.pkg.tar.zst.sig could not be verified.Offline
That is just the command to verify the signature. It ends with an error since the signature has expired, but in the lines above you should see that the signature is valid, but comes from an expired key. Afterwards you'll still have to copy and install.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
That is just the command to verify the signature. It ends with an error since the signature has expired, but in the lines above you should see that the signature is valid, but comes from an expired key. Afterwards you'll still have to copy and install.
Ok, thanks. that worked. why does copying the pkg and using pacman -U work but using pacman -Sy doesn't?
Offline
It works because you are allowed to install packages without signatures from the local filesystem with pacman -U. Since you copied only the package and not the signature, there was no signature to check and pacman installed it. That is why I added the manual signature verification with pacman-key as an additional step.
Last edited by progandy (2021-08-02 09:53:43)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Pages: 1