Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Michael Newman via macports-users
More of the story. When I got up this morning I found that a couple of scripts that I run overnight had failed with error 127. It seems that the scripts couldn’t find curl. So I checked, and sure enough, curl was missing. No worries, I can reinstall it. And then I wonder, what else is missing?

Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Ryan Schmidt
On Dec 21, 2019, at 23:42, Dave Horsfall wrote: > On Sat, 21 Dec 2019, Ryan Schmidt wrote: > >> And more generally, remove anything you have in /usr/local. >> >> https://trac.macports.org/wiki/FAQ#usrlocal > > I use /usr/local all the time for stuff I either wrote myself That's fine. > or

Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Ryan Schmidt
On Dec 22, 2019, at 04:13, Michael Newman wrote: > When I got up this morning I found that a couple of scripts that I run > overnight had failed with error 127. It seems that the scripts couldn’t find > curl. So I checked, and sure enough, curl was missing. No worries, I can > reinstall it.

Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Dave Horsfall
On Sun, 22 Dec 2019, Ryan Schmidt wrote: I use /usr/local all the time for stuff I either wrote myself That's fine. Thanks :-) or grabbed from somewhere else, without any problems; I reserve /opt/local for MacPorts stuff. If the stuff you grabbed from somewhere else is something like a l

Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Michael Newman via macports-users
On Dec 22, 2019, at 22:04, Ryan Schmidt wrote: > Since reclaim prints a list of the ports it will remove, it seems like it's > up to you to verify that there isn't anything on the list that you want to > keep before confirming the action, and it should not be surprising or scary > to you that

Re: /usr/local/bin/lynx: Bad CPU type in executable

2019-12-22 Thread Andrew Udvare
Sorry, sent to wrong place. Stupid modern mail clients. > On Dec 22, 2019, at 00:42, Dave Horsfall wrote: > > On Sat, 21 Dec 2019, Ryan Schmidt wrote: > >> And more generally, remove anything you have in /usr/local. >> >> https://trac.macports.org/wiki/FAQ#usrlocal > > I use /usr/local all t

Migrating from macOS High SIerra Server dovecot to macOS Mojave macports dovecot

2019-12-22 Thread Gerben Wierda
I am migrating an old dovecot 2.2.30 (macOS High Sierra, macO S Server) to a new server with dovecot 2.3.7 (macOS Mojave, macports). To get the data over, I’m trying to do a reverse backup with doveadm between an old and a new mail server, but failing to do so. I’m trying (from the new server,

Re: Migrating from macOS High SIerra Server dovecot to macOS Mojave macports dovecot

2019-12-22 Thread Steven Smith
I suggest posting a question to the upstream dovecot mailing list too: https://www.dovecot.org/mailing-lists I personally haven’t used doveadm for this task. Also, you’ll want to upgrade your MacPorts dovecot to the latest version. That version has a vulnerability with a reasonably serious CVE