<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Apr 30, 2022, at 12:43 PM, John Hoyt <<a href="mailto:john.hoyt@gmail.com" class="">john.hoyt@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><div class="">I would have lost money that I did selfupdate, but clearly I did not. Doing that now.</div></div></blockquote><div class=""><br class=""></div><div class="">you may have. On one of my systems, I have to run selfupdate twice to get it to pull down the latest ports tree from git. For that reason, I usually run with the -d flag to see the git traffic in case I run into this "feature”. </div></div></div></div></blockquote><br class=""></div><div>If selfupdate has to update the port command (ie the MacPorts infrastructure), then it doesn’t update the port tree. You should get a message saying prompting you to run selfupdate again. (But I know the messages can be awfully ‘chatty’ and it is easy to ignore and important message when there is dross surrounding it.)</div><br class=""><div class="">Craig</div></body></html>