© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
I actually remember filing the bug several years ago about gparted not supporting dmraid and talking with you about how it could do that. I'm also reading a book on autotools at the moment. While I grok the theory of operation, I don't yet have the details down. It sounds like you are saying that you are in the same boat, and that you agree that if it detects at least version 2.3.0 of libparted, then phase out DMRaid.cc, but are asking if I can help with actually implementing the test for >= 2.3.0. Hopefully by the time I finish this book I will.
I can certainly get in a patch for natty, and that is what I want to do, but updating to a whole new upstream release is not allowed AFAIK. That is why I am trying to figure out the minimum patch required to fix the duplicate device issue. That seems to mean fixing DMRaid.cc to add the 'p'. It either needs to always add it like dmraid and libparted do, or dmraid and libparted need patched to conform with the kpartx behavior. I am leaning towards the latter.
I wonder though, if you are going to backport the latest gparted to 8.04, why wouldn't you also want to backport libparted along with it?
Also I do not quite understand this: http://
It looks like another bug with the Natty version of gparted. To fix that, you should open another bug report about it. If it does happen in Natty, and that upstream patch fixes it, then it can easily be cherry picked.