This still seems to be a problem. I've gotten these errors frequently over the past year, and finally seem to have stopped them by switching to the Costa Rican mirror:
deb http://mirrors.ucr.ac.cr/medibuntu/ precise free non-free Neither the :8080 port change nor the IP-address substitution above worked for me. The first gave me same "Failed to fetch" errors. The latter I didn't specifically try because browsing: http://88.191.101.8 by itself didn't get a response. (At least the other URLs could be accessed within a browser, even though they didn't repsond to apt-get's fetches.) Besides, relying on an unchanging IP doesn't seem wise, especially since people will be looking up this info for years to come. Changing mirrors in /etc/apt/sources.list is an acceptable workaround, but won't help less technical folks. I don't know if I should reopen this bug or create a new one, as I don't yet have the repository-fetch troubleshooting experience to analyze all the moving components discussed above, so I'll just post this here and call for better minds to consider it. -- You received this bug notification because you are a member of Medibuntu Packaging Team, which is subscribed to Medibuntu. https://bugs.launchpad.net/bugs/985441 Title: Medibuntu offline To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/985441/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~medibuntu-maintainers Post to : [email protected] Unsubscribe : https://launchpad.net/~medibuntu-maintainers More help : https://help.launchpad.net/ListHelp

