Hello and thanks for this bug report. The SONAME bump has been done deliberately, see this changelog entry (from version 0.3.113-6):
- Perform a SONAME bump to avoid stomping on upstream SONAME. Once and if
the new symbols are accepted by upstream then we can merge that back
into libaio.so.1 and drop the t64 packages and temporarily provide
a compat symlink for the t64 SONAME for a smooth transition back. This
should also be an easier way to revert this transition when there are
no file conflicts involved, and does not block on upstream support.
I didn't go into the details of the problem, but I doubt the compatibility symlink can be added as it would potentially cause the "stomping on upstream SONAME" that the package maintainer wants to avoid.
If you still believe this can be done, I suggest filing a bug against the libaio Debian package:
Hello and thanks for this bug report. The SONAME bump has been done deliberately, see this changelog entry (from version 0.3.113-6):
- Perform a SONAME bump to avoid stomping on upstream SONAME. Once and if
the new symbols are accepted by upstream then we can merge that back
into libaio.so.1 and drop the t64 packages and temporarily provide
a compat symlink for the t64 SONAME for a smooth transition back. This
should also be an easier way to revert this transition when there are
no file conflicts involved, and does not block on upstream support.
I didn't go into the details of the problem, but I doubt the compatibility symlink can be added as it would potentially cause the "stomping on upstream SONAME" that the package maintainer wants to avoid.
If you still believe this can be done, I suggest filing a bug against the libaio Debian package:
https:/ /bugs.debian. org/cgi- bin/pkgreport. cgi?src= libaio
as the Ubuntu package is currently a sync from Debian, and this kind of issue is better fixed upstream (= in Debian) when possible.
I'm marking this as Incomplete for now, but if you agree this won't be fixed as suggested, please mark this bug as a Wontfix. Thanks!