Hello,
> 

> > I managed to setup a Debian Forky VM with a separate 20G qcow disk and 
> > format/mount it as ZFS. Wasn't too
> > much trouble.
> > 
> > But the test suite (built the package with gbp buildpackage on the VM 
> > directly) on both ext4 and ZFS
> > built and the tests ran fine.
> > 
> > I wonder if my ZFS setup isn't as "complicated" as yours ? Perhaps the VM 
> > adds some perfection into the mix ?
> 
> It turns out upstream has found the root-cause, described it very well in the 
> GitHub issue and fixed the issue
> in https://github.com/folbricht/desync/pull/356

So for completeness I managed to reproduce the issue with the same ZFS settings 
as upstream:

  echo 1 | sudo tee /sys/module/zfs/parameters/zfs_bclone_enabled
  sudo zfs set recordsize=128K tank/build


And I made double sure the build was done on that drive too:

  export TMPDIR=/tank/build/tmp
  mkdir -p "$TMPDIR"
  dpkg-buildpackage -us -uc -b



> Once upstream releases a new version I will attempt to get it into Debian 
> fairly quickly, or would you like it
> sooner and for me to backport the patch ?

Upstream has released a new version with this fix; and it no longer FTBFS on 
ZFS for me ! I will upload it into the
archive soon.


Cheers!

Chris

Reply via email to