With DSM7, which is now in beta, a new version was released: 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 computer -arch=('i686' 'x86_64')ĭepends=('glibc' 'libsm' 'binutils' 'fontconfig' -13,11 +13,11 conflicts=('cloudstation-beta' 'cloudstation-3.0' 'cloudstation-drive' ) Not sure how to do pull requests, but here's my PKGBUILD diff. If not on beta DSM, still using 6, drive client updated to 2.0.3. I even tried to delete those entries and add an immutable extended attribute to the filter.sqlite file before starting the application, but that makes it crash on startup.Īnyone else with the same issue? I truly apologize asking this here. And upon closing and opening the application, that table is repopulated with those entries (plus any manual exclusions one can put in place from the GUI). Keep in mind that I tried to manually delete them from the database on-the-fly, but it doesn't help. I noticed this exactly when I realized that no PDF or ODT files were being neither fetched from my NAS nor being sent to it. These are the filetypes I see on that table. Not only I can't upload such files to Drive but my client also doesn't download them due to the filters. That's when I got confirmation that Synology is explicitly blocking A LOT of filetypes on the Linux client. Upon playing around with the Filter option available on the GUI, I could pinpoint that it was adding the entries to the table filter_table. I continued my investigation and found ~/.SynologyDrive/data/db/filter.sqlite. Since you all most likely also USE it, I though it'd be a good place to ask, as I couldn't find it when searching the web.ĭo any of you also noticed that the Synology Drive application (for Linux only!) doesn't sync some very specific filetypes? I investigated this deep, first by looking into the application logs on ~/.SynologyDrive/log and realizing that it was denying syncing such files by saying: T19:28:25 (32080:45248) download-remote-handler.cpp(525): Filtered Event (session): '/path/to/some/file.pdf'. I don't think it's a problem with the package provided here, but rather with the application itself. I can see it finally being killed all together.Guys, I created my account here so I could ask this question: I was just able to analyze Synology Drive application for Linux (v2.0.3-11102, but same applies for v3.0.0-12467 for what I've checked) and I'm baffled that nobody else mentioned it here. Honestly the moment google chrome has a snap package. The software in third party continues to get updated for now but no new additions are accepted. It will eventually go away entirely as snap packages take over the burden with these troublesome packages. It is a horrible system, it has several issues that are unavoidable due to the way it has to operate to comply with licensing and as such can never be "fixed". This is done in real time on the users system every time someone installs software from third party.Ī maintainer takes care of updating these "instructions" as necessary on the backend. To get around this the third party section has the users system follow package build instructions to download and repackage a. This is due to the licencing restrictions of the software contained in this section which do not allow redistribution. The software in the third party section is not actually in the repository. It's a completely new offering from Synology. As already explained its not the same software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |