On Mon, 2008-04-28 at 10:48 -0700, Andrew Farris wrote: > seth vidal wrote: > > On Mon, 2008-04-28 at 10:13 -0700, Per Bothner wrote: > >> When I do a 'yum upgrade' (on F9), I get the attached result. > >> I looks like it's trying to connect to the Stanford network. > >> And indeed yesterday I was at Stanford with my laptop, and > >> it did try to connect to Stanford's wireless network, which is > >> one of those that requires a code/logon, which I don't have. > >> > >> But now I'm home again, and I still get this weird error. > >> This is even after re-booting twice, stopping NetworkManager, > >> and manually bringing up eth0, which I connecting through just fine. > >> > >> How do I "unstick" yum? > > > > run: > > yum clean expire-cache > > > > see if that fixes it up for you. > > If he's using fastestmirror it may also be stuck on the prior decision to use > standford right? Then it would be good to also run? > yum clean plugins > > Or would fastestmirror automatically abandon a fastest it cannot get to? I've > never had it stuck on an inaccessible network so I'm not sure. > yum clean expire-cache will nuke the mirrorlist and I'm pretty sure fastest-mirror will refresh itself if mirrorlist is new. -sv -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
