It's the new privilege-dropping mode that's enabled by default in MacPorts 2.0.0. I'll bet you started building LilyPond with MacPorts 1.9.2 (state file would be owned by root), interrupted the build somehow, then upgraded to MacPorts 2.0.0, then tried to resume the build (macports users does not have permission to deal with the state file owned by root). Cleaning is the solution, as you found.
On Jul 26, 2011, at 09:14, Siegfried wrote: > Got it to work on by cleaning up /opt/local/var/macports/build > > Quite strange, permission when running sudo… Anyway, thanks! > > On 26/07/2011, at 11:02, Siegfried wrote: > >> I'm trying to install LilyPond but I keep getting this error: >> >> $ sudo port install lilypondError: Unable to execute port: couldn't open >> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_lilypond/lilypond/work/.macports.lilypond.state": >> permission denied >> To report a bug, see <http://guide.macports.org/#project.tickets> _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
