.Actually, the subject is just a title, probably not the subject (multiple issues).
I continue to believe svn, (pkg...) (gpart) should have a *flowchart* so issues could be resolved without consulting forums, wikis, ... quicker. Should one compose one for svn, the following fixed "checksum mismatch" svn halts on the ports tree. #problem dir# svn co --set-depth empty (or it was svn up...) #problem dir# svn co --set-depth infinity (or it was svn up...) #/usr/ports# svn up /usr/ports However, that worked only on about ninety percent of the problematic ports, of which there were too many. I quit using it however, and had to re-svn a ports tree, when svn could no longer operate because of segfaulting. (Maybe it is unstable once it is fixed in a nonstandard way...) Hope that hint helps someone. One needs a recent version of svn for it to work. ........................................................................................................................... Two issues, however, seem problematic here. ......................................................................................................................... One, many gnome ports (pkg_add) fail upon the (pkg_delete && pkg_add ) pkg_add, "playpen: cannot change back to ' ' " and have done so for years, so the machine on which the install is to be done (say, an xargs-fed portmaster) halts with the port newly deinstalled. (for which I found this week, the following make install -C /usr/ports/[category][port] if one is in a hurry...) (Most Freebsd users probably know it already, I had always changed to the directory first.) Anyway, I am wondering if the unknown cause (year after year here) of that pkg_add error will occur also in the equivalent command of pkg, if the cause is not known and determined to be a factor in the new code. .................................................................................................................................................................................. The other pressing issue, For instance, today reinstalling p5-Text-RecordParser (which btw wont' patch) with portmaster -d -B -P -i -g ... installed p5-Pod-* (2 of) "into" perl 5.14 although I still use 5.12.5.... So if I am upgrading hundreds of perl ports at a time, I try to recheck the /usr/local/lib/perl5 to see if they have installed into 5.14, and recompile them for 5.12. I expect the same problem will be present in the /pkg/ repository? IE there is not a pkg-stable-still-perl-5.12 -v10 pkg-stable-perl-5.14-v10 branching of either the repository, or some way to know that the slew of packages intalling are mismatched in the dependent langauge to be installed. ............................................................................................................................................................................................ Sorry if anything is unclear. No time to rewrite... J. Bouquet _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
