Thanks for the -v suggestion. I did a 'sudo port -v selfupdate' which updated to 2.3.2, then updated to XCode 6.1 (for 10.9--haven't updated to 10.10 yet) and downloaded the CLI tools. I did a 'sudo port clean --dist postfix' and then 'sudo port -v install postfix +dovecot_sasl+pcre+tls'. Following <https://trac.macports.org/wiki/MisbehavingServers> I also changed my DNS servers from Google back to Cox DNS but I still get:
---> Checksumming postfix-2.11.2.tar.gz Error: Checksum (rmd160) mismatch for postfix-2.11.2.tar.gz Portfile checksum: postfix-2.11.2.tar.gz rmd160 a9ca0d269144e6b45848c4a6c414acdcc3bb896b Distfile checksum: postfix-2.11.2.tar.gz rmd160 c0aeb72ec03c4fb8674523522942e052fd7022d3 Error: Checksum (sha256) mismatch for postfix-2.11.2.tar.gz Portfile checksum: postfix-2.11.2.tar.gz sha256 aa6eba4842457c88c48fb65faeb4fc6496cb3e9ceb9e0ddcb3c13b501821a258 Distfile checksum: postfix-2.11.2.tar.gz sha256 f5e4f9dcdc63139c3f5a3540026d9cc78126ce32caed82e26293cd2cc8888ba3 *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: <https://trac.macports.org/wiki/MisbehavingServers> *** The file has been moved to: /opt/local/var/macports/distfiles/postfix/postfix-2.11.2.tar.gz.html Error: org.macports.checksum for port postfix returned: Unable to verify file checksums Warning: targets not executed for postfix: org.macports.activate org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port postfix for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_postfix/postfix/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port postfix failed Thanks for any pointers. -Terry On Oct 16, 2014, at 2:04 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Wednesday October 15 2014 20:31:04 Brandon Allbery wrote: > > I've learned to run almost all port commands with -v to follow what is > actually being done. It doesn't print everything that ends up in the log, so > it's easier to spot issues in there than "post-mortem" from main.log (or > `port log`). > >> This means it thinks it downloaded it already but it's not there for some >> reason. `sudo port clean postfix` should reset it. (Possibly incorrect >> saved state should be handled better, especially for the early phases.) > > Yes, in this case it shouldn't be very hard to try to revert to the fetch > stage to download the missing file. > Slightly more progress output could be helpful too, between the regular very > terse output and the (overly) verbose mode. Say, the commands being executed, > and the reason for failure (if failure there was). > > R. > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > Terry Barnum digital OutPost http://www.dop.com _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
