[MacPorts] #60343: Xemacs @21.4.22_16+sumo: archivefetch failure in trace mode: error: realpath failed: Permission denied

[MacPorts]

#60343: Xemacs @21.4.22_16+sumo: archivefetch failure in trace mode:  error:
realpath failed: Permission denied
------------------------+--------------------
  Reporter:  spiralbit  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.2
Resolution:             |   Keywords:
      Port:  xemacs     |
------------------------+--------------------

Comment (by ryandesign):

 Installing Xcode via any method (App Store or manual download from Apple
 Developer web site) is fine. The value you show for xcode-select is fine
 and normal. No additional steps are required to tell MacPorts about your
 Xcode installation.

 The attached main.log actually documents 6 separate installation attempts.
 The first attempt tried to download an archive, failed to find one, then
 tried to build from source:

 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 11:38:32 BST
 2020
 :debug:fetch fetch phase started at Sat Apr 11 11:38:32 BST 2020
 :debug:checksum checksum phase started at Sat Apr 11 11:38:32 BST 2020
 :debug:extract extract phase started at Sat Apr 11 11:38:33 BST 2020
 :debug:patch patch phase started at Sat Apr 11 11:38:39 BST 2020
 :debug:configure configure phase started at Sat Apr 11 11:38:40 BST 2020
 :debug:build build phase started at Sat Apr 11 11:39:10 BST 2020
 }}}

 It failed because of a texinfo error:

 {{{
 :info:build lispref/ldap.texi:108: misplaced }
 }}}

 My understanding is that this type of error occurs when you try to use a
 modern version of texinfo to build old texi files.

 The second attempt tried to download an archive, failed to find one, then
 resumed the previously failed build:

 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 11:40:57 BST
 2020
 :debug:build build phase started at Sat Apr 11 11:40:57 BST 2020
 }}}

 It failed for the reason described in #59502:

 {{{
 :info:build Malformed UTF-8 character: \xe4\x2c\x20 (unexpected non-
 continuation byte 0x2c, immediately after start byte 0xe4; need 3 bytes,
 got 1) in pattern match (m//) at
 /opt/local/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
 :info:build Malformed UTF-8 character (fatal) at
 /opt/local/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
 }}}

 This is also a problem of trying to build old texi files with modern
 texinfo, so solving this issue will probably solve the issue seen in the
 first attempt.

 Both of the first two attempts occurred when, as far as MacPorts was able
 to determine, Xcode was not installed.

 The third, fourth, fifth, and sixth attempts took place when Xcode 10.1
 was installed. For these attempts, MacPorts tried to download an archive
 and stopped there:

 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 11:50:47 BST
 2020
 }}}
 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 11:55:17 BST
 2020
 }}}
 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 11:56:19 BST
 2020
 }}}
 {{{
 :debug:archivefetch archivefetch phase started at Sat Apr 11 12:01:49 BST
 2020
 }}}

 These attempts all failed for the same reason: the inexplicable `realpath
 failed: Permission denied` error. I don't know why this is happening. I
 can't find any other occurrences of this error on the Internet. The
 presence or absence of Xcode should have no influence on our ability to
 fetch archives. Ports can't really influence the archive fetch stage, so
 any failure here is happening in MacPorts base and is unrelated to the
 specific port you're installing.

 The archive that MacPorts failed to download for you back on April 11,
 2020 now exists on our server. It was created December 4, 2020. If you
 `sudo port clean xemacs` and try again, with luck you should receive that
 archive and hopefully avoid the problems you saw before. Or you might
 continue to see the `realpath failed: Permission denied` error with this
 or any other port, since it comes from MacPorts base and we don't know why
 it's happening for you.

-- 
Ticket URL: <https://trac.macports.org/ticket/60343#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS