On Oct 10, 2009, at 20:49, Thomas De Contes wrote:
+ port -u upgrade outdated
MacPorts running without privileges. You may be unable to complete
certain actions (eg install).
---> Computing dependencies for readline
MacPorts running without privileges. You may be unable to complete
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete
certain actions (eg install).
---> Applying patches to readline
Error: Target org.macports.patch returned: shell command " cd "/
Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/
build/
_Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline
/work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/
prgm/bin/autoinstall/macports/var/macports/sources/
rsync.macports.org/release/ports/devel/readline/files/patch-shobj-
conf.diff'" returned error 1
Command output: patching file support/shobj-conf
Hunk #1 FAILED at 152.
Hunk #2 FAILED at 176.
2 out of 2 hunks FAILED -- saving rejects to file support/shobj-
conf.rej
Error: Unable to upgrade port: 1
Since the first thing shown for readline is "Applying patches" instead
of "Fetching" or "Extracting", this suggests you had previously
started installing readline and cancelled it just after it finished
the patch phase but before it recorded that it had finished the patch
phase. So now it's trying to apply the patches a second time, and
failing, because they are already applied.
In those situations you usually see the message "Reversed (or
previously applied) patch detected! Assume -R? [n]". But the readline
port not only applies patchfiles to the source files, it also has a
post-patch step which does a reinplace on shobj-conf. Therefore the
way the file looks now is not exactly the way it would look after only
applying the patches, therefore the patch program doesn't know what to
do.
The solution should be to clean the port, selfupdate to make sure you
have the latest MacPorts and port definitions, and try again. This is
probably the first step you should try any time any port fails.
sudo port clean readline
sudo port selfupdate
sudo port upgrade readline
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
