Yeah, this is fixed in Warty ... looks like Goswin tripped the same bug as us
and lied in his bug report (the actual libdir is /usr/lib64/../lib or
something); our dpkg-shlibdeps is more intelligent about this.
I don't think it's a libtool bug either, Garbage-In-Garbage-Out.
I haven't punted the fix to Debian yet, am waiting until post-sarge before
another dpkg so the release managers don't have my balls for dinner.
Yeah, this is fixed in Warty ... looks like Goswin tripped the same bug as us
and lied in his bug report (the actual libdir is /usr/lib64/../lib or
something); our dpkg-shlibdeps is more intelligent about this.
I don't think it's a libtool bug either, Garbage- In-Garbage- Out.
I haven't punted the fix to Debian yet, am waiting until post-sarge before
another dpkg so the release managers don't have my balls for dinner.