All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>,
	Eli Schwartz <eschwartz@gentoo.org>,
	"Carl E. Thompson" <cet@carlthompson.net>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: PSA: Avoid Debian Stable
Date: Wed, 07 Aug 2024 20:58:23 +0200	[thread overview]
Message-ID: <4609869.LvFx2qVVIh@lichtvoll.de> (raw)
In-Reply-To: <41409810.56.1723052597872@mail.carlthompson.net>

I amended the subject line a bit. I am not sure whether Debian Testing or 
Debian Unstable should also be avoided.

And by the way, you probably have the same issue with Ubuntu, unless they 
update bcachefs-tools to new versions in stable releases.

Carl E. Thompson - 07.08.24, 19:43:17 CEST:
> 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.

An option would be to at least ask for a backport.

Whether that is feasible with system based Rust packages in Debian 12 aka 
Bookworm is another story. Or probably there might also be a way to ask 
for removal of the outdated bcachefs-tools package. I agree it has been 
too early to include it in Debian 12. There are users who expect 1. stable 
and 2. most current software. I.e. expect they could use up-to-date 
BCacheFS in Debian 12. But the development process of Debian does not 
really cater for that. Either you have quite recent software, but face 
temporary instabilities or you have stable and soon to be outdated 
software.

One idea to use system based packages is to fix security issues once, 
instead of recompiling a lot of packages that use their own version of 
some Rust dependency.

For Debian 13 I expect BCacheFS tools to be stable enough for inclusion 
into stable release. However… that would still not solve the issue with 
fixing bugs in there during stable support – unless there would be some 
kind of LTS branch of BCacheFS tools by then. Critical fixes probably could 
be backported, that is the usual approach for Debian packages in stable, 
but this also does not work with Firefox ESR after a certain point. They 
update it to the newest ESR once the support for the old one is dropped by 
Mozilla. Cause it would be too much work to backport all security fixes.

Best would probably be to have a bcachefs-tools backport even for Debian 
13. If possible.

Best,
-- 
Martin



  reply	other threads:[~2024-08-07 19:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07  4:34 PSA: Avoid Debian Kent Overstreet
2024-08-07 15:01 ` Eli Schwartz
2024-08-07 16:01   ` Kent Overstreet
2024-08-07 16:09     ` Eli Schwartz
2024-08-07 17:29       ` Kent Overstreet
2024-08-07 17:43         ` Carl E. Thompson
2024-08-07 18:58           ` Martin Steigerwald [this message]
2024-08-07 19:55             ` PSA: Avoid Debian Stable Kent Overstreet
2024-09-03 21:37               ` Martin Steigerwald
2024-09-03 22:15                 ` Kent Overstreet
2024-09-03 23:44                   ` Eli Schwartz
2024-09-04  0:04                     ` Kent Overstreet
2024-09-04  0:31                       ` Eli Schwartz
2024-09-04  0:38                         ` Kent Overstreet
2024-08-07 17:44         ` PSA: Avoid Debian Carl E. Thompson
2024-08-07 18:19           ` Kent Overstreet
2024-08-07 19:04             ` Carl E. Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4609869.LvFx2qVVIh@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=cet@carlthompson.net \
    --cc=eschwartz@gentoo.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.