Comment 42 for bug 596327

Revision history for this message
Adam Stylinski (kungfujesus06) wrote :

Ahh, it will replace the headers (the libexiv2-dev package), however the libraries seem to be ok, as most of the Ubuntu packages I've looked at are linked against the full so name and not the top level one.
e.g.:

ldd /usr/lib/libgexiv2.so.0.0.0
 linux-gate.so.1 => (0x00137000)
 libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00266000)
 libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00764000)
 librt.so.1 => /lib/librt.so.1 (0x00aa6000)
 libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x00138000)
 libexiv2.so.6 => /usr/lib/libexiv2.so.6 (0x0045e000)
 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00110000)
 libpthread.so.0 => /lib/libpthread.so.0 (0x00241000)
 libc.so.6 => /lib/libc.so.6 (0x00769000)
 libpcre.so.3 => /lib/libpcre.so.3 (0x00c5a000)
 /lib/ld-linux.so.2 (0x00440000)
 libz.so.1 => /lib/libz.so.1 (0x00bd8000)
 libexpat.so.1 => /lib/libexpat.so.1 (0x00bab000)
 libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00d43000)
 libm.so.6 => /lib/libm.so.6 (0x00207000)

Hopefully the newly built packages against this lib will from this point forward look at the symlink destination for the so.0.0 when they undergo linking.