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: 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: 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: 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: 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

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

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

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 to how

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

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

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

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:

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

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

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: 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

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

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

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

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

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

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

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

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: 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

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

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: 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

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

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: 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: 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

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.

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: >

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: 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: 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: 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

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

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

Re: Cannot build glib2

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, Dave Horsfall wrote

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

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

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

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

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

Re: Issue with installing port

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

Re: PortIndex file corrupt?

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: 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

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: 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

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

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: 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

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

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: 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: 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: Unable to install xz

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 "Killed by sign

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?

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

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?

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: 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

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

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

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: 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: 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

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: 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

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

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: Macports user on login screen after migration from old Mac to new Mac

On 2022-8-1 03:27 , Murray Eisenberg wrote: In a message posted already in this list’s archives but not yet appearing in the batched emails I receive from the list, Johsua Root writes: “ … the 'macports’ user… should be as unprivileged as possible, and thus not a member of any groups other

Re: Macports user on login screen after migration from old Mac to new Mac

I don't know what 'macadmin' is. If you mean the 'macports' user, it should be as unprivileged as possible, and thus not a member of any groups other than its own. TBH, the easiest fix is probably to delete the 'macports' user and group, and let them be recreated by the installer during step

Re: Problem with rsync.macports.org mirror?

There hasn't been a base release recently, so that output is completely expected when updating the base sources. There should be some more output involving "---> Updating the ports tree" which, if you have an rsync-based source configured in sources.conf, will run additional rsync commands to

Re: openal-soft fails to build (fwd)

Looks like openal-soft is linking with libsndfile despite not depending on it (and fails because the lack of a declared dependency also means the architectures haven't been made to match.) File a ticket. - Josh

Re: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled:

We have a wiki page with an in-depth explanation of what this warning means: The executive summary for end users is that this is something that the port's maintainer needs to look into, so you can file a ticket about it, but it may

Re: zsh problems MacOS High Sierra

Ryan Schmidt wrote: On May 2, 2022, at 23:49, Sriranga Veeraraghavan wrote: >/I am not a zsh user, but according to zsh's documentation, ~/.zprofile is run only when zsh is used as a login shell, whereas ~/.zshenv is read for nearly every instance of zsh (including scripts):

Re: Corrupted ports.tar file?

Bill Cole wrote: Theory: it's a problem related to running the reclaim from the prompt at the tail end of a selfupdate. Incomplete 'portindex' run perhaps? Good theory. It's likely that when the periodic reclaim run at exit was added, it wasn't considered that it might be running after code

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’. The message could be improved for that case,

Re: Remove "Phantom" Ports

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. They show up when I run "port upgrade installed -u outdated” as follows: Warning: No port

MacPorts 2.7.2 has been released

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

Re: Is this git handling of a problem on my macports-ports fork OK?

Gerben Wierda wrote: But I have been advised a pull is not enough, I should first do a fetch. If you're referring to my private reply, what I said was that a rebase was not enough to bring master up to date with upstream/master, you have to fetch as well. As per the git-pull man page:    

Re: Is this git handling of a problem on my macports-ports fork OK?

On 2022-2-21 10:12 , Gerben Wierda wrote: The time I did a successful pull request, I think I did not first merge my working branch back into my own master, but I did a pull request from my branch from the GitHub website (after having pushed my branch to my own fork) It seemed to me, using

Re: Is this git handling of a problem on my macports-ports fork OK?

On 2022-2-21 10:01 , Gerben Wierda wrote: Stuff like ‘—autostash' and ‘popping the stash’ is gobbledygook to me. git is just something that covers so many complex scenario’s and I am using it so little in those scenarios that most of it is simply out of my understanding.

Re: Understaning rleaves, rdepof

Gerben Wierda wrote: So, how would you go about finding the ports on which what is actually installed depends? E.g.: if I have dovecot+solr8 installed, how would I find out which ports dovecot truly depends on on my system? Is there a reason that information is required apart from

Re: Is this git handling of a problem on my macports-ports fork OK?

Our suggested method of updating a fork is here: Hopefully you're not committing to master locally, as that's just asking for trouble. If you're not, no resetting or force pushing of master should be necessary. If you have

Re: What have I forgotten about specifying which Perl should be /opt/local/bin/perl?

Richard L. Hamilton wrote: >/On Jan 22, 2022, at 11:13, Ryan Schmidt > wrote: />//>/Release date information is not available in MacPorts. Are you proposing that the maintainer of every port should do research to discover the release

Re: port upgrade outdated hangs networking

This is extraordinary .. it presumably is a bug in MacOS. Running MacOS 10.15.7  on MacBook Pro 2016 I am updating various already installed packges in the usual way: sudo port upgrade outdated Everything goes along fine until the software reached gd2. I then see: --->  Fetching archive for

Re: Installation location for python code, tools, etc.

I'm not very experienced with Python, yet, but with regard to MacPorts, I'm trying to understand why when I do a pip3 install, or a direct install from a project tree ie: "python setup.py install" the tool(s) end up in this directory instead of /opt/local/bin|sbin etc:

Re: Building Ruby gems with MacPorts Ruby

It appears that the ruby31 port is missing something, as I can install ruby30, switch to it with sudo port select --set ruby ruby30, then install gems no problem. I just had a look and ruby31 is indeed doing something wrong. Here's the ticket I filed:

Re: [numpy @ bigsur: multithreading]

Maxim Abalenkov wrote: Dear all, I’m looking for guidance please. I would like to make sure, that I use all eight of my CPU cores, when I run Python’s 3.9.9 NumPy on my macOS BigSur 12.1. When I run my NumPy code, I see in ‘htop’, that only one ‘python’ process is running and the core

Re: python ports depend on openssl not in index

SeaQuench wrote: After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to

Re: What is up with perl5.26 on Snow Leo?

Ulrich Wienands wrote: The funny thing is that almost every Macports install seems to want to upgrade this perl5.26; although as far as I can tell my perl5.26 is perfectly fine. So I am forced to use -n for each install to get anything done, which I fond a bit unsettling. Maybe I need to

Re: Does MacPorts need ALL of Xcode?

Ryan Schmidt wrote: Ports that include the xcode portgroup also most probably require Xcode. I would have thought that the xcode 1.0 portgroup would declare "use_xcode yes" somewhere in it, but it doesn't seem to. Maybe that is an oversight. It isn't. Setting build.type to "xcode" also sets

Re: Running MacPorts on macOS 12?

First of all, please be aware of . Sorry for bugging the mailing list with a day-one beta. Trying to run macports with 'sudo port’ errors out with a OS platform mismatch error. Error: Current platform "darwin 21" does not match expected

Re: zathura install but fails with libjson.5.dylib not found

Uli Wienands wrote: I got zathura to install (and it rebuilt even through it seem like there should have been a binary). Then got the pdf -poppler plugin needed to actually decode pdf files. My problem is that zathura does not start up but bombs with libjson-c.5 not found. Her is the error

MacPorts 2.7.1 has been released

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

Re: macports << I run Mojave and can test that build

On 2021-5-24 00:04 , Jeffrey Jay Hayes wrote: Hi Joshua I have Xcode 11.3.1 installed .. I will have to check which version of the SDK is installed The definitive test is whether you get the SQL error shown in the ticket after selfupdating to 2.7.0 from an earlier version. You can check the

  1   2   3   >