> I think it is the same thing that @paelzer also encountered

Indeed it is. We have lib64 and include symlinks conflicting. So the issues are:
a) the conflicting symlinks between packages
b) the fact that a non-dev package has a include directory (for header files).

Ideally, we should have:
libfooN install only the lib64 symlink
libfoo-dev install only the include symlink

But these symlinks are also library-independent, so some sort of base
package that is always installed should create them. There are options,
but not this late in the release.

Anyway, right now these issues are not creating errors, just a lintian
warning, and an odd smell. And you have tested it as is. Introducing
that change now is risky since we are so close to release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141744

Title:
  [needs-packaging] cuda-13-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cuda-cccl-13-1/+bug/2141744/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to