Okay, I get errors when I do "archive" the port. soohyunc@davinci: ~ $ sudo port fetch xorg-proto soohyunc@davinci: ~ $ sudo port checksum xorg-proto soohyunc@davinci: ~ $ sudo port configure xorg-proto soohyunc@davinci: ~ $ sudo port build xorg-proto soohyunc@davinci: ~ $ sudo port destroot xorg-proto soohyunc@davinci: ~ $ sudo port archive xorg-proto ---> Packaging tgz archive for xorg-proto 20070907_0 Error: Target org.macports.archive returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/.macports.xorg- proto.state" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/destroot/+STATE": no such file or directory Error: Status 1 encountered during processing. soohyunc@davinci: ~ $ Anyone got a clue why I'm getting this errors and how I can cure? Thanks, Soo-Hyun On 10/30/07, Daniel J. Luke <dluke@geeklair.net> wrote:
On Oct 30, 2007, at 2:19 PM, markd@macports.org wrote:
That port is supposed to do nothing but trigger dependencies.
fetch { } checksum { } configure { } build { } destroot { } activate { }
Is there another stage that needs to be eliminated? I'm not familiar with ports like this.
archive { }
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+