On Sun, Aug 23, 2015 at 22:26:34 +0200, Sandro Knauß wrote: > the version 1.6.4+dfsg-1 of owncloud client can't interact with owncloud > server > 8.1 [#791721]. This versionnumber 1.7.0~beta1+really1.6.4+dfsg-1 > is created by acident. It is simply the upstream version 1.6.4. The > prefix is only needed, becuase one time 1.7.0~beta1 was push to unstable > instead of experimental. > > The problem is so far that upstream server checks the version of the client > and disallows the connection with an older client (< 1.7). Upstream says, > that they do it, because the older client is very unstable und not > reliable. It is so far possible to disable this feature on the server. > > As far as I see different solutions to improve: > * Either we say, okay client+server from stable works together and do > nothing. > > * Mention the needed change in the stable package. > * Ship a new version via stable > * Ship a version in backports, you only need the client when a new > server is used. > > I think the best UX would be shipping the new client to stable, but I > want to hear yout opition about this issue. > > So far as I looked at the code it is very hard to extract a subset to > cherrypick, there were overall improvments were made. > > I didn't prepare anything for the request so far, because I want to > wait, till I know what possibilities you see. For sure we have to rebuild > owncloud-client another time with qt4 for stable. Because qt5 shipped in > stable is not current enough. > > As diff of the upstream: > > git clone git://anonscm.debian.org/pkg-owncloud/owncloud-client.git > cd owncloud-client > git diff upstream/1.6.4+dfsg..upstream/1.7.1+dfsg --stat csync src > 188 files changed, 8362 insertions(+), 5347 deletions(-) > > Please feel to ask anything, if you missing informations. > Hi,
sorry for the lack of reply for so long. I don't think we're going to want to update stable to a new upstream version, jessie-backports is probably the way to go here. Cheers, Julien
