Comment 9 for bug 259139

Hate to bump an old bug... but it seems silly to create another one for essentially the same issue.

I am currently packaging a proprietary application as an Ubuntu package (the MacroView SCADA system, as it so happens). Host platform is Ubuntu 10.04 LTS i386.

In previous releases, the upstream software package linked against libncurses.so.5. Now it links against libtinfo.so.5, and thus I now have an issue getting dpkg-buildpackage to co-operate.

I tried making a dummy package to install the necessary symlink... this might fool a runtime application, but it does not fool dpkg-shlibdeps, which complains loudly:

dpkg-shlibdeps: warning: /lib/libtinfo.so.5 has an unexpected SONAME (libncurses.so.5)
dpkg-shlibdeps: error: no dependency information found for /lib/libtinfo.so.5 (used by debian/macroview/usr/lib/macro/imgstat64).

Now, all very well to argue that the build scripts should take care of this; however in my situation, the "build" scripts are taking a tarball containing precompiled binaries and copying them into the appropriate directories for packaging -- I do not control the linking process. So the "solution" in comment #8 will not work for this use case.

Is it possible that this issue could be addressed?