Is Sailsync OwnCloud still working for you?

Applications
13

Hi, Sailsync ownCloud developer here.

Thanks to the users who reported the issue (and thanks to nephros for building and packaging a new version of the client).

A bit of background:

Nextcloud 31 requires a minimum client version of 2.7.0. Sailsync ownCloud currently ships with owncloudcmd 2.5.2. I’ve attempted to upgrade to 2.7.0 but it has a minimum build dependency of Qt 5.12 (SailfishOS ships Qt 5.6).

The issue is further complicated by the fact that I live in Australia. Last year, Australia shutdown its 3G network, and in the process blacklisted a large number of 4G/5G phones (including most Sony phones that support SailfishOS). This means I’ve been without a fully-working SailfishOS device since ~October last year.

Possible solution (based on nephros’s packages, thanks):

See if you can override the path to the sync command in: /usr/share/harbour-io.edin.projects.sailsync-owncloud/buildconstants.py

Currently the values are set to:

OWNCLOUDCMD_COMMAND = "/usr/share/harbour-io.edin.projects.sailsync-owncloud/lib/owncloud/bin/owncloudcmd -u {username} -p {password} {local_path} {remote_url}"
OWNCLOUDCMD_TRUSTSSL_COMMAND = "/usr/share/harbour-io.edin.projects.sailsync-owncloud/lib/owncloud/bin/owncloudcmd --trust -u {username} -p {password} {local_path} {remote_url}"
OWNCLOUDCMD_VERSION_COMMAND = "/usr/share/harbour-io.edin.projects.sailsync-owncloud/lib/owncloud/bin/owncloudcmd --version"
OWNCLOUDCMD_LD_LIBRARY_PATH = "/usr/share/harbour-io.edin.projects.sailsync-owncloud/lib/owncloud/lib64"

I’m unsure if sandboxing will allow the owncloudcmd binary to exist outside the Sailsync ownCloud directory structure, but it’s worth a try.

Finally, there’s currently too much friction (e.g. outdated libraries, unavailable phones) for me to continue maintaining my applications. If anyone wants to take up maintainership, I’d be happy to hand it over (and help where I can).

8 Likes