Again, my point was (in my opinion) the bcachefs mailing list is probably not the best place to argue about whether Debian's policies / procedures are a good idea.
Of course I wasn't suggesting that bcachefs and the corresponding userspace tools need to be "perfect" before being included in Debian stable. But IMO they should at least be reasonably _stable_ to be included in Debian stable and bcachefs definitely wasn't at the time of its inclusion. Debian isn't Arch. As far as Debian unstable goes, I have no strong opinions on that. BTW, I'm not trying to be critical of you or of bcachefs. I have been using it on my personal systems for years now since long before it was in the kernel and there have been relatively few bumps on the road along the way and I have never lost any data. I'm impressed with what you've accomplished and have even donated my own personal money to you. However, as good as bcachefs is, based on the bug reports and rapid changes I've seen on this list I don't think it's truly stable yet. That's just my opinion. Carl > On 2024-08-07 11:19 AM PDT Kent Overstreet <[email protected]> wrote: > > > On Wed, Aug 07, 2024 at 10:44:19AM GMT, Carl E. Thompson wrote: > > Whether or not the concept of Debian is a good idea probably isn't a > > constructive discussion for this list. > > > > The problem here is that what was essentially an _alpha_ piece of > > software for what at the time was essentially an _alpha_ filesystem > > was allowed into the _stable_ release of Debian at all. Whoever on the > > Debian side allowed its inclusion dropped the ball. > > We're primarily talking about the package in Debian _unstable_, although > the ancient -tools package in stable is also causing problems. The > package in unstable is at 1.9.1, and we're just trying to get it to > 1.9.4. > > And you're blameshifting and making excuses. System critical packages > (and the filesystem is about as critical as it gets) absolutely need > timely updates, no matter what stage of the lifecycle it's at. > > "Don't include it until it's perfect" is not an answer, because: > a) there will also be a period of stabilization for the distro rollout > itself where we find bugs that are specific to distro packaging and > distro process > b) software is never perfect > > a) is what's going on here, and it's turning into a whole thing because > it's a Debian policy that's causing problems, and the Debian package > maintainer's response to that was "of course we won't change our policy". > > So given that, and the number of bugs in my inbox from Debian users for > stuff that's already been fixed, I really have no choice but to tell > users to stay away from Debian until this gets sorted.
