Package Details: dropbox 220.4.4126-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
Submitter: mtorromeo
Maintainer: mtorromeo
Last Packager: mtorromeo
Votes: 2378
Popularity: 2.24
First Submitted: 2009-01-22 14:21 (UTC)
Last Updated: 2025-03-26 08:13 (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

1 2 3 4 5 6 .. 97 Next › Last »

flamesoulis commented on 2025-03-25 19:07 (UTC)

There appears to be an issue with this being out of date and copying its source into /opt, when the service usually operates from the user's home directory. With 221.3, DropBox decided to remove the preferences GUI and now require CLI operations for most tasks, which makes this setup nearly unusable.

I'm still getting used to things, but I can update this with v220.4.4126, which will resolve the GUI situation while remaining compatible (for now). However, this also requires the user set the .dropbox-dist folder to read only so it cannot update it. I have yet to find an elegant solution for this, so I'll have to see how the Debian/Ubuntu systems work and try to mirror the setup.

dpecos commented on 2025-03-21 13:39 (UTC)

On a fresh arch installation, I was failing to get the popup dialog asking me to confirm moving my dropbox folder to a different location, but it was printed on the terminal (if dropbox launched from terminal) but without any option to confirm or cancel.

Installing the package libappindicator-gtk3 and its dependencies (gtk3-1:3.24.49-1 libdbusmenu-glib-16.04.0.r498-2 libdbusmenu-gtk3-16.04.0.r498-2 libappindicator-gtk3-12.10.0.r298-4) solved the problem.

robme commented on 2024-12-23 23:43 (UTC)

I haven't made a read only directory ~/.dropbox-dist. Dropbox updated itself and still syncs fine.

npreining commented on 2024-10-28 09:32 (UTC) (edited on 2024-10-28 09:32 (UTC) by npreining)

Is there any progress? The last statement from the maintainer is 10/22

The package should work now.

but it definitely does not work.

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

1 2 3 4 5 6 .. 97 Next › Last »