"printf: write error: Broken Pipe" on upgrading archlinux-keyring

weirddan455 · 2015-02-14 05:55:30

Is this anything to worry about? The upgrade seems to have otherwise succeeded.

(1/3) upgrading archlinux-keyring                                   [#####################################] 100%
==> Appending keys from archlinux.gpg...
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:  62  signed:   5  trust: 62-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-01-22
==> 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...
usr/bin/pacman-key: line 609: printf: write error: Broken pipe
==> Importing owner trust values...
==> 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: next trustdb check due at 2016-01-22

Last edited by weirddan455 (2015-02-14 05:58:08)

mauritiusdadd · 2015-02-14 07:19:02

Hi, according to line 609 of pacman-key

/urs/bin/pacman-key wrote:

608	# we cannot use --yes here as gpg would still ask for confirmation if a key has more than one uid
609	printf 'y\ny\n' | LANG=C "${GPG_PACMAN[@]}" --command-fd 0 --quiet --batch --lsign-key "${key_id}" 2>/dev/null

it seems that gpg has died when it tried to sign locally the key FFF979E7. If a key is not locally signed you could have problems when installing packages signed with that key.

Does it work if you run the following command?

pacman-key --populate archlinux

weirddan455 · 2015-02-16 08:39:26

If I'm understanding this correctly, the key looks like it's signed.

$ gpg --homedir /etc/pacman.d/gnupg --edit-key FFF979E7
gpg: WARNING: unsafe ownership on homedir '/etc/pacman.d/gnupg'
gpg: can't connect to the agent: IPC connect call failed

gpg: Note: trustdb not writable
pub  rsa4096/FFF979E7
     created: 2011-11-29  expires: never       usage: SC  
     trust: marginal      validity: full
[  full  ] (1). Allan McRae (Arch Linux Master Key) <allan@master-key.archlinux.org>

The only thing I can think of that might have messed things up is that pacman pulled down a GPG upgrade at the same time as archlinux-keyring (archlinux-keyring got applied first.)

mauritiusdadd · 2015-02-16 09:40:22

weirddan455 wrote:

The only thing I can think of that might have messed things up is that pacman pulled down a GPG upgrade at the same time as archlinux-keyring (archlinux-keyring got applied first.)

I'm not sure if it was that the cause of the issue, however the key seems ok.

Arch Linux

#1 2015-02-14 05:55:30

"printf: write error: Broken Pipe" on upgrading archlinux-keyring

#2 2015-02-14 07:19:02

Re: "printf: write error: Broken Pipe" on upgrading archlinux-keyring

#3 2015-02-16 08:39:26

Re: "printf: write error: Broken Pipe" on upgrading archlinux-keyring

#4 2015-02-16 09:40:22

Re: "printf: write error: Broken Pipe" on upgrading archlinux-keyring

Board footer