#16506 closed defect (invalid)
"port extract" in current directory extracts nothing
Reported by: | vinc17@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: |
Description
I want to extract in the current directory because I have another source that has the precedence. But this doesn't work:
$ pwd /Users/vinc17/software/dports/net/rrdtool $ ls -l total 4 -rw-r--r-- 1 vinc17 vinc17 1227 2008-09-10 12:57:42 Portfile $ sudo port -v -f extract $ ls -l total 8 -rw-r--r-- 1 vinc17 vinc17 1227 2008-09-10 12:57:42 Portfile lrwxr-xr-x 1 root vinc17 76 2008-09-10 15:54:16 work -> /opt/local/var/macports/build/_Users_vinc17_software_dports_net_rrdtool/work/ $ ls -l work/ total 0
Change History (8)
comment:1 Changed 16 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 16 years ago by vinc17@…
Here's debug information:
$ sudo port -v -f -d extract DEBUG: Changing to port directory: /Users/vinc17/software/dports/net/rrdtool DEBUG: Requested variant powerpc is not provided by port rrdtool. DEBUG: Requested variant darwin is not provided by port rrdtool. DEBUG: Requested variant macosx is not provided by port rrdtool. DEBUG: Changing to port directory: /Users/vinc17/software/dports/net/rrdtool DEBUG: Requested variant powerpc is not provided by port rrdtool. DEBUG: Requested variant darwin is not provided by port rrdtool. DEBUG: Requested variant macosx is not provided by port rrdtool. DEBUG: Skipping completed org.macports.main (rrdtool) DEBUG: Skipping completed org.macports.fetch (rrdtool) DEBUG: Skipping completed org.macports.checksum (rrdtool) DEBUG: Skipping completed org.macports.extract (rrdtool) $ ls -l work/ total 0
Why does it think it is completed?
comment:3 Changed 16 years ago by vinc17@…
Resolution: | → invalid |
---|---|
Status: | new → closed |
OK, there was a remaining file work/.macports.rrdtool.state I didn't see. BTW, it isn't a very good idea to use hidden files...
comment:4 Changed 16 years ago by jmroot (Joshua Root)
Shouldn't using -f have caused it to ignore the state file anyway?
comment:5 Changed 16 years ago by danielluke (Daniel J. Luke)
force doesn't override the state file.
see #11143 and http://lists.macosforge.org/pipermail/macports-users/2006-December/000876.html
comment:6 Changed 16 years ago by raimue (Rainer Müller)
The -f flag does not override the state, but if the modified timestamp on the Portfile is newer than on the state file, port will delete the state file and start from beginning. So touch Portfile
would have resolved this without manually deleting the state file.
comment:7 Changed 16 years ago by tobypeterson
Milestone: | MacPorts base bugs → MacPorts Future |
---|
Milestone MacPorts base bugs deleted
comment:8 Changed 15 years ago by jmroot (Joshua Root)
Milestone: | MacPorts Future |
---|
I may be missing something, but this works for me: