Several other people, including myself, have had this problem before. See the mailing list conversation from Oct 3 entitled "Can't find port "atlas"."
Scott On Sat, Dec 3, 2011 at 11:49 PM, Ryan Schmidt <[email protected]> wrote: > > On Dec 3, 2011, at 23:14, Lawrence Velázquez wrote: > >> This started happening to me regularly a month or two ago. I generally have >> to run selfupdate twice to make sure the index problem goes away. >> >> I'd like a permanent solution, though, if there is one. > > The only reason you should have to run selfupdate twice to get the index > built properly is if the first time, the MacPorts base version got updated. > MacPorts 2.0.2 tell you in this case that you have to do this; with earlier > versions, you just had to know. If the MacPorts base version did not change > when you ran selfupdate, the index should generate properly the first time. > > > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
