| Oh, the author's completely misrepresenting what happened here. We had a major snafu with Debian, where a maintainer volunteered to package bcachefs-tools (this was not something I ever asked for!), and I explained that Debian policy on Rust dependencies would cause problems, and asked him not to do that. But he did debundle, and then down the road he broke the build (by debundled bindgen and ignoring the minimum version we'd specified), and then _sat on it for months_, without even reporting the issue. So Debian users weren't getting updates, and that meant they didn't get a critical bugfix that fixed passing of mount options. Then a bunch of Debian users weren't able to mount in degraded mode when a drive died. And guess who was fielding bug reports? After that is when I insisted that if bcachefs-tools is packaged for debian, dependencies don't get debundled. If you're going to create a mess and drop it in my lap, and it results in users not able to access their filesystem, don't go around bitching about being asked to not repeat that. |
Some suggestions:
- Only "supporting" the latest mainline kernel and latest tools. I prefer to point to CI system configurations to show exactly what it "supported"
- Make this clear via your website and a pinned issue on Github.
- Force users to report the versions they use via an issue template: https://docs.github.com/en/communities/using-templates-to-en.... Immediately close any issues not meeting your version/system requirements without further discussion or thought.