[MacPorts] #61683: remoted hangs on Big Sur when installing p5* ports, losing network and sometimes panicking kernel
MacPorts
noreply at macports.org
Mon Mar 15 13:30:35 UTC 2021
#61683: remoted hangs on Big Sur when installing p5* ports, losing network and
sometimes panicking kernel
-----------------------------+--------------------
Reporter: BishopBerkeley | Owner: (none)
Type: defect | Status: new
Priority: High | Milestone:
Component: base | Version: 2.6.4
Resolution: | Keywords: bigsur
Port: |
-----------------------------+--------------------
Comment (by minusf):
Replying to [comment:38 kencu]:
> grand total time invested = 120 seconds
>
> {{{
> cd /tmp
> git clone https://github.com/macports/macports-base.git
> cd macports-base
> ./configure && make && sudo make install
> cd ..
> rm -rf macports-base
> }}}
my grand total time invested in this issue is in days already.
this issue is not new. it has been widely reported by many people.
although it causes no kernel panic at the moment ("only" full networking
loss until reboot), the going advice is "use master" and/or with some
undocumented option overrides.
yes, it's not directly macports' fault per se, but it triggers it, and it
makes running macports akin to playing russian roulette. i know macports
is a volunteer effort, but i find it strange not to release a minor patch
version with a temporary fix while the dust settles around the other
software involved: macos, little snitch, etc. the others would be hardly
hugely affected, 200+ mirrors for any package makes little sense to me,
just to speed test them would be slower than grabbing a random mirror.
running master is not officially recommended by the project, otherwise
what would be the point of releases. can we have a fix please even if
only temporary?
--
Ticket URL: <https://trac.macports.org/ticket/61683#comment:41>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list