[MacPorts] #71047: emacs-app @29.4_1+imagemagick+nativecomp+rsvg+treesitter: Failed to activate
MacPorts
noreply at macports.org
Tue Oct 8 15:35:02 UTC 2024
#71047: emacs-app @29.4_1+imagemagick+nativecomp+rsvg+treesitter: Failed to
activate
------------------------+---------------------------
Reporter: eschnett | Owner: drkp
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.10.2
Resolution: | Keywords: sequoia arm64
Port: emacs-app |
------------------------+---------------------------
Comment (by ryandesign):
But you'll notice the new log is 3.8MB compared to the old log's 11.4KB so
we now have more information we can analyze.
For example, I see this in the new log:
{{{
:info:install a ./Applications/MacPorts/Emacs.app/Contents/Frameworks
/native-lisp/29_4-ca101c6e/subr--trampoline-
782d7365727665722d6d61782d726571756573742d73697a65_x_server_max_request_size_0.eln
:info:install a ./Applications/MacPorts/Emacs.app/Contents/Frameworks
/native-lisp/29_4-ca101c6e/ebnf-dtd-3a6441e4-ed9e4a3a.eln
:info:install x ./Applications/MacPorts/Emacs.app/Contents/Frameworks
/native-lisp/29_4-ca101c6e/._subr--trampoline-
782d7365727665722d6d61782d726571756573742d73697a65_x_server_max_request_size_0.eln
:info:install x ./Applications/MacPorts/Emacs.app/Contents/Frameworks
/native-lisp/29_4-ca101c6e/ebnf-dtd-3a6441e4-ed9e4a3a.elna
./Applications/MacPorts/Emacs.app/Contents/Frameworks/native-
lisp/29_4-ca101c6e/vcursor-f24573d4-9fbe65a0.eln
}}}
Lines beginning with `a` are adding files to an archive. Lines beginning
with `x` are extracting files from an archive. They seem to be happening
simultaneously. This seems unusual to me but the way that ports are
activated was overhauled in MacPorts 2.10.0 and I am not yet familiar with
it so it may be normal.
What caught my eye about this though is that for this file that you're
having a problem with—`subr--trampoline-
782d7365727665722d6d61782d726571756573742d73697a65_x_server_max_request_size_0.eln`—I
see an entry where its name is preceded by `._` (and this is the only file
that does this). Such files have caused us problems with activation
before; see #60749. The question is why this port seems to have a `._`
file and how we can get rid of it.
--
Ticket URL: <https://trac.macports.org/ticket/71047#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list