On Tue, Jan 27, 2009 at 09:06:56PM +1100, vincent.mcint...@csiro.au wrote: > > >> umm - can't see it. I checked the bug as well. Could you resend please? > >> The 65d108f.diff patch does not apply cleanly. > >Attached now. > > Thanks. I got it to apply after one small hiccup. > See attached log file. Did you resolve the conflict by hand?. Otherwise kpartx won't work. I can send a patch against 0.4.8-7 instead of 0.4.8-13 if that's easier for you. But since you only need kpartx I recommend to apply the patch I send against 0.4.8-13 (see below).
> I'll give the new partx binary a try and then try installing the new.debs: > libdevmapper1.02.1_1.02.24-4_i386.deb > multipath-tools-boot_0.4.8-7~bpo40+1_i386.deb > multipath-tools_0.4.8-7~bpo40+1_i386.deb > kpartx_0.4.8-7~bpo40+1_i386.deb > > Do I need > dmsetup_1.02.24-4_i386.deb > as well? > Presumably Yes. But since you're only interested in kpartx you can just use all of multipath tools from etch and only the kpartx binary you backported. That should ease things considerably on etch. -- Guido P.S.: I tried to reproduce this here but I can't setup a loop back device >2TB. The kpartx with the patch I send at least doesn't break for < 2TB. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
