Stopping a container that was already stopped now no longer returns an
error code. This behaviour was adapted to match the return values for
VMs, to get a more consistent API. Both VMs and containers now return
an error when starting an already started guest, and both do not show
an error when stop
Signed-off-by: Stoiko Ivanov
---
debian/patches/0005-Enable-zed-emails.patch | 4 ++--
.../0009-Patch-move-manpage-arcstat-1-to-arcstat-8.patch | 4 ++--
upstream | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
following debian upstream (which pulled it in from Ubuntu in
44915cf387d45a123b11a8c24d3f30a8fdbcc532)
Signed-off-by: Stoiko Ivanov
---
debian/control| 13 +
debian/zfs-dracut.install | 2 ++
2 files changed, 15 insertions(+)
create mode 100644 debian/zfs-dracut.install
following commit da40a1b007d2a99bac95bd67ec6dd7b8e217c0cf from
debian-upstream.
However since some of our rust-packages seem to depend on
libcurl4-gnutls-dev (via librust-curl-sys-dev) we add a
option for the dependency - I would assume that both should work
equally well (the callers are in upstre
The ZFS 2.1.5 tag was released recently
The following patchset adapts to the changes.
The changelog looks small enough.
One commit should fix an issue quite a few users have reported in our
community forum:
https://github.com/openzfs/zfs/pull/13338
https://forum.proxmox.com/threads/.107709
https
