Package: php-horde-dav Version: 1.0.4-1 Severity: normal Control: affects -1 php-sabre-dav
Hi Mathieu,
Thomas Müller announced yesterday [1] that ownCloud 7 will ship
SabreDAV 1.8. We thus intend to maintain those versions for Debian
Jessie. A pre alpha version of ownCloud 7 is already available in
experimental, and I just updated the experimental php-sabre-dav package
to version 1.8 (as 2.0.0+really1.8.10-2 since we already pushed the
version 2 recently).
1: http://mailman.owncloud.org/pipermail/devel/2014-May/000248.html
We intend to follow upstream schedule [2] as closely as possible, and
will upload ownCloud 7 (and thus SabreDAV 1.8) to unstable once ready,
i.e. on July 16th according to the current plan.
2: https://github.com/owncloud/core/wiki/ownCloud-7-Features
In order to check that everything will work as planned, the current
php-sabre-dav from experimental is ready for a transition. You’re
welcome to prepare an experimental php-horde-dav package depending on:
php-sabre-dav (>= 2.0.0+really1.8),
php-sabre-dav (<< 2.0.0+really1.9)
dropping the current conflicts (php-sabre-dav already depend on the
needed php-sabre-vobject version and conflicts with php-sabre-http), and
of course without the current embedded code copy of php-sabre-dav (and
php-sabre-vobject).
php-sabre-dav already breaks and replaces php-horde-dav (<< 1.0.4-1+) so
you should be able to use any version string you like for experimental.
Around July 16th, I intend to push this version of php-sabre-dav to
unstable, and the real transition can then begin, with a proper version
string, i.e. you’ll need to update the dependencies in unstable to:
php-sabre-dav (>= 1.8), php-sabre-dav (<< 1.9)
Does the proposed plan sound good to you, did I miss anything, do you
need something else from me? I’ll ping this bug (or open a new one) when
the transition will be ready for unstable, or use any other
communication way you’d prefer.
Cheers
David
signature.asc
Description: Digital signature
