[MacPorts] #55136: sudo port -d upgrade outdated hangs

MacPorts noreply at macports.org
Sat Oct 21 20:47:08 UTC 2017


#55136: sudo port -d upgrade outdated hangs
-----------------------+-------------------
 Reporter:  micrology  |      Owner:
     Type:  defect     |     Status:  new
 Priority:  Normal     |  Milestone:
Component:  base       |    Version:  2.4.2
 Keywords:  upgrade    |       Port:
-----------------------+-------------------
 Running Mac Ports on El Capitan (OS darwin/14.5.0 (Mac OS X 10.10)) I did
 a `mac port selfupdate`, and it  updated to 2.4.1 to 2.4.2.  Then I did a
 `sudo port upgrade outdated, and it hangs with no output.  I repeated the
 upgrade with the -d flag and got the following trace.
 {{{
 sudo port -d upgrade outdated
 Password:
 DEBUG: Copying /Users/scs1ng/Library/Preferences/com.apple.dt.Xcode.plist
 to /opt/local/var/macports/home/Library/Preferences
 DEBUG: epoch: in tree: 0 installed: 0
 DEBUG: apache2 2.4.28_2 exists in the ports tree
 DEBUG: apache2 2.2.34_0 +preforkmpm is the latest installed
 DEBUG: apache2 2.2.34_0 +preforkmpm is active
 DEBUG: Merging existing variants '+preforkmpm' into variants
 DEBUG: new fully merged portvariants: preforkmpm +
 DEBUG: Changing to port directory:
 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/www/apache2
 DEBUG: OS darwin/14.5.0 (Mac OS X 10.10) arch i386
 DEBUG: Sourcing PortGroup apache2 1.0 from
 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/apache2-1.0.tcl
 DEBUG: adding the default universal variant
 DEBUG: Reading variant descriptions from
 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
 DEBUG: Executing variant preforkmpm provides preforkmpm
 DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies
 }}}
 and it then hung (I was able to interrupt with a CTL-C).

 Nothing has changed about the system from the previous time I did a
 selfupdate/upgrade outdated about 2 weeks ago.  So it seems at first sight
 as though the problem arises from the new, 2.4.2, version of the base.

--
Ticket URL: <https://trac.macports.org/ticket/55136>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list