[MacPorts] #61796: Activation broken on Tiger

[MacPorts]

#61796: Activation broken on Tiger
-----------------------+--------------------
 Reporter:  fhgwright  |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  Normal     |  Milestone:
Component:  ports      |    Version:  2.6.4
 Keywords:  tiger      |       Port:
-----------------------+--------------------
 A few days ago, "port upgrade outdated" started failing on Tiger (both
 i386 and ppc), due to activations failing in a manner like this:

 {{{
 mact:~ fw$ sudo port activate p5.28-encode
 The following versions of p5.28-encode are currently installed:
  1) p5.28-encode @3.70.0_0
  2) p5.28-encode @3.80.0_0
 Enter a number to select an option: 1
 --->  Activating p5.28-encode @3.70.0_0
 Error: port activate failed: error deleting
 "/opt/local/var/macports/software/p5.28-encode/mpextractpjw3MR7y/opt/opt/local/opt/local/lib/opt/local/lib/perl5/opt/local/lib/perl5/vendor_perl/opt/local/lib/perl5/vendor_perl/5.28/opt/local/lib/perl5/vendor_perl/5.28
 /darwin-thread-multi-2level/opt/local/lib/perl5/vendor_perl/5.28/darwin-
 thread-multi-2level/auto/opt/local/lib/perl5/vendor_perl/5.28/darwin-
 thread-multi-2level/auto/Encode/opt/local/lib/perl5/vendor_perl/5.28
 /darwin-thread-multi-
 2level/auto/Encode/opt/local/lib/perl5/vendor_perl/5.28/darwin-thread-
 multi-2level/auto/Encode/Byte/opt/local/lib/perl5/vendor_perl/5.28/darwin-
 thread-multi-2level/auto/Encode/opt/local/lib/perl5/vendor_perl/5.28
 /darwin-thread-multi-
 2level/auto/Encode/CN/opt/local/lib/perl5/vendor_perl/5.28/darwin-thread-
 multi-2level/auto/Encode/opt/local/lib/perl5/vendor_perl/5.28/darwin-
 thread-multi-
 2level/auto/Encode/EBCDIC/opt/local/lib/perl5/vendor_perl/5.28/darwin-
 thread-multi-2level/auto/Encode/opt/local/lib/perl5/vendor_perl/5.28
 /darwin-thread-multi-2level/auto/Encode/Encode.bundle": file name too long
 }}}

 Note that in this example, it's trying to activate a version that was
 previously active, so it's not a problem with the port itself.  A cursory
 examination of the git history doesn't show any likely PortGroup
 candidates, which suggests that it's a problem with base, but this didn't
 appear until long after updating base to 2.6.4 (with many successful
 activations).

 The directories are so deep that it's not even possible to remove them
 with `rm -rf`, so I'll need to write a program just to clean up the mess.
 But moving the existing trees to a different directory to "effectively
 delete" them doesn't help, so it's not just a case of one-time poisoning.

 It seems that whatever creates the
 `.../macports/software/<port>/mpextract*` trees is badly broken on Tiger
 for some reason.

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