[18.04] Upgrade multipath-tools to upstream version 0.7.4

[bugproxy]

== Comment: #0 - Rodrigo R. Rosatti Galvao <email address hidden> - 2017-08-14 09:20:21 ==
The current version of multipath-tools package on debian is 0.6.4, while the current upstream version is 0.7.2.

The uscan command is not working, because the debian/watch file is not working properly:

#debian/watch
        version=3
        http://christophe.varoqui.free.fr/multipath-tools/multipath-tools-([\d\.]*)\.tar\.bz2

The link inside this file is not available, which might be the reason why it's not being updated.

mulitpath-tools on debian: https://packages.debian.org/search?keywords=multipath-tools
multipath-tools upstream: https://github.com/openSUSE/multipath-tools/

[Steve Langasek (vorlon)]

As we are past feature freeze, we will most likely not include this in 17.10.

Matt, would you look into this for 18.04?

[Julian Andres Klode (juliank)]

debdiff of a work-in-progress merge. It builds fine, the diff is virtually unchanged from the previous upload, but tgtbasedmpaths fails to see dm-0. No idea why yet.

[Julian Andres Klode (juliank)]

OK, I got the thing further. It now runs the tests sucessfully until removing the second-last member of a multipath device, at which point it lists weird stuff for the device it was supposed to remove. The journal tells me that it never processed (or received?) an uevent for that removal. Not entirely sure how that's different than the two or three devices it removed before that.

Changes since the last one:

* Disable the enable-find-multipaths.patch patch from bug 1463046 as somehow devices are not correctly detected
* Install dm-parts.rules, kpartx.rules was split up
* Re-add the split-out code to kpartx.rules - just installing the new file did not help - weird
* Fix a crash in multipathd when removing nodes, this is probably the same issue as the first item
* Fixed a path in 11-dm-mpath.rules

[Julian Andres Klode (juliank)]

Uploaded 0.7.4-2ubuntu1

[Launchpad Janitor (janitor)]

This bug was fixed in the package multipath-tools - 0.7.4-2ubuntu1

---------------
multipath-tools (0.7.4-2ubuntu1) bionic; urgency=medium

  * Merge from Debian. (LP: #1710697, LP: #1711749) Remaining changes:
    - d/control:
      - multipath-udeb: add sg3-udeb Depends
    - d/rules: Move udev rules to priority 95, because rules that load modules
      should be >90.
    - d/multipath-tools.preinst: modprobe dm-multipath; This will make sure
      that multipathd will be able to start.
    - Split kpartx initramfs bits into kpartx-boot for dmraid (LP 941874)
      - d/initramfs/kpartx.hook
      - d/kpartx-boot.postinst
      - d/kpartx-boot.postrm
      - d/control: Add kpartx-boot package for dmraid
      - d/rules: Install kpartx initramfs hook
      - d/kpartx.install: install all arch /lib* kpartx udev rules
    - patches to multipath source
      - d/p/1000--set-umask-in-multipathd.patch: Set umask in multipathd.
      - d/p/kpartx_more_loopback_fixes.patch: fix loopback mounted
        files some more: since we stat() the loopback device node, we can't rely
        on S_ISREG() tests to handle this case, and should look at the device
        itself instead. (LP 1543430)
      - d/p/enable-find-multipaths.patch: re-enable find_multipaths
        by default -- see the removed 'add_find-multipaths.patch' (LP 1463046)
   - multipath initramfs fixes for booting from multipathed devices
      - d/initramfs/hooks: also copy wwids file on the installed system to
        ensure all paths come up on boot. (LP 1479929)
      - d/initramfs/hooks: install multipathd and required directories.
      - d/initramfs/hooks: copy multipath udev rules to initramfs
      - d/initramfs/hooks: do not copy kpartx rules to initramfs
      - d/initramfs/local-bottom: remember to stop multipathd.
      - d/initramfs/local-premount: wait for udev to settle before the call to
        resolve_device() in local_mount_root(), so the by-uuid/ symlinks have a
        chance to be updated by the multipath udev rules (LP 1503286).
      - d/initramfs/local-premount: Run multipath with -B so not to assign names
        nor change /etc/multipath/bindings during initramfs (LP 1561103)
      - d/rules: install d/initramfs/local-bottom
      - d/rules: install d/initramfs/local-premount
   - Disable -fexceptions on multipath-udeb (LP 1489379): the flag causes
     libchecktur.so to link with libgcc_s.so.1 (even with -static-libgcc),
     which is not available in the installer environment.
     - d/p/disable-fexceptions-udeb.patch: conditionally disable -fexceptions
       with CFLAGS_DISABLE_FEXCEPTIONS.
     - d/rules: set CFLAGS_DISABLE_FEXCEPTIONS to build multipath-udeb.
   - Remove d/initramfs/local-top (redundant with other initramfs scripts):
     - init-top: take over loading modules (dm-multipath and SCSI device
       handlers); move the missing dm-emc there (now scsi-dh-emc;
       see BTS 567014).
     - d/rules: do not install local-top anymore.
     - remove d/initramfs/local-top
    - Fixes typo in package description (availibility -> availability)
      (LP 1231182)
    - d/control mark transition of file /etc/init.d/multipath-tools-boot
      according to...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-02-12 04:17 EDT-------
Hi,

I have verified that multipath-tools (0.7.4-2ubuntu1) has the patches we wanted to be backported.
This bug can be closed!

Thanks,
Rodrigo