Some are detected to be hardware issues, some are not. Also when it's considered a hardware issue people have reported that a removal fixes the issue; see for instance comment #5 in bug #1346809.
Is it really necessary that dpkg carries out that check? Can't it just install the link and overwrite whatever with the same name was there before? I agree it would be good to fix it in dpkg. If that's not possible, some workaround in ubuntu-docs would indeed be helpful.
These are the latest of the kind, except for this one:
https:/ /launchpad. net/bugs/ 1365719
https:/ /launchpad. net/bugs/ 1363695
https:/ /launchpad. net/bugs/ 1347781
https:/ /launchpad. net/bugs/ 1346809
https:/ /launchpad. net/bugs/ 1346754
https:/ /launchpad. net/bugs/ 1341690
https:/ /launchpad. net/bugs/ 1315177
https:/ /launchpad. net/bugs/ 1295481
https:/ /launchpad. net/bugs/ 1295442
Some are detected to be hardware issues, some are not. Also when it's considered a hardware issue people have reported that a removal fixes the issue; see for instance comment #5 in bug #1346809.
Is it really necessary that dpkg carries out that check? Can't it just install the link and overwrite whatever with the same name was there before? I agree it would be good to fix it in dpkg. If that's not possible, some workaround in ubuntu-docs would indeed be helpful.