The Pullrequest for zfs 0.8.4 got merged yesterday - see [0]. For the greatest part it contains compatibility fixes for newer kernels (5.5 - 5.7)
Commit e1b0704568b1674f47d43786180613e585aea2cf made dpkg-buildpackage fail because dh_missing was confused about the new location of 'etc/zfs/zfs-functions' and 'etc/default/zfs' (they now exist both in the source tree as well as in DESTDIR=debian/tmp) The merge request for debian-upstream - see [1] addressed the issue in a similar way as my initial workaround during testing - so I went ahead and cherry-picked theirs Additionally I took the time to pick and adapt a few commits from debian-upstream to keep them synchronized (patches 2-4). Testing was done by letting a kernel with the proposed patchset run on my workstation and various VMs for more than a week. Additionally a user, requesting some performance related patches to ZFS ran a kernel containing (a earlier version of) the proposed patchset along with 2 performance-related commits - see [2]. [0] https://github.com/openzfs/zfs/pull/10209 [1] https://salsa.debian.org/zfsonlinux-team/zfs/-/merge_requests/23 [2] https://bugzilla.proxmox.com/show_bug.cgi?id=2666 Antonio Russo (3): Use installed python3 Add dependencies for zfs-test Refresh debian/not-installed Stoiko Ivanov (3): update submodule and patches for zfs-0.8.4 Bump Standards-Version to 4.5.0 (no change). Remove the unnecessary --with systemd dh option. debian/control | 4 +- debian/not-installed | 2 + ...ith-d-dev-disk-by-id-in-scan-service.patch | 4 +- .../patches/0007-Use-installed-python3.patch | 60 +++++++++++++++++++ debian/patches/series | 1 + debian/rules | 3 +- upstream | 2 +- 7 files changed, 71 insertions(+), 5 deletions(-) create mode 100644 debian/patches/0007-Use-installed-python3.patch -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
