Arch Linux User Repository

If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again. See https://gitlab.com/yan12125/aur/issues/21 for details.

Due to more and more comments unrelated to the package itself, I decided to disable AUR comment notifications. If you believe there's really an issue in PKGBUILD and/or relevant packaging scripts, please open an issue at https://gitlab.com/yan12125/aur with a title starting with "dropbox:".

Some useful places for Dropbox issues:

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

@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

https://github.com/soderstrom-rikard/arch-linux-package-dropbox/commit/1c0db3a058091bb4fae9f36859f05845c7d2f191

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)

[1] https://github.com/archlinuxcn/lilac

If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again. See https://gitlab.com/yan12125/aur/issues/21 for details.

@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.

49.4.68 is announced, anyway.

BTW, @jorgicio, how did you find the new URL before it's announced?

In fact, althought no news were published, the 49.4.68 is up. I'm now in Gentoo, I maintain the dropbox package on my overlay, and that version is up.

https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86-49.4.68.tar.gz https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-49.4.68.tar.gz