On 2021-11-23 17:55:54 +0100, Guillem Jover wrote: > Nice cleanup with the odbc packaging! Unfortunately the new > transitional package looks a bit broken. It contains a dangling > symlink: > > $ ls -la /usr/lib/x86_64-linux-gnu/libodbccr.so.1 > ls: cannot access '/usr/lib/x86_64-linux-gnu/libodbccr.so.1': No such file > or directory > > Which whould point to libodbccr.so.2. But then the package is also > missing a dependency on libodbccr2.
I'm wondering. Why was the soname incremented? This should normally not be done unless the ABI is backward-incompatible. But in such a case, providing a symlink is wrong and could break applications that expect the old ABI. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
