New Insync version: 1.3.16

latestfaq

#3

Looks like the trusty amd64 build failed, the packaged is not available for download.


#5

@kubrick: Apologies, it should be available now.


#6

I’m getting the package is not signed error on F25 on kernel 4.10.11-200 when use dnf to update. Looks just like New Insync version: 1.3.4 (Fedora Linux only). LMK if I can provide anything to help with a fix, thanks!
Error: Package insync-1.3.16.36155-fc25.x86_64.rpm is not signed


#7

Hi, the package insync-1.3.16.36155-fc25.x86_64.rpm doesn’t seem to be signed. dnf refuse to install unless you disable gpg checking with the option “gpgcheck = 0” in insync.repo file. This, of course, is less secure.


#8

I have installed the new version however I am still getting “could not delete ###” errors.

How do I resolve this?


#9

790/5000
Thanks, it worked perfectly on Ubuntu 16.04 (KDE Neon).
Anyway I make the following comment as suggestion of a possible improvement: The old “warning” message that the item was deleted (moved) did not necessarily bother me, therefore, I could have accidentally deleted or moved, and if that was the case the Message would at least alert me and maybe be able to recover on time. What I did not like was to have to “give Ok” in each message, one by one. That is, perhaps not as an “action required” option, but a simple alert (synthetic, not one by one) that there was an exclusion of several items could be useful in case of accidental deletion (which was not my case , Since I had actually moved the folder with several files purposely).
Kind regards.
Deivid


#10

I am on OS X 10.12.4.

Another item to mention. I use the selective sync feature and the Folder with the Folders inside that are causing the message has been “un-tagged”. So this folder and its contents should not be syncing to my drive. However if I do anything with this folder even though it is not checked it still syncs to gdrive.


#11

Ditto here also… don’t you folks sign your rpms?


#12

Guys, what is going on there? The previous release had this same issue and on top of that, it isn’t signed. I had to turn off GPG check to install - which is a no no. Seriously? I can understand having the unpacking issue in one rpm, but back to back releases? This was reported and acknowledged over a week ago. Just looks extremely sloppy.

Upgrading : insync-1.3.16.36155-fc25.x86_64 1/2
Error unpacking rpm package insync-1.3.16.36155-fc25.x86_64
Error unpacking rpm package insync-1.3.16.36155-fc25.x86_64
error: unpacking of archive failed: cpio: lstat
insync-1.3.16.36155-fc25.x86_64 was supposed to be installed but is not!
Verifying : insync-1.3.16.36155-fc25.x86_64 1/2
insync-1.3.9.36089-fc21.x86_64 was supposed to be removed but is not!
Verifying : insync-1.3.9.36089-fc21.x86_64 2/2

Failed:
insync.x86_64 1.3.16.36155-fc25


Insync-1.3.16.36155-fc25.x86_64.rpm is not signed
#13

Hello @gbcox, we’re using our new build system for Linux and thank you for pointing out those issues. We’ll work on it.


#14

Hello @Fulwave, what action did you do to trigger it?


#15

The problem is on Update, this happen on Fedora 24 and 25.

Command: sudo dnf update

Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Upgrading : insync-1.3.16.36155-fc24.x86_64 1/2
Error unpacking rpm package insync-1.3.16.36155-fc24.x86_64
Error unpacking rpm package insync-1.3.16.36155-fc24.x86_64
error: unpacking of archive failed: cpio: lstat
insync-1.3.16.36155-fc24.x86_64 was supposed to be installed but is not!
Verifying : insync-1.3.16.36155-fc24.x86_64 1/2
insync-1.3.14.36131-fc21.x86_64 was supposed to be removed but is not!
Verifying : insync-1.3.14.36131-fc21.x86_64 2/2

Failed:
insync.x86_64 1.3.16.36155-fc24


#16

Nothing. Another user who shared a file with me modified his files.


#17

Went back to Insync v1.3.14 and the issue went away.


#18

I’m getting the same thing. The RPM file is bad and will not update.


#19

Same problem, Fedora 24, 64bit


#20

@POC @Piotr_Antosik: Apologies for the trouble. Could you try again? What is the output of sudo dnf update? If retrying does not work please try uninstalling Insync, deleting the folder /usr/lib/insync, and reinstalling Insync.


#21

$ sudo dnf update insync
^[[Binsync repo 4% [=== ] 61 kB/s | 22 kB 00:07 insync repo 574 kB/s | 490 kB 00:00
Dependencies resolved.

Package Arch Version Repository Size

Upgrading:
insync x86_64 1.3.16.36155-fc25 insync 79 M

Transaction Summary

Upgrade 1 Package

Total download size: 79 M
Is this ok [y/N]: y
Is this ok [y/N]: y
Downloading Packages:
insync-1.3.16.36155-fc25.x86_64.rpm 7.3 MB/s | 79 MB 00:10

Total 7.3 MB/s | 79 MB 00:10
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Upgrading : insync-1.3.16.36155-fc25.x86_64 1/2
Error unpacking rpm package insync-1.3.16.36155-fc25.x86_64
Error unpacking rpm package insync-1.3.16.36155-fc25.x86_64
error: unpacking of archive failed: cpio: lstat
insync-1.3.16.36155-fc25.x86_64 was supposed to be installed but is not!
Verifying : insync-1.3.16.36155-fc25.x86_64 1/2
insync-1.3.14.36131-fc21.x86_64 was supposed to be removed but is not!
Verifying : insync-1.3.14.36131-fc21.x86_64 2/2

Failed:
insync.x86_64 1.3.16.36155-fc25


After doing that I uninstalled insync and removed /usr/lib/insync, then reinstalled. That worked.

The problem appears to have been that the update couldn’t remove the old version.


#22

After the automatic update I had multiple files remove themselves from my google drive, however they still appear locally?


#23

please send your log files to support@insynchq.com so we can look into it :slight_smile: How to find the log files