[MacPorts] #16506: "port extract" in current directory extracts nothing
#16506: "port extract" in current directory extracts nothing ---------------------------------+------------------------------------------ Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Keywords: | Port: ---------------------------------+------------------------------------------ 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 }}} -- Ticket URL: <http://trac.macports.org/ticket/16506> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by dluke@macports.org): I may be missing something, but this works for me: {{{ % pwd /Volumes/Extra/dluke/Projects/macports/dports/net/rrdtool % port extract ---> Fetching rrdtool ---> Verifying checksum(s) for rrdtool ---> Extracting rrdtool % ls work/ rrdtool-1.3.2/ }}} -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by vinc17@macports.org): 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? -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: invalid | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by vinc17@macports.org): * status: new => closed * resolution: => invalid Comment: 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... -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: invalid | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by jmr@macports.org): Shouldn't using -f have caused it to ignore the state file anyway? -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: invalid | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by dluke@macports.org): force doesn't override the state file. see #11143 and http://lists.macosforge.org/pipermail/macports- users/2006-December/000876.html -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16506: "port extract" in current directory extracts nothing ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: invalid | Keywords: Port: | ----------------------------------+----------------------------------------- Comment(by raimue@macports.org): 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. -- Ticket URL: <http://trac.macports.org/ticket/16506#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts