On Apr 17, 2007, at 7:27 PM, David Liontooth wrote:
I believe that if you pass the -p flag to port, that this error (and any others) in a particular port will be ignored. The -p flag basically says that, while processing multiple ports (such as those furnished by all) that an error in one should be ignored. Hi James,
I just upgraded to your hot-off-the-stove 1.4.3 flawlessly, and then tried
sudo port -f clean -p --all all
This command should have been: sudo port -f -p clean --all all which would have ignored the problem with gtk26 no longer being present.
It stumbled here:
Error: Unable to open port: couldn't change working directory to "/opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate_dports/x11/gtk26": no such file or directory
The gtk26 maintainer just requested the package be removed, and Maun Suang reported, "Done in r24129." I found /opt/local/etc/ports/sources.conf, where it seems port is downloading a fresh list -- what's the design feature that throws up this disagreement?
That's due, unfortunately, to the PortIndex being generated at a lower frequency than the sync of the subversion tree to the rsync repository. So the PortIndex is slightly out of date with respect to the rest of the rsync files.
This time I created a fake directory and portfile and got past that point, only to stumble again on the same package as when I was not using the -p flag:
nhc98 is not supported on OS X i386 yet
I would much prefer you were correct that the -p flag would inspire port to take such troubles in its stride, but alas, it fell on its face again.
Yeah, even -p (properly placed) won't get you past this one. The port author was calling exit, on i386, whenever the Portfile was opened. I've checked in a revision to that port (r24159) which defers the error report until build time, and then does so in a somewhat nicer fashion. Thanks for the report. James.