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#49323 - [dosfstools] Missing symlinks
Attached to Project:
Arch Linux
Opened by Nicolai Syvertsen (saivert) - Friday, 13 May 2016, 20:52 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 14 May 2016, 18:36 GMT
Opened by Nicolai Syvertsen (saivert) - Friday, 13 May 2016, 20:52 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 14 May 2016, 18:36 GMT
|
Detailsdosfstools has to be configured so symlinks are generated.
The current PKGBUILD does not do this. From README: The ./configure script has an option --enable-compat-symlinks that will configure the build to symlink older names of the tools to the current ones on installation. These are dosfsck, fsck.msdos and fsck.vfat for fsck.fat, mkdosfs, mkfs.msdos and mkfs.vfat for mkfs.fat and dosfslabel for fatlabel. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Saturday, 14 May 2016, 18:36 GMT
Reason for closing: Fixed
Additional comments about closing: 4.0-2
Saturday, 14 May 2016, 18:36 GMT
Reason for closing: Fixed
Additional comments about closing: 4.0-2
Should we report to upstream all tools that still refer to the now missing symlinks?
What if these projects refuse to do that? Or that Arch Linux is the only distro that packages dosfstools without the symlinks?
Sticking close to upstream is one thing, breaking things is another.