The issue is not fixed by simply quoting policy and taking no action to
correct the problem.
10.5 specifies that "In general, symbolic links within a top-level directory
should be relative".
It should be fairly easy to make a symlink that does work on the target
system if it takes into acc
Package: linux-headers-2.6.32-5-common
Version: 2.6.32-15
If /usr/src is symlinked to a different location, the symlinks within the
package for 'Kbuild' and 'scripts' end up being broken since ../.. traverses
from the actual location.
This is likely a problem for all the versions of this pac
2 matches
Mail list logo