Pacman-key problem

A new install from September CD iso. I went through install process but dumped at package install with unsigned or corrupted package error.
I burned another disc, same problem, restarted but installed Base only (I initially tried base & base-devel) to get a working box, and then updated this.
Rebooted and attempted to install base-devel, but still unsigned package error.
Next I used pacman -Sc to remove uninstalled packages (in case a corrupt package was in cache) but the same result. I changed mirror, but this did not resolve problem.
Next step was deleting gnupg & rebuilding (pacman-key --init, etc) but still unsigned package/corrupt error when I tried to install base-devel.
I installed each package in group individually, and found the error came with cloog, followed further and found dependency isl-0.10.1-1 was unsigned/corrupt package. Looking through forums, news and don't see anything regarding this so (giving that this iso has been around a week or two) I assume the problem is at my end somewhere.
Installed links & downloaded package, installed with pacman -U (this suggests that the package was not corrupt) and then installed cloog, followed by rest of base-devel.
What I don't understand is isl, cloog, gcc all have the same maintainer and therefore (presumably) signed by the same person. Why should I get an unsigned error for just one of the maintainers' packages?

Thanks for your thoughts, this was a fresh installation of the latest CD ISO. I downloaded/burned a second one with the same result.
Base-devel would not install as isl-0-10.1-1 was not securely signed (according to my installation).
I was able to download isl package and install, when 'pacman -S base-dev' worked, and system is now running fine. (just have to sort out this 'windows' printer now - thanks HP)

Similar Messages

[SOLVED] Can't sign key with pacman-key

I've been reading and digging all over the place but I can't seem to find anything on this.
1. I have created my own keys for signing packages that I want to put in a local repo so I don't have to compile the same package over and over on all my machines.
2. I have imported said key using sudo pacman-key --add rdjack21.pgp
3. Used sudo pacman-key --lsign rdjack21 I get this output:
-> Locally signing key rdjack21...
==> ERROR: rdjack21 could not be locally signed.
4. Ok so lets sudo pacman-key --edit rdjack21 output:
gpg> sign
pub rsa2048/3D1B5544
created: 2014-11-30 expires: never usage: SC
trust: ultimate validity: ultimate
Primary key fingerprint: B0D7 C728 31FA B2B0 6A3C 7086 DC7F DE0C 3D1B 5544
Richard Jackson <[email protected]>
Are you sure that you want to sign this key with your
key "Pacman Keyring Master Key <pacman@localhost>" (645ECB0E)
Really sign? (y/N) y
gpg: signing failed: No pinentry
gpg: signing failed: No pinentry
gpg>
5. To hack this and make pacman work with my local repo signed by the rdjack21 key I had to change the trust to ultimate but I do not like that solution. I would prefer to sign the key and move the trust back down to full which is where it should be.
This is happening on all of my boxes not just one of them. I did find something on the web about "No pinentry" message above and the sugestion was to change the owner of the tty I'm using to be root for the signing to work but that did not work for me (su'ed to root first instead of running everything with sudo).
While changeing the trust works that just feels wrong to me. I really should beable to sign the key.
Last edited by rdjack21 (2014-12-01 01:50:05)

Taking a clue post gnupg 2.1.0-4 upgrade breaks passphrase via STDIN I was able to solve the problem and I can now sign keys.
The solution is add "pinentry-mode loopback" to /etc/pacman.d/gnupg/gpg.conf
And create the file /etc/pacman.d/gnupg/gpg-agent.conf and put "allow-loopback-pinentry" in the file.
Once that is done everythings works as expected!
Marking this as solved.

Pacman-key isn't working

pacman-key --init
gpg: Generating pacman keyring master key...
gpg: agent_genkey failed: End of file
gpg: key generation failed: End of file
gpg: Done
==> Updating trust database...
gpg: no need for a trustdb check
Whoa... I was googling around and no one seems to have encountered this problem before. I had JUST chrooted into the environment to install:
I was following this pretty carefully as far as I can tell:
https://wiki.archlinux.org/index.php/In … ting_Linux
Any guesses? I tried following the tips on dbus etc. None of these tips seemed helpful cuz none of those files exist. This is just the bootstrap installer.
Thanks, Oh MySQL !!

Did you try generating more entropy?
https://wiki.archlinux.org/index.php/Pa … he_keyring

