| 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: | 2374 |
| Popularity: | 1.54 |
| First Submitted: | 2009-01-22 14:21 (UTC) |
| Last Updated: | 2024-10-30 08:51 (UTC) |
I'd like to drop dropbox@.service in favor of dropbox.service to fix https://gitlab.com/yan12125/aur/issues/23. Please leave comments there if you object.
<del>I'll carry out the change if no one objects in two weeks.</del>
UPDATE: as mentioned by Francesco Sanesi, dropping dropbox@.service might break multi-user scenarios. I'll postpone the original plan.
@yan12125
Here is a permanent fix for dropbox service reloading.
Dropbox actually works correctly by forking itself, and it even gives us ~/.dropbox/dropbox.pid so systemd can know which process id to track.
There were some minor issues with dropbox return SIGKILL between process which really doesn't work with restart=on-failure alone. Therefore, SuccessExitStatus for SIGKILL was needed. Finally I also noticed that dropbox doesn't properly clean up (i.e. removing the dropbox.pid file from last session) so had to add an ExecStopPost command for that.
You can see all of this here
This way automatic updates works again an you no longer need to make ~/.dropbox-dist read-only.
One concern I have is haven't tested this for default.target only for the multi-user.target, so might be worth checking out.
Also note that, be a journal entry of the form "dropbox@$USER.service: Can't open PID file /home/$USER/.dropbox/dropbox.pid (yet?) after start: No such file or director"
This is because dropbox takes longer than some timeout before creating the dropbox.pid file. Essentially it is triggering because of the "yet" part of that message. The line after will be "Started Dropbox" and everything is fine.
At least the ground labor is done now.
Enjoy your day.
@mtorromeo: Is it OK for you if I add lilac as a co-maintainer? I'd like to configure the lilac bot [1] to update this package automatically. (I can do that myself as I'm now a trusted user, just ask for approval)
If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again.
@parnmatt & @sl13kp
Just edit the PKGBUILD, find this line and remove the bold text.
find "$pkgdir"/opt/dropbox/ -type f -exec chmod 644 {} \;
chmod 755 "$pkgdir"/opt/dropbox/dropboxd
chmod 755 "$pkgdir"/opt/dropbox/dropbox{,_py3}
Got the same problem as parnmatt.
I'm getting an error with the recent update; are you missing a file?
chmod: cannot access '/var/cache/pacman/pkg/dropbox25812/dropbox/pkg/dropbox/opt/dropbox/dropbox_py3': No such file or directory
chmod: impossibile accedere a '/tmp/yaourt-tmp-stefano/aur-dropbox/pkg/dropbox/opt/dropbox/dropbox_py3
If I'm not mistaken then the current pkgrel should be reset to 1 now that pkgver was upgraded to 50.4.71.
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..."
Alternatively, you can download Dropbox's public key from https://linux.dropbox.com/fedora/rpm-public-key.asc and import it with:
You can check whether keys are successfully imported or not using the output of
gpg -k. You should find something like this: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):
https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016 Official Dropbox user feedback forum
Arch Linux discussion places: https://bbs.archlinux.org/, #archlinux on freenode.net, https://lists.archlinux.org/listinfo/aur-general