---------- Forwarded message ---------- From: Ludovic Rousseau <ludovic.rouss...@gmail.com> Date: 2009/7/18 Subject: Re: Bug#535667: kpilot: Possible runtime problem with libpisock9 0.12.4 To: Sune Vuorela <s...@vuorela.dk> Cc : Ludovic Rousseau <rouss...@debian.org>, 535...@bugs.debian.org
Sune Vuorela a écrit : > > On Saturday 04 July 2009 11:19:54 Ludovic Rousseau wrote: >> >> Package: kpilot >> Severity: normal >> >> Hello, >> >> Your package kpilot (and also kdepim-kfile-plugins) depends on >> libpisock9. I uploaded a new upstream version of pilot-link 0.12.4 and >> users discovered unplanned problems (#532798 #535565 #535588) with >> jpilot, another application also using libpisock9. >> >> The problem appears when jpilot is compiled against libpisock-dev 0.12.3 >> but executed using libpisock9 0.12.4. > > Hi. That kind of behaviour changes is not acceptable. Packages with their > dependencies fulfilled should just work. > > You basically have the following possibilities: > Rename the libpisock9 package or > roll back the libpisock9 behaviour change or > put in appropriate breaks to libpisock9 I never used Breaks: before. Do I need something like: Package: libpisock9 Breaks: kpilot (<< 4:4.2.4-1), gnome-pilot (<< 2.0.15-2.4), etc. How do I get the exact release number of the broken packages? I you upload kpilot 4:4.2.4-2 to unstable but still linked with the old version of libpisock9 the breaks rule will be incorrect. Or maybe I should only take care of version numbers of the broken packages in Lenny and only support the Lenny -> Squeeze upgrade? Thanks -- Dr. Ludovic Rousseau -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
