It just moves some initialization code into a new function and calls this lazily. It does not change any API/ABI. It has been tested a long time in lucid and should be fairly safe.
However, I'd like to keep the current workaround in devicekit-disks in karmic-proposed for now (please test that this properly disables SMART probing). I'd like to hear some more confirmations from affected people here that things indeed work fine with Lucid beta-1 on a variety of hardware platforms before re-enabling smart probing and this patch in karmic again.
Thank you, and sorry for the trouble that this caused!
For Karmic we can backport http:// git.0pointer. de/?p=libatasma rt.git; a=commitdiff; h=a223a4f6277a9 f006b722b13671d 5292dc6339bb to fix this properly. If we do this, we should also apply http:// git.0pointer. de/?p=libatasma rt.git; a=commitdiff; h=54f846c2115e7 addf5468a9c10ec f9ba844b946e on top, to avoid exporting this as a new symbol.
It just moves some initialization code into a new function and calls this lazily. It does not change any API/ABI. It has been tested a long time in lucid and should be fairly safe.
However, I'd like to keep the current workaround in devicekit-disks in karmic-proposed for now (please test that this properly disables SMART probing). I'd like to hear some more confirmations from affected people here that things indeed work fine with Lucid beta-1 on a variety of hardware platforms before re-enabling smart probing and this patch in karmic again.
Thank you, and sorry for the trouble that this caused!