Comment 27 for bug 680627

Yes, other packages could be affected, although this was the case in Debian also, so most packages should already have the required goo to handle this gracefully.

I agree if someone went from hardy or karmic to lucid and is now on maverick or natty they would still have the broken symlinks in place. As you said, I'm not sure there's enough users that have done that and have been living with a broken virtinst for that long that it would be worthwhile to fix it in more recent releases.