ImageMagick and rust?

[James Secan]

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 on 
new machines in the past, there’s always one or two port builds where the fans 
start spinning like a turbofan about to take off.  So far I’ve not heard any 
fan noise from this new machine, and the outer case has been only slightly warm 
at one point (although it’s warming up again on the rust build).

Jim
Seattle, WA

> On Feb 2, 2023, at 9:12 PM, Joshua Root  wrote:
> 
> On 3/2/2023 14:22, Ryan Schmidt wrote:
>> Generating the portindex from scratch takes hours, but just updating a 
>> slightly out-of-date portindex with the latest changes shouldn't take that 
>> long. Also, the slightly outdated portindex on the public rsync servers 
>> should correspond exactly to their slightly outdated collection of ports so 
>> no updating should be needed.
> 
> I was avoiding going into too much detail before, but depending on the exact 
> timing of the power going out and the mirror syncing from the origin, it's 
> possible that the indices for some subset of OS versions could be one update 
> behind the ports tree. But I haven't checked whether that's actually the case.
> 
> - Josh

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Ryan Schmidt]

On Feb 5, 2023, at 20:40, Alan Needleman wrote:
> On Feb 5, 2023, at 8:30 PM, Ryan Schmidt wrote:
>> Please run:
>> 
>> sudo port clean poly2tri-c
>> sudo port selfupdate
>> 
>> Then try again. If it fails again, please attach the new main.log file to 
>> the ticket.
> 
> That did it! Works now. Many thanks. Much appreciated!

Great! Yes, remember to run "sudo port selfupdate" or "sudo port sync" anytime 
you want to receive any changes that we've committed. It takes a little while 
after we commit a change before it is published to the rsync server, but 
typically if you wait at least an hour after we commit something that should be 
enough time.

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Alan Needleman]

Ryan:

That did it! Works now. Many thanks. Much appreciated!

Best regards.

Alan




> On Feb 5, 2023, at 8:30 PM, Ryan Schmidt  wrote:
> 
> On Feb 5, 2023, at 20:27, Alan Needleman wrote:
>> 
>> On Feb 5, 2023, at 6:32 PM, Ryan Schmidt wrote:
>> 
>>> On Feb 5, 2023, at 16:01, Alan Needleman wrote:
 
 I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports 
 installation. All ports installed and seem to be working fine except for 
 poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to 
 “installing patches”  and hangs so I kill the process (I haven’t seen any 
 error message in the log file).
>>> 
>>> This was filed here:
>>> 
>>> https://trac.macports.org/ticket/66851
>>> 
>>> I hope I've fixed it.
>> 
>> Ryan:
>> 
>> Sorry. Still hangs.
>> 
>> --->  Computing dependencies for gimp2
>> The following dependencies will be installed:  
>> gegl
>> glib-networking
>> poly2tri-c
>> Continue? [Y/n]:  --->  Fetching archive for poly2tri-c
>> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
>> https://packages.macports.org/poly2tri-c
>> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
>> https://ywg.ca.packages.macports.org/mirror/macports/packages/poly2tri-c
>> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
>> http://mirror.fcix.net/macports/packages/poly2tri-c
>> --->  Applying patches to poly2tri-c
> 
> Please run:
> 
> sudo port clean poly2tri-c
> sudo port selfupdate
> 
> Then try again. If it fails again, please attach the new main.log file to the 
> ticket.
> 

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Ryan Schmidt]

On Feb 5, 2023, at 20:27, Alan Needleman wrote:
> 
> On Feb 5, 2023, at 6:32 PM, Ryan Schmidt wrote:
> 
>> On Feb 5, 2023, at 16:01, Alan Needleman wrote:
>>> 
>>> I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports 
>>> installation. All ports installed and seem to be working fine except for 
>>> poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to 
>>> “installing patches”  and hangs so I kill the process (I haven’t seen any 
>>> error message in the log file).
>> 
>> This was filed here:
>> 
>> https://trac.macports.org/ticket/66851
>> 
>> I hope I've fixed it.
> 
> Ryan:
> 
> Sorry. Still hangs.
> 
> --->  Computing dependencies for gimp2
> The following dependencies will be installed:  
> gegl
> glib-networking
> poly2tri-c
> Continue? [Y/n]:  --->  Fetching archive for poly2tri-c
> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
> https://packages.macports.org/poly2tri-c
> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
> https://ywg.ca.packages.macports.org/mirror/macports/packages/poly2tri-c
> --->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
> http://mirror.fcix.net/macports/packages/poly2tri-c
> --->  Applying patches to poly2tri-c

Please run:

sudo port clean poly2tri-c
sudo port selfupdate

Then try again. If it fails again, please attach the new main.log file to the 
ticket.

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Alan Needleman]

Ryan:

Sorry. Still hangs.

 --->  Computing dependencies for gimp2
The following dependencies will be installed:  
 gegl
 glib-networking
 poly2tri-c
