following commit ec311430e2fd66492498a1559f56ef25e1192266 upstream
However since libzfs increased both the current as well as the age
the soname of the library remained at libzfs4.so - following
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
I left the package name at libzfs4linux
Si
upstream/master has a few commits addressing an incompatibility of
the files generated by abigail-tools > 1.8 with the ones generated
with earlier versions.
This commit adds 2 patches porting these changes. Without it building
in bullseye fails (due to the abigail-tools version)
Note: this commit
Signed-off-by: Stoiko Ivanov
---
...ith-d-dev-disk-by-id-in-scan-service.patch | 6 +-
.../0006-dont-symlink-zed-scripts.patch | 5 +-
.../patches/0007-Use-installed-python3.patch | 4 +-
...-move-manpage-arcstat-1-to-arcstat-8.patch | 61 +--
upstream
Signed-off-by: Stoiko Ivanov
---
debian/zfsutils-linux.install | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/debian/zfsutils-linux.install b/debian/zfsutils-linux.install
index 4f93aa70..b7501b30 100644
--- a/debian/zfsutils-linux.install
+++ b/debian/zfsutil
Signed-off-by: Stoiko Ivanov
---
...itions-with-abigail-tools-1.8-and-ne.patch | 25768
debian/patches/series | 1 +
2 files changed, 25769 insertions(+)
create mode 100644
debian/patches/0012-update-abi-definitions-with-abigail-tools-1.8-and-ne.patc
This patchset updates our packaging for the changes of ZFS 2.1
Sending as RFC because:
* I'm still not 100% sure my solution to the ABI-changes and updated
package names is correct
* It's based on the current tip of upstream's zfs-2.1.1-staging branch,
which yet needs to be tagged
I'm intenti
Not doing so leads to an off-by-one error, and pruning in a dumpdir
really should behave the same way as pruning in a storage.
Reported in the community forum:
https://forum.proxmox.com/threads/problem-mit-prune-backups.95737/
Signed-off-by: Fabian Ebner
---
PVE/VZDump.pm | 2 +-
1 file changed
This is the same as fix 40ff84b138bb7127ecc05a2f587cca4e7a917810 in
proxmox-backup. When returning a boolean instead of the expected
{negative, 0, positive}, the behavior is browser-dependent.
Signed-off-by: Fabian Ebner
---
www/manager6/window/Prune.js | 4 +---
1 file changed, 1 insertion(+),
Previously, top-level vdevs like log or special were wrongly added as
children of the previous outer vdev instead of the root.
Fix it by also showing the vdev with the same name as the pool and
start counting from level 1 (the pool itself serves as the root and
should be the only one with level 0)
