https://bugs.kde.org/show_bug.cgi?id=445391
Simon Persson changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=445391
--- Comment #8 from Jacek Rzęsista ---
(In reply to Simon Persson from comment #7)
> (In reply to Jacek Rzęsista from comment #6)
> > (In reply to Chris Rizzitello from comment #2)
> > > This is not a "bug"
> > > The end user must mount a SMB share to
https://bugs.kde.org/show_bug.cgi?id=445391
--- Comment #7 from Simon Persson ---
(In reply to Jacek Rzęsista from comment #6)
> (In reply to Chris Rizzitello from comment #2)
> > This is not a "bug"
> > The end user must mount a SMB share to use as an rsync target.
> > Rsync is known to not
https://bugs.kde.org/show_bug.cgi?id=445391
Jacek Rzęsista changed:
What|Removed |Added
CC||ja...@jcentrum.net
--- Comment #6 from Jacek
https://bugs.kde.org/show_bug.cgi?id=445391
Simon Persson changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=445391
--- Comment #4 from lrdarkne...@yahoo.de ---
Hmm okay that makes this problem a lot clearer to me.
My server (TrueNAS) supports the rsync daemon, but it seems quite complicate to
setup and use the rsync protocol.
Kup doesn't provide any feedback to the
https://bugs.kde.org/show_bug.cgi?id=445391
--- Comment #3 from i...@gmx.net ---
Yes. The application really needs to either make it clear that it has created
an invalid definition. Or better, not allow an invalid definition that cannot
work.
Alternatively, if mounting is really necessary, it
https://bugs.kde.org/show_bug.cgi?id=445391
Chris Rizzitello changed:
What|Removed |Added
CC||rizzite...@kde.org
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=445391
i...@gmx.net changed:
What|Removed |Added
CC||i...@gmx.net
--- Comment #1 from i...@gmx.net