Continue? [Y/n]:  --->  Fetching archive for poly2tri-c
--->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
https://packages.macports.org/poly2tri-c
--->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/poly2tri-c
--->  Attempting to fetch poly2tri-c-0.1.0_0.darwin_22.arm64.tbz2 from 
http://mirror.fcix.net/macports/packages/poly2tri-c
--->  Applying patches to poly2tri-c

Also (just to show the rest of the installation is ok),

--->  Computing dependencies for gimp2
The following dependencies will be installed:   
 gegl
 glib-networking
 poly2tri-c
Continue? [Y/n]: n
--->  Scanning binaries for linking errors
--->  No broken files found.  
--->  No broken ports found.

Best wishes.

Alan


> On Feb 5, 2023, at 6:32 PM, Ryan Schmidt  wrote:
> 
> On Feb 5, 2023, at 16:01, Alan Needleman wrote:
>> 
>> I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports 
>> installation. All ports installed and seem to be working fine except for 
>> poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to 
>> “installing patches”  and hangs so I kill the process (I haven’t seen any 
>> error message in the log file).
> 
> This was filed here:
> 
> https://trac.macports.org/ticket/66851
> 
> I hope I've fixed it.
> 
> 
>> On the Macports website listing for poly2tri-c  there is a “?” for Ventura 
>> (arm64) so this may be a known issue.
> 
> The arm64 Ventura build machine has not yet been set up so there will be a 
> "?" on the ports web site for all ports on arm64 Ventura.
> 

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Ryan Schmidt]

On Feb 5, 2023, at 16:01, Alan Needleman wrote:
> 
> I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports 
> installation. All ports installed and seem to be working fine except for 
> poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to “installing 
> patches”  and hangs so I kill the process (I haven’t seen any error message 
> in the log file).

This was filed here:

https://trac.macports.org/ticket/66851

I hope I've fixed it.


> On the Macports website listing for poly2tri-c  there is a “?” for Ventura 
> (arm64) so this may be a known issue.

The arm64 Ventura build machine has not yet been set up so there will be a "?" 
on the ports web site for all ports on arm64 Ventura.

Re: mac and ssl/openssl

[Ryan Schmidt]

On Feb 5, 2023, at 16:08, Riccardo Mottola wrote:

> Old versions of macs which I use, like 10.4 up to 10.7 have openssl and ssl.h
> 
> I tested that 10.13 doesn't have, so GNUMail doesn't compile.
> 
> Did Mac switch to a different ssl version and/or changed the location of it? 
> with which version?
> Do you have experience supporting it?
> I'd like to keep GNUMail working on vintage macs, but also support newer ones.

https://web.archive.org/web/20221129062249/http://lists.apple.com/archives/macnetworkprog/2015/Jun/msg00025.html

Re: Getting errors when upgrading to Ventura

[Ryan Schmidt]

On Feb 5, 2023, at 16:25, Mannucci, Anthony J wrote:

> I recently upgraded to Ventura and I am following the migration procedure.
>  
> I updated Xcode etc. When restoring ports, I am getting errors associated 
> with perl and llvm. Should I file a bug report?
>  
> Here is a list of error messages before the process quit:
> 223:Error: Failed to configure perl5.16: configure failure: command execution 
> failed
> 224:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.16/main.log
>  for details.
> 231:Error: Failed to configure perl5.22: configure failure: command execution 
> failed
> 232:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.22/main.log
>  for details.
> 239:Error: Failed to configure perl5.24: configure failure: command execution 
> failed
> 240:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.24/main.log
>  for details.
> 247:Error: Failed to configure perl5.26: configure failure: command execution 
> failed
> 248:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.26/main.log
>  for details.
> 626:Error: Failed to configure llvm-3.3: consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/build/config.log
> 627:Error: Failed to configure llvm-3.3: configure failure: command execution 
> failed
> 628:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/main.log
>  for details.
> 1024:Error: Failed to build cctools: command execution failed
> 1025:Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log
>  for details.
> 1026:Error: Requested variants "+xcode" do not match those the build was 
> started with: "+llvm10".
> 1027:Error: Please use the same variants again, or run 'port clean cctools' 
> first to remove the existing partially completed build.
>  
> Errors associated w/ perl seem to be like:
> 1080::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404
> 1082::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404
> 1084::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404
> 1172::error:configure Failed to configure perl5.26: configure failure: 
> command execution failed
> 1173::debug:configure Error code: NONE
> 1177::error:configure See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.26/main.log
>  for details.
>  
> Errors associated with llvm are like:
> 240::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404
> 242::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404
> 244::debug:archivefetch Fetching archive failed: The requested URL returned 
> error: 404

Each failure will need individual investigation by reading the main.log file.

404 errors when fetching archives are not a problem. When MacPorts cannot fetch 
an archive, it builds from source. If *that* fails, *that's* a problem.

Some of the ports you mentioned, like perl5.16 and llvm-3.3, are ancient and 
may not be buildable on Ventura, or even if they build they may have bugs that 
were fixed a long, long time ago. Use newer versions of these ports, for 
example perl5.34 and llvm-15.

