On Tue, Sep 06, 2005 at 05:07:55PM +0200, Christoph Martin wrote: > severity 321133 normal > tags 321133 wontfix > thanks
> Steve Langasek schrieb: > > Well, this version of libssl0.9.7 was never in a stable release; there was > > no libssl0.9.7 in woody, and sarge shipped with 0.9.7e-3. So, since this > > problem wasn't noticed until now, that's definitely an unsupported > > configuration that isn't going to be fixed (there's no way we're going to go > > back now and change the package name in sarge). > openssl is still considered as unstable from upstream. So they change > ABI without notification. I can't do anything now since sarge is released. > I am considering changing the shlibs.local files any time when I release > a new upstream version. When you get to the point that you're ready to package a new upstream version, I'd like to talk to you about some debhelper-based options that would let you reliably detect ABI changes, so you can avoid both ABI breakage and gratuitous package renames. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
