- Arch Linux User Repository
- krassecommits commented on 2023-01-02 15:40 (UTC)
- ThinOrangeHaze commented on 2022-12-24 17:01 (UTC)
- oysstu commented on 2022-11-25 17:32 (UTC)
- Panzki commented on 2022-11-19 09:28 (UTC)
- ZEBofx commented on 2022-11-01 20:24 (UTC) (edited on 2022-11-01 20:27 (UTC) by ZEBofx)
- fmartingr commented on 2022-11-01 19:53 (UTC) (edited on 2022-11-01 19:57 (UTC) by fmartingr)
- rlees85 commented on 2022-11-01 19:45 (UTC) (edited on 2022-11-01 19:50 (UTC) by rlees85)
Arch Linux User Repository
I installed it on 4/26 and it works fine on my machine. I dont think it’s out of date.
krassecommits commented on 2023-01-02 15:40 (UTC)
Seems like they dumped the i686 build, it even says (64 bits, deb) on the download page. Nevertheless, it would be nice to update this package with the commit from @ThinOrangeHaze
ThinOrangeHaze commented on 2022-12-24 17:01 (UTC)
Patch for new update. Can’t find the i686 version of the latest release however.
diff --git a/PKGBUILD b/PKGBUILD index 6c4f770..fc802e4 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -1,23 +1,19 @@ # Maintainer: Felipe Martin pkgname="synology-drive" -pkgver="3.2.0_13258" +pkgver="3.2.1_13271" pkgrel="1" pkgdesc="Drive for PC, the desktop utility of the DSM add-on package, Drive, allows you to sync and share files owned by you or shared by others between a centralized Synology NAS and multiple client computers." -arch=('i686' 'x86_64') +arch=('x86_64') url="https://www.synology.com" license=('custom') -depends=('glibc' ) -optdepends=('nautilus: For nautilus integration' ) +depends=('glibc') +optdepends=('nautilus: For nautilus integration') conflicts=() source=() -md5sums=() -source_i686=(https://global.download.synology.com/download/Utility/SynologyDriveClient/3.2.0-13258/Ubuntu/Installer/i686/synology-drive-client-13258.i686.deb) -md5sums_i686=('cb34a639d2dcaf02912f8cb08cf8e536') - -source_x86_64=(https://global.download.synology.com/download/Utility/SynologyDriveClient/3.2.0-13258/Ubuntu/Installer/x86_64/synology-drive-client-13258.x86_64.deb) -md5sums_x86_64=('e220b81a00a39bb032315eabf30dccec') +source_x86_64=(https://global.download.synology.com/download/Utility/SynologyDriveClient/3.2.1-13271/Ubuntu/Installer/x86_64/synology-drive-client-13271.x86_64.deb) +md5sums_x86_64=('1f0ef71fac95217bc529ec3dbfc0e639') package() < cd "$" base-commit: 985988bb5807c615e8d650d6939fbc1aa64ff681 prerequisite-patch-id: 55dcae52e311a26b5e68d848027fb76dc4073d49 --
oysstu commented on 2022-11-25 17:32 (UTC)
The certificate thing seems to be fixed in 3.2.0-13258
Panzki commented on 2022-11-19 09:28 (UTC)
I encountered the same issue, and I was able to resolve it by manually adding the needed root CAs certificate the ~/.SynologyDrive/data/certs.pem file.
I'm using a certificate issued by Let's Encrypt and the root certificate for my certificate was ISRG Root X1. I copied the the root certificate by running:
cat /etc/ca-certificates/extracted/cadir/ISRG_Root_X1.pem > ~/.SynologyDrive/data/certs.pem
After restarting the Synology Drive client HTTPS is working again.
ZEBofx commented on 2022-11-01 20:24 (UTC) (edited on 2022-11-01 20:27 (UTC) by ZEBofx)
I have the same thing : ~/.SynologyDrive/data/certs.pem is empty after the error or after restarting the client. I tried to delete the files, but it recreated it empty.
I just recreated it "by hand" (cat all my CAs > certs.pem), and then "chmod u-w ~/.SynologyDrive/data/certs.pem". Seems to work for now.
fmartingr commented on 2022-11-01 19:53 (UTC) (edited on 2022-11-01 19:57 (UTC) by fmartingr)
I use my linux machine mostly headless now, so I have not been using Synology Drive lately from there. I just upgraded my entire system (including synology drive which is still there) and connected to my synology without problems, using a self-signed certificate but ignoring the warning. Files are syncing both ways just fine. Where are you getting this errors from?
My synology drive server version is 3.0.3-12689.
Edit: ~/.SynologyDrive/data/certs.pem is populated on my case. Maybe deleting it will make the client restore it?
Edit2: Just moved my certs.pem file to somewhere else, closed drive and opening it again create the file again, poppulated.
rlees85 commented on 2022-11-01 19:45 (UTC) (edited on 2022-11-01 19:50 (UTC) by rlees85)
Spoke too soon - still broken after downgrade suggesting its local config issue that gets broken by the new version.
edit: after downgrading I had to:
edit again: turns out its something to do with: ~/.SynologyDrive/data/certs.pem. On 3.2.0 its empty and 3.1.0 its populated.
Copyright © 2004-2023 aurweb Development Team.
AUR packages are user produced content. Any use of the provided files is at your own risk.