> > Package: libssl0.9.8 > > Version: 0.9.8-3 [Kurt Roeckx] > You mean 0.9.8a-1 has the bug since 0.9.8-3 didn't have symbol > versioning yet.
Uh, yeah. Sorry. I started to file the bug before upgrading, since that's when I noticed the effects. > It looks like we did something wrong, or something is broken. We > have this in shlibs.local: > libcrypto 0.9.8 libssl0.9.8 (>= 0.9.8a-1) > libssl 0.9.8 libssl0.9.8 (>= 0.9.8a-1) > > Yet /var/lib/dpkg/info/libssl0.9.8.shlibs says: > libcrypto 0.9.8 libssl0.9.8 > libssl 0.9.8 libssl0.9.8 I guess the latter is autogenerated because the tools couldn't find the former. I'd double-check the filename they're looking for. > > I had a previous version of libssl0.9.8 on my system, and got a > > failure trying to link to a library that uses libssl0.9.8, because > > of lack of symbol versions. > > I assume that the library you're trying to link to is linked against > a newer libssl0.9.8 with symbol versioning? I can only assume so. I have no way of knowing for sure. It did look for versioned symbols, and upgrading libssl0.9.8 fixed my problem. > There never was a version (of libssl0.9.8) in testing that didn't > have symbol versioning. So it isn't that important to get fixed, but > I'll look into it. Agreed that it isn't a very serious bug. OTOH, making sure your shlibs file is actually being used might pay off later. (:
signature.asc
Description: Digital signature
