#38586: atlas @3.10.1_3: log file contents missing when -k option used --------------------------+-------------------------------- Reporter: jdgleeson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jdgleeson@…): I have started to systematically collect log files and debug output when I do "{{{sudo port -kd upgrade foo}}}" or "{{{sudo port -kd install foo}}}" under different circumstances. So far I have looked carefully at only the case where an outdated port is upgraded after "{{{sudo port selfupdate}}}". I am happy to report that the results are extremely consistent across about 30 upgrades. But they are not what I expected: I expected to see logging of all phases of the upgrades, but I always see only the activation phase. I've attached the log (svmain.log) and debug output (svtermout.txt) from "{{{sudo port -kd upgrade postgresql92 &> svtermout.txt}}}". I expected all of the phases of the upgrade to be present in svmain.log, much like they are in svtermout.txt. But svmain.log has only the activate phase. Should the upgrade log be roughly as complete as the debug output, or not? Keep in mind that the new version postgresql92@9.2.4_0 was not previously fetched, built, installed, upgraded, uninstalled, etc. Furthermore, all of its dependencies are installed and up-to-date (otherwise there would be more variables introduced into the problem that i'd rather not deal with). I noticed that "{{{DEBUG: Starting logging for postgresql92}}}" occurs 3 times in svtermout.txt: [[BR]] LINE 399: at the start of the dependency check phase [[BR]] LINE 6477: at the start another dependency check phase [[BR]] LINE 6514: at the start of the activation phase Is it true that each time we see "{{{Starting logging for foo}}}" in the debug output, any previous logging for foo during that same run of "{{{port upgrade}}}" is lost? In the single instance of upgrading atlas where I have both the debug output and a log file that contains all phases, "{{{Starting logging for atlas}}}" occurs exactly once near the beginning of the debug output. It has an activation phase, too, but so there is some condition under which log file do not get clobbered at the start of the activation phase. This was run under different circumstances (after uninstall -f and clean). -- Ticket URL: <https://trac.macports.org/ticket/38586#comment:16> MacPorts <http://www.macports.org/> Ports system for OS X