moving here the latest news anouncement from Arch homepage
Having pacman verify packages
For the past six months, pacman's package verification features were turned off by default while we were figuring out the details of our public-key infrastructure.
They have finally been enabled in pacman-4.0.3-2; when you upgrade, you will be prompted to run:
pacman-key --populate archlinux
This sets up a local keyring for pacman, and populates it with the data needed to authenticate official packages. This includes five master keys used to authenticate Arch Linux packagers (developers and trusted users), so you do not need to know who joins or leaves the team: you only have to verify those five master keys once and for all. The populate command will prompt you to do so; please do this cautiously by checking the fingerprints displayed against those published on our website.
Then, merge your pacman.conf with pacman.conf.pacnew, that is, enable package verification through the SigLevel option, and you should be good to go.
Please, what do you mean with
'merge your pacman.conf with pacman.conf.pacnew
Sorry, I'm not expert with this language...
It is a standard operation in Arch Linux. Since file pacman.conf is maintained by each individual user, if an upgrade simply replaced the file, each user would lose any changes he had made. So, they create new file pacman.conf.pacnew, which you are to inspect for new/changed things that you do not have in your pacman.conf file and add/change them manually.
This is a double with my earlier post: http://bbs.archbang.org/viewtopic.php?id=2911
Thanks for your positive contributions to the forums lately which don't go unnoticed, but please search forums before posting to avoid double posting.
Getting your questions answered here at ArchBang Forums
Please! Always give hardware info, if there is a chance that 's relevant: #lspci -vnn
On Arch(bang) and Openbox: http://stillstup.blogspot.com/