Please backport dmraid to edgy - works in feisty

Bug #68294 reported by Richard Bailey on 2006-10-25
8
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Medium
Unassigned
Edgy
High
Ubuntu Backporters

Bug Description

Binary package hint: dmraid

dmraid in edgy has been broken ever since. See bug https://launchpad.net/distros/ubuntu/+source/dmraid/+bug/54246

Unfortunately it hasn't been fixed during the edgy development cycle and since dmraid worked in dapper this can be considered a regression.

New version is in feisty. It will be tested by myself (rmjb) and others, then we can backport.

This has been tested by 3 persons in feisty and it works. There does not seem to be many dmraid users in total so I think 3 is enough.

Richard Bailey (rmjb) wrote :
Richard Bailey (rmjb) wrote :
Richard Bailey (rmjb) wrote :
Richard Bailey (rmjb) wrote :

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.

Changed in dmraid:
assignee: nobody → motu-uvf
Daniel Holbach (dholbach) wrote :

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

Changed in dmraid:
importance: Undecided → Medium

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.

Tormod Volden (tormodvolden) wrote :

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.

Richard Bailey (rmjb) on 2006-11-04
Changed in dmraid:
assignee: motu-uvf → motu-sru
StefanPotyra (sistpoty) wrote :

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.

Changed in dmraid:
status: Unconfirmed → Confirmed
Daniel T Chen (crimsun) wrote :

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?

Reinhard Tartler (siretart) wrote :

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.

Changed in dmraid:
status: Confirmed → Needs Info
StefanPotyra (sistpoty) wrote :

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.

Changed in dmraid:
assignee: motu-sru → nobody
Richard Bailey (rmjb) wrote :

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.

Changed in dmraid:
assignee: nobody → rmjb
StefanPotyra (sistpoty) wrote :

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.

Changed in dmraid:
status: Needs Info → Rejected
assignee: nobody → ubuntu-backporters
assignee: rmjb → nobody
status: Rejected → Confirmed
Richard Bailey (rmjb) on 2006-12-10
description: updated

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.

Richard Bailey (rmjb) on 2006-12-20
description: updated
Richard Bailey (rmjb) on 2006-12-20
description: updated
Tormod Volden (tormodvolden) wrote :

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.

Tormod Volden (tormodvolden) wrote :

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).

Changed in dmraid:
status: Unconfirmed → Confirmed
Phillip Susi (psusi) wrote :

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

Changed in dmraid:
importance: Undecided → High
Sergio Zanchetta (primes2h) wrote :

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.

Changed in dmraid:
status: Confirmed → Invalid
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers