Re: missing pre-compiled packages

Werner LEMBERG wrote: I wonder why some pre-compiled packages are missing: * ccache – the directory `https://packages.macports.org/ccache/` is empty * git – the directory `https://packages.macports.org/git/`

Re: missing pre-compiled packages

Chris Jones wrote: Binaries aren’t available if the licenses of the port, and its dependencies, do not allow it. To check if this is the case you should refer to the build logs which you can find from the ports site. E.g. https://ports.macports.org/port/git Then check the builds tab. Pick o

Re: Unable to build XV

If someone wanted to update the xv port to use this repo, that would make it compatible with jasper 3 (among other things): - Josh

MacPorts 2.8.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.8.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

Re: py27-pygtk

Lukas Oberhuber wrote: I'm trying to build gimp2.10.32 (I'm the mac maintainer). I've got a custom Portfile, but for the life of me, I can't get gimps autotools (configure.ac) to pick up on `py27-pygtk`. I've set done this: set python_framework${frameworks_dir}/Python.framework/Version

Re: py27-pygtk

On 2022-10-13 03:58 , Lukas Oberhuber wrote: Here is the Portfile: https://gitlab.gnome.org/Infrastructure/gimp-macos-build/-/blob/dee2dcff05491fd5cd455fe1ab4164633720339b/ports/graphics/gimp2/Portfile

Re: python3, tabs, and Terminal

Langer, Stephen A. (Fed) wrote: I don’t know if I have something wrong in my settings or expectations, or if this is a bug. Typing a tab in an Apple Terminal window while using any version of Python3 from MacPorts makes the terminal enter some kind of editing mode, instead of just indenting

Re: python3, tabs, and Terminal

On 2022-10-13 08:05 , Joshua Root wrote: Langer, Stephen A. (Fed) wrote: I don’t know if I have something wrong in my settings or expectations, or if this is a bug.  Typing a tab in an Apple Terminal window while using any version of Python3 from MacPorts makes the terminal enter some kind

MacPorts 2.8.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.8.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 sh

Re: ports.tar corrupt?

Dave Horsfall wrote: I don't know what it is with MacPorts and me, but here's the latest problem; when doing my weekly "port upgrade outdated" I get: Warning: Port cairo not found: Warning: It looks like your PortIndex file forrsync://rsync.macports.org/macports/release/tarballs/port

MacPorts 2.8.0 has been released

