id summary reporter owner description type status priority milestone component version resolution keywords cc port 53587 buildbot: portwatcher should not run if portbuilder is still running ryandesign admin@… "portwatcher is designed to wait until all its triggered portbuilders finish. This is supposed to ensure that portwatcher does not run while any portbuilder runs, but there is one situation where that is not the case. If the machine is unexpectedly restarted while portbuilders are running (due to power outage, kernel panic, etc.) then, when it boots back up, the portbuilders that had been scheduled will pick up where they left off, ''and'' the next scheduled portwatcher will begin running, which will include syncing the ports tree and regenerating the portindex. Doing this while portbuilders are building can cause the portbuilder to fail, for example https://build.macports.org/builders/ports-10.5_ppc_legacy-builder/builds/21093 : {{{ ---> Computing dependencies for gettext DEBUG: gettext has no conflicts DEBUG: Searching for dependency: expat DEBUG: Found Dependency: receipt exists for expat DEBUG: Searching for dependency: libiconv DEBUG: Didn't find receipt, going to depspec regex for: libiconv Warning: It looks like your PortIndex file for file:///opt/bblocal/var/buildworker/ports/build/ports may be corrupt. Error: Dependency 'libiconv' not found. }}} (The ""It looks like your PortIndex file may be corrupt"" message is easy to reproduce on your own system if you begin installing a port from source and, before it finishes, run `sudo port sync` (or just `portindex` in the ports directory) in a second terminal window.) " defect new Normal buildbot/mpbb buildbot mojca mascguy