[MacPorts] #22261: odcctools fails to patch extract.sh
MacPorts
noreply at macports.org
Tue Oct 27 13:08:00 PDT 2009
#22261: odcctools fails to patch extract.sh
---------------------------------+------------------------------------------
Reporter: saml@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: High | Milestone:
Component: ports | Version: 1.8.1
Resolution: duplicate | Keywords: odcctools Portfile patch-extract.sh twice
Port: odcctools |
---------------------------------+------------------------------------------
Changes (by blb@…):
* status: new => closed
* resolution: => duplicate
Old description:
> bash-3.2# port install odcctools
> ---> Computing dependencies for odcctools
> ---> Applying patches to odcctools
> Error: Target org.macports.patch returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_odcctools/work/odcctools/odcctools"
> && /usr/bin/patch -p0 <
> '/opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/odcctools/files
> /patch-extract.sh'" returned error 1
> Command output: can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |--- extract.sh.orig 2009-09-13 11:24:01.000000000 -0700
> |+++ extract.sh 2009-09-13 11:24:14.000000000 -0700
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 1 out of 1 hunk ignored
>
> Error: Status 1 encountered during processing.
>
> As you can see above, it's replacing ${workpath}/${name} with odcctools
> twice in the name. I've verified this below:
>
> I tried editing the portfile line 35:
> system "patch -p0 -d ${workpath}/${name} -i ${filespath}/patch-
> extract.sh"
>
> I've changed the -d to ${workpath/odcctools and it does that same thing,
> I've changed it to ${workpath} and it gives an error with no odcctools
> directory appended
> (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_odcctools/work)
> I've changed it to name and it gives just plain odcctools once, but some
> reason it keeps spitting out odcctools twice in the default configuration
> and also replacing ${name} with the odcctools.
>
> This is on leopard 10.5.8. I'm trying to install odcctools to
> troubleshoot a g95 problem with some custom code.
New description:
{{{
bash-3.2# port install odcctools
---> Computing dependencies for odcctools
---> Applying patches to odcctools
Error: Target org.macports.patch returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_odcctools/work/odcctools/odcctools"
&& /usr/bin/patch -p0 <
'/opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/odcctools/files
/patch-extract.sh'" returned error 1
Command output: can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- extract.sh.orig 2009-09-13 11:24:01.000000000 -0700
|+++ extract.sh 2009-09-13 11:24:14.000000000 -0700
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Error: Status 1 encountered during processing.
As you can see above, it's replacing ${workpath}/${name} with odcctools
twice in the name. I've verified this below:
I tried editing the portfile line 35:
system "patch -p0 -d ${workpath}/${name} -i ${filespath}/patch-extract.sh"
I've changed the -d to ${workpath/odcctools and it does that same thing,
I've changed it to ${workpath} and it gives an error with no odcctools
directory appended
(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_odcctools/work)
I've changed it to name and it gives just plain odcctools once, but some
reason it keeps spitting out odcctools twice in the default configuration
and also replacing ${name} with the odcctools.
}}}
This is on leopard 10.5.8. I'm trying to install odcctools to troubleshoot
a g95 problem with some custom code.
--
Comment:
Dup of #21693. See also #21355.
--
Ticket URL: <http://trac.macports.org/ticket/22261#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list