Package Details: insync 3.9.4.60020-1

Git Clone URL: https://aur.archlinux.org/insync.git (read-only, click to copy)
Package Base: insync
Description: An unofficial Dropbox, Google Drive, and OneDrive client that runs on Linux, with support for various desktops
Upstream URL: https://www.insynchq.com/downloads
Keywords: drive dropbox google onedrive
Licenses: custom:insync
Submitter: xzy3186
Maintainer: thenaterhood
Last Packager: thenaterhood
Votes: 321
Popularity: 1.45
First Submitted: 2012-09-07 17:45 (UTC)
Last Updated: 2024-08-11 22:53 (UTC)

Latest Comments

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 65 Next › Last »

dhux commented on 2018-03-19 01:00 (UTC)

Builds but won't start, even with yan12125's line added to the PKGBUILD.

thenaterhood commented on 2018-03-19 00:54 (UTC)

yan12125: Thanks for the info! Very interesting; I have that file (and it's not a symlink) so I wonder how it got lost for you. I want to look into this more before I add that symlink to the package since I'm worried that could have side effects later.

yan12125 commented on 2018-03-18 08:43 (UTC) (edited on 2018-03-18 08:51 (UTC) by yan12125)

I got an issue after upgrading to 1.4.3

$ insync start --no-daemon
Traceback (most recent call last):
  File "<string>", line 6, in <module>
  File "__main__.py", line 128, in <module>
  File "__main__insync__.py", line 116, in <module>
  File "isyncd/linux/headless/cli.py", line 49, in run
  File "__main__insync__.py", line 25, in main
  File "PySide/QtGui.py", line 26, in <module>
  File "PySide/QtGui.py", line 17, in _bbfreeze_import_dynamic_module
ImportError: /usr/lib/insync/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var

I "fixed" this by adding the following line after the libfontconfig line in PKGBUILD

ln -sf "/usr/lib/libfreetype.so.6" "${pkgdir}/usr/lib/insync/libfreetype.so.6"

thenaterhood commented on 2018-03-17 20:04 (UTC)

Well, waddya know. At long last, here's 1.4! Seems to have just been a drop-in, but let me know if anything is weird.

thenaterhood commented on 2018-03-17 19:32 (UTC)

I've added sni-qt as an optional dependency for the system tray icon. I'm willing to make it required, but since the tray icon works for me without it, there might be more details there so I don't want to commit just yet.

I also updated the PKGBUILD so that the tar call is not verbose. It saves a little bit of time when untarring the package so it's not taking the time to write to the console.

RE: 1.4. Sweet! I'll start working on updating the package to it. Hopefully, it's just a drop-in replacement and everything will "just work".

txelu commented on 2018-03-17 11:20 (UTC)

Regarding the missing icon I can confirm that installing sni-qt package and restarting my PC made the insync icon to appear. I am using Gnome Desktop version 3.26.2.

saverio commented on 2018-03-16 17:30 (UTC)

Please, update. Thanks in advance!

poppycock commented on 2018-03-15 19:19 (UTC)

1.4 has been officially released now. @thenaterhood according to https://forums.insynchq.com/t/faq-on-prime-plan/8280 all @gmail accounts were given a free upgrade to Prime (all others (@gapps/3rd party) receive a 30% discount).

Installing sni-qt worked for me when using Gnome and not having a tray icon.

Thank you for your work on this package @thenaterhood - appreciate it may be a while before you can make 1.4 available in the AUR (it's beyond my skills)

thenaterhood commented on 2018-03-08 04:03 (UTC)

@yochaigal: I don't have sni-qt installed, and my tray icon works. I'm willing to add sni-qt as an optional dependency once I can confirm that it's required on QT-based environments, since it appears it's not required on GTK ones.

@dahankzter: I'm not sure what you're experiencing. The package takes several minutes to build on a reasonably modern system (i5, 12GB ram, SSD in my case) which is not uncommon for AUR packages. The resulting package is around 200MB, which is a little on the large side for pacman packages, but should install in a reasonable amount of time (couple minutes, depending on the speed of your disk - it's a large number of files). The short answer, I suppose, is "yes it is supposed to take several minutes". There isn't much I can do to improve on that, other than make the decompression not print to the console which might save a minute or so in the build.