Joey Hess wrote: > > Of course it's difficult to tell without any technical details, but my > educated guess would be that the non-free binary-only software they tried > to use was linked with -rpath, so it will only work if some library is in a > specific place. Which is of course, its own fault, and can be worked > around.
Another possibility is that their 'technician' was incorrect, and that it was actually the *versions* of libraries that was at fault. For example, the application was built against glibc 2.1.x, but they tried running it on Slink with glibc 2.0.7 (and it didn't work). This is nobody's fault, but IMHO doesn't mean that Debian is 'incompatible' - all it takes is an upgrade of libc to get it to work. Matthew
