Debian Bug report logs - #1083104
RFH: multipath-tools -- maintain multipath block device access

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Chris Hofstaedtler <zeha@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RFH: multipath-tools -- maintain multipath block device access

Date: Tue, 01 Oct 2024 21:06:39 +0200

Package: wnpp
Severity: normal
X-Debbugs-Cc: multipath-tools@packages.debian.org, debian-devel@lists.debian.org, team+linux-blocks@tracker.debian.org, agx@debian.org, rrs@debian.org, mitchell.dzurick@canonical.com
Control: affects -1 + src:multipath-tools

I request assistance with maintaining the multipath-tools package.

multipath-tools has Ritesh, Guido and me as maintainers. I think Guido
has moved on to other important topics in Debian, and Ritesh is busy. I
myself no longer have test hardware that uses a multipath setup, so it's
become harder for me to really test and work on the packaging.

There is a new upstream version (0.10.0) that needs packaging. Don't
know yet if it will just work or if it will need a lot of changes.

Anyway, multipath-tools needs to continue existing for a few more years
until the world has moved on to exclusive use of NVMe and NVMe-oF. Until
then, all sorts of setup need multipath-tools.

There is a kernel component (dm-multipath) and some integration with
lvm2 and systemd that one should also at least kinda know about.

Whoever wants to help, probably best to join the salsa group and start
making changes.

Thanks,
Chris


The package description is:
 These tools are in charge of maintaining the disk multipath device maps and
 react to path and map events.
 .
 If you install this package you may have to change the way you address block
 devices. See README.Debian for details.

Send a report that this bug log contains spam.