I think I need to explain my priorities. My #1 priority is ensuring that users have a reliable filesystem. There are real consequences for mistakes in this work. We've seen that with btrfs, where there are still users showing up regularly on IRC and the mailing list with bricked filesystems trying to get help. That shouldn't happen, and ensuring that it doesn't is my number one goal.
Think about the users, and think about what happens if the filesystem fails. That's people's work, that's people's lives at risk. While I'm sure you're all wonderful people, and I'd never want to be a dick to any of you for no reason (I've been running Debian for decades) - your feelings are not my biggest priority. Getting this right so users can have something reliable is. Once we've got all the difficult issues sorted out, once we know our priorities are in the right place, _then_ we can get a beer and be nice to each other. Responsibilities come first. So: If bcachefs-tools is going to be packaged for Debian, I just want it done right. Let me make it clear that I didn't ask for bcachefs-tools to be packaged for Debian; Jonathan took that on himself and dropped a hot mess in my lap. Let's please not do that again; users weren't able to access their filesystems because of what happened. I laid out my asks on the bcachefs mailing list here: https://lore.kernel.org/linux-bcachefs/36xhap5tafvm4boiy3acu5kxlhkvnp32wp3oknbfbkxbdkeq7r@galecvidi3bn/T/#m854ffaa195fe62d67e0a120943d52dcb97b9bdbf If Debian isn't able to be flexible on its unbundling policies, and if we expect there'll be future friction - that's ok! don't package it! There's other distros out there, bcachefs doesn't have to be in all of them, at least not any time soon.
