Package Details: dropbox 258.4.3749-1

Git Clone URL: https://aur.archlinux.org/dropbox.git (read-only, click to copy)
Package Base: dropbox
Description: A free service that lets you bring your photos, docs, and videos anywhere and share them easily.
Upstream URL: https://www.dropbox.com
Licenses: custom:Dropbox
Submitter: mtorromeo
Maintainer: mtorromeo
Last Packager: mtorromeo
Votes: 2377
Popularity: 2.41
First Submitted: 2009-01-22 14:21 (UTC)
Last Updated: 2026-07-04 11:06 (UTC)

Pinned Comments

yan12125 commented on 2019-01-05 16:39 (UTC) (edited on 2019-02-27 08:11 (UTC) by yan12125)

Run the following command in case you got errors during "Verifying source file signatures with gpg..."

gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E

Alternatively, you can download Dropbox's public key from https://linux.dropbox.com/fedora/rpm-public-key.asc and import it with:

gpg --import rpm-public-key.asc

You can check whether keys are successfully imported or not using the output of gpg -k. You should find something like this:

pub   rsa2048 2010-02-11 [SC]
      1C61A2656FB57B7E4DE0F4C1FC918B335044912E
uid           [ unknown] Dropbox Automatic Signing Key <linux@dropbox.com>

yan12125 commented on 2018-08-01 11:41 (UTC) (edited on 2020-01-24 15:13 (UTC) by yan12125)

If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again.

yan12125 commented on 2017-11-06 15:13 (UTC) (edited on 2019-03-18 03:50 (UTC) by yan12125)

Some useful places for issues about Dropbox itself (not the package):

  1. https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016 Official Dropbox user feedback forum

  2. Arch Linux discussion places: https://bbs.archlinux.org/, #archlinux on freenode.net, https://lists.archlinux.org/listinfo/aur-general

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 99 Next › Last »

thule commented on 2024-10-26 21:43 (UTC) (edited on 2024-10-26 22:16 (UTC) by thule)

Hi @mtorromeo,

I sent you a patch tonight to address the issue with the package installation.

Note: The 32 bit version fails the compilation on dropbox's build
servers. To keep the functionality restrain momentarily the 32
bit package to 205.4.5765.

Please feel free to apply it at your earliest convenience, if you find it useful.

Thanks and Regards,

thule

NZCyrus commented on 2024-10-24 03:27 (UTC)

running 'updpkgsums' in the same directory as the PKGBUILD generated new checksums which sorted the error.

darkfish commented on 2024-10-23 01:09 (UTC) (edited on 2024-10-23 01:11 (UTC) by darkfish)

@username227 A packager would generate the signatures just as this (-g flag). In this particular case, it just so happens that upstream removed 32-bit packages, which possibly broke mtorromeo's process of generating sigs for rest of the sources. These then didn't get updated in the PKGBUILD, prior to pushing to AUR. One must also not SKIP these checks in general. You will find more info in the Wiki under makepkg and PKGBUILD entries.

username227 commented on 2024-10-23 00:31 (UTC)

@darkfish, thanks for the info.When I did a --geninteg, I got the download error. But, I was able to get the downloads themselves from the .cache directory when pamac and paru tried to build, or when I tried to actually build in a chroot. The error I was getting was the validity check, not the download itself. So I changed the failing validity check to 'SKIP' and built that way.

So how does a packager generate integrities for a package that's set up like this?

darkfish commented on 2024-10-22 23:15 (UTC) (edited on 2024-10-22 23:23 (UTC) by darkfish)

Thanks @mtorromeo, just saw your message after I edited my previous comment.

Edit: P.S. You should perhaps also increment the pkgrel given the updated PKGBUILD

mtorromeo commented on 2024-10-22 22:43 (UTC) (edited on 2024-10-22 22:44 (UTC) by mtorromeo)

Seems like i686 package is no longer available, and that broke my procedure to update checksums.

The package should work now.

darkfish commented on 2024-10-22 22:42 (UTC) (edited on 2024-10-22 23:14 (UTC) by darkfish)

@username227 Did you figure out the issue of curl returning 403? I compared my {pacman,makepkg}.conf files and even list of keys from pacman-key output (assuming key error), and both base and chroot versions are same. So I am just as clueless.

UPDATE: Never mind. I wasn't paying close attention to the URL which was returning 403 error. So as it happens, when doing makepkg -g it tries to download all sources, including those not for current architecture, despite current arch explicitly set in makepkg.conf. The reason why makechrootpkg or just makepkg was succeeding was because it was only downloading source for current arch. I had to comment out the *_i686 arrays.

username227 commented on 2024-10-22 13:18 (UTC)

@Richardk2n, you beat me to this comment. But a strange thing happened while I was trying to generate the new shasums - when I tried to run makepkg, it said that there was a 403 error from the source. When I tried to build in a chroot using "SKIP' instead of the shasums, though, it downloaded just fine. Never experienced anything like that before.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 99 Next › Last »