It looks like the reason is that python-fstab is not touched (intrepid and jaunty version are the same) during the upgrade. This may also happen if a python package gets upgraded before the new runtime is unpacked I suspect.
It looks like the reason is that python-fstab is not touched (intrepid and jaunty version are the same) during the upgrade. This may also happen if a python package gets upgraded before the new runtime is unpacked I suspect.