From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-bcachefs@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Roman Lebedev <lebedev.ri@gmail.com>
Subject: Debian repository: missing release channel (was: Re: bcachefs: DKMS availability/migration general announcement)
Date: Sun, 12 Oct 2025 16:01:16 +0200 [thread overview]
Message-ID: <8592586.T7Z3S40VBb@laptop> (raw)
In-Reply-To: <wpunhwfhumd76tzitnd3zoxnpwq6ipxxzq7rx2igxmtpsr6jns@k3ip5mm6mxtj>
Hi Kent. Hi.
Kent Overstreet - 28.09.25, 21:01:19 CEST:
> - Debian, Ubuntu
>
> We're providing an external repository that has both release channels
> (note: the debian packaging refers to nightly as snapshot). A big thank
> you to Roman Lebedev who did nearly all the work here and put a ton of
> effort into making this clean and well automated.
>
> https://apt.bcachefs.org/
Thanks a lot for this repository! It works nicely with self-compiled 6.16
and 6.17.
I appears to me that the release channel "release" is gone since some
days:
Ign:3 https://apt.bcachefs.org/unstable bcachefs-tools-release InRelease
Err:4 https://apt.bcachefs.org/unstable bcachefs-tools-release Release
404 Not Found [IP: 2a[…]f3::1 443]
Error: The repository 'https://apt.bcachefs.org/unstable bcachefs-tools-
release Release' no longer has a Release file.
In https://apt.bcachefs.org/dists/unstable/dists/ I only find
bcachefs-tools-snapshot
For now I assume that the intention is to bring it back. Especially as the
documentation on https://apt.bcachefs.org still refers to it.
If otherwise, please tell us what your plans are, Kent and Roman.
Thank you.
Best,
--
Martin
next prev parent reply other threads:[~2025-10-12 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 19:01 bcachefs: DKMS availability/migration general announcement Kent Overstreet
2025-10-12 14:01 ` Martin Steigerwald [this message]
2025-10-14 5:47 ` Debian repository: missing release channel (was: Re: bcachefs: DKMS availability/migration general announcement) Martin Steigerwald
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=8592586.T7Z3S40VBb@laptop \
--to=martin@lichtvoll.de \
--cc=kent.overstreet@linux.dev \
--cc=lebedev.ri@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox