Results 1 to 2 of 2
I just updated (automatically) and I time out at update #103 of 105. This is the error message: "The repository might be no longer available or could not be contacted ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 03-02-2007 #1
Update error - Lost repositories
This is the error message:
"The repository might be no longer available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and the correct writing of the repository address in the preferences.
"http://givre.cabspace.com/ubuntu/dists/edgy/Release.gpg:" Could not connect to givre.cabspace.com:80 (188.8.131.52), connection timed out
"http://givre.cabspace.com/ubuntu/dists/edgy/main/i18n/Translation-en_US.bz2:" Could not connect to givre.cabspace.com:80 (184.108.40.206), connection timed out
"http://givre.cabspace.com/ubuntu/dists/edgy/main-all/i18n/Translation-en_US.bz2:" Could not connect to givre.cabspace.com:80 (220.127.116.11), connection timed out"
Here's my question. Do I just add "http://givre.cabspace.com" to the updatemanager repository list?
I've done this once before... But... I might need to be pointed in the right direction once again if someone doesn't mind.
There was another error message:
W: GPG error: "http://medibuntu.sos-sts.com" edgy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EBC26B60C5A2783
What do I do about this one?
- 03-02-2007 #2
OK Well I got the PGP key installed... "partially".
The "givre.cabspace.com/ubuntu..." repository is timing out. It's been that way for a couple of hours.. Anybody else having the same trouble?
Is this par for the course, or do I need to be looking into something