My two centavos:
1. Thanks a bunch! I was wondering what happened to the Medibuntu repo's (and even why I had them!)
2. This might be slightly off topic, but (IMHO) this appears to disclose a wicked nasty bug with the Update Manager.
If, during the repository check process, a repository fails - in this case with a "404" error, or an "unable to resolve [link]" error - the Update Manager just throws in the towel and fails to update ANYTHING.
IMHO, the desired behavior should be to emit an error message - perhaps recording it to the logs, or requiring a click-through dialog - but then still continuing with the update using whatever repositories are available.
Having the Update Manager simply finish its beer, pay, and then go home if the update phase generates errors seems, (at least to me), to be a bad choice, (
), as this inhibits the ENTIRE update process, not just the single depreciated - or temporarily unavailable - repository.
Does anybody know if a bug has been filed?
Thanks again for all your help here!
Update 11/12/2013 12:45 pm EST:
I edited /etc/apt/sources.list commenting out the depreciated mediabuntu repository, added the new videolan repository, and updated the keyring using the command you provided to accomplish the update.
Running the Update Manager disclosed six updates, at least five of wich were updates to older mediabuntu files.
Again, my thanks for an excellent distribution and an even more excellent support forum!