Hi Klaas, Danimo,
On Monday, November 18, 2013 11:09:25 Sebastian Kügler wrote:
> On Tuesday, November 05, 2013 13:03:30 Sebastian Kügler wrote:
> > > BTW, is it planned to release for example the KCM module with "normal"
> > > desktop KDE at some point of time?
> >
> > No. I'd like to keep it al
On Tuesday, November 05, 2013 13:03:30 Sebastian Kügler wrote:
> > BTW, is it planned to release for example the KCM module with "normal"
> > desktop KDE at some point of time?
>
> No. I'd like to keep it all in one repository, and merge the plasmaclient
> branch upstream, so we don't run into o
Hi Klaas,
On Tuesday, November 05, 2013 10:25:56 you wrote:
> On 01.11.2013 13:12, Sebastian Kügler wrote:
> > That said, you'll need to build mirall to get the headless Plasma client.
> > Pull from https://github.com/sebasje/mirall.git, checkout the
> > plasmaclient branch and build that. It will
On 01.11.2013 13:12, Sebastian Kügler wrote:
Hi Sebas,
That said, you'll need to build mirall to get the headless Plasma client. Pull
from https://github.com/sebasje/mirall.git, checkout the plasmaclient branch
and build that. It will build what you need additionally to the "normal"
mirall. The
Sebastian,
thanks for asking.
It's not really urgent but on the long run it would be nice to have this
gui-less sync daemon.
It would be even much more useful to me, if the ocsync client certificate
auth patch which I sent to this list in a different thread could be made
available to owncloudsyncd
On Friday, November 01, 2013 19:30:09 Dr. Johannes Zellner wrote:
> thanks
>
> does it work with csync as pulled
> from git://git.csync.org/users/freitag/csync.git ?
>
> compilation stops with this:
>
>
> csyncthread.cpp:337:74: error: ‘csync_set_overall_progress_callback’ was not
> declared in
On 03.11.2013 20:26, Jakub Moscicki wrote:
Hi Klaas,
Do you mind if we maintain that in ownClouds github for people who are
interested to build on their own? And maybe enhance it to build a git checkout?
Well, maybe you can do this enhancement?
Absolutely! The easier it will be for people t
Hi Klaas,
> Do you mind if we maintain that in ownClouds github for people who are
> interested to build on their own? And maybe enhance it to build a git
> checkout? Well, maybe you can do this enhancement?
Absolutely! The easier it will be for people to build, test and integrate
owncloud - t
Hi,
thanks. The syntax for accessing ownclouds://... was the missing piece of
information I'd needed. This seems also to work with ocsync as it comes
with debian.
It complains about not trusting the server certificate and asks me every
time for confirmation→ how can I tell ocsyue to trust the se
On 01.11.2013 19:50, Jakub Moscicki wrote:
Hi Kuba,
Here you have my ocsync build script for linux.
https://box.cern.ch/owncloud/public.php?service=files&t=f694ef2c0f2c109df87b2fd90c9f8079
Wow, this seems like a little gem given the kind of mess we created with
the various branches and proje
Hello,
Yes, it does the background sync of the owncloud account - just like the
desktop client but without the gui. Very useful in some cases.
Here you have my ocsync build script for linux.
https://box.cern.ch/owncloud/public.php?service=files&t=f694ef2c0f2c109df87b2fd90c9f8079
You may need t
Kuba,
does ocsync work with webdav, i.e. synchronizing with the owncloud server?
--
Johannes
2013/11/1 Jakub Moscicki
> Hello,
>
> For your information, I use quite successfully the ocsync executable from
> a cron: ocsync -d 100 -c local_dir remote_dir
>
> kuba
>
> --
>
> On Nov 1, 2013, at
Sebastian,
thanks
does it work with csync as pulled from git://
git.csync.org/users/freitag/csync.git ?
compilation stops with this:
csyncthread.cpp:337:74: error: ‘csync_set_overall_progress_callback’ was
not declared in this scope
csync_set_overall_progress_callback( _csync_ctx, cb_overa
Hello,
For your information, I use quite successfully the ocsync executable from a
cron: ocsync -d 100 -c local_dir remote_dir
kuba
--
On Nov 1, 2013, at 1:12 PM, Sebastian Kügler
wrote:
> On Friday, November 01, 2013 12:04:47 Dr. Johannes Zellner wrote:
>> yes I'd be interested to use the
On Friday, November 01, 2013 12:04:47 Dr. Johannes Zellner wrote:
> yes I'd be interested to use the plasma non-gui sync process, since I didn't
> succeed in compiling mirall according
> to http://doc.owncloud.org/desktop/1.4/building.html (it fails with the
> error ‘CSYNC_STATUS’ not being declare
Mirall 1.5 has a different build process (requires ocsync from a different
repo/branch) and is not fit for public use atm.
Am 01.11.2013 um 12:04 schrieb Dr. Johannes Zellner:
> Sebastian,
>
> yes I'd be interested to use the plasma non-gui sync process, since I didn't
> succeed in compiling m
Sebastian,
yes I'd be interested to use the plasma non-gui sync process, since I
didn't succeed in compiling mirall according to
http://doc.owncloud.org/desktop/1.4/building.html (it fails with the error
‘CSYNC_STATUS’ not being declared).
--
Johannes
2013/11/1 Sebastian Kügler
> On Thursday
On Thursday, October 31, 2013 22:34:12 Dr. Johannes Zellner wrote:
> what's the best way to synchronize on a box which doesn't run X (without the
> gui client) on linux?
The Plasma client uses a non-gui synchronization process (controlled via
DBus). If you have an existing configuration (can be c
Hi Daniel,
thanks // is owncloudcmd yet available somewhere at least as source for
compiling myself?
--
Johannes
2013/10/31 Daniel Molkentin
>
> Am 31.10.2013 um 22:34 schrieb Dr. Johannes Zellner:
>
>
> what's the best way to synchronize on a box which doesn't run X (without
> the gui clien
Am 31.10.2013 um 22:34 schrieb Dr. Johannes Zellner:
>
> what's the best way to synchronize on a box which doesn't run X (without the
> gui client) on linux?
>
There is (was?) pyOwnCloud (https://github.com/csawyerYumaed/pyOwnCloud), a
python frontend for csync.
Starting with owncloud Clie
Hi,
what's the best way to synchronize on a box which doesn't run X (without
the gui client) on linux?
--
Johannes
___
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud
21 matches
Mail list logo
