From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH zfsonlinux 0/8] update to ZFS 2.3.1
Date: Tue, 20 May 2025 14:44:15 +0200 [thread overview]
Message-ID: <174774502991.2042026.6019979217342548588.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250331134128.168524-1-s.ivanov@proxmox.com>
On Mon, 31 Mar 2025 15:41:20 +0200, Stoiko Ivanov wrote:
> the following patchset updates ZFS to version 2.3.1, and synchronizes our
> packaging with upstream debian[0], where it makes sense.
>
> Apart from the usual patch-refreshing and updating of the submodule the
> patches include:
> * one ZFS-upstream fix from 2.3.2-staging[1] - fixing userspace<->kernel
> breakage I noticed while running replication with an old kernel pinned
> * those patches in debian-upstream which are not related to usrmerge (will
> send those in a separate series addressing usrmerge for our packaging
> before our first trixie release)
>
> [...]
Applied to master targetting Debian Trixie and updated to latest ZFS 2.3.2 and
usrmerge on top of that, thanks!
[1/8] update zfs submodule to 2.3.1 and refresh patches
commit: 50f355367ddae528d852165f3ce0a211e06711b6
[2/8] Install new manpages for zpool-{ddtprune, prefetch}
commit: 6b4f18d9859fbce2ee306e3ca59aa989e720a9b9
[3/8] d/copyright: remove files deleted by upstream
commit: f3cb5e1ac99c914f26b2e02bc6d9ac16484eba60
[4/8] d/control: Bump library SONAMEs: libzfs4 -> libzfs6, libzpool5 -> libzpool6
commit: fa939f3a9c446b43b43c128839b7e4e0d99b248f
[5/8] d/control: remove transitional dummy package spl
commit: c417d3d45a8d8b8f2026dd9f0f76afbadb3b5ff2
[6/8] d/control: libzfslinux-dev Depends: libtirpc-dev, zlib1g-dev (Closes: #1095855)
commit: 1c691f157ef7831aa2a7cbd4ca8cc6c4b229e1fe
[7/8] d/control: add Multi-Arch attributes for binary packages
commit: 1ce7da5d9310b03a74c0f13088b7fed71cdae422
[8/8] cherry-pick fix for ABI break from zfs 2.3.2-staging
(no commit info)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-05-20 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 13:41 Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 1/8] update zfs submodule to 2.3.1 and refresh patches Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 2/8] Install new manpages for zpool-{ddtprune, prefetch} Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 3/8] d/copyright: remove files deleted by upstream Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 4/8] d/control: Bump library SONAMEs: libzfs4 -> libzfs6, libzpool5 -> libzpool6 Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 5/8] d/control: remove transitional dummy package spl Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 6/8] d/control: libzfslinux-dev Depends: libtirpc-dev, zlib1g-dev (Closes: #1095855) Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 7/8] d/control: add Multi-Arch attributes for binary packages Stoiko Ivanov
2025-03-31 13:41 ` [pve-devel] [PATCH zfsonlinux 8/8] cherry-pick fix for ABI break from zfs 2.3.2-staging Stoiko Ivanov
2025-05-20 12:44 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=174774502991.2042026.6019979217342548588.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.