#24040: Logging: Errors ending up in wrong log file with livecheck ---------------------------------+------------------------------------------ Reporter: raimue@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 1.9.0 Component: base | Version: 1.8.99 Keywords: logging log | Port: ---------------------------------+------------------------------------------ I experimented a bit with a new livecheck.type and made some mistakes while writing this. The following happened when I used livecheck with a faulty Portfile for `stellarium` in place: {{{ $ port -v livecheck maintainer:raimue allegro seems to be up to date ... qbzr seems to be up to date Error: Target org.macports.livecheck returned: The defaults could not be loaded from '/Users/raim/src/macports/trunk/dports/_resources/port1.0/livecheck/foo.tcl'. Warning: the following items did not execute (for stellarium): org.macports.livecheck Log for stellarium is at: /opt/local/var/macports/logs/_Users_raim_src_macports_trunk_dports_devel_allegro/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} The report mentions a log file for allegro which does not contain anything related to this livecheck. It was produced at an previous build attempt. Interesting is that this log output does not appear if I run livecheck directly on the faulty stellarium port: {{{ $ port -v livecheck stellarium Error: Target org.macports.livecheck returned: The defaults could not be loaded from '/Users/raim/src/macports/trunk/dports/_resources/port1.0/livecheck/foo.tcl'. Warning: the following items did not execute (for stellarium): org.macports.livecheck Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} -- Ticket URL: <http://trac.macports.org/ticket/24040> MacPorts <http://www.macports.org/> Ports system for Mac OS