[MacPorts] #30034: scite 2.24 Patch error due to .. path component
MacPorts
noreply at macports.org
Tue Jul 5 09:20:43 PDT 2011
#30034: scite 2.24 Patch error due to .. path component
--------------------------------+-------------------------------------------
Reporter: datouxia@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: scite
--------------------------------+-------------------------------------------
Old description:
> When install scite My log says:[[BR]]
> :debug:patch Assembled command: 'cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_scite/work/scite/gtk"
> && /usr/bin/patch -p0'[[BR]]
> :info:patch /usr/bin/patch: **** rejecting file name with ".." component:
> ../../scintilla/gtk/makefile[[BR]]
> :info:patch shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_scite/work/scite/gtk"
> && /usr/bin/patch -p0 <
> '/opt/local/var/macports/sources/rsync.macports.org/release/ports/editors/scite/files
> /patch-scite-makefile.diff'" returned error 2[[BR]]
>
> Maybe this question caused by patch 2.5.8.
> https://bugzilla.redhat.com/show_bug.cgi?id=667529
New description:
When install scite My log says:
{{{
:debug:patch Assembled command: 'cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_scite/work/scite/gtk"
&& /usr/bin/patch -p0'
:info:patch /usr/bin/patch: **** rejecting file name with ".." component:
../../scintilla/gtk/makefile
:info:patch shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_scite/work/scite/gtk"
&& /usr/bin/patch -p0 <
'/opt/local/var/macports/sources/rsync.macports.org/release/ports/editors/scite/files
/patch-scite-makefile.diff'" returned error 2
}}}
Maybe this question caused by patch 2.5.8.
https://bugzilla.redhat.com/show_bug.cgi?id=667529
--
Comment(by ryandesign@…):
Yes, it is caused by new security enhancements in the version of patch
2.5.8 in Mac OS X 10.6.8 and 10.7.0. (The version of patch 2.5.8 in Mac OS
X 10.6.7 did not have these enhancements and thus did not experience this
problem.)
--
Ticket URL: <https://trac.macports.org/ticket/30034#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list