Comment 8 for bug 1629644

Revision history for this message
Louis Bouchard (louis) wrote :

Hello,
The patches added between those two versions are not maintained in git but are quilt patches applied above the same source code found in multipath-tools_0.4.9.orig.tar.gz.

You could do something similar to a bisection by following these steps :

# sudo apt-get install ubuntu-dev-tools devscripts
# sudo apt-get build-dep multipath-tools
# mkdir bisect
# cd bisect
# pull-lp-source multipath-tools 0.4.9-3ubuntu7.4
# pull-lp-source -d multipath-tools 0.4.9-3ubuntu7.5
# debdiff *dsc > newpatches.patch
# cd multipath-tools-0.4.9
# patch -p1 < ../newpatches.patch
# quilt pop -a
# quilt push -a
# quilt pop 41

This will bring your source package to the patch level of 0.4.9-3ubuntu7.4. You can run the following to test that the created package does work : build the binary packages with the current set of quilt patches applied.

# dch -rm
and add a suffix to the version number using the ~ marker. This will make sure that the version is lower than the 7.5 version in the archive

multipath-tools (0.4.9-3ubuntu7.5~test1) trusty; urgency=medium
# sudo fakeroot debian/rules binary

Install the packages with the 0.4.9-3ubuntu7.5~test1 version and verify that your environment still works.

Then iterate over each new patch added between 0.4.9-3ubuntu7.4 and 0.4.9-3ubuntu7.5 by doing the following :

# quilt push
# dch -rm
multipath-tools (0.4.9-3ubuntu7.5~test2) trusty; urgency=medium
# fakeroot debian/rules binary

Install & test

When you get a package that doesn't work in your environment, it means that the last patch applied is causing your failure. You can identify the patch with :

# quilt applied | tail

The last one in the list is the patch you are looking for.

You may want to use LXC containers to create your build environment as this will install a sensible amount of packages.