You are not logged in.
- Topics: Active | Unanswered
#1 2015-01-21 16:45:54
- slackcub
- Member
- Registered: 2009-03-14
- Posts: 144
[SOLVED] Issues installing key of unofficial repo
So I'm working on installing pipelight via the unofficial repositories, and I've run into an issue when adding the repo to pacman. Below is what I'm getting. I hope I'm just missing something, but I've looked through the forums and I can't seem to figure it out.
[root@laptop pacman.d]# mv gnupg/ ~/
[root@laptop pacman.d]# pacman-key --init
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
gpg: Generating pacman keyring master key...
gpg: key ******** marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: Done
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
[root@laptop pacman.d]# pacman-key --populate archlinux
==> Appending keys from archlinux.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Locally signing trusted keys in keyring...
-> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
-> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
-> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
-> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
-> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
-> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
-> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
-> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
-> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
-> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
-> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
-> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
-> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
-> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
-> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
-> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
-> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 5 signed: 62 trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2 valid: 60 signed: 5 trust: 60-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-01-22
[root@laptop pacman.d]# pacman-key --add /home/me/tmp/Release.key
==> Updating trust database...
gpg: no need for a trustdb check
[root@laptop pacman.d]# pacman -Syy
error: pipelight: signature from "Pipelight Dev Team (Package Builder) <webmaster@fds-team.de>" is unknown trust
:: Synchronizing package databases...
core 121.6 KiB 1643K/s 00:00 [####################################################################################################################] 100%
extra 1805.9 KiB 1901K/s 00:01 [####################################################################################################################] 100%
community 2.5 MiB 1993K/s 00:01 [####################################################################################################################] 100%
multilib 121.2 KiB 1731K/s 00:00 [####################################################################################################################] 100%
pipelight 129.1 KiB 269K/s 00:00 [####################################################################################################################] 100%
pipelight.sig 543.0 B 0.00B/s 00:00 [####################################################################################################################] 100%
error: pipelight: signature from "Pipelight Dev Team (Package Builder) <webmaster@fds-team.de>" is unknown trust
error: failed to update pipelight (invalid or corrupted database (PGP signature))
error: database 'pipelight' is not valid (invalid or corrupted database (PGP signature))
[root@laptop pacman.d]# grep -C3 pipelight /etc/pacman.conf
[multilib]
Include = /etc/pacman.d/mirrorlist
[pipelight]
Server = http://repos.fds-team.de/stable/arch/$arch
# An example of a custom package repository. See the pacman manpage for
[root@laptop pacman.d]# Last edited by slackcub (2015-01-21 17:13:47)
Offline
#2 2015-01-21 16:54:08
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 30,543
- Website
Re: [SOLVED] Issues installing key of unofficial repo
You're missing the local signing step(s): https://wiki.archlinux.org/index.php/Pa … icial_keys
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
#3 2015-01-21 17:13:34
- slackcub
- Member
- Registered: 2009-03-14
- Posts: 144
Re: [SOLVED] Issues installing key of unofficial repo
*facepalm* Thank you. I knew it was something simple, just couldn't figure out what.
Offline