[Pkg-gtkpod-devel] Bug#620065: fixed in libimobiledevice 1.1.0-3

Julien Lavergne julien.lavergne at gmail.com
Sun Apr 24 20:54:09 UTC 2011


Le 22 avr. 2011 à 08:07, Raphael Hertzog <hertzog at debian.org> a écrit :

> On Fri, 22 Apr 2011, Julien Lavergne wrote:
>> Le Monday 18 April 2011 à 21:27 +0200, Raphael Hertzog a écrit : 
>>> Hi,
>>> 
>>> First of all, I wanted to suggest to drop the Conflicts and just keep the
>>> Replaces. The Replaces is enough, the only problem is that the FDI file
>>> will be lost if libimobiledevice2 is removed while some application
>>> still use libimobiledevice1 (the other cases are correctly handled by dpkg
>>> whatever the order of installation of the packages).
>> Ok, It sounds reasonable. I'll try to update it this week-end, but feel
>> free to NMU it if it's an emergency.
> 
> This WE should be fine, thanks.
> 
>>>> Those uploads will be needed anyway, as I think libimobiledevice2
>>>> is/will not be API-compatible with libimobiledevice1. So, could be a
>>>> moot point.
>>> 
>>> Julien (Lavergne), do you know if this is the case?
>> For now, only new API was added, but as they declared the API not
>> stable, we can't be sure what is going to change. To be safe, I prefer
>> to assume that the API can change, that's why it should stay in
>> experimental until 1.2.0 is released.
> 
> The stable release of "gvfs" depends on this new API apparently due
> to this new feature:
> https://bugzilla.gnome.org/show_bug.cgi?id=636132
> 
> Do you know when upstream plans to release 1.2.0?

No release date, unfortunately.
The devs are working on it, but as there are not many, the policy is "When it's done". Last time I check, the progress was good, and not so far from the release.

Regards,
Julien Lavergne




More information about the Pkg-gtkpod-devel mailing list