Re: [Opensync-devel] Updating debian unstable

[Michael B. <mb...@gm...>]

Hi,

On Wed, Sep 15, 2010 at 03:01:45AM -0400, Chris Frey wrote:
> On Wed, Sep 15, 2010 at 06:56:13PM +1200, Daniel Gollub wrote:
> > Actually we asked all distros to not package 0.3x ... i guess thats the 
> > reason. I would prefer to keep it like that, without complete capabilities 
> > implementation a slow-sync will cause data-loss or every single entry 
> > duplicated. Without this and with 0.3x packages in Distros, people would 
> > install them and turn their "productive" device into a "testing" device 
> > without knowing it ...
> 
> Oh no, not for official release, but there is already a libopensync1exp7
> package in debian unstable which is out of date, and with 0.22 gone in
> Debian, there's no harm anymore in 0.39 staying in the unstable and
> experimental trees.

It is not out of date, it is the currently released development release,
as far as I know.  Also 0.22, is still in the stable release, it is not
gone from Debian entirely, just from testing/unstable. (There was talk
about reviving 0.22 just for the python plugins, which apparently seem
to work well for some people still, but I did not get around it so far,
and with the freeze in effect I doubt it is doable)

We could package subversion snapshots as well, but for the first part of
2010, I was not aware of any major advances in opensync which would have
warranted that.

Note that libopensync1exp* has to be manually approved for each new
version right now as the API keeps changing and so does the package
name, so I am not sure very frequent uploads make that much sense.

> > Once capabilities support got implemented i'm happy with realsing 0.40 and 
> > lift the package ban. Anything else would be releasing software which is 
> > broken.
> 
> I don't want to see any distro including 0.39 in official releases.
> This is for testing.  Users would test things for us if there
> were binary packages available.  Right now I end up on IRC trying to
> help people compile, or trying to figure out why old binary packages
> don't work. :-)

There's no danger of Debian shipping 0.3x in the next stable release, at
least :)


Michael