Am 17/10/2022 um 20:09 schrieb Stoiko Ivanov: > While discussing whether to push the 2.1.6 packages further we noticed > that a small glitch happened on debian-upstream. > Our build should not be affected (we don't ship init-scripts), but syncing > the changes could help in a few corner cases (user installed 2.1.6-1 from > debian-upstream and then changed to our repositories is the one situation > I think might cause issues) > > The remaining patches were included due to being quite limited in what > they do. > > minimally tested on 2 VMs of mine with the current tip of pve-kernel/master > and on a hardware machine with ZFS on / > > Stoiko Ivanov (2): > cherry-pick a few patches from zfs-2.1.7-staging > install zfs-load-key.service > > ...ramfs-use-mount.zfs-instead-of-mount.patch | 74 +++++++++++++++++++ > .../0013-etc-mask-zfs-load-key.service.patch | 37 ++++++++++ > ...ould-have-its-argument-list-marked-v.patch | 40 ++++++++++ > debian/patches/series | 3 + > debian/zfsutils-linux.install | 1 + > 5 files changed, 155 insertions(+) > create mode 100644 > debian/patches/0012-initramfs-use-mount.zfs-instead-of-mount.patch > create mode 100644 debian/patches/0013-etc-mask-zfs-load-key.service.patch > create mode 100644 > debian/patches/0014-kcfpool_alloc-should-have-its-argument-list-marked-v.patch >
applied, thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