The MacPorts Project is happy to announce that the 2.8.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 12 Monterey and all older releases back to Mac OS X 10.4 Tiger (universal

Re: Recommendation for installing Python modules: pip or Macports

Tom Gederberg wrote: It appears that you can either install Python modules (py310-matplotlib, py310-numpy, etc) either directly from MacPorts or you can install pip (for example py30-pip) with MacPorts and then use pip to install the modules. Is there a recommendation on which way to go? The

Re: Unable to install xz

Kenneth Wolcott wrote: Killed by signal: 9 Error: Failed to extract xz: command execution failed Happens with many of the ports. What is wrong with my system? This seems to only happen on Ventura and only when using trace mode. There's a ticket open in Trac, but I don't think anyone has bee

Re: Unable to install xz

wrote: HI Josua; It fails without "-t" as well. Thanks, Ken On Fri, Dec 9, 2022 at 3:59 AM Joshua Root wrote: Kenneth Wolcott wrote: Killed by signal: 9 Error: Failed to extract xz: command execution failed Happens with many of the ports. What is wrong with my system? Th

Re: Unable to install xz

ried to install again, now it works with verbose mode enabled but disabled trace mode. I'm quite confused. Thanks, Ken Wolcott On Fri, Dec 9, 2022 at 6:24 PM Joshua Root wrote: If it fails in exactly the same way without trace mode, i.e. during the extract phase with the message

Re: Unable to install xz

On 2022-12-10 15:03 , Kenneth Wolcott wrote: Is the correct takeaway from this is not to use the trace flag with the port commands for now on MacOS Ventura? Until there's a fix for this issue, yes. - Josh

Re: How to clean up failed build with lots of dependencies?

Does MacPorts have a way to uninstall the dependencies it installed in attempting to build NetSurf (or any complex port that fails to build) without uninstalling the dependencies that were already installed? Will "port reclaim" catch these? Yes, port reclaim will clean up such ports for you.

Re: How to clean up failed build with lots of dependencies?

dbus[2197]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! That is provided by dbus, which should be somewhere in the recursive dependencies of gtk3 I think? - Josh

Re: Finding dependents

Postfix *with no variants* has no dependencies. That's what you will be shown if you run simply 'port deps postfix', because of course you have not specified any variants (and no variants are on by default). I think what's wanted here is: port deps postfix and installed Or if you're more inte

Re: list of packages that are always compiled

Werner LEMBERG wrote: Folks, is there an option to `port` that shows me the names of all packages that must be built from source, and which are not available pre-compiled from 'packages.macports.org'? Or maybe this list is somewhere else, ideally also giving a reason? [My use-case is 'ghosts

Re: list of packages that are always compiled

Richard L. Hamilton wrote: A plausible test case with the first of those (ffmpeg +nonfree) gave the expected result: return code 1, i.e. non-redistributable; and without the +nonfree variant, also gave the expected result of return code 0 (redistributable). That nicely shows that the results

Re: Error: Failed to fetch rust: The requested URL returned error: 404

Marcus Calhoun-Lopez wrote: For reasons that are not entirely clear, the Rust distfiles are not being mirrored. See https://trac.macports.org/ticket/60511 As a workaround, you can download them yourself from https://github.com/MarcusCalhoun-Lopez/rust/releases/tag/1.66.0 and put them in /opt

Re: Error: Failed to fetch rust: The requested URL returned error: 404

On 2022-12-30 04:58 , mcalh...@macports.org wrote: Please forgive my ignorance, but I am not sure how `variant mirror_i386` works. It exists but is *not* default, so how would it be set by the mirroring mechanish? If it is not set, how will `if {[variant_exists mirror_i386] && [variant_isset mi

Re: Error: Failed to fetch rust: The requested URL returned error: 404

, mcalh...@macports.org wrote: Thank you for the explanation. Perhaps this is a question better suited to the development mailing list, but why doesn’t the `universal` variant (which exists) achieve the same goal as the `mirror_i386` variant? -Marcus On Dec 29, 2022, at 7:43 PM, Joshua Root wrote

Re: PortIndex file corrupt?

See . - Josh Today, while doing a port update, I did a port reclaim and received the followed errors (just a subset of the errors are listed). What could cause this and how could I fix it? You haven't run 'sudo p

Re: PortIndex file corrupt?

Tom On Jan 22, 2023, at 1:12 PM, Joshua Root wrote: See <https://lists.macports.org/pipermail/macports-users/2022-October/051512.html>. - Josh Today, while doing a port update, I did a port reclaim and received the followed errors (just a subset of the errors are listed). What could

Re: Issue with installing port

I'm trying to get pandoc to install. The ticket for this is , FWIW. - Josh

MacPorts 2.8.1 has been released

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. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new install

Re: Install on Ventura 14.2

Putting together a new machine (M2Pro Mini, Ventura 14.2) and have hit a snag installing MacPorts. I’ve not installed Xcode on any of my systems for a number of years now, I simply install the appropriate CLI package from the Apple site. In this case, I downloaded and installed v14.2. I then

Re: Install on Ventura 14.2

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 sl

Re: gtk3 on Snow Leopard build failed

...and things had gone so nicely on Snow Leopard for awhile now, until this: :notice:build ---> Building gtk3 :debug:build Executing org.macports.build (gtk3) :info:build ---> Building gtk3 for architecture x86_64 :debug:build setting option build.dir to /opt/local/var/macports/build/_opt_loca

Re: Cannot build glib2

On Mon, 24 Apr 2023, Dave Horsfall wrote: [ Disabling "+universal" ] Yes, that seems to be it; thanks. Now, is there a way to globally disable "universal" without cleaning every port and rebuilding with "-universal"? You don't have to rebuild everything, but there's no getting around rein

Re: Cannot build glib2

have installed that would fail to upgrade due to not supporting the M1 chip? If, so what command would I issue so that I could determine the risk involved of doing that massive upgrade operation? Thanks, Ken Wolcott On Sun, May 28, 2023 at 4:30 PM Joshua Root wrote: On Mon, 24 Apr 2023,

Re: gcc12 fault?

Ken Cunningham wrote: what you see is difficult to explain, unless the PATH changed between the two tests. if 'which gcc' gives /opt/local/bin/gcc then gcc --version should give exactly the same as /opt/local/bin/gcc --version Not necessarily. Shells cache command locations, so if 'gcc'

Re: gcc12 fault?

On 2/6/2023 16:47, Ken Cunningham wrote: You have probably already noted that which and type are both built in to the default zsh on Ventura and as far as I can tell from my testing here give identical results in every case. Both correctly predict the binary that will be executed in every cas

Re: Exa port dependencies

The list below is the current list of build dependencies when I do a port install of "exa +doc+git". The list seems pretty ridiculous though. I just cloned the exa repository and did a cargo build outside macports. None of these dependencies are required. The vast majority of those are dependencie

Re: Exa port dependencies

errors. But I know others feel differently. I know I can set -doc in variants.conf, but then you’re building everything. K On Jun 9, 2023, at 04:01, Joshua Root wrote:  The list below is the current list of build dependencies when I do a port install of "exa +doc+git". The list se

Re: best Xcode version for Mojave?

After updating Xcode while keeping the same OS, should one delete and reinstall all MacPorts packages? No, there's no reason to do that if you have only changed the Xcode version. - Josh

Re: selfupdate fails

% sudo port -v selfupdate ---> Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) Please see . - Josh

Re: Timing of MacPorts Support for New macOS Versions

I’m curious if you’ve revisited the NDA recently, since a skim of the verbiage makes it seem to me that discussing the new OSes should be OK, assuming we don’t review it or post screenshots. Fromhttps://developer.apple.com/support/terms/apple-developer-program-license-agreement/#ADPLA9.1: > Fu

Re: Is there anyone who has successfully migrated Macport to Sonoma?

1)  For 1. below , should I use Xcode15 or older version? Xcode 15 or later is required on Sonoma.   2) Does the following procedure work? Is there anyone who has successfully migrated Macport to Sonoma? I haven't heard of any problems with the procedure that are specific to Sonoma. Individ

Re: Is there anyone who has successfully migrated Macport to Sonoma?

On 9/10/2023 10:34, Tao Zhang wrote: Hi Josh,  Thanks for your helpful comments. One more question:    gfortran and ifort  do not work after upgrading to Sonoma. see below.  1) Should I upgrade to the latest Xcode15 or old Xcode14 to fix this problem?  2)  It is reported that Xcode15 does

Re: FYI: The meld port depends on the p5.36-xml-parser port, which does not exist

FYI: The meld port depends on the p5.36-xml-parser port, which does not exist sudo port -v -s install meld ---> Computing dependencies for meld Error: Dependency 'p5.36-xml-parser' not found. Error: Followhttps://guide.macports.org/#project.tickets if you believe there is a bug. Error:

Re: Help with zef Portfile

raf wrote: The destroot part looks like this: destroot { "${prefix}/bin/rakudo" -I"${worksrcpath}" bin/zef \ --to="inst#${destroot}${prefix}/share/perl6/site" \ install "${worksrcpath}" ln -s "${prefix}/share/perl6/site/bin/zef" "${prefix}/bin/zef"

Re: Help with zef Portfile

raf wrote: I tried just putting "system" before the command but it didn't work. I couldn't find the documentation for tcl's system, System isn't a standard Tcl thing, it's provided by MacPorts. It's closely analogous to system(3). It takes a single string which is passed to 'sh -c'. It's d

Re: Portfile magic / xinstall usage / defect?

The brotli Portfile:https://github.com/macports/macports-ports/blob/master/archivers/brotli/Portfile Contains: post-destroot { xinstall -m 640 {*}[glob ${worksrcpath}/docs/*.1] ${destroot}${prefix}/share/man/man1/ … } However, after port installation, I look in the work directory an

Re: Portfile magic / xinstall usage / defect?

(Moving to macports-dev) Frank Stock wrote: My main focus is .pkg component installers targeting systems where a development toolchain is not realistic. * Do you think it would be possible to use mtree and add_users data to generate code for a postinstall script handling user/group creation

Re: Idiomatic process for handling needed external language modules for which there is no port

How do you do package management on MacPorts for languages which might need modules which MacPorts doesn't have? This problem exists for many languages supported by MacPorts; ie: Perl, Python, Raku, Julia, etc The answer is different for each language. For Python, standard procedure is to u

Re: How to download builds from macports?

Be aware that not all ports are available as binary archives, and some ports rely on post-activate code in the Portfile being run in order to work properly. - Josh PavelTurk wrote: Hi Dave, Thank you very much for your answer. Best regards, Pavel On 12/26/23 5:19 PM, Dave Allured - NOAA A

MacPorts 2.9.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.9.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

Re: Borg backup is complaining about msgpack python package version

On 5/1/2024 23:45, Clemens Lang wrote: For reasons I don't understand, borgbackup wants to allow-list every new version of the msgpack library manually, so every update of the msgpack library breaks borgbackup. It's likely because many python module projects have a culture of very poor backwar

Re: Borg backup is complaining about msgpack python package version

On 6/1/2024 00:07, Clemens Lang wrote: Actually, the relevant commit is https://github.com/borgbackup/borg/commit/39761ebadc9325a7cc7e931144e2709effe8f0f0, and that has been backported to the 1.2 branch of borgbackup and is in 1.2.7, so just make sure you have the latest borgbackup installed and

MacPorts 2.9.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.9.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 sh

MacPorts 2.9.0-rc2 now available for testing

Source code and pkgs for MacPorts 2.9.0-rc2 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 sh

Re: /opt/local/var/macports

Are there negative side-effects to moving this largish subdirectory to an external drive and connecting via soft link? I haven't tried it myself in a while, but as far as I know having it on another volume should work fine. You don't need the link, since this location is configurable as 'port

MacPorts 2.9.0 has been released

The MacPorts Project is happy to announce that the 2.9.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 14 Sonoma and all older releases back to Mac OS X 10.4 Tiger (universal

MacPorts 2.9.1 has been released

The MacPorts Project is pleased to announce the release of version 2.9.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 instal

Re: Port reclaim unexpectedly wants to uninstall a subport, when the top level port is installed

I'm puzzling over some weird "port reclaim" behaviour on one machine. On the problematic machine, I installed py-matplotlib, which correctly installed py312-matplotlib. But, if I run "port reclaim", it wants to uninstall py312-matplotlib as a "Unrequested ports without requested dependents fo

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'. - Josh Kenneth Wolcott wrote: Hi Noam; I do not have gfortran, therefore I must not have gcc? Here is a filtered list of the ports that I have installed that pertain to gcc: gcc12 @12.3.0_4+stdlib_flag (active)

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

Yes. Or as Eric suggested, you can use 'port select' to create a 'gfortran' link. - Josh On 2/3/2024 15:35, Kenneth Wolcott wrote: Should I be using gfortran-mp-13? ls /opt/local/bin | grep fortran arm64-apple-darwin23-gfortran-mp-12 arm64-apple-darwin23-gfortran-mp-13 gfortran-mp-12 gfortran

Re: MacPorts vs. Apple compiler issues, Handle

MacPort installs: $ clang-mp-9.0 --version clang version 9.0.1 Apple: $ clang --version Apple LLVM version 9.1.0 (clang-902.0.39.1) Is there some Apple "trick" or is it the slight compiler difference in version? The version difference is less slight than you might think. Apple clang version n

Re: MacPorts vs. Apple compiler issues, Handle

On 13/3/2024 20:52, Riccardo Mottola wrote: I found a minor patch by Firefox to solve this namespace collision. So for whatever reason Apple's did differently, it now compiles on all compilers. However clang9 generates a crashing executable. I tried on both 10.11 and 10.13. - Apple clang: w

Re: ld: can't write output file for architecture ppc

raf wrote: I've been told that macports needs to be selfupdated at least annually. If it's been too long between selfupdates, it can fail (It did for me once on 10.6.8). You might need to reinstall macports instead of selfupdate. To any expoerts out there, does that sound helpful? I wouldn't

Re: MacPorts vs. Apple compiler issues, Handle

(Moving to macports-dev as it is a better fit for this topic.) On 18/3/2024 22:50, Riccardo Mottola wrote: I will do another compilation reducing the optimization level. GCC has an issue where beyond gcc6 certain optimizations need to be disabled, or AF crashes. Issues that only appear at hig

Re: Library libtdbc used in restore_ports script is unsigned

I recently upgraded from macOS 13.x to macOS 14.3.1 Sonoma and started running the MacPorts Migration process. I got interrupted and did the minor macOS update to macOS 14.4 and tried to run the “restore_ports.tcl” script, which worked for a while but then threw an error about the libtdbc libra

Re: Library libtdbc used in restore_ports script is unsigned

On 21/3/2024 23:33, Eric Gallager wrote: On Thu, Mar 21, 2024 at 12:53 AM Joshua Root wrote: Hopefully we can ship automatic migration in MacPorts base soon and retire restore_ports.tcl. Yeah, please notify me once this happens; I've been reluctant to update from Big Sur just due t

MacPorts 2.9.2 has been released

The MacPorts Project is pleased to announce the release of version 2.9.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 insta

MacPorts 2.9.3 has been released

The MacPorts Project is pleased to announce the release of version 2.9.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 inst

Re: MacPorts 2.9.3 has been released

On 4/4/2024 15:29, Peter West wrote: I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port install. Is this something you’re aware of? It always takes a little time for releases to propagate to the rsync mirrors. 2.9.2 took longer than usual because of some downtime for

Re: MacPorts 2.9.3 has been released

Dave Horsfall wrote: I hadn't got around to installing 2.9.2 yet (I do those admin tasks on Mondays); will 2.9.3 drop cleanly onto 2.9.1? I ask because I got bitten by a Linux upgrade; apparently Debian (if not all of them) requires all intermediate upgrades be performed... We aim for direct

Re: force rebuild a port

Richard L. Hamilton wrote: A URL likehttps://ports.macports.org/port/harfbuzz/builds/ in your browser (but put in the port name you want in place of harfbuzz) will show what if anything is pre-built for that port. Other views are available,

Re: what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?)

what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?) https://www.gnu.org/software/emacs/manual/html_node/emacs/Tags-Tables.html

Re: Macports, pip, and vent

I’m setting up to use a collection of python codes developed by someone else, and to run them I’ll need to use some python modules/packages that aren’t available via MacPorts (nvector, pykml, and stripy). From looking over old posts it appears that the best way to do this is to install all of

Re: xcode not found while building

Ryan Schmidt wrote: On May 26, 2024, at 14:33, Riccardo Mottola wrote: > > Hi, > > MacVim is difficult to build, I want to get a version build on older versions of MacOS. > I am trying to get a version building on 10.11. The current versions and most previous versions don't build, because X

Call for testing: port migrate

A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially buggy pre-release code, and reporting any issues, we would greatly appreciate you giving it a try. The ne

Re: Call for testing: port migrate

. Will let you know the outcome… Ciao Franco On 12 Jun 2024, at 09:00, Joshua Root wrote: A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially

Re: py-numpy 2.0.0

>/Would introducing a py-numpy2 port be a possible solution? />//>/Nils. / Unfortunately, that’s not how python packages work. They need to install into the same directory spaces as to be available for other packages, e.g. /opt/local/Library/Frameworks/Python.framework/Versions/3.12/lib/python

MacPorts 2.10.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.10.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

Re: MacPorts 2.10.0-beta1 now available for testing

Bill Cole wrote: Surprisingly few issues, and I like the way this spat out at the end so I didn't need to read the whole scrollback: ---> Note: Migration finished with errors. The following ports could not be restored: - clang-12 Skipped becuase its dependency llvm-

Re: MacPorts 2.10.0-beta1 now available for testing

Nils Breunese wrote: Bill Cole https://lists.macports.org/mailman/listinfo/macports-users>>: > The following ports were restored with changes: > - openjdk17-zulu > state changed from 'installed' to 'inactive' > - openjdk21-temurin > state changed from 'installed' to 'inactive' > In what circums

MacPorts 2.10.0-beta2 now available for testing

Source code and pkgs for MacPorts 2.10.0-beta2 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.10.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.10.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.10.0 has been released

The MacPorts Project is happy to announce that the 2.10.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 14 Sonoma and all older releases back to Mac OS X 10.5 Leopard (un

Re: port outdated complains after self-update to version 2.10 of MacPorts

port outdated sqlite error: attempt to write a readonly database (8) while executing query: CREATE INDEX registry.snapshot_file_id ON snapshot_files(id) while executing "registry::open $db_path" (procedure "mportinit" line 832) invoked from within "mportinit ui_options global_option

Re: Error upgrading to macport 10.0

hello, It is bizarre! Here is what I get: Error: Current platform "darwin 23" does not match expected platform "darwin 23" Error: Please run 'sudo port migrate' or follow the migration instructions:https://trac.macports.org/wiki/Migration OS platform mismatch while executing "mporti

Re: Platform mismatch error

Hello macports, Still the same error: As the subject says, Platform mismatch error. Some details: Sonoma 14.6.1 on M1 Max 64Gb. I reinstalled completely macports after removing all. And I get the same error. What to do in this case? I suspect you are running your terminal or shell through Rose

Re: Platform mismatch error

On 15/8/2024 02:35, Raoul MEGELAS wrote: Hello Joshua Please see the screenshot of info: It seems to me than open rosetta is unchecked. Another point: The shell is zsh (native on install). I will try your suggestions and report. Bests Raoul Could you please show the output of the following co

Re: Platform mismatch error

On 15/8/2024 17:04, Raoul MEGELAS wrote: On 15 Aug 2024, at 00:48, Joshua Root wrote: Could you please show the output of the following commands in the shell you use to run the port command? sysctl sysctl.proc_translated => 1 echo $SHELL => /bin/zsh lipo -info $SHELL => Architectur

MacPorts 2.10.1 has been released

The MacPorts Project is pleased to announce the release of version 2.10.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 inst

file conflict between qemu and dtc

Kenneth Wolcott wrote: circular dependency between qemu and dtc This is not a circular dependency. Qemu (now) depends on dtc, dtc does not depend on qemu. self-update qemu fails due to conflict with dtc deactivating dtc then trying to update qemu fails because it activates dtc The prev

Re: 2.10.1 macports SQL error on 10.6

on my MacBook (64bit) after upgrading to macports 2.10.1, "port selfupdate" yields: ---> Checking for newer releases of MacPorts MacPorts base version 2.10.1 installed, MacPorts base version 2.10.1 available. ---> MacPorts base is already the latest version ---> Updating the ports tree The p

Re: 2.10.1 macports SQL error on 10.6

On 7/9/2024 02:14, Riccardo Mottola wrote: The first step toward fixing it is to find out which ports' db rows are affected. Try running this: sqlite3 /opt/local/var/macports/registry/registry.db "select * from ports where id=726" sqlite3 /opt/local/var/macports/registry/registry.db "select

Re: 2.10.1 macports SQL error on 10.6

Bill Cole wrote: On 2024-09-06 at 22:25:07 UTC-0400 (Sat, 7 Sep 2024 12:25:07 +1000) Joshua Root https://lists.macports.org/mailman/listinfo/macports-users>> is rumored to have said: [...] > First install the macports.sqlext port. Then run this command (all one > line): >

Re: Doubly Active PHP

When I type ‘port installed’, I notice I have 2 php8* ports (php82 @8.2.23_0 and php83 @8.3.11_0) and both are active. Here is the list of php ports I have: php82 @8.2.23_0+libedit (active) php82-gd @8.2.23_0 (active) php82-mbstring @8.2.23_0 (active) php82-mcrypt @1.0.7_0 (active)

Re: Dependencies/Dependents

bernard.remacle wrote: What is the meaning of ‘rdepends’? (The manual page on port(1) is a little difficult to understand): I understand ‘r’ is the prefix for recursive. What is the difference between ‘rdepends’ and ‘rdependentof’? The rdepends: selector is the recursive version of depends:,

Re: Pseudo-Portname Selectors

When I run port echo depends:vim neovim-qt p5-text-vimcolor py-neovim rails.vim libvmaf gutils-suite-core mpvim neovim-remote nvimpager vim2html vimpager dosfstools (12 ports are listed) But when I run port echo rdepends:vim dosfstools gutils-suite gutils-suite-core gutils-suite-extra libvma

Caution: CLTs appear to be broken on Sequoia

See for the details. It may be a good idea to wait a while to upgrade. If you have to use MacPorts on Sequoia right now, it may work best to install only Xcode 16 without the Command Line Tools. - Josh

MacPorts 2.5.4 has been released

The MacPorts Project is pleased to announce the release of version 2.5.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 installs,

Re: port not installing

Ryan Schmidt wrote: > Your output still does not show the portindex being fetched or generated, and > I don't know why that would happen. In fact selfupdate appears to be exiting > entirely, before printing the output that should always be printed at the > end, as I showed before: That may be <

Re: Mojave and Migration

Michael Newman wrote: > I followed the migration instructions which are found here: > https://trac.macports.org/wiki/Migration > > > That sort of worked, except that some ports didn’t get reinstalled. For > example, neither ImageMagick nor MPlayer were

  1   2   3   >