Opened 13 years ago

Closed 12 years ago

#31236 closed defect (invalid)

"port logfile" does not print correct location

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.0.3
Keywords: Cc:
Port:

Description

Warning: the following items did not execute (for mongodb): org.macports.build
Log for mongodb is at: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_mongodb/mongodb/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
$ ls -l $(port logfile )
ls: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_mongodb/main.log: No such file or directory

Note: "port logfile" said the logfile is here:

/opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_mongodb/main.log

The logfile is actually here, as the install failure message said:

/opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_mongodb/mongodb/main.log

Or maybe "port logfile" is printing what should be the correct location, but MacPorts base is writing the logfile in the wrong place. There didn't used to be that intermediate portname directory in previous versions of MacPorts; maybe that change was unintentional.

Change History (1)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

Invalid. The intermediate directory is intentional; it's for subports. "port logfile" was fixed for this in r78177. I forgot I had a "port logfile" shell alias defined, from before MacPorts had a "logfile" command.

Note: See TracTickets for help on using tickets.