Getting a Broken Pipe for a Dropbox File?

I have a dropbox upgrade that has been pending for a bit, and keeps getting a cat write error of “broken pipe”:

==> Making package: dropbox 125.4.3474-1 (Mon 05 Jul 2021 04:17:14 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found DropboxGlyph_Blue.svg
  -> Found terms.txt
  -> Found dropbox.service
  -> Found dropbox@.service
  -> Downloading dropbox-lnx.x86_64-125.4.3474.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 97.2M  100 97.2M    0     0  20.8M      0  0:00:04  0:00:04 --:--:-- 22.1M
  -> Downloading dropbox-lnx.x86_64-125.4.3474.tar.gz.asc...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   473  100   473    0     0   5217      0 --:--:-- --:--:-- --:--:--  5255
==> Validating source files with sha256sums...
    DropboxGlyph_Blue.svg ... Passed
    terms.txt ... Passed
    dropbox.service ... Passed
    dropbox@.service ... Passed
==> Validating source_x86_64 files with sha256sums...
    dropbox-lnx.x86_64-125.4.3474.tar.gz ... Passed
    dropbox-lnx.x86_64-125.4.3474.tar.gz.asc ... Skipped
==> Verifying source file signatures with gpg...
    dropbox-lnx.x86_64-125.4.3474.tar.gz ... cat: write error: Broken pipe
==> ERROR: One or more PGP signatures could not be verified!
Finished with result: exit-code
Main processes terminated with: code=exited/status=1
Service runtime: 5.860s
CPU time consumed: 1.665s
Error: Failed to build dropbox

This doesn’t appear to be the usual PGP verification issue. Maybe an issue with the package? How could I upgrade this?

The issue is fixed with gnupg 2.2.29, but until then…

1 Like

I’ve got gnupg 2.2.32-2, but I have the same issue as @Sarah.

@horror-vacui See this comment on the AUR page:

I had done it before. Has not helped. I’ve just checked again the PGP keys with gpg -k. I’ve even found on Dropbox’s webpage the latest tutorial/guide. It has the same PGP key. I am clueless how to debug. I would have expected a more direct error message, such as pointing the name of the missing key.