Comment 7 for bug 561560

Just stumbled across this bug attempting to do a hardy->lucid upgrade. I use an approx proxy.

The error message is very uninformative, so I second Fionn's suggestion above.

Why does this check the identity of the mirror in the first place--is there not a chain of gpg signatures used to verify the integrity of the components to be installed independently of the ostensible name of the archive server? If not, that seems . . . alarming.

There are several approaches possible here:

1) a more informative error message

2) informing the system administrator performing the upgrade the name of the archive host being used, that the host is unrecognized, and then querying whether to proceed or not

3) removing the check entirely