<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Josh<br>
<br>
Thanks for your brilliantly helpful response.<br>
<font color="red">Yes.. the pings are indirectly to blame!!</font><br>
No, I am not running a third party firewall.<br>
But I read the notes and noticed the comments about<br>
changing the <font color="blue">max_hosts_to_ping</font>: I had
noticed<br>
after the hang that there were upwards of a dozen<br>
hung pings.<br>
<br>
In order I had done the following<br>
<br>
1. After 24 hours I tried the exact same <font color="blue">port
upgrade</font> command again... same result.<br>
<br>
2. So, ok, after 15 minutes or so, I donned my debugging hat and
executed:<br>
<font color="blue"> port -v -v -v upgrade outdated</font><br>
... now it did not choke on gd2! ... several other packages are
installed .... then it hangs on ghostscript!!<br>
<br>
<br>
Clearly, something extremely odd was going on here. I think it has
nothing to<br>
do with turning on debug (<font color="blue">-v -v -v</font>) -- I
think that is a red herring.<br>
It seems that some other condition on the network cleared,<br>
possibly a condition on the macports mirror, which now allowed gd2<br>
to download. <font color="red">Yes consistent with the ping
stuff... variations in response<br>
to pings could easily give different result<br>
<br>
So I change the max_hosts_to_ping to 10.<br>
Eureka. It works. No hang.<br>
It is very clear, I believe, that there is some serious bug<br>
in MacOS networking stack which is present not only in BigSur<br>
but also in Catalina.<br>
<br>
I am posting this followup on the user group<br>
</font><br>
<div class="moz-cite-prefix">On 2022-01-15 21:36, Joshua Root wrote:<br>
</div>
<blockquote type="cite">This is extraordinary .. it presumably is a
bug in MacOS. <br>
<br>
Running MacOS 10.15.7 on MacBook Pro 2016 <br>
<br>
I am updating various already installed packges in the usual way:
<br>
sudo port upgrade outdated <br>
<br>
Everything goes along fine until the software reached gd2. <br>
I then see: <br>
<br>
---> Fetching archive for gd2 <br>
---> Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2
from <br>
<a class="moz-txt-link-freetext"
href="https://packages.macports.org/gd2">https://packages.macports.org/gd2</a>
<br>
---> Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2
from <br>
<a class="moz-txt-link-freetext"
href="https://nue.de.packages.macports.org/gd2">https://nue.de.packages.macports.org/gd2</a>
<br>
---> Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2
from <br>
<a class="moz-txt-link-freetext"
href="https://ema.uk.packages.macports.org/gd2">https://ema.uk.packages.macports.org/gd2</a>
<br>
---> Fetching distfiles for gd2 <br>
<br>
At this point the networking on the machine hangs. <br>
I cannot kill the port process. I cannot reach the <br>
offending machine even by ping; I cannot use <br>
the network from another terminal nor browser. <br>
</blockquote>
Are you running any third-party firewall? This looks a lot like <a
class="moz-txt-link-rfc2396E"
href="https://trac.macports.org/ticket/61683"><https://trac.macports.org/ticket/61683></a>,
though that was on Big Sur. I would agree it's certainly an OS bug
in any case. <br>
<br>
You can try the edits mentioned in the ticket to see if it's the
pings that are triggering the bug. A quick workaround if you just
need to get gd2 installed is to download the distfile manually as
per <a class="moz-txt-link-rfc2396E"
href="https://trac.macports.org/wiki/ProblemHotlist#fetch-failures"><https://trac.macports.org/wiki/ProblemHotlist#fetch-failures></a>.
<br>
<br>
- Josh
</body>
</html>