Pacman-key --edit-key without any TTY

Hi, I want to enable package signing on my vServer.
The problem is there is no TTY available.
# LANG=C pacman-key --edit-key 0x6AC6A4C2 ...
gpg: cannot open tty `/dev/tty': No such file or directory
==> ERROR: The key identified by 0x6AC6A4C2 could not be edited.
After adding "no-tty" to gpg.conf:
gpg: Sorry, no terminal at all requested - can't get input
==> ERROR: The key identified by 0x6AC6A4C2 could not be edited.
Please help me to solve this.
Thanks
- Radioactiveman

I have copied the gnupg directory from my PC to the server but that should be just a workaround.
Does nobody have an idea?

Pacman.conf problem [solved]

Hi im having a problem with yaourt, and packer and i cant also install any package form Aur for example:
packer -S opencascade
grep: /etc/pacman.conf: Permission denied
error: config file /etc/pacman.conf could not be read: Permission denied
error: config file /etc/pacman.conf could not be read: Permission denied
Aur Targets (1): opencascade
Proceed with installation? [Y/n] y
Dependencies for `opencascade' are not met, not building..
i have the same problem with yaourt
if i try to install from a tarball for example i get this
makepkg -s
==> Making package: plank-bzr 820-1 (Fri Jun 7 13:06:26 ART 2013)
==> Checking runtime dependencies...
error: config file /etc/pacman.conf could not be read: Permission denied
==> ERROR: 'pacman' returned a fatal error (1):
[dam2@dam1d plank-bzr]$
i installed arch linux again yesterday and i copy the pacman.conf file that i have in my older arch linux to my new one
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
modedit: added code tags /Xyne
Last edited by adcdam (2013-06-07 19:28:32)

grep: /etc/pacman.conf: Permission denied
error: config file /etc/pacman.conf could not be read: Permission denied
error: config file /etc/pacman.conf could not be read: Permission denied
This tells you that you have incorrectly configured permissions when you copied the file. Fix that with
chmod 644 /etc/pacman.conf
Also note that I have added code tags ([code]) to your post. Please use them in the future when you post command output or file contents.

Follow up to my Luma Key problem

Hi again,
Tom has answered to my Luma Key problem of bad quality by recomending me to put the oval form under my clip instead from above, and it worked verz well.
But now I have another problem, I want now my oval to cross disolve to have the full scene that is now under to come gradually fully on screen. I have a cross disolve at the begining and at the end of the oval. Its fine for the oval to come gradually from full black screen to an oval with behind the 2nd scene, but when it shall starts to disolve, nothing happens. I also try with the pen, adding points and then pulling down in order to have the oval clip gradually dissolving, but nothing works ! Any clue ?
Thanks,
Nic

Nicolas,
One way to do this is:
- Oval on V1
- Clip1 on V2 with Composite Mode > Travel Matte Luma
- Clip1 also on V3. Change it's opacity so it is 0 until the required number of frames before the end of the Oval. Then increase it's opacity to 100 at the end of the Oval.
There might be a more efficient way to do this.

[SOLVED] Pacman Key Signing Strange Activity

Hi,
I was just setting up the package verification system with pacman when I noticed it was doing something unusual. When I ran:
pacman-key --init
instead of waiting for entropy, it just returned the prompt. Next, when I ran:
pacman-key --populate archlinux
it seemed to go through the entire signing process itself, stating that they didn't need to be signed again (sorry for the vagueness as I can't fetch exactly what it said by redirecting it into a file or something). The point is, usually I have to confirm each signature.
Is this normal?
Last edited by Mindstormscreator (2012-08-26 15:42:40)

