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

Bug#885765: marked as done (btrfs-progs: Please package 4.14)



Your message dated Tue, 19 Mar 2019 16:50:02 -0600
with message-id <20190319224959.GA4019@navis>
and subject line Re: Bug#885765: btrfs-progs: Please package 4.14
has caused the Debian Bug report #885765,
regarding btrfs-progs: Please package 4.14
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
885765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: btrfs-progs
Version: 4.13.3
Severity: wishlist

Dear maintainer,

please package version 4.14 to get the advantage of zstd running on
kernel 4.14.

Thanks in advance
-- 
   Elimar

--- End Message ---
--- Begin Message ---
Hi Elimar,

On Fri, Dec 29, 2017 at 07:34:17PM +0100, Elimar Riesebieter wrote:
> Source: btrfs-progs
> Version: 4.13.3
> Severity: wishlist
> 
> Dear maintainer,
> 
> please package version 4.14 to get the advantage of zstd running on
> kernel 4.14.
> 
> Thanks in advance
> -- 
>    Elimar

Closing this wishlist bug now, since the requested version of
btrfs-progs has been packaged for a while.  Please note that you might
not want to use any transparent compression supported by btrfs, due to
corruption caused by copying in sparse or hole-punched files. (present
in VM images and some databases).  See the linux-btrfs thread titled
as follows for more info

  Reproducer for "compressed data + hole data corruption bug, 2018
  edition" still works on 4.20.7


Cheers,
Nicholas

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: