Unavailability of NuGet source causes failure

Feb 24, 2014 at 8:24 PM
I have 3 Nuget Sources - first one is a local/internal NuGet source that I inserted, the remaining two are the default ones (http://chocolatey.org/api/v2 and http://www.myget.org/F/boxstarter/api/v2).

I installed a boxstarter package I have installed/uninstalled many times - the package is on my internal NuGet server (which is the first one in my NugetSources) - but the package failed and I had to re-run it (2nd time it worked). Below is the error.
Could not connect to the feed specified at 'http://www.myget.org/F/boxstarter/api/v2'. Please verify that the package source (located in the Package Manager Settings) is valid and ensure your network connectivity.

Command 'install' failed (sometimes this indicates a partial failure). Additional info/packages: tcWebBuild
Chocolatey reported an unsuccesful exit code of 1
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Error
So I'm guessing that there was an intermittent issue hitting the external Boxstarter repo hostedy on myget.org, but I would've expected that since I had the package I'm installing in my local repository and my local repo was first in order, that it wouldn't have tripped over the 3rd ordered repo not being available.

Any thoughts?