multipath-tools (0.9.9-1ubuntu1) oracular; urgency=medium

  The decision was made to remove the split of kpartx into the following
  packages:

   - kpartx
   - kpartx-boot

  This was historically done to support dmraid boot. At the time it made sense
  to split the package for 2 primary reasons (that I can tell):

    1. It made sense with multipath-tools also having a *-boot package
    2. It made the SRU easier as you only add a new package to affected systems

  These reasons aren't enough to keep the delta, so it was decided to align with
  Debian with regards to the kpartx package holding the udev rules.

  The size increase is neglible for the udev rules, but the obvious ramification
  is that the kpartx udev rools will now run on non-udev systems. This is not
  expected to be an issue, but will be monitored for negative consequences.

 -- Mitchell Dzurick <mitchell.dzurick@canonical.com>  Thu, 27 Jun 2024 16:27:50 -0700

multipath-tools (0.9.8-1) unstable; urgency=medium

  Socket activation as introduced in 0.9.4-6 was turned off again,
  as upstream does not support it and claims it does not work.

  Please make sure you have multipathd.service enabled:

    systemctl enable multipathd.service

 -- Chris Hofstaedtler <zeha@debian.org>  Thu, 13 Jun 2024 02:39:11 +0200

multipath-tools (0.9.4-7) unstable; urgency=medium

  Booting from multipathed devices has significantly changed. It is recommended
  testing your specific setup still boots properly, if you rely on this.

  SysV init scripts have been removed, as they may clash with socket activation
  and upgrade scenarios, especially when multipathd itself is not needed.

 -- Chris Hofstaedtler <zeha@debian.org>  Sat, 11 Nov 2023 00:41:23 +0100

multipath-tools (0.9.4-6) unstable; urgency=medium

  The systemd service for multipathd is now entirely socket-activated.  On
  new installations without any multipath device present in the system,
  only multipathd.socket will be enabled and active.  If there are
  multipath devices available, then multipath.service will be activated (but
  not enabled).

  If you are upgrading from an existing installation and would like to use
  socket activation from now on, please manually disable
  multipathd.service and enable multipathd.socket:

    systemctl disable multipathd.service
    systemctl enable multipathd.socket

  However, please keep in mind that socket activation does NOT work if
  your root partition is located on a multipath device (in other words,
  if the multipath-tools-boot package is installed).  If that is your
  case, then keep multipathd.service enabled:

    systemctl enable multipathd.service

 -- Sergio Durigan Junior <sergiodj@debian.org>  Sun, 15 Oct 2023 22:25:37 -0400

multipath-tools (0.7.7-1) unstable; urgency=medium

  systemd support is well integrated for multipath-tools now. The old
  initscripts are still provided and will be supported on a best effort basis
  but users are advised to move to a systemd based setup

 -- Ritesh Raj Sarraf <rrs@debian.org>  Sun, 07 Oct 2018 20:16:36 +0530

multipath-tools (0.5.0-4) unstable; urgency=medium

  The systemd support has been dropped.

  Device Mapper multipath is a core component in the SAN Stack. The
  flexibility provided by shell init scripts were flexible. With
  systemd, it is not the same anymore. We sure can create shell scripts
  and pass it to systemd to run, but then it forfeits the philosophy of
  systemd that "shell is evil". So rather that passing shell units to
  systemd, we'll let systemd run this service in SysV compatibility
  mode.

 -- Ritesh Raj Sarraf <rrs@debian.org>  Fri, 05 Sep 2014 18:03:12 +0530

multipath-tools (0.4.7-2) unstable; urgency=low

  udev, which provides scsi_id, moved the binary to /lib/udev.
  The old name will stop working in the future.

  The default config now uses /lib/udev/scsi_id. And you have to
  update /etc/multipath.conf by hand to reflect the new location.

 -- Bastian Blank <waldi@debian.org>  Wed, 29 Mar 2006 12:08:32 +0200

multipath-tools (0.4.5-1) unstable; urgency=low

  This version removes creation of devices via udev in /dev. All
  device-mapper devices are created by libdevmapper in /dev/mapper.

  To readd the creation of devices in /dev, add the following line to
  the udev rules (e.g. /etc/udev/rules.d/multipath.rules):
  KERNEL=="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", NAME="%k", SYMLINK="%c", OPTIONS+="last_rule"

 -- Bastian Blank <waldi@debian.org>  Mon, 19 Sep 2005 15:03:31 +0200

