Steve Langasek writes:
> You can't leave the name as it is. If you can't support a stable ABI, you
> can't have a shared library shipped in a stable release. Given that the
> name "libopenalpp-cvs" was already used in sarge, you must either change the
> binary package name or drop the shared library to have openalpp-cvs in
> etch.
>
> > The binary was recompiled on the latest unstable and since the upstream
> > version changed I understood it was not necessary to prepend the c2a.
> > Was I wrong ?
>
> New upstream versions are only relevant if they include soname changes.
I understand. I'll maintain shared library numbers and change
them when appropriate. I'll upload an openalpp-cvs1 to avoid problems
with the sarge openalpp-cvs package.
Thanks for educating me and my apologies for not being a
literate debian citizen.
Cheers,
--
Loic Dachary, 12 bd Magenta, 75010 Paris. Tel: 33 8 71 18 43 38
http://www.fsffrance.org/ http://www.dachary.org/loic/gpg.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
