Hello Helmut, On 20.04.2018 20:06, Helmut Grohne wrote: > I just looked into the package and only then noticed Christoph's upload. > Let me share a few remarks though: > > * The new upstream release is a bit "strange". Even github uses the > same commit id for both 6.1.5 and 6.1.7. That looks like a mistake to > me.
It is a deliberate decision made by upstream to ensure that the three components of the Seafile client "suite" always use the same version number... Therefore they always re-tag ccnet, even if there are no changes in the meantime. (Strangely, for searpc, they don't do that, but use an even stranger tagging scheme, where there's currently only a Git tag v3.1-latest, though the "internal" version is [correctly] set to 3.0.8...). We decided to just follow along this decision by upstream since just rebuilding the package with a new version is only minorly inconvenient and we wanted to not divert too much from their recommendation. Although I just now thought that if we think this trough, we should also have strict same-version dependencies between the three components, which we don't have right now. > * Did you consider porting to Python 3? It seems that for searpc, there > is a patch to support Python 3 at > https://github.com/haiwen/libsearpc/pull/21. I noticed the Lintian warning and did not override it to keep it as a marker to do that soon. Best regards, Moritz
