Thanks for the info. I managed to get around the problem for now using libqt4-maemo5 and writing in all dependencies manually, thus leaving out the newest libhildon* libraries. Even if the application was compiled against the newest libraries, it didn't seem to be a problem to run it on the device. In my situation I was moving towards Qt4.6 anyways, so using libqt4-maemo5 was not really an issue in the end.
you can try to force install that package without manually modifying depencies and just let the ${shlibsepends} set them. For the libhildon case it may work, at least it did for my packages...
dpkg --force all -i package.deb
Didn't see a solution anywhere, but managed to squeeze my Search Tool through the new libhildon1 dependencies. Just create a debian/shlibs.local file and fill it with
That should be enough to keep the autobuilder dpkg-shlibdeps happy.
EDIT: The main problem actually was to find what exactly mean the first two values (which should be name and version). Turned out they are the name of the library in /usr/lib and the major version that comes right after .so. Didn't expect libhildon1 to have major version of 0...
epends} set them. For the libhildon case it may work, at least it did for my packages...