On Mon, Nov 21, 2005 at 02:59:55PM +0100, jerome lacoste wrote: > libmultisync-plugin-evolution needs to be built against libebook1.2-5 > instead of libebook1.2-3 and deployed in experimental.
The multisync maintainer seems to be absent and upstream development has stopped, and now concentrates on opensync. Thus, I am not sure an upload to experimental is warranted. > 2 questions: > > - I tried changing the source package to point to the new libebook, > but it seems that this information is not in the package, but found at > runtime. The package only depends on libebook1.2. I guess there's not > much I can do... Just rebuilding against the experimental libraries should work, then, I guess. > - Could the priority be increased? Otherwise when evolution 2.4 goes > into unstable, multisync will be broken (as it is for me right now, > using experimental). Looking at the bug list, I would assume multisync is broken in unstable as well, with or without experimental libraries. I plan to update the multisync package to the last version in CVS (to which no more commit apparently are made), and get it built for unstable, before moving on to opensync. If the package will need rebuilds for new versions of evolution libraries in unstable, those will be done. This is all assuming that the maintainer will not pop up again. Michael -- Michael Banck Debian Developer [EMAIL PROTECTED] http://www.advogato.org/person/mbanck/diary.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
