Help request to undestand the portmon report

Bill Moran wmoran at
Fri Jul 11 10:51:21 UTC 2008

In response to "Rodrigo OSORIO (ros)" <ros at>:

> Hello everyone,
> I just take a quick look at the portmon report about my first port submit, omegaT[1], a translation memory editor.
> As I can see, portmon reports a 'failed to build' state for the amd64-8-latest environment, but if I took a close look, the log file looks ok (the port and the pakage was build without errors).

The link doesn't seem to jump to the correct position on this page:

But it says this about your error:
    The port leaves ${PREFIX} in a state that is not consistent with the mtree definition after pkg_delete. This usually means some files are missing from PLIST. It could also mean that your installation scripts create files or directories not properly deleted by the deinstallation scripts. Another possibility is that your port is deleting some directories it is not supposed to, or incorrectly modifying some directory's permission.

> My question is why portmon think an error occurs during the build (maybe something wrong is hide in the log).

Because of this:
=== Checking filesystem state
list of filesystem changes from before and after port installation and deinstallation
usr/local/share/java/apache-ant/bin/antRun changed
	permissions expected 0555 found 0444

> And how can I fix this situation to avoid unnecesary problems reported for the port tree.

Well ... here's where I'm not much help, as I'm not very familiar with
the care and feeding of Java apps.

Bill Moran

More information about the freebsd-ports mailing list