Control: severity -1 important > Severity: serious > Justification: Debian Policy violation
> /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations. I don't believe this is in any way RC -- for Buster nor likely any future release. There's no functional lossage, AFAIK. fsck probably should indeed be moved away from /bin -- it's a legacy atavistic thing that's not of much use to users. Filesystems of old suffered corruption on every unexpected power loss and thus required automated fsck. That's not the case during current millenium. Among mainstream filesystems, only ext4 still ships real fsck (mostly for historic reasons), I think jfs has it trigger log replay; the rest (btrfs, xfs, f2fs, ...) ship just a stub that does nothing. There are actual repair tools but those shouldn't generally be run other than as a hail mary effort; regular checks are supposed to use online scrub instead, without downtime. Moving that stub has been requested in #798072. mkfs on the other hand is widely used by non-root users these days. On raw metal, you generally mkfs once per hardware replacement, while VMs or board images get created often. Thus, I'd rather ask for Policy change than to alter the package. This means, I don't consider the bug to be serious. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Sometimes you benefit from delegating stuff. For example, ⢿⡄⠘⠷⠚⠋⠀ this way I get to be a vegetarian. ⠈⠳⣄⠀⠀⠀⠀
