In my experience it sometimes works to say "no" and try again immediately, or at most a few hours later. As near as I can gauge the issue is server availability, they never seem to stay inaccessible for long.
On Fri, October 2, 2009 10:47 am, Richard C. Steffens wrote: > [email protected] wrote: >> I would say no, simply as it has not committed anything at this point. >> I'd give it a day or two and see if anything has changed. You might >> also try changing your repo servers in synaptic. I usually use osuosl >> repos here in the valley. They always seem to perform well. >> > Scott Garman wrote: >> I always answer "No" when this happens and re-run the update - the >> packages you successfully downloaded will be cached so it won't take as >> long the second time. >> >> Since apt uses dependency checking (and the update notifier app uses apt >> in the background), if you tried to continue with the install I assume >> it would only update the packages it downloaded that have met >> dependencies. So you shouldn't be able to bork your system with either >> answer, but to be on the safe side I always say No and run the updates >> again. >> > > Thanks. I shall answer "No" and try again another day. > > -- > Regards, > > Dick Steffens > www.dicksteffens.com > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > -- Tim Wescott Control systems and communications consulting http://www.wescottdesign.com Land line: 503.631.7815 Cell: 503.349.8432 _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
