On Aug 5, 2010, at 14:50, Matthew Gordon wrote: > Yep, makes perfect sense. I watched the output in terminal and found it was > still trying to hit the trakker site. So, I just tried the "port selfupdate" > followed by the "clean --all slocate" again and still got the error. So, I > just switched them, did the "clean --all" then "selfupdate" and this time it > hit the slackware server for a good install.
The order of operations should not have mattered. "selfupdate" would have retrieved the new portfile (which as far as I can tell no longer references any nonexistent servers), and "clean --all" would have deleted the old incorrect distfile (which probably wasn't a distfile but an HTML error page). > I've got internal DNS running at my office but they forward to opendns > servers that we use to help restrict unwanted web access, so I'm sure the > >1.9.2 update will help. Thanks for the feedback. Yes, unfortunately even the much-praised OpenDNS has this broken behavior by default. You can turn it off by creating an OpenDNS account, logging in and turning it off. Note that MacPorts 1.9.2 will not automatically fix these situations in the future. The patch I originally submitted did, but Joshua didn't want to do it that way. Instead, 1.9.2 will just point out to you why you are experiencing the error, with the intention that you then ask your DNS provider to change their servers to comply with the Internet standards they're currently violating that are causing this problem. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
