From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH zfsonlinux 0/2] update to 2.0.5 and follow-up on the last cleanup
Date: Fri, 9 Jul 2021 17:41:16 +0200 [thread overview]
Message-ID: <20210709154118.2221085-1-s.ivanov@proxmox.com> (raw)
This patchset follows-up on the last cleanup I sent:
https://lists.proxmox.com/pipermail/pve-devel/2021-June/048802.html
I decided to drop the symbols-file generation for now - since it adds
complexity, and I am not aware of any package which would benefit from it.
Currently all our zfs packages depend on the libraries in the same version -
thus they need to get upgraded along with e.g. zfsutils-linux - which feels to
me a bit more robust - Additionally it seems like ZFS 2.1 added some breaking
abi changes - which would need to be reflected in new library package names
anyways.
Will gladly send the symbols-files should anyone object, or see a benefit in
having them.
Additionally I updated the submodule to ZFS 2.0.5, which should contain the
fix for https://bugzilla.proxmox.com/show_bug.cgi?id=2546
minimal tests in a VM running pve 7 were done (ztest, created a bullseye
container, snapshotted it and rolled back).
Stoiko Ivanov (2):
do not restart most services upon upgrade
update submodule and patches to ZFS 2.0.5
debian/rules | 8 ++++++++
upstream | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2021-07-09 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 15:41 Stoiko Ivanov [this message]
2021-07-09 15:41 ` [pve-devel] [PATCH zfsonlinux 1/2] do not restart most services upon upgrade Stoiko Ivanov
2021-07-09 15:41 ` [pve-devel] [PATCH zfsonlinux 2/2] update submodule and patches to ZFS 2.0.5 Stoiko Ivanov
2021-07-12 6:38 ` [pve-devel] applied-series: [PATCH zfsonlinux 0/2] update to 2.0.5 and follow-up on the last cleanup Thomas Lamprecht
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=20210709154118.2221085-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.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.