The cctools failure is explained in the error message. Clean the port and try 
again. Probably you want to run "sudo port install cctools" without specifying 
any variant, to let MacPorts pick the best variant for your system, if indeed 
you need to install the port at all. If you don't know that you need the port, 
don't install it. MacPorts will install it if it's needed as a dependency later.

You should probably read through the list of ports in myports.txt and remove 
any that you do not explicitly want rather than just reinstalling all the ports 
you had on your old system, some of which may have at one point been needed as 
a dependency of something but which aren't anymore.

Getting errors when upgrading to Ventura

[Mannucci, Anthony J (US 3350) via macports-users]

I recently upgraded to Ventura and I am following the migration procedure.

I updated Xcode etc. When restoring ports, I am getting errors associated with 
perl and llvm. Should I file a bug report?

Here is a list of error messages before the process quit:
223:Error: Failed to configure perl5.16: configure failure: command execution 
failed
224:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.16/main.log
 for details.
231:Error: Failed to configure perl5.22: configure failure: command execution 
failed
232:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.22/main.log
 for details.
239:Error: Failed to configure perl5.24: configure failure: command execution 
failed
240:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.24/main.log
 for details.
247:Error: Failed to configure perl5.26: configure failure: command execution 
failed
248:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.26/main.log
 for details.
626:Error: Failed to configure llvm-3.3: consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/build/config.log
627:Error: Failed to configure llvm-3.3: configure failure: command execution 
failed
628:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/main.log
 for details.
1024:Error: Failed to build cctools: command execution failed
1025:Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log
 for details.
1026:Error: Requested variants "+xcode" do not match those the build was 
started with: "+llvm10".
1027:Error: Please use the same variants again, or run 'port clean cctools' 
first to remove the existing partially completed build.

Errors associated w/ perl seem to be like:
1080::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404
1082::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404
1084::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404
1172::error:configure Failed to configure perl5.26: configure failure: command 
execution failed
1173::debug:configure Error code: NONE
1177::error:configure See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5/perl5.26/main.log
 for details.

Errors associated with llvm are like:
240::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404
242::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404
244::debug:archivefetch Fetching archive failed: The requested URL returned 
error: 404

-Tony

--
Tony Mannucci
Deputy Section Manager, Tracking Systems and Applications (335)
 Mail-Stop 238-600, Tel > (818) 354-1699
 Jet Propulsion Laboratory,Fax > (818) 393-5115
 California Institute of Technology   Email > 
anthony.j.mannu...@jpl.nasa.gov
 4800 Oak Grove Drive
https://communicationstrackingradar.jpl.nasa.gov/sections/sec-335/
 Pasadena, CA 91109

mac and ssl/openssl

[Riccardo Mottola via macports-users]

Hi all!

tangent question for mac development and different MacOS versions.

Old versions of macs which I use, like 10.4 up to 10.7 have openssl and 
ssl.h


I tested that 10.13 doesn't have, so GNUMail doesn't compile.

Did Mac switch to a different ssl version and/or changed the location of 
it? with which version?

Do you have experience supporting it?
I'd like to keep GNUMail working on vintage macs, but also support newer 
ones.


Riccardo

poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

[Alan Needleman]

I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports 
installation. All ports installed and seem to be working fine except for 
poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to “installing 
patches”  and hangs so I kill the process (I haven’t seen any error message in 
the log file). On the Macports website listing for poly2tri-c  there is a “?” 
for Ventura (arm64) so this may be a known issue. The problem is that 
poly2tri-c  is needed for gimp2. There is a working  native Apple Silicon gimp2 
app for  Ventura on the Gimp website so it is not urgent but I did have the 
Macports gimp2 working on Monterey.

Best to all.

Alan

Re: MacPorts 2.8.1 has been released

[Will Senn]

On 2/5/23 1:12 PM, Dave Horsfall wrote:

On Tue, 31 Jan 2023, Joshua Root wrote:


The MacPorts Project is pleased to announce the release of version
2.8.1. This is a bugfix release with small changes only. See the
ChangeLog [1] for the list of changes.

Smooth as a baby's bottom on High Sierra; many thanks.

-- Dave

Same here, on Mojave!

dia port (from source) fails to install on Ventura 13.1 (with M1 chip)

[Kenneth Wolcott]

HI;

  The dia port (from source) fails to install on Ventura 13.1 (with M1 chip).

  The compressed install log file is attached.

Thanks,
Ken Wolcott


install_dia_main.log.bz2
Description: BZip2 compressed data

Re: MacPorts 2.8.1 has been released

[Dave Horsfall]

On Tue, 31 Jan 2023, Joshua Root wrote:

> The MacPorts Project is pleased to announce the release of version 
> 2.8.1. This is a bugfix release with small changes only. See the 
> ChangeLog [1] for the list of changes.

Smooth as a baby's bottom on High Sierra; many thanks.

-- Dave