[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted btrfs-progs 6.16-2 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 07 Sep 2025 16:03:07 -0400
Source: btrfs-progs
Architecture: source
Version: 6.16-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas D Steeves <sten@debian.org>
Changed-By: Nicholas D Steeves <sten@debian.org>
Closes: 1060069
Changes:
 btrfs-progs (6.16-2) unstable; urgency=medium
 .
   * Drop support for converting from reiserfs, because reiserfs was dropped from
     Linux during the 6.13 release cycle
     (http://kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13). Debian 13
     "trixie" included support for converting reiserfs filesystems to btrfs and
     may be used by anyone who wishes to experiment with in-place conversion
     (Closes: #1060069).  Backup and restore or replication continues to be
     recommended over in-place conversion.
Checksums-Sha1:
 d37748b5c08820108a7668738c6d2e0c138bc69d 2536 btrfs-progs_6.16-2.dsc
 f43696e4bb694a26204ed57086f67df3a77cc622 20356 btrfs-progs_6.16-2.debian.tar.xz
 fb2070ebe0499330271bc9a1dfdfb99b6c2293c8 11418 btrfs-progs_6.16-2_amd64.buildinfo
Checksums-Sha256:
 ab21512a446cdeb2e8cb05cc469d3b5991e9800ce536728db940283e1aa9108e 2536 btrfs-progs_6.16-2.dsc
 f6ffa607644ca80f812987d647f51c6ef814b45551f59ecd821e16a425f317fc 20356 btrfs-progs_6.16-2.debian.tar.xz
 aced577e03b0106769933e19cfd6ff8fc484ea8401e9b2d8acd4e811f50d6633 11418 btrfs-progs_6.16-2_amd64.buildinfo
Files:
 9c56c1d4f1bd18b23b7112899f001af5 2536 admin optional btrfs-progs_6.16-2.dsc
 b57008abc16c190726e3ea1e4edc09e0 20356 admin optional btrfs-progs_6.16-2.debian.tar.xz
 9662ef0f4d276f4682d74a40dcbfb3d0 11418 admin optional btrfs-progs_6.16-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmi95aAACgkQWogwR199
EGF+uA//U9SiZb0/EyyFdcjstKLAkMESxfp4t090R3+sqQXj785n9NQCZiee6HZY
j9petnw/3mqWaZqVBke07I23qeqhYoSoskMv7c6QP9fDlmLboZ99XbYHWnWLhBYP
MRy/LQJQgFhNz6HxKfTgq6//zKjRwR36+LDmdhwexnpNfG33Z5FZEl3UsZ5OT3pr
CvHRZU5c2ebpJ5TMkBfdj0BS1RsrdjHaB+dssO95u3RPjdNNQMzCzsx7SnrFHFpH
UagQ6V0RGHjvvsuwUeByiHvJIqtS7t/Ch9iBhGlPrfzo+D2DUJwQZgJJHLQOdC3M
ETHN6EtlK5c1UGxaBDYgS8GQ9MtHFOeqz9jKosrVnxKXH+5x6b7TOrFM/AofX3wy
kQXM8EIkGarCbfCvpsl7LmpLbnQlCZvn38wntF/hY+z0Sg718Z6ZgVdkd2Q6I4Su
QU9y1O9OcHBVG1iK+4egndwt+KwU7Cyu6DV6e4sDfXQvaimeP4+ONe0j8ROFkRiI
xr9+0eEitTkfisP8NC21Y71fHz+0Ql5z1NPim+WPGPFAic9+kXD4wvfDBeBKQzTA
oGMBINGZnhddmWq5ApSUuHynt6g27lADftZDPM9s5elVDe2g2mN13SRAcpID58RI
36NkfVO9HwmnEl6mAnCfP6pENC3aXKCcqdqKhCyzWTD8c3HFQ2k=
=xPwM
-----END PGP SIGNATURE-----

Attachment: pgpg1WhPWEVZu.pgp
Description: PGP signature


Reply to: