[Bug 789229] Re: using a blacklist and a blacklist_exception section results in multipathd filtering out paths it shouldn't

[Clint Byrum]

As a follow up, first I forgot to say, thanks for the great work.

I took a look at the patches, and there are some fixes necessary.

First off, make sure you start from the latest version of the package
for the desired release. multipath-tools has been updated in lucid,
maverick, and natty, so you need to get the source from there rather
than the release pocket.

One way to make sure you have the latest is to use 'rmadison':

$ rmadison multipath-tools
multipath-tools | 0.4.8-7ubuntu2 |         hardy | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu4 |         lucid | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu4 |      maverick | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu4.10.04.2 | lucid-updates | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu4.10.10.2 | maverick-updates | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu10 |         natty | source, amd64, i386
multipath-tools | 0.4.8-14ubuntu10.1 | natty-updates | source, amd64, i386
multipath-tools | 0.4.9-2ubuntu1 |       oneiric | source, amd64, i386

So first off, you'll need to update your debdiffs to take all of these
updates into account. Make sure the version number is one that fits into
the scheme you already see above. So you will want your lucid updated to
be

0.4.8-14ubuntu4.10.04.3

and maverick

0.4.8-14ubuntu4.10.10.3

and natty

0.4.8-14ubuntu10.2

Also make sure you specify 'release-proposed' in the changelog.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/789229

Title:
  using a blacklist and a blacklist_exception section results in
  multipathd filtering out paths it shouldn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/789229/+subscriptions