Le 11 oct. 09 à 22:23, Ryan Schmidt a écrit :


On Oct 11, 2009, at 09:43, Thomas De Contes wrote:

no, it made an error, and i just run it again

Ah, ok. Still, the error you reported was caused by running it a second time without cleaning.

true (but it's unusual)



port clean readline
and then :

+ port selfupdate
...
+ 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).
--->  Fetching readline
MacPorts running without privileges. You may be unable to complete certain actions (eg install).
--->  Verifying checksum(s) for readline
MacPorts running without privileges. You may be unable to complete certain actions (eg install).
--->  Extracting readline
MacPorts running without privileges. You may be unable to complete certain actions (eg install).
--->  Applying patches to readline
Error: Target org.macports.patch returned: could not set group for file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/ macports/build/ _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so urces_rsync.macports.org_release_ports_devel_readline/work/ readline-6.0/support/shobj-conf": not owner
Error: Unable to upgrade port: 1

Ok, that's the first and real error, and is:

http://trac.macports.org/ticket/20896

As shown in the ticket, I identified the change that caused that problem. Joshua, what do you think we should do about this? We could apply the patch I supplied, which would revert one of your prior changes. Or we could try to figure out a way to allow your change while still avoiding this issue.


any news ?

is it possible to upgrade readline nevertheless ?


--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to