Package Details: dropbox-cli 2024.04.17-2

Git Clone URL: https://aur.archlinux.org/dropbox-cli.git (read-only, click to copy)
Package Base: dropbox-cli
Description: Command line interface for Dropbox
Upstream URL: https://www.dropbox.com
Keywords: dropbox
Licenses: GPL-3.0-or-later
Submitter: msquared
Maintainer: Muflone
Last Packager: Muflone
Votes: 472
Popularity: 0.27
First Submitted: 2010-02-04 14:03 (UTC)
Last Updated: 2024-04-21 22:34 (UTC)

Pinned Comments

Muflone commented on 2024-04-21 22:26 (UTC)

Since version 2024.04.17-1 dropbox-cli is built from the nautilus-dropbox source as currently the dropbox.py source file is not aligned with the latest release in https://linux.dropbox.com/packages/

Latest Comments

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

bluesheep commented on 2015-08-30 11:32 (UTC)

I get the error that 'dropbox.py' did not pass the validity check. Could you take a look at that please?

erikw commented on 2015-08-28 15:05 (UTC)

How to easily add a 'restart' command to dropbox-cli :-) https://github.com/erikw/dotfiles/blob/personal/bin/dropbox

1ace commented on 2015-03-03 07:50 (UTC)

I also suggest adding this patch, making `dropbox-cli running` compatible with the shell (why wasn't it already?) https://gist.github.com/c789158b4c4adf612dc4 This allows for something like this for instance: if dropbox-cli running then dropbox-cli status else dropbox-cli start fi

klusark commented on 2015-02-14 07:33 (UTC)

Thanks for the suggestions everyone. I'll update the package as soon as I'm home from vacation, this Monday.

thiagowfx commented on 2015-02-14 04:07 (UTC)

Hi, could you please rename /usr/bin/dropbox to /usr/bin/dropbox-cli, so this doesn't conflict with the dropbox package anymore? See @cfr42's suggestion. Also, since this script depends on dropboxd, I'd suggest you to alter the dropbox-cli-arch.patch file to use the /opt/dropbox/dropbox file now (instead of /usr/bin/dropboxd). That is, this patch would solve everything: --- PKGBUILD 2014-11-20 03:35:37.000000000 -0200 +++ PKGBUILD.new 2015-02-14 02:06:50.029800477 -0200 @@ -25,5 +25,5 @@ } package() { - install -D -m 755 "$srcdir/build/dropbox.py" "$pkgdir/usr/bin/dropbox" + install -D -m 755 "$srcdir/build/dropbox.py" "$pkgdir/usr/bin/$pkgname" } --- dropbox.py 2011-04-04 20:32:01.000000000 +0200 +++ dropbox.py 2011-04-28 22:55:17.976623103 +0200 @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/python2 # # Copyright 2008 Evenflow, Inc. # @@ -610,6 +610,8 @@ def start_dropbox(): db_path = os.path.expanduser(u"~/.dropbox-dist/dropboxd").encode(sys.getfilesystemencoding()) + if not os.path.exists(db_path): + db_path = u"/opt/dropbox/dropbox" if os.access(db_path, os.X_OK): f = open("/dev/null", "w") # we don't reap the child because we're gonna die anyway, let init do it

cfr42 commented on 2015-02-12 23:09 (UTC)

Maybe something like this? --- PKGBUILD 2014-11-20 05:35:37.000000000 +0000 +++ PKGBUILD 2015-02-12 23:02:30.672555629 +0000 @@ -25,5 +25,6 @@ } package() { - install -D -m 755 "$srcdir/build/dropbox.py" "$pkgdir/usr/bin/dropbox" + install -D -m 755 "$srcdir/build/dropbox.py" "$pkgdir/usr/bin/dropbox-cli" + ln -s ../../opt/dropbox/dropbox "$pkgdir"/usr/bin/dropboxd } The script seems to use /usr/bin/dropboxd, which is why I had the package add a sym link.

ManyPopes commented on 2015-02-12 22:11 (UTC)

You can get around that for now by renaming the dropbox binary, installing, renaming the new dropbox binary to dropbox-cli then restoring the original binary. I've no idea if this is a terrible idea but it seems to work fine for me so far.

linduxed commented on 2015-02-12 14:36 (UTC)

Since the "dropbox" package now has a binary placed in /usr/bin/dropbox, this package can't be installed since it wants to place its binary in the same place.

ilpianista commented on 2015-01-23 08:40 (UTC)

Also, using source=("${pkgname}-${pkgver}.gz"::https://linux.dropbox.com/packages/dropbox.py.gz) you avoid future issues about wrong checksums. Because some people sets SRCDIR in makepkg.conf.