Pacman rendered useless

Lockheed · 2012-01-18 09:33:24

I was trying to install yaourt-git, to do which I followed a guide

yaourt -G package-query-git yaourt-git
sudo pacman -Rs yaourt package-query
sudo pacman -Syu
cd package-query-git
makepkg -si
cd ../yaourt-git
makepkg -si

but I got stuck at the 5th line. I was told to run

pacman-key --init

and so I did, except now I cannot install anything with pacman, because I get this:

error: yajl: signature from "Dave Reisner <d@falconindy.com>" is unknown trust
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

jasonwryan · 2012-01-18 09:38:21

Read the news, or your .pacnew file...

Lockheed · 2012-01-18 09:45:15

Excellent. Thanks. For the record, the solution is:

To disable PGP key checking completely, add the following line under [Options] to /etc/pacman.conf:

SigLevel     = Never

wonder · 2012-01-18 09:47:47

is already there but you didn't merge pacman.conf.pacnew. In general you want to merge pacnew files.

stefanwilkens · 2012-01-18 10:07:45

Lockheed wrote:

Excellent. Thanks. For the record, the solution is:
To disable PGP key checking completely, add the following line under [Options] to /etc/pacman.conf:
SigLevel     = Never

In light of getting the message across:

If adding SigLevel = Never to /etc/pacman.conf is _all_ you did then you're doing it wrong.

Pacman, by definition, does not overwrite user configuration. The fact that you ran into those signature warnings means that pacman found that you changed your original pacman.conf in some way, thus meaning that you probably had some user configuration in that file. At this point, pacman installed the new pacman.conf to /etc/pacman.conf.pacnew, and told you about this in the terminal.

You _need_ to look at your current /etc/pacman.conf and the /etc/pacman.conf.pacnew files. You need to compare them and merge them:
https://wiki.archlinux.org/index.php/Pa … save_Files

If you do so, you'll find that /etc/pacman.conf.pacnew already has the option you manually put into your old pacman.conf. In fact, you'll find that that's not the only thing that changed, a whole block was added

# PGP signature checking
# NOTE: None of this will work without running `pacman-key --init` first.
# The compiled in default is equivalent to the following line. This requires
# you to locally sign and trust packager keys using `pacman-key` for them to be
# considered valid.
#SigLevel = Optional TrustedOnly
# If you wish to check signatures but avoid local sign and trust issues, use
# the following line. This will treat any key imported into pacman's keyring as
# trusted.
#SigLevel = Optional TrustAll
# For now, off by default unless you read the above.
SigLevel = Never

Lockheed · 2012-01-18 10:14:41

You are quite right. I had extra repositories added.
Thank you.

I just hope the new pacman/yaourt version will be able to update 'linux' packages automatically during system upgrade, because so far I had to run it manually as cumulative update did never built modules.

Last edited by Lockheed (2012-01-18 10:16:05)

bernarcher · 2012-01-18 12:07:35

Yaourt does work perfectly here with the new pacman. It did upgrad itself to 1.0-1.

So, if your current issues are solved, please mark this thread [SOLVED].

Arch Linux

#1 2012-01-18 09:33:24

Pacman rendered useless

#2 2012-01-18 09:38:21

Re: Pacman rendered useless

#3 2012-01-18 09:45:15

Re: Pacman rendered useless

#4 2012-01-18 09:47:47

Re: Pacman rendered useless

#5 2012-01-18 10:07:45

Re: Pacman rendered useless

#6 2012-01-18 10:14:41

Re: Pacman rendered useless

#7 2012-01-18 12:07:35

Re: Pacman rendered useless

Board footer