#68010 closed defect (duplicate)
activation failed with trace mode
| Reported by: | ThoAppelsin (Utkan Gezer) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.8.1 |
| Keywords: | ventura | Cc: | drkp (Dan Ports) |
| Port: |
Description
I was hoping to install texlive -doc -medium +full (@2023) and psutils (@p17_1) being a part of it fails to install. To give it a try, and also to keep the main.log simple, I tried installing psutils (@p17_1) individually, and it also fails with the following message:
Error: Failed to activate psutils: command execution failed
while executing
"system $cmdstring"
P.S.: psutils appears to have no maintainer.
Attachments (1)
Change History (4)
Changed 8 months ago by ThoAppelsin (Utkan Gezer)
comment:1 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
The log says:
:msg:activate ---> Activating psutils @p17_1 :debug:activate Using bsdtar with HFS+ compression (if valid) :debug:activate Using /usr/bin/bzip2 :debug:activate system: /usr/bin/bzip2 -d -c /opt/local/var/macports/software/psutils/psutils-p17_1.darwin_22.arm64.tbz2 | ( bsdtar -xvp --hfsCompression -f - ) :info:activate Command failed: /usr/bin/bzip2 -d -c /opt/local/var/macports/software/psutils/psutils-p17_1.darwin_22.arm64.tbz2 | ( bsdtar -xvp --hfsCompression -f - ) :info:activate Killed by signal: 9
So why did bzip2 and/or bsdtar get killed? Did you use trace mode (the -t flag)? If so, trace mode is broken on macOS 13 and later so you'll have to forgo trace mode.
comment:2 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|---|
| Keywords: | ventura added; activate failed executing removed |
| Port: | texlive psutils removed |
| Resolution: | → duplicate |
| Status: | new → closed |
| Summary: | psutils @p17_1: activate error, failed while executing "system $cmdstring" → activation failed with trace mode |
Ah, the log also says you are using trace mode:
:debug:activate Tracelib Sandbox is:
:debug:activate Tracemode will respect recursively collected port dependencies:
So that confirms it. Duplicate of #66358.
comment:3 Changed 8 months ago by ThoAppelsin (Utkan Gezer)
Oh, wow, thank you! (Still having some issues, but those would be a topic for another ticket if they persist, and...) I have now passed that part of the installation.
It might be worthwhile to put a warning/note right where the -t flag is recommended, here (MacPorts Guide, section 3.1.11 `port install`), as the last resort before filing such tickets.
main.log