On Apr 22, 2015, at 7:40 AM, Mojca Miklavec <[email protected]> wrote:
> Maybe I need to explain a bit more. > > I have a sparse SVN checkout configured as: > file:///Users/me/app/macports/trunk/dports [nosync] > > I used [nosync] because I'm often bitten by failures during svn > updates when my local changes conflict with upstream changes in the > repository and I prefer to solve those manually, not during "port > selfupdate". > > I ran "svn up" in "~/app/macports/trunk", but I didn't run portindex. > The texlive-bin port was one of those ports in my sparse checkout > (maybe I initially even forgot to run "svn up"). From my understanding > that fully explains the situation. Apparently I run portindex often > enough that I have never been bitten by this particular type of the > problem in years. Yes, this explains it. Simply running `port upgrade foo` will evaluate your local portfile and correctly perform the upgrade, but the "outdated" pseudoport used by `port upgrade outdated` is computed using the portindex. vq _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
