Please backport dmraid to edgy - works in feisty

This new package will also fix another bug in dmraid:

https://launchpad.net/distros/ubuntu/+source/dmraid/+bug/67606

This one was filed by myself, however.

This will need to be turned into an SRU. (http://wiki.ubuntu.com/StabledReleaseUpdates) - if at all.

This thread lists persons that don't have dmraid working for them in Edgy:
http://ubuntuforums.org/showthread.php?t=266807

From my count everyone but tormod's dmraid was broken, but tormod was using an Intel raid, where problems existed for via and nvidia raids, as far as I know.

As it is now dmraid is broken in edgy and this updated packages fixes the problem. The fix worked wonders for risidoro and it also worked for Eleazar, WattoDaToydarian and myself. I have not heard final reports from the others.

Notice that I was only mounting the raid using the live cd, I did not try to install and eventually boot from the raid. So I can not confirm that the dmraid package would work perfectly on Intel, only that the sanity check in question seemed fine for me.

Hi,

this is definitely a high impact bug, so -updates is ok. However dmraid also is quite risky imo, so we should make sure to not introduce new bugs with the update. Thus I'd personally prefer to backport patches for these particular bugs to the version in edgy. Other opinions on this?

Please also update the description of this bug to point exactly to the bugs that you want to address with the update.

Thanks,
       Stefan.

I second Stefan's opinion: Backported patches are preferable to importing a new upstream version wholescale. Would you please work with upstream [if you're not directly involved in its development] to break out the patches with clear explanations of their fixes?

I see 2 ways to go from here:

request the package to be included in edgy-backports. This can be done via uploading a fixed version to feisty and sync that to edgy-backports (preferable), or by manually uploading it to edgy-backports. Please file a seperate bug against the 'ubuntu-backports' product for this, referencing this bug.

The other thing is to find out which of the patches in http://librarian.launchpad.net/4936315/diffstat.txt is necessary to fix the bug. rc9 seem to have worked in dapper for at least some folks, and we don't like to introduce potential regressions by updating to rc13.

Unassigning motu-sru for now. Please subscribe motu-sru, if you have backported the indivual patches.

As Reinhard stated, backports might also be a place to shove the update in. In case the package can be backported, please assign the backporters team.

Ann update on the progress of this. I'm taking the advice of going the backport route. I'm pushing to get the new version synced to feisty. This version has already made it to debian unstable. You can see the sync request here:
https://launchpad.net/distros/ubuntu/+source/dmraid/+bug/71980

Once it's synced I'll confirm it works with Herd 1 then request a backport to edgy.

Ok, great. Thanks for your work.

However for a backport, you'll need to assign the bug to ubuntu-backporters (once the new version is in the archives). Thus, motu-sru is not needed here ;)

Cheers,
      Stefan.

I can also confirm that the edgy released package broke my system, and the rc13 package fixes it.

There are 1-2 small new features between rc11 and rc13, but I don't think it is important to strip out the added features and only backport the bug fixes, since rc11 regressed for the vast majority of those using this package; I don't think we need to worry about rc13 regressing from an already broken version.

I have tested the feisty dmraid 1.0.0.rc13-2ubuntu1 package in a feisty herd-2 live session on my Intel fakeraid (isw) and it works perfectly.

I can also add that I rebuilt the dmraid 1.0.0.rc13-2ubuntu1 package on Edgy (with no changes) and tested it with the Ubuntu 6.10 Desktop CD, and it worked fine on my Intel fakeraid (mirror).

Marking as high importance as it causes severe breakage ( can't boot ) to effected users.

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the Edgy Eft task.