MacPorts 2.10.2 has been released

The MacPorts Project is pleased to announce the release of version 2.10.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new ins

Re: failed migration to Sequoia

Artemio González López wrote: Yesterday I tried to migrate my Sonoma MacPorts installation to the newly installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure, i.e., sudo port migrate The procedure produced the following errors: <...> It seems that there is currently a pr

Fix for CLTs C++ issue

For those who haven't been following the ticket, we've determined that the problem is caused by the CLTs installer not deleting everything left over from older versions when updating, combined with some unfortunate logic in how clang++ constructs its include paths. Fresh CLTs installations are

Re: failed migration to Sequoia

On 19/9/2024 18:30, Artemio González López wrote: Thanks, Josh! In fact, I renamed the /Library/Developer/CommandLineTools and got most of my ports to succesfully build after executing “sudo port restore —last”. Unfortunately, there is still a problem with libgcc14 that prevents emacs-app to

Re: Foiled Again

Michael Newman wrote: This morning I upgraded my 2019 iMac to Sequoia and then did a port migrate. I think everything went OK, except for the following: The following ports could not be restored: - nbsmtp Failed: Unable to execute target 'activate' for port nbsmtp - see its

Re: Foiled Again

On 2/10/2024 15:06, Michael Newman wrote: I did my best with the bug report. I had no idea what to put in the comments section. The Description field is for any additional information or analysis that is not present in the log and too long to put in the Summary. If you don't have anything to

MacPorts 2.10.2 Sonoma installer updated

Unfortunately, the MacPorts 2.10.2 installer for macOS 14 Sonoma contained a misconfiguration that can cause port builds to fail. Other macOS versions are not affected. A new build of the installer has been uploaded. The version number is unchanged because it is built from exactly the same sou

Re: How to Reinstall postgresql96 for Data Migration; Was: Time to delete old PostgreSQL from MacPorts?

The EOL versions should definitely be deprecated, but removal was only on the table because no one was willing to do the work to backport the patches to get them building again. If you are, then great! The old versions are indeed useful to have available for the purpose of getting your data int

Re: Should preferred_hosts honour relative ordering within the line?

Normally, MacPorts tries hosts in ping order. Without having looked at the code, I assume the same applies to preferred hosts: that they are tried in ping order, before any of the other hosts. The list of download URLs is indeed sorted by host ping time. A stable sort algorithm is used, so ho

Security issue in MacPorts 2.10.4 and older

MacPorts versions 2.10.4 and older contain a vulnerability that can allow a compromised rsync mirror to add Portfiles to the synced ports tree, thus allowing arbitrary code to be executed when those Portfiles are parsed. (Note that we currently have no reason to believe that any of our mirrors

Re: Problem after upgrade to 2.10.5

On 1/2/2025 00:16, Jurgen Defurne wrote: It is actually 'port -df selfupdate' (described at the end of the ticket) that you need to do. It seems that this starts something more elaborate, because there is also a whole of building going on. It's no more elaborate than a normal selfupdate when t

Re: Problem after upgrade to 2.10.5

On 31/1/2025 22:58, Riccardo Mottola wrote: I get the stupid error right while executing selfupdate. I issued it several times, I always got the error with the same ID as duplicate. If issue outdated, instead, I get consistently another ID as duplicate port outdated even shows a couple of ports

Re: Failed to activate imath

---> Activating imath @3.1.12_0 Error: Failed to activate imath: The following ports have active files that conflict with imath's: ilmbase @2.3.0_1 /opt/local/lib/libImath.dylib This is . According to one of the imath maintainers in the ticket, it on

Re: Failed to activate imath

On 11/2/2025 01:10, Christoph Kukulies wrote: I ran the sudo port upgrade, and it failed: Well, qemu failed; the other 726 ports including imath and openexr succeeded. :) As usual, please file a ticket if there isn't already one for the qemu build failure that you're seeing. - Josh

Re: Failed to activate imath

>/Am 09.02.2025 um 05:40 schrieb Joshua Root <https://lists.macports.org/mailman/listinfo/macports-users>>: />//>/Running 'sudo port migrate' may be the most reliable way to upgrade a very old installation./ Thanks. This will probably a monster job, re-installin

MacPorts 2.10.5 has been released

The MacPorts Project is pleased to announce the release of version 2.10.5. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: mpkg build with Apple Silicon

Hello, We've build a few packages using the mpkg command on an Apple Silicon Mac. When we want to install any of these packages, Rosetta 2 installation is required. We want to avoid using Rosseta 2, if there a way of forcing the architecture to arm64 when building a mpkg? Unfortunately Apple's

Re: Problem after upgrade to 2.10.5

Riccardo Mottola wrote: during/after upgrade I got this: $ port outdated Error: process_cmd failed: sqlite error: another row available (100) while executing query: SELECT cxx_stdlib FROM registry.ports WHERE id=1184 Jurgen Defurne wrote: Yesterday evening I upgraded to macports 2.10.5. After

