Hi, For me there was a problem which slipped through a release, ok that's unfortunate, but now I would naively expect we try to make it less intrusive to users who have been caught in this. (IMO I am not sure on Debian side it was a good idea to push a soname change + package name change which had always meant to be temporary and reverted before the release, but this is not a discussion for this thread). For me I don't really see how just adding the symlink mentioned at the beginning can cause more harm than the soname and package name caused already, and on the other side I see this fix at least some cases (it would in particular make Oracle instant client work out of the box, provided you install the package libaio1t64 beforehand).
The second part of the potential "compatibility fix" is the problem of package being renamed, and naively I would expect to have some compat package that would install the "new" (which is temporary) name. Indeed I don't see much the value in forcing every third party packager to have a special case in their own dependencies, and depend on libaio1 in Ubuntu <= 22.04 and future Ubuntu >= 26.04 but depend on libaio1t64 in Ubuntu 24.04, and I do see frustration on third part side for this specific case. (Note: this is my view only, as both a user of ubuntu, and a third party packager for packages internal to my organization, which depend on libaio and did hit this issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067501 Title: Ubuntu noble is missing libaio.so.1 compat symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/2067501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
