You are not logged in.
That's because you're trying to add it to the makepkg keyring, you have to use
pacman-key --recv-key <KEYID>
pacman-key --lsign <KEYID>
instead.
edit: or not? now I'm confused.
Last edited by Soukyuu (2015-01-11 11:50:56)
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
That's because you're trying to add it to the makepkg keyring, you have to use
pacman-key --recv-key <KEYID> pacman-key --lsign <KEYID>
instead.
edit: or not? now I'm confused.
If you're directing that at @enihcam, then it's the wrong solution. @enihcam is trying to build the package, not install it from graysky's repositories, hence the use of @enihcam's gpg keyring and not the pacman keyring. See allan's blog post on the two.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Yes, I probably should have quoted (and read their post more closely), sorry.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
enihcam wrote:clfarron4 wrote:==> Verifying source file signatures with gpg... linux-3.18.tar ... FAILED (unknown public key 79BE3E4300411886) patch-3.18.2 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build linux-ck.
It doesn't work.
Works here:
$ sudo gpg --recv-key 5EE46C4C gpg: keyserver receive failed: No keyserver available $ sudo gpg --lsign 5EE46C4C gpg: key "5EE46C4C" not found: No public key
If it doesn't work, you might need to head over to a keyserver like http://pgp.mit.edu, download the key and import it manually.
Also, don't use sudo when adding the key to YOUR keyring.
claire ~ % gpg --recv-key 5EE46C4C
gpg: key 5EE46C4C: public key "graysky (used to sign repo-ck packages) <graysky@archlinux.us>" imported
gpg: Total number processed: 1
gpg: imported: 1
claire ~ % gpg --keyserver http://pgp.mit.edu --recv-key 5EE46C4C
gpg: key 5EE46C4C: "graysky (used to sign repo-ck packages) <graysky@archlinux.us>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Thanks, here's what I got:
nanw@archnet ~ $ gpg --keyserver http://pgp.mit.edu --recv-key 5EE46C4C
gpg: directory '/home/nanw/.gnupg' created
gpg: new configuration file '/home/nanw/.gnupg/gpg.conf' created
gpg: WARNING: options in '/home/nanw/.gnupg/gpg.conf' are not yet active during this run
gpg: keybox '/home/nanw/.gnupg/pubring.kbx' created
gpg: /home/nanw/.gnupg/trustdb.gpg: trustdb created
gpg: key 5EE46C4C: public key "graysky (used to sign repo-ck packages) <graysky@archlinux.us>" imported
gpg: Total number processed: 1
gpg: imported: 1
nanw@archnet ~ $ gpg --lsign 5EE46C4C
pub rsa2048/5EE46C4C
created: 2012-12-11 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/7DA7DA52
created: 2012-12-11 expires: never usage: E
[ unknown] (1). graysky (used to sign repo-ck packages) <graysky@archlinux.us>
[ unknown] (2) [jpeg image of size 5969]
Really sign all user IDs? (y/N) y
gpg: no default secret key: No secret key
Key not changed so no update needed.
and after that, I still got the error 'unknown public key'. Can I just disable gpg check? how?
Last edited by enihcam (2015-01-17 04:38:39)
Offline
.
Last edited by cestlaz (2015-07-17 03:23:42)
Offline
See https://wiki.archlinux.org/index.php/Ma … e_checking
If necessary, you could disable the signature check with --skippgpcheck on the makepkg line
You are missing the keys for 79BE3E4300411886 & 38DBBDC86092693E which are listed in the PKGBUILD file
pub rsa4096/6092693E 2011-09-23 uid [ unknown] Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com> sub rsa4096/76D54749 2011-09-23 pub rsa2048/00411886 2011-09-20 uid [ unknown] Linus Torvalds <torvalds@linux-foundation.org> sub rsa2048/012F54CA 2011-09-20
Also note the green Tip section in the link above, if you add
keyserver-options auto-key-retrieve
to your ~/.gnupg/gpg.conf file, then the keys will be retrieved automatically.
If you want to install linux-ck from graysky's repo-ck, then you need graysky's key in your pacman-key ring. You don't need graysky's key in you personal keyring to build linux-ck.
Thanks, but
keyserver-options auto-key-retrieve
does not work either.
I also tried:
nanw@archnet ~/.gnupg $ gpg --recv-key 79BE3E4300411886
gpg: keyserver receive failed: No keyserver available
nanw@archnet ~/.gnupg $ gpg --recv-key 38DBBDC86092693E
gpg: keyserver receive failed: No keyserver available
How to make '--skippgpcheck' a permanent change to gpg?
Thanks.
Offline
This has been an ongoing issue for many months now, where I would have to run pacman's updater a few times until kernel upgrades were fully downloaded. The kernel upgrades would always stop transferring 1/3 . . . 1/2 way through. Today, though, was my first solid download. Idk if anything's has changed, but I thought I'd mention it.
Offline
This has been an ongoing issue for many months now, where I would have to run pacman's updater a few times until kernel upgrades were fully downloaded. The kernel upgrades would always stop transferring 1/3 . . . 1/2 way through. Today, though, was my first solid download. Idk if anything's has changed, but I thought I'd mention it.
https://wiki.archlinux.org/index.php/Re … _regularly
Graysky is using godaddy as his web host. Some of the transfers from their poorly implemented server end in an incomplete transfer. To combat this, list the repository address multiple times and pacman will automatically try the next available server. As repo-ck has only one address (no mirrors), use the same server line:
[repo-ck]
Server = http://repo-ck.com/$arch
Server = http://repo-ck.com/$arch
Server = http://repo-ck.com/$arch
Server = http://repo-ck.com/$arch
Server = http://repo-ck.com/$arch
Alternatively, change the pacman downloader to wget, which automatically resumes downloads.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
.
Last edited by cestlaz (2015-07-17 03:24:17)
Offline
enihcam wrote:Thanks, but
keyserver-options auto-key-retrieve
does not work either.
I also tried:
nanw@archnet ~/.gnupg $ gpg --recv-key 79BE3E4300411886 gpg: keyserver receive failed: No keyserver available nanw@archnet ~/.gnupg $ gpg --recv-key 38DBBDC86092693E gpg: keyserver receive failed: No keyserver available
EIther of these should work if you have a ~/.gnupg/gpg.conf file. The "No keyserver available" error might indicate you don't have the gpg.conf file.
Can you post the content of your ~/.gnupg/gpg.conf file?mine looks like:
cat ~/.gnupg/gpg.conf no-greeting no-permission-warning lock-never keyserver hkp://pgp.mit.edu:11371 keyserver-options timeout=10 auto-key-retrieve
The auto-key-retrieve works for me. I verified with gpg --list-keys before and after building linux-ck and noting the needed keys were initially not present but were present after the build completed.
I removed ~/.gnupg, and ran the commands, and finally everything worked. I don't have the original gpg.conf, but I believe it must have something wrong inside.
Thanks for help!
Offline
Hey - as noted in https://aur.archlinux.org/packages/broadcom-wl/ and https://bbs.archlinux.org/viewtopic.php?id=192287&p=4, someone found a patch (broadcom-sta-6.30.223.248-linux-3.18-null-pointer-crash.patch) which allows broadcom-wl to work on 3.18 kernels without crashing on Arch. I've already tested it with 3.18-ck from this repo (the bobcat version). Could you update the broadcom-wl packages on the repo to use that patch?
Avatar by Ditey: https://twitter.com/phrobitey
Offline
Beat you by 1 minute
Glad to hear that someone finally unfucked this for broadcom-wl folks. Updated broadcom-wl-ck with this patch for those of you ticking on linux-ck powered machines; [repo-ck] is updated as well.
Last edited by graysky (2015-01-20 21:05:43)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Beat you by 1 minute
graysky wrote:Glad to hear that someone finally unfucked this for broadcom-wl folks. Updated broadcom-wl-ck with this patch for those of you ticking on linux-ck powered machines; [repo-ck] is updated as well.
Thanks. Ended up compiling linux-lts-ck to tide me over while waiting for that to get fixed, and the process of doing that on my desktop with a different setup than my netbook and compiling it for my netbook made me appreciate your work a lot.
Avatar by Ditey: https://twitter.com/phrobitey
Offline
Thanks for the kind words. Enjoy.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
thanx for broadcom update.
at last i can remove 3.17.8.
p.s. works ok on ivybridge (compiled myself).
Last edited by chaonaut (2015-01-21 11:24:27)
— love is the law, love under wheel, — said aleister crowley and typed in his terminal:
usermod -a -G wheel love
Offline
@chaonaut and soukyuu - does 3.8.2-2-ARCH give panics?
I have been using the official 3.18.x kernel for a while now and no kernel panics. I guess it's something about the linux-ck kernel for bobcat that causes it as I'm not getting any issue on my C2D laptop
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
I hate to be that guy, but after reading through this thread's previous posts about key issues, I'm still getting the `unknown public key` errors, even after installing the keys.
$ sudo pacman-key -l
...
pub rsa2048/00411886 2011-09-20
uid [ full ] Linus Torvalds <torvalds@linux-foundation.org>
sub rsa2048/012F54CA 2011-09-20
pub rsa4096/6092693E 2011-09-23
uid [ full ] Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>
sub rsa4096/76D54749 2011-09-23
And then:
$ yaourt -Sa linux-ck
...
==> Verifying source file signatures with gpg...
linux-3.18.tar ... FAILED (unknown public key 79BE3E4300411886)
patch-3.18.4 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build linux-ck.
==> Restart building linux-ck ? [y/N]
==> ---------------------------------
==>
I'm sure it's a simple fix, right? I tried running `sudo pacman-key --refresh-keys`, changing the keyserver to "http://pgp.mit.edu", and running `sudo pacman -Scc`. I also tried removing "/etc/pacman.d/gnupg", running `sudo pacman-key --init`, and then running `sudo pacman-key --recv-key XXX` and `sudo pacman-key --lsign-key XXX` again. Does anyone have any ideas? Thanks in advance.
Last edited by GreenRaccoon23 (2015-01-29 19:51:40)
Offline
$ yaourt -Sa linux-ck ... ==> Verifying source file signatures with gpg... linux-3.18.tar ... FAILED (unknown public key 79BE3E4300411886) patch-3.18.4 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build linux-ck. ==> Restart building linux-ck ? [y/N] ==> --------------------------------- ==>
I'm sure it's a simple fix, right? I tried running `sudo pacman-key --refresh-keys`, changing the keyserver to "http://pgp.mit.edu", and running `sudo pacman -Scc`. I also tried removing "/etc/pacman.d/gnupg", running `sudo pacman-key --init`, and then running `sudo pacman-key --recv-key XXX` and `sudo pacman-key --lsign-key XXX` again. Does anyone have any ideas? Thanks in advance.
pacman-key manages the pacman keyrings, that is, those for repositories for installing pre-built packages.
The issue you're facing here is not a repository keyring, and thus you put it into YOUR keyring with gpg, not pacman-key. See the Wiki (or Allan's blog) for more details.
Last edited by clfarron4 (2015-01-29 20:05:40)
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
GreenRaccoon23 wrote:$ yaourt -Sa linux-ck ... ==> Verifying source file signatures with gpg... linux-3.18.tar ... FAILED (unknown public key 79BE3E4300411886) patch-3.18.4 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build linux-ck. ==> Restart building linux-ck ? [y/N] ==> --------------------------------- ==>
I'm sure it's a simple fix, right? I tried running `sudo pacman-key --refresh-keys`, changing the keyserver to "http://pgp.mit.edu", and running `sudo pacman -Scc`. I also tried removing "/etc/pacman.d/gnupg", running `sudo pacman-key --init`, and then running `sudo pacman-key --recv-key XXX` and `sudo pacman-key --lsign-key XXX` again. Does anyone have any ideas? Thanks in advance.
pacman-key manages the pacman keyrings, that is, those for repositories for installing pre-built packages.
The issue you're facing here is not a repository keyring, and thus you put it into YOUR keyring with gpg, not pacman-key. See the Wiki (or Allan's blog) for more details.
Ah I see. That was exactly it! When I read that blog post earlier, I read "gpg" as "pacman-key" for some reason. Thanks a ton!
Offline
I was having a weird problem installing the "linux-ck" package from the AUR, but I figured it out. I was missing the "objdump" binary on my computer. I have no idea how it was missing, since "binutils" was installed. Plus other packages I've installed had to have used it. No idea--maybe a recent Arch update removed it or something. If anyone else has this problem, reinstalling "binutils" fixes it.
Offline
Guys, please keep the conversation in this thread limited to issues or questions with repo-ck not general building issues. Thanks.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Is anyone on the nvidia-340xx branch experiencing "random" X deaths on startup? It started happening after updating (lib32-)nvidia-340xx-ck-core2 from 340.65-6 to 340.76-1
At first I thought it was just a coincidence, but installing arch on my main PC, I'm seeing the same behavior (-ck-k10).
Xorg logs say "failed to find any screen" and manual modprobe nvidia says either "no device" or "no such module". Rebooting miraculously makes things work, until it fails for some reason again... I don't have a "failed" log atm anymore, will provide as soon as it happens again.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
I run that on my atom based machine with no errors (ck-atom).
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
So today I had decided to install ck-sandybridge. I got welcomed by kernelpanic, it turned out to be missing initramfs in grub.cfg. Why did grub-mkconfig missed it ?
Offline
So today I had decided to install ck-sandybridge. I got welcomed by kernelpanic, it turned out to be missing initramfs in grub.cfg. Why did grub-mkconfig missed it ?
No idea. I tend to run os-prober before running grub-mkconfig, so it has detected what is there on the system.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline