Hi,
Chris Zubrzycki writes:
> Here is the fix, or you can move zfs-share to zfs-zed for some reason:
I can confirm this patch works.
Aron Xu writes:
> I'm temped to not ship init.d scripts for Buster if there is any
> important issue open when freeze approaches (e.g. bug #915831).
Please l
> Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
> the package hadn't landed in backports yet, and discovered it broke on
> dpkg --configure :
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exit
> Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
> the package hadn't landed in backports yet, and discovered it broke on
> dpkg --configure :
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exit
[Rich Ercolani]
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header
An alternative to dropping the boot order relation is to change the
order the scripts
Package: zfsutils-linux
Version: 0.7.12-1
Severity: normal
Dear Maintainer,
Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
the package hadn't landed in backports yet, and discovered it broke on
dpkg --configure :
Setting up zfsutils-linux (0.7.12-1) ...
insserv: Service
5 matches
Mail list logo
