I did my best with the bug report. I had no idea what to put in the comments section.
I attached what I hope is a gzip version of the main.log. I’m a bit gun shy about creating a ticket. Last time it turned out not to be a port problem, but something to do with the command line tools; a something that I really didn’t understand. Somehow it seems that tickets should generally be filed by people who actually know what they’re doing. -- https://www.mgnewman.com > On Oct 2, 2024, at 10:58 AM, Joshua Root <[email protected]> wrote: > > Michael Newman wrote: > >> This morning I upgraded my 2019 iMac to Sequoia and then did a port migrate. >> >> I think everything went OK, except for the following: >> >> The following ports could not be restored: >> - nbsmtp >> Failed: Unable to execute target 'activate' for port nbsmtp - see its >> log >> for details >> >> When I look at what I think is the log, I see this at the end, which means >> nothing to me: >> >> :error:build Failed to build nbsmtp: command execution failed >> :debug:build Error code: CHILDSTATUS 70925 2 >> :debug:build Backtrace: command execution failed >> :debug:build while executing >> :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" >> :debug:build invoked from within >> :debug:build "command_exec -callback portprogress::target_progress_callback >> build" >> :debug:build (procedure "portbuild::build_main" line 10) >> :debug:build invoked from within >> :debug:build "$procedure $targetname" >> :error:build See >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_mail_nbsmtp/nbsmtp/main.log >> for details. > > About all that particular part of the log means is "running some shell > command failed during the build phase". The relevant error will be earlier. > This is part of why we always ask for full logs; end users can't be expected > to know which parts of the log are relevant. > >> When I search for a ticket for nbsmtp I find nothing. (But I’m not very good >> at searching.) > > The easiest way to check if there are any tickets open against a port is > probably to go to its page on ports.macports.org, click "Details", and check > the "Trac Tickets" tab. It looks like there are not any open tickets in this > case. There's a handy "Report an Issue with this port" link on the same page. > >> What next? > > Open a ticket and add the complete main.log as an attachment. > > - Josh >
smime.p7s
Description: S/MIME cryptographic signature
