Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29635 - kmod's symlinks should be same-directory links
Attached to Project:
Arch Linux
Opened by Jerome Leclanche (Adys) - Friday, 27 April 2012, 06:40 GMT
Last edited by Allan McRae (Allan) - Friday, 27 April 2012, 09:29 GMT
Opened by Jerome Leclanche (Adys) - Friday, 27 April 2012, 06:40 GMT
Last edited by Allan McRae (Allan) - Friday, 27 April 2012, 09:29 GMT
|
DetailsDescription:
symlinks to /bin/kmod (such as modprobe) should be same-directory symlinks. Currently, at least modprobe points to ../usr/bin/kmod. This is a problem if a user attempts a manual usrmerge (merging /bin with /usr/bin and /sbin with /usr/sbin) as the link would then point to /usr/usr/bin/kmod which does not exist. Admittedly it's not specifically recommended anywhere (though the forums deemed it safe), but this should still be corrected. Additional info: Name : kmod Version : 8-1 |
This task depends upon

There are many symlinks that will need manually adjusted if you do a manual usr move... Also, you will likely break your system on the update of any package that has a file of the same name in both /usr/bin and /bin. This change will happen but is entirely unsupported for now.