Does the contents of /etc/pacman.d/gnupg look normal? You could compare that directory with the one on the live media (diff -rq) to test that theory.
When I set up package signing, I think I signed five master keys manually which I'd compared from two somewhat independent sources. After that, I don't remember having to *sign* any more signatures but only to confirm it was OK to import them. And now pacman seems to handle much of that automatically... But it is hard to imagine it would be meant to sign the master keys automatically since that would seem to undermine the point of having them in the first place.
On a fresh install, too, the init should take longer because so little is going on. (Hence all the threads here about it hanging because people haven't read the instructions for creating entropy .)

Circular: can't install libusb-compat for `pacman-key --init` [SOLVED]

So like a lot of people on here have upgraded to pacman 4.
I can't run `pacman-key --init` to update the keyring:
[stuart@myhost ~]$ sudo pacman-key --init
Password:
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
chmod: cannot access `/etc/pacman.d/gnupg/trustdb.gpg': No such file or directory
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
==> Updating trust database...
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
And because of signature issues can't install libusb-compat:
[stuart@myhost ~]$ sudo pacman -S libusb-compat
Password:
resolving dependencies...
looking for inter-conflicts...
Targets (1): libusb-compat-0.1.3-2
Total Installed Size: 0.06 MiB
Net Upgrade Size: -0.02 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [######################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Last edited by Skipper_the_eye_child (2012-01-26 19:24:00)

That worked - thanks. It'd have helped had I remembered to write over pacman.conf of course! I've not done any mainentance for while, got a little rusty i'm afraid.
Last edited by Skipper_the_eye_child (2012-04-11 14:02:52)

[SOLVED] pacman signature problem (haskell repo)

Hi,
Tried to enable unofficial haskell repo (this is a config which runs on another box):
[haskell]
# Arch-Haskell repository
# Discussion: http://www.haskell.org/mailman/listinfo/arch-haskell
Server = http://xsounds.org/~haskell/$arch
# Server = http://www.kiwilight.com/haskell/$arch
Got this:
$ sudo pacman-key -r 4209170B
gpg: requesting key 4209170B from hkp server pool.sks-keyservers.net
gpg: key 4209170B: "ArchHaskell (Magnus Therning) <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
==> Updating trust database...
gpg: next trustdb check due at 2014-01-22
$ sudo pacman -Syy
error: haskell: signature from "ArchHaskell (Magnus Therning) <[email protected]>" is unknown trust
:: Synchronizing package databases...
core 105.4 KiB 13.4K/s 00:08 [############] 100%
haskell 243.0 KiB 39.1K/s 00:06 [############] 100%
haskell.sig 96.0 B 0.00B/s 00:00 [############] 100%
error: haskell: signature from "ArchHaskell (Magnus Therning) <[email protected]>" is unknown trust
error: failed to update haskell (invalid or corrupted database (PGP signature))
extra 1516.4 KiB 23.0K/s 01:06 [############] 100%
community 1943.1 KiB 39.2K/s 00:50 [############] 100%
multilib 106.2 KiB 358K/s 00:00 [############] 100%
error: database 'haskell' is not valid (invalid or corrupted database (PGP signature))
What's wrong?
Last edited by Llama (2013-05-01 20:02:02)

Allan wrote:It is a key that is not signed by the Arch master keys, so you have to manually assign it trust.
Thanks, Allan! It's your inherent modesty which prevented you from giving this link, I presume.
$ sudo pacman-key --lsign 4209170B
[sudo] password for alexey:
-> Locally signing key 4209170B...
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 64 trust: 1-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2 valid: 64 signed: 1 trust: 64-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2014-01-22
$ sudo pacman -Syy
:: Synchronizing package databases...
core 105.4 KiB 12.9M/s 00:00 [#############] 100%
haskell 243.0 KiB 11.9M/s 00:00 [#############] 100%
haskell.sig 96.0 B 0.00B/s 00:00 [#############] 100%
extra 1516.4 KiB 350K/s 00:04 [#############] 100%
community 1943.0 KiB 6.32M/s 00:00 [#############] 100%
multilib 106.2 KiB 10.4M/s 00:00 [#############] 100%
$
Is it enough? The article has a lot more, not for hoi polloi sometimes...
Last edited by Llama (2013-04-29 11:35:38)

I am running CC on Windows 7. My Control key is sticking only in PPS. It is not a sticky key problem

I am running CC on Windows 7. My Control key is sticking only in PPS. It is not a sticky key problem and I am not running any similar program.

yes, photoshop.
Col. 3:17
Sam Collins

'Keys' problem when trying to re install 10.2 on Power Mac G4

Have had my Power Mac G4 wiped clean prior to selling and am now trying to reinstall 10.2.
Install disc one reached the end of its loading process and then froze.
Install disc two did not respond when loaded.
Put install disc one back in while holding down 'C' key. Started to install but soon stopped.
Went to Disc First Aid > verify disc > 'keys out of order HD need repairing'.
Clicked 'repair disc' and indicated 'repair complete'.
Returned to 'verify disc' > HD needs repairing, key length too short.
Repaired once more, keys still out of order.
Removed Install disc one and loaded Disc Warrior.
Speed inhibited by malfunction stage 5 when rebuilding directory.
So with no full operating system loaded, how do we progress?

John:
"Keys problems" are directory issues which, if not repairable by Disk Utility need a third party package like Tech Tool Pro, DriveGenius, or Disk Warrior. However, in some cases the disk hardware may be damaged or the HDD may have failed and unable to hold the format. When in DU check the SMART status. Even if the SMART Status is Verified and the HDD is more than 3 years old you should consider replacement.
cornelius

[SOLVED] [pacman] My 'pacman-key --init' issue

pacman-key --init
gpg: Generating pacman keychain master key...
Not enough random bytes available. Please do some other work to give
the OS a chance to collect more entropy! (Need 211 more bytes)
Well, I thought that I could resolve it using random bytes from RANDOM.ORG (http://www.random.org/, in particularly http://www.random.org/bytes/), a really useful website.
Is it a good solution, or is it mandatory to generate random bytes using my PC? And in that case, how can I use random bytes generated from that site?
Last edited by metre (2011-10-14 09:48:31)

teratomata wrote:
hussam wrote:
I installed pacman 4.0 from testing. I did pacman-key --init
but now I can't install anything again
trying to install hplip
Proceed with installation? [Y/n] y
(1/1) checking package integrity [####################################] 100%
error: hplip: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-20? [Y/n] y
(1/1) checking package integrity [####################################] 100%
error: hplip: signature from "Eric Belanger <[email protected]>" is unknown trust
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
I found that my pacman.conf didn't get updated, but once I moved /etc/pacman.conf.pacnew to /etc/pacman.conf, everything worked.
I just wanted to say thanks teratomata. I did everything that was mentioned and was continually being asked if I wanted to import keys. Moved pacman.conf.pacnew to pacman.conf and everything works great!

Usr/bin/pacman-key: line 615: printf: write error: Broken pipe

I've got some instances of same error from pacman which I think is abnormal when I tried to upgrade pacman-keyring via "pacman -Syu".
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
What action should I take for the errors to maintain my system?
Searching the web and this forum won't answer my question...
The quotation of pacman.log of the upgrade sesson which evoked pacman-keyring upgrading is below:
[2013-04-20 22:04] [PACMAN] Running 'pacman -Syu'
[2013-04-20 22:04] [PACMAN] synchronizing package lists
[2013-04-20 22:04] [PACMAN] starting full system upgrade
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 1 valid: 5 signed: 64 trust: 0-, 0q, 0n, 5m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 2 valid: 64 signed: 1 trust: 64-, 0q, 0n, 0m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Updating trust database...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [PACMAN] upgraded archlinux-keyring (20130224-1 -> 20130406-1)
[2013-04-20 22:05] [PACMAN] upgraded bash-completion (2.0-3 -> 2.1-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generating locales...
[2013-04-20 22:05] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] ja_JP.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generation complete.
[2013-04-20 22:05] [PACMAN] upgraded glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded binutils (2.23.2-1 -> 2.23.2-2)
[2013-04-20 22:05] [PACMAN] upgraded m4 (1.4.16-2 -> 1.4.16-3)
[2013-04-20 22:05] [PACMAN] upgraded bison (2.7-1 -> 2.7.1-1)
[2013-04-20 22:05] [PACMAN] upgraded curl (7.29.0-2 -> 7.30.0-1)
[2013-04-20 22:05] [PACMAN] upgraded expat (2.1.0-1 -> 2.1.0-2)
[2013-04-20 22:05] [PACMAN] upgraded freeglut (2.8.0-2 -> 2.8.1-1)
[2013-04-20 22:05] [PACMAN] upgraded gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gcc (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gpm (1.20.7-1 -> 1.20.7-2)
[2013-04-20 22:05] [PACMAN] upgraded harfbuzz (0.9.14-1 -> 0.9.16-1)
[2013-04-20 22:05] [PACMAN] upgraded isl (0.11.1-1 -> 0.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded kmod (12-1 -> 13-1)
[2013-04-20 22:05] [PACMAN] upgraded libldap (2.4.34-1 -> 2.4.35-1)
[2013-04-20 22:05] [PACMAN] upgraded krb5 (1.11.1-1 -> 1.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded lib32-glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded lib32-gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded libcap (2.22-3 -> 2.22-4)
[2013-04-20 22:05] [PACMAN] upgraded libpng (1.5.14-1 -> 1.5.15-1)
[2013-04-20 22:05] [PACMAN] upgraded libtasn1 (3.2-1 -> 3.3-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'default'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'fallback'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux-fallback.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [PACMAN] upgraded linux (3.8.5-1 -> 3.8.7-1)
[2013-04-20 22:05] [PACMAN] upgraded orc (0.4.16-1 -> 0.4.17-1)
[2013-04-20 22:05] [PACMAN] upgraded perl (5.16.3-1 -> 5.16.3-2)
[2013-04-20 22:05] [PACMAN] upgraded psmisc (22.19-1 -> 22.20-1)
[2013-04-20 22:05] [PACMAN] upgraded sqlite (3.7.16.1-1 -> 3.7.16.2-1)
[2013-04-20 22:05] [PACMAN] upgraded sudo (1.8.6.p7-2 -> 1.8.6.p8-1)
[2013-04-20 22:05] [PACMAN] upgraded systemd (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded systemd-sysvcompat (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded tar (1.26-2 -> 1.26-3)
[2013-04-20 22:05] [PACMAN] upgraded wayland (1.0.6-1 -> 1.1.0-1)
Thanks in advance!

I just encountered the same issue with the latest update. I never had something similar to this:
:: Retrieving packages ...
archlinux-keyring-20130525-2-any 367,2 KiB 1023K/s 00:00 [################################################################] 100%
linux-3.9.5-1-x86_64 45,5 MiB 1015K/s 00:46 [################################################################] 100%
linux-headers-3.9.5-1-x86_64 5,6 MiB 1117K/s 00:05 [################################################################] 100%
gnome-bluetooth-3.8.1-2-x86_64 835,0 KiB 955K/s 00:01 [################################################################] 100%
gnome-documents-3.8.3-1-x86_64 305,0 KiB 1034K/s 00:00 [################################################################] 100%
vlc-2.0.7-2-x86_64 7,6 MiB 1162K/s 00:07 [################################################################] 100%
(6/6) checking keys in keyring [################################################################] 100%
(6/6) checking package integrity [################################################################] 100%
(6/6) loading package files [################################################################] 100%
(6/6) checking for file conflicts [################################################################] 100%
(6/6) checking available disk space [################################################################] 100%
(1/6) upgrading archlinux-keyring [################################################################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
-> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
-> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
-> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
-> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...

Replication for Data on DEV and QA - bad idea - primary key problem now

I goofed. I tried to use replication to keep the data on my dev machine up to date with the live server. Now when I try to work on the database, adding new stuff, it fails. It says there is a primary key problem every time I try to add
a new item to a table with my program. I should have realized this would happen! Now, even though I've removed the replication, I'm having the problem. Can anyone help me get my database functional again :/ Or should I resort to a database
restore. Thanks!

So you have an IDENTITY column in your table? Run a
DBCC CHECKIDENT (Transact-SQL) command with option RESEED to fix the current identity value to see if it works then.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Pacman-key wiki: Incorrect information

Good Morning all
The new pacman-key wiki has some misleading information within it, that should be corrected/clarified.
https://wiki.archlinux.org/index.php/Pa … e_checking
specifically
Edit /etc/pacman.conf and uncomment the following line under [options]:
SigLevel = Never
try it. The repositories are below this line and therefore the parser takes the last invocation of the SigLevel (global) option at a local level and doesn't honour the setting. You also need to comment any 'SigLevel' lines within the [core], [community] or [extra] repositories.
It should be clarified because it causes confusion.
Thanks
GregW
Last edited by GregW (2012-01-25 10:52:44)

It is a wiki... edit it.
You do not have permission to edit this page, for the following reasons:
The action you have requested is limited to users in the group: Users.
You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences.
You can view and copy the source of this page:
Oh well, nevermind, i've mentioned it.

Pacman-key problem

Similar Messages

Maybe you are looking for