Re: Transferring Port Across Systems

Anthony M. Agelastos wrote: I have 2 macOS systems on ARM64. There are some Ports I'm able to build on System A that I cannot on System B. I would like to transfer the build from A to B. This doesn't happen often and is only for a few Ports. So, setting up a binary mirror and all of that is sign

Re: Ventura Installation fails in /opt/ports

Something is looking for '/opt/local/libexec/macports/lib/sqlite3.44.2/libsqlite3.44.2.dylib’ , but that looks like a hardcoded path, because I’m not installing into /opt/local. That dylib is present in /opt/ports. From the backtrace, it's Pextlib. Confirm with `otool -L /opt/ports/libexec/

Re: which texlive bit to get a particular package

I have once again lost track of the list of which packages are installed with various texlive ports. In particular, I expected that texlive-math-science would contain esint.sty. It apparently does not. How now I need to figure out what else I need to install to get that package? I thought

MacPorts 2.10.7 has been released

The MacPorts Project is pleased to announce the release of version 2.10.7. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For ne

MacPorts 2.10.6 has been released

The MacPorts Project is pleased to announce the release of version 2.10.6. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: py39-pdm-backend fails to build in Sonoma 14.7.6

Since a few days ago the py39-pdm-backend package fails to build under Sonoma 14.7.6 using Macports 2.10.5 or 2.10.6 :/debug:build system: cd /"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-pdm-backend/py39-pdm-backend/

Re: flang-20 port is building VERY SLOWLY, "memory pressure" (Activity monitor) is very high

Building flang has always been CPU+RAM intensive, but it looks like it is thrashing now. Is there a way to make it go single threaded? I have like ten "stuck" clang processes... A better solution would be to set build.mem_per_job to something higher in the port. It defaults to 1024 (MB) an

Re: What's up with Macports' DNS?

Happened twice now (but works some time later): mackie$ sudo port -v selfupdate ---> Checking for newer releases of MacPorts % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft

Re: selfupdate failure: rsync: [sender] change_dir "/release/tarballs" (in macports) failed: Permission denied (13)

Dave Horsfall wrote: On Fri, 30 May 2025, Clemens Lang wrote: >/No, see https://trac.macports.org/ticket/72556. / Hmmm; that could explain my own problem... Probably not, since the problem in the ticket only existed for a few hours and was not related to DNS. - Josh

Re: MacPorts 2.11.0-beta1 now available for testing

Well, it's been a week and no bugs have been reported against the beta. Either this is a flawless release with no regressions, or we could use some more testing. :) Historically there have usually been a few issues that get reported right after the final release, so it would be nice to catch t

Re: Dovecot will not compile (Sonoma 14.7.5, MacPorts 2.10.7, Intel). cstddef.h not found.

On 26/6/2025 01:57, Gerben Wierda wrote: :info:build /opt/local/include/CLucene/SharedHeader.h:57:10: fatal error: 'cstddef' file not found :info:build57 | #include //need this for wchar_t, size_t, NULL :info:build | ^ Is there something I can do to fix this?

MacPorts 2.11.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.11.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

MacPorts 2.11.0 has been released

The MacPorts Project is happy to announce that the 2.11.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers [1] for macOS 15 Sequoia and all older releases back to Mac OS X 10.5 Leopard

MacPorts 2.11.1 has been released

The MacPorts Project is pleased to announce the release of version 2.11.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new ins

MacPorts 2.11.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.11.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no s

MacPorts 2.11.2 has been released

The MacPorts Project is pleased to announce the release of version 2.11.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new in

MacPorts 2.11.3 has been released

The MacPorts Project is pleased to announce the release of version 2.11.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new i

port mpkg error (was: ditem_95)

I'm trying to create a custom Barman 3.14.1 mpkg using the latest MacPorts version (macOS - Apple Silicon). When building I get the following error: Error: Failed to mpkg barman: can't read "ditem_95 6.5 0": no such variable Checking the logs it seems to be caused by: debug:mpkg Sourcing Por

Re: Failed to build wxWidgets-3.2

Running my weekly update, I get: Error: Failed to destroot wxWidgets-3.2: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_aarnet.au.rsync.macports.org_pub_macports_graphics_wxWidgets-3.2/wxWidgets-3.2/main.log for details. Error: Prob

Re: port mpkg error

H. D. Saviolaan 8 1700 Dilbeek T. : 00 32 02 466 5000 On 24 Jul 2025, at 20:43, Joshua Root wrote: I'm trying to create a custom Barman 3.14.1 mpkg using the latest MacPorts version (macOS - Apple Silicon). When building I get the following error: Error:

MacPorts 2.11.4 has been released

The MacPorts Project is pleased to announce the release of version 2.11.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: Definitions out of date?

Update to 2.11.4 just now, and ran "port upgrade outdated: Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. Nothing to upgrade. ---> Scanning binaries for linking errors ---> No broken files found.

<    1   2   3   4