ImageMagick and rust?

Continuing to install all my MacPort ports on the new M2Pro Mini. I’m watching ImageMagick install, and suddenly I’m seeing that rust is being installed. I was not expecting that. Is ImageMagick being ported to rust? All in all I’m pretty impressed with the new machine. In loading MacPorts

Re: Install on Ventura 14.2

Thanks for all the info. I had just updated the new machine from macOS 13.1 to 13.2 before the MacPorts install and the download time was pretty normal. I’m now installing all my ports on the new machine and it seems to be moving along at a good clip (over 200 ports). This new Mac Mini is

Re: Quick Question

t; over my user folder and then nearly all my applications are already installed. > > Which reminds me, you may have some MacPorts application builds in > /Applications/MacPorts > > > > >> On May 7, 2022, at 14:10, James Secan wrote: >> >> Should hav

Re: Quick Question

Should have mentioned I’ve already done that as my final fall-back, but I’d rather be able to get back to exactly where I was vis-a-vis MacPorts if I step on something I shouldn’t have. Jim Seattle, WA > On May 7, 2022, at 11:00 AM, chilli.names...@gmail.com wrote: > > May want to save a copy

Re: curl and openSSL

Thanks. I’ll pass that along to the person from NASA who contacted me. Jim > On Apr 13, 2022, at 1:07 AM, Clemens Lang wrote: > > On Tue, Apr 12, 2022 at 02:16:08PM -0700, James Secan wrote: >> It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on >> the

Re: curl and openSSL

this morning. I’ve sent them everything I know, but have heard nothing back. That was just this morning, so it’s too soon to be getting antsy about a response from them. Jim > On Apr 12, 2022, at 1:19 PM, Clemens Lang wrote: > > Hi, > > On Tue, Apr 12, 2022 at 09:17:03AM -07

curl and openSSL

I switched from using the macOS-supplied curl to MacPorts curl recently, and one of my download scripts which uses curl immediately stopped working. The error message from curl was: curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled From some googling it sounds like

Re: PHP8 and Apple Apache

Thanks. I suspected as much, but wanted to ask first. Jim > On Apr 8, 2022, at 3:58 PM, Ryan Schmidt wrote: > > On Apr 8, 2022, at 17:40, James Secan wrote: > >> I’m just getting started on php, and started by putting php81 on a Big Sur >> system. While

PHP8 and Apple Apache

I’m just getting started on php, and started by putting php81 on a Big Sur system. While looking at how to tweak the configuration on this setup, I find that I need libphp8.0.so. The Apple setup for apache2 has libphp7.so, but nothing for 8. This was not part of the Macports-installed php81

Re: Python

I just recently upgraded one of my machines to macOS 12.3. It has Python 3.8.9 installed in /usr/bin as python3. Being a backsliding miscreant, I have the MacPorts Python 2.7 installed as my default (and 3.10 for testing). Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 17,

Re: port diagnose and xcode

nd that is a >> lowercase L, not an uppercase i). MacPorts will work better with the latter >> ln alias, not the former finder created alias. >> >> -- >> Richard Smith >> xpl...@wak.co.nz >> >> >> >> >>> On 14/03/2022, at 06:

Re: port diagnose and xcode

that confuse port diagnose? (I just checked, and if I click on the Xcode alias it works just as one would expect, so the alias linkage is OK.) Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 12, 2022, at 6:42 PM, Ryan Schmidt wrote: > > On Mar 10, 2022, at 18:40, James Se

Re: port diagnose and xcode

I truly appreciate everyone who maintains things for MP - couldn’t live without this stuff. My initial query was just trying to understand whether ‘port diagnose’ was telling me something I should be concerned about. I think the answer was ‘no’. Jim 3222 NE 89th St Seattle, WA 98115 (206)

Re: Remove "Phantom" Ports

022, at 12:34 AM, Ryan Schmidt wrote: > > On Mar 9, 2022, at 17:13, James Secan wrote: >> >> when I run "port upgrade installed -u outdated” > > This command doesn't make a great deal of sense. You're asking MacPorts to > upgrade the "installed" ports

Re: Remove "Phantom" Ports

were foolish, and five were wise.” > >> On 10 Mar 2022, at 9:13 am, James Secan wrote: >> >> I have a number of apparently old/replaced ports (p5.26-*) that have been >> replaced at some point by their p5.28-* updates that are still in some way >> “alive” on my system

Remove "Phantom" Ports

I have a number of apparently old/replaced ports (p5.26-*) that have been replaced at some point by their p5.28-* updates that are still in some way “alive” on my system. They show up when I run "port upgrade installed -u outdated” as follows: Warning: No port p5.26- found in the index

Variance Handling Question

I’m moving to a Big Sur system, and since I don’t use Xcode for anything I manually download and install the CLI tools by themsleves. I installed v12.5.1 as per the info on the MacPorts wiki (https://trac.macports.org/wiki/XcodeVersionInfo) about which Xcode goes with which macOS. Now the

Variance Handling Question

I have a port installed with a default variant which I want to override. Do I need to uninstall the current port with that variant prior to installing without the variant, or just go on to “port install prog -variant”? Also, from here on do I need to specify in some manner that I’ve disabled a

Update on Big Sur Problems

I just checked the MacPorts wiki page for Big Sur problems and noted that it hasn’t been updated for three months (at least that’s what the wiki page says). With the possibility that new M1 iMacs might show up soon can you provide a short update on where things stand vis-a-vis Big Sur and

Re: sudo port install plplot +fortran

Isn’t the +g95 variant what he needs? Jim 3222 NE 89th St Seattle, WA 98115 (206) 430-0109 > On Mar 31, 2021, at 9:03 AM, Ryan Schmidt wrote: > > On Mar 31, 2021, at 10:53, Brian Miller wrote: > >> When running your program sudo port install plplot +fortran, I do not get >> any results. Can

Re: OS Platform mismatch - while installing stm32flash

Not sure I understand this. Do we now need to “migrate” when we update from x.x.y to x.x.y+1? Has Apple fouled things up that badly? I thought migration was only needed in a major OS upgrade, which I would consider to be from macOS x to maxOS x+1. Jim 3222 NE 89th St Seattle, WA 98115 (206)

Re: Build servers offline due to failed SSD

James, Thanks for the Tower of Hanoi reminder. I used that many (many) years ago with 9" tapes on a Big Iron machine but had forgotten the technique. I’ve been using a FIFO seven-day rotation backup of my main user directory (using CCC), but I’m going to reconfigure it to get the longer

Re: info

I think a large number of us are very interested in the status of ports vis-a-vis both Apple Silicon (M1) and Big Sur. Some sort of simple red-yellow-green status board for ports that have been checked would be very useful. Verified support for the MacPorts codes I use regularly is a major