Re: failed migration to Sequoia

On 21/9/2024 03:36, Artemio González López wrote: I just ran port selfupdate, but the only outdated port it found is xorg- libXi  (which I updated). I guess it is not worth to give port restore — last another try, since the problematic por was libgcc14, which hasn’t¡t been updated. Am I right

Re: During the octave port install from source I noticed that a fortran compiler was requested and not found

Thank you, that helps a lot in my understanding of MacPorts, fortran and ports requiring (or should be requiring) fortran. I'll uninstall the ports that were successfully installed prior to encountering the perl circular depedency hell and log those unsuccessful searches for a fortran compiler. T

Re: During the octave port install from source I noticed that a fortran compiler was requested and not found

Hi The LLVM fortran compilers (flang) are very much ‘work in progress’ and far from being ready for any production work. For that reason no port build will currently consider them as a viable fortran compiler. They are provided ‘as is’ to allow testing etc. Any port build that does require a

Re: several ports cannot be installed due to a Perl circular dependency hell...

ld break this > circular dependency hell, then please show me which one (or ones) will > solve the problem. I suppose that I could try to list all my desired > ports as requested then uninstall everything and re-install? That's older migration method (and would be a reasonable thing to try). -- Daniel J. Luke

Re: several ports cannot be installed due to a Perl circular dependency hell...

that I could try to list all my desired ports as requested then uninstall everything and re-install? Thanks, Ken Wolcott On Fri, Sep 20, 2024 at 10:37 AM Gilles Caulier wrote: > > Hi, > > I faced the same problem while installing the huge list of > dependencies for the digiKam pro

Re: rust port complaint at time of selfupdate

You should learn to check trac tickets. Or just check https://trac.macports.org/wiki/SequoiaProblems for the known problems. R will not work on macOS15 until its maintainers bumps ints gcc and clang versions to those support on this OS https://trac.macports.org/ticket/70799 Chris On 20 S

Re: rust port complaint at time of selfupdate

Hi; So how do I fix the problem? I have a similar problem with R now... Failed to parse file R/R-pbdMPI/Portfile: can't read "mpi_port": no such variable Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.

Re: failed migration to Sequoia

> On 20 Sep 2024, at 01:07, Joshua Root wrote: > >> >> Unfortunately, after executing supo port restore —last I got exactly the >> same error as before (libgcc14 and lib sodium failed, and cause several >> ports, like emacs-app, not to compile). I do not know what else to do. Could >> execut

Re: several ports cannot be installed due to a Perl circular dependency hell...

Hi, I faced the same problem while installing the huge list of dependencies for the digiKam project under Intel and arm64 targets. The main problem arrives when Perl is used to compile Qt in my case but not only. Look these rules in my install script : https://invent.kde.org/graphics/digikam/-/b

Re: failed migration to Sequoia

On 20/9/2024 08:27, Artemio González López wrote: Before reading your message, I deleted the directory /Library/Developer/ CommandLineTools and reinstalled the Command Tools for Xcode 16 (which I also have installed) from scratch using the dmg at the Developer website. This should be equivale

Re: failed migration to Sequoia

> On 19 Sep 2024, at 20:46, Joshua Root wrote: > > 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

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: failed migration to Sequoia

> On Sep 18, 2024, at 5:29 PM, Joshua Root wrote: > > 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 procedu

Re: what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

Hi Joshua; That helps greatly; I'll make that change in macports.conf. But, is there a way to prevent x86_64 and amd64 ports from being installed? If it is a port that I want but it does not support arm64, I think I'd rather skip it if at all possible. Thanks, Ken Wolcott On Wed, Sep 18, 20

Re: what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

Clearing universal_archs in macports.conf will disable universal entirely. Some ports that don't support arm64 may still install as x86_64 if they don't require any universal dependencies. - Josh

Re: rust port complaint at time of selfupdate

I think that the `rust-bootstrap` port is supposed to track the `rust` port and only the `rust` port has been updated recently. -a On Wed, Sep 18, 2024 at 6:22 PM Kenneth Wolcott wrote: > Hi; > > Just did a selfupdate, there's an issue with the rust port... > > Creating port index in > /

Re: my ports are screwed up after OS upgrade and port migrate; some things are fine, many are not

On Sep 17, 2024, at 11:12, Mark E Anderson wrote:Make sure you update command line tools.Make sure you *uninstall* the command line tools. Having them installed causes ports to fail to build on Sequoia. #70750 (MacOS Sequoia: C++ headers are not found with CLTs installed)trac.macports.org

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

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: > >Migration finished with e

Re: my ports are screwed up after OS upgrade and port migrate; some things are fine, many are not

On Sep 17, 2024, at 1:34 AM, Kenneth Wolcott wrote: > I tried many times to install, uninstall, install, upgrade various > ports. Many fail, (especially low-level dependencies that most ports > require), looks like the tools are not visible... What do the errors look like? I had to do `sudo xco

Re: Caution: CLTs appear to be broken on Sequoia

Hi Mark, hi everybody, mine also. Besides the fact, that on port I'm using (psutils) doesn't. But I upgraded Xcode plus CLI tools as recommended. Best Fausto Am Tue, Sep 17, 2024 at 12:13:39PM -0400 schrieb Mark E Anderson: > Mine have been working - but I remember needing an update from Appl

Re: Caution: CLTs appear to be broken on Sequoia

Mine have been working - but I remember needing an update from Apple - also, I just got one yesterday, which means I was never using them, I was using Xcode maybe? —Mark On Tue, Sep 17, 2024, at 8:30 AM, Joshua Root wrote: > See for the details

Re: my ports are screwed up after OS upgrade and port migrate; some things are fine, many are not

t; Sequoia is very early (and MacPorts support for it may be incomplete or > minimally tested, as the Xcode detection issues suggest). I usually run most > of my systems at least one OS major release behind for at least a few months, > or only run them earlier or run betas in an expendable (

Re: my ports are screwed up after OS upgrade and port migrate; some things are fine, many are not

Sequoia is very early (and MacPorts support for it may be incomplete or minimally tested, as the Xcode detection issues suggest). I usually run most of my systems at least one OS major release behind for at least a few months, or only run them earlier or run betas in an expendable (just re

Re: GDB fails to build on High Sierra (fwd)

-- Date: Fri, 6 Sep 2024 07:54:18 +1000 (AEST) From: Dave Horsfall To: macports-users Subject: GDB fails to build on High Sierra (fwd) Re-submitted, this time with a compressed main.log... -- Dave -- Forwarded message -- Date: Fri, 6 Sep 2024 07:40:10 +1000 (AEST) From: Dave

Re: building seamonkey - python setup - imp module

Hi, Bill Cole wrote: But this was easy to find:https://docs.python.org/3.11/library/imp.html and it seems to indicate that you should backrev your Python to 3.11 at most. seamonkey dev guys told me indeed 3.12 is not compatible, I selected python 3.11 and compilation begins... fails now in

Re: 2.10.1 macports SQL error on 10.6

Hi Joshua, Joshua Root wrote: > > First install the macports.sqlext port. Then run this command (all one > line): > > sqlite3 /opt/local/var/macports/registry/registry.db ".load > /opt/local/lib/sqlite3/macports.sqlext" "PRAGMA integrity_check" > > That will check that the database is internall

Re: asymptote port install is hanging, nothing seems amiss, puzzling

Hmmm... 1. sudo port -v -s install asymptote 2. it hangs... 3. killed the hanging command 4. sudo port clean asymptote 5. sudo port -v -s install asymptote Works fine... Interesting... Thanks, Ken Wolcott On Thu, Sep 12, 2024 at 12:06 PM Kenneth Wolcott wrote: > > Hi; > > The asymptote

Re: Status on macOS Sequoia? (v.15)

Yeah, I've done this. I recommend it, It rules - APFS is a very cool file system. —Mark On Thu, Sep 12, 2024, at 6:03 PM, Nils Breunese wrote: > You can install multiple versions of macOS on a single computer: > https://support.apple.com/en-us/118282 > > Nils. > > > Op 12 sep 2024, om 22:45 h

Re: Status on macOS Sequoia? (v.15)

You can install multiple versions of macOS on a single computer: https://support.apple.com/en-us/118282 Nils. > Op 12 sep 2024, om 22:45 heeft André-John Mas het > volgende geschreven: > > If you are worried then best wait for a .1 release, that way anything that > didn’t get in QA will be f

Re: Status on macOS Sequoia? (v.15)

There are a number of tickets out on the Trac - I've been running it for a while and haven't had too many issues, but it won't be smooth exactly. Also, I don't think many people are out there testing so I'm sure there are hidden issues. qt5 and qt6 come to mind, but I have a workaround. There ar

Re: Status on macOS Sequoia? (v.15)

Maybe wait until the NDA is lifted and then ask the questions you need to? Waiting until the 16th shouldn’t be a huge delay? André-John Sent from my phone. Envoyé depuis mon téléphone. > On 12 Sep 2024, at 16:53, g...@iltofa.com wrote: > > I’m not worried by Sequoia in itself, I’ve used .0s

Re: A deep clone of a MacPorts setup (especially the uid/gid of created users/groups)?

On Sep 10, 2024, at 4:20 PM, Gerben Wierda wrote: > Basically, my plan is to compare the local database > (/var/db/dslocal/nodes/Default) to see which items have been created by > MacPorts installs, copy these over so that a next MacPorts install would find > the users already created > > But

Re: Status on macOS Sequoia? (v.15)

I’m not worried by Sequoia in itself, I’ve used .0s before and usually with good luck (it seems I use way fewer weird software than the typical user). I’m just worried that some of the ports I need are broken with the new compiler (tbh, macports in my experience are often the most susceptible to

Re: Status on macOS Sequoia? (v.15)

If you are worried then best wait for a .1 release, that way anything that didn’t get in QA will be found by the general public. At the same time, if you are needing a feature that only exists on the latest release, then I’d recommend getting a second ‘sacrificial’ computer. André-John Sent

Re: Port website down?

Yeah, I'd like to help out on either a web-app or infrastucture basis, but I have no idea where to even start. I've downloaded the code and stuff, but I don't know how any of this stuff is actually deployed and who needs to look. —Mark On Wed, Sep 11, 2024, at 3:03 AM, contextnerror wrote: > I

Re: using port:usbmuxd instead of the system version on (older) Macs?

Succinct answer to self : yes and no.

Re: Port website down?

I spoke too soon. It’s down again.

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

Re: A deep clone of a MacPorts setup (especially the uid/gid of created users/groups)?

> On 10 Sep 2024, at 21:30, Ryan Carsten Schmidt > wrote: > > On Sep 10, 2024, at 06:08, Gerben Wierda wrote: >> >> Is there a way I can clone the MacPorts created users/groups first keeping >> them at the same uid/gid and then do a reinstall, so MacPorts finds already >> created users and le

Re: building seamonkey - python setup - imp module

Python's imp module was deprecated in Python 3.4 in favor of ‘importlib’, and removed in Python 3.12. This is confirmed by the deprecation warning printed by Python 3.11, which does still have the imp module: ❯ /opt/local/bin/python3.11 Python 3.11.10 (main, Sep 7 2024, 05:47:53) [Clang 15.0.0

Re: building seamonkey - python setup - imp module

On 2024-09-10 at 16:02:06 UTC-0400 (Tue, 10 Sep 2024 22:02:06 +0200) Riccardo Mottola via macports-users is rumored to have said: > I understand it is not finding module “imp”. I wonder if my python 3.12 > misses some module to isntall? any python expert here? I am NOT a python expert. I could

Re: A deep clone of a MacPorts setup (especially the uid/gid of created users/groups)?

On Sep 10, 2024, at 06:08, Gerben Wierda wrote: > > Is there a way I can clone the MacPorts created users/groups first keeping > them at the same uid/gid and then do a reinstall, so MacPorts finds already > created users and leaves them alone? If MacPorts needs a user account that doesn't exist

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: Dependencies/Dependents

> On Sep 9, 2024, at 14:39, Bernard via macports-users > wrote: > > About dependents/dependencies: > > 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 ‘rdepe

Re: Doubly Active PHP

Is the above list to be expected? Why do I have 2 php8* ports? Should I do anything at all? There are really only two reasons a port is installed: 1. Someone ran 'port install' to install that specific port, or 2. Some other port depends on it. You can check whether any other installed po

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: Doubly Active PHP

On 2024-09-09 at 10:20:32 UTC-0400 (Mon, 9 Sep 2024 16:20:32 +0200) Bernard via macports-users is rumored to have said: [...] How does the ‘port’ software decide on deactivation of the older version? Is it perhaps done on the basis of some usage algorithm? If you want actual deactivation, yo

Re: Doubly Active PHP

Good day Jim, > Only two PHP8* ports? That's nothing! I have 8 Python* ports installed! > > Seriously, it is common in macports to have distinct ports or subports > for different versions of software where users might want to keep > multiple versions on hand for easy use. > > The `port select`

Re: Doubly Active PHP

On 2024-09-08 23:27, Bernard via macports-users wrote: 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. ...[detail elided]... Why do I have 2 php8* ports? Should I do anything at all? Only two PHP8* ports? That's nothing! I

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): > > sqlite3 /opt/local

Re: 2.10.1 macports SQL error on 10.6

On 2024-09-06 at 22:25:07 UTC-0400 (Sat, 7 Sep 2024 12:25:07 +1000) Joshua Root is rumored to have said: [...] First install the macports.sqlext port. Then run this command (all one line): sqlite3 /opt/local/var/macports/registry/registry.db ".load /opt/local/lib/sqlite3/macports.sqlext" "PRA

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

Hi, thanks, Joshua Root wrote: This looks like database inconsistency. The id column is a primary key and so should always be unique, meaning there shouldn't be more than one row that has a given id. Hard to say how it happened. The problem could potentially have been there for some time, on

Re: Port website down?

I’m able to access the website now since my original email at least. Can’t speak for load times though.

Re: Port website down?

I thought maybe it was just me. Been getting a lot of 502 and 503 errors and slow runs. —Mark On Thu, Sep 5, 2024, at 6:04 PM, aeiouaeiouaeiouaeiouaeiouaeiou wrote: > The website has been running extra slow since last week, it feels like > it has been under DDoS attack. > > > > *Attachments:

Re: Port website down?

The website has been running extra slow since last week, it feels like it has been under DDoS attack. OpenPGP_0x67D486317A51FABE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature

Re: XV and GV hanging

On Thu, 5 Sep 2024, Ken Cunningham wrote: > 1. Do you have an X11 server installed? Look in /Applications/MacPorts > for it. Mine is called X11.app. Yep. > 2. Does it run if you double click it? Yep. > 3. If it does run, open an xterm terminal from the "Applications" menu > in the X11.app. (

Re: XV and GV hanging

1. Do you have an X11 server installed? Look in /Applications/MacPorts for it. Mine is called X11.app. 2. Does it run if you double click it? 3. If it does run, open an xterm terminal from the "Applications" menu in the X11.app. (you obviously do need xterm installed for it to open). 4. If xterm

Re: XV and GV hanging

On Thu, 5 Sep 2024, Chris Jones via macports-users wrote: > p.s. As much as you probably want to fix your X11 server, you do not > need it just to print a file. > > Install ghostscript, use 'ps2pdf' to convert the file to PDF then just > open that and print it using the standard OS tools. Bing

Re: XV and GV hanging

On Thu, 5 Sep 2024, Chris Jones via macports-users wrote: > Sounds like you have an issue with your X11 server, as these > applications are perhaps hanging at the point they are waiting for it to > start up. Sounds about right (it used to work). > 1. Does it automatically start if you run a ve

Re: XV and GV hanging

On 04/09/2024 10:50 pm, Dave Horsfall wrote: 13" mid-2010 MacBook Pro, running High Sierra 10.13.6. Did a graphics library change recently, and broke something? Both XV and GV are now hanging on startup, with no output; I don't know where to start with this. Hmmm... GIMP is also hanging?

Re: XV and GV hanging

Sounds like you have an issue with your X11 server, as these applications are perhaps hanging at the point they are waiting for it to start up. 1. Does it automatically start if you run a very basic X11 application, like xeyes ? > sudo port install xeyes > xeyes If that does not trigge

Re: Port website down?

I'm getting that too, was just about to write. On Mon, Sep 2, 2024, at 5:38 PM, contextnerror wrote: > When trying to visit ports.macports.org I get "Error 503 Backend fetch > failed”. Is anyone else having problems?

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: python3 alias or executable

On 2024-08-31 at 11:39:29 UTC-0400 (Sat, 31 Aug 2024 17:39:29 +0200) Nils Breunese is rumored to have said: Riccardo Mottola wrote: I have several python versions installed an dused as dependencies my macports itself. Fine. To build ArcticFox browser, I need python2 and on 10.9 this is no is

Re: python3 alias or executable

Riccardo Mottola wrote: > I have several python versions installed an dused as dependencies my macports > itself. Fine. > To build ArcticFox browser, I need python2 and on 10.9 this is no issue, I > guess the system python is getting used. > Now I want to try do build current SeaMonkey since no

Re: progress display during port de/activation

On Aug 30, 2024, at 04:47, René J.V. Bertin wrote: > > was anything changed w.r.t. GMane on the MacPorts side?! I don't think we have anything to do with gmane. We don't endorse or recommend the use of third party mirrors of our mailing lists.

Re: progress display during port de/activation

On Sunday August 11 2024 14:52:37 Clemens Lang wrote: >Feel free to contribute a macports.conf option in a pull request. Here it is (now without stupid error): https://github.com/macports/macports-base/pull/348 NB: I had posted this almost a week ago, via the GMane mirror of the ML. I see that

Re: Any alternative strategies to limit the proliferation of perl and python packages?

On Mon, Aug 26, 2024 at 01:19:32PM +0200, "René J.V. Bertin" wrote: > Hi, > > This is one of those periods where I notice that "damn, I should > update my Perl5 and/or Python interpreters, but then I'll also have to > reinstall a whole bunch of modules for them and figure out which old > ones I

Re: Using port command to see installation method

From personal experience: if you installed package X from source with a given variant(s) and an updated version of X exists in binary version for the same variant(s), then “port upgrade outdated” will install that binary version. -- Mircea Trandafir Senior researcher Rockwool Foundation Research

Re: Using port command to see installation method

On 2024-08-20 at 15:32:44 UTC-0400 (Tue, 20 Aug 2024 15:32:44 -0400) Nate Ijams via macports-users is rumored to have said: And I suppose one follow up, if that is the case: how are upgrades handled by MacPorts when someone has originally installed a package from source vs binary? Take this

Re: Using port command to see installation method

> On Aug 20, 2024, at 11:56 AM, Nate Ijams via macports-users > wrote: > > Hello, all. I have struggled to find relevant documentation for this, and I > hope I haven't just missed something obvious. I have installed some packages > using the binaries available online, but I have also installed

Re: Using port command to see installation method

And I suppose one follow up, if that is the case: how are upgrades handled by MacPorts when someone has originally installed a package from source vs binary? Take this scenario: – Install package X from source; – Install package Y from binary; – Later, both packages are upgraded in the ports tr

Re: Using port command to see installation method

On Aug 20, 2024, at 10:56, Nate Ijams wrote: > > Is there any way to determine whether a package was installed from source or > binary besides manually going through folders in /opt/local? Not that I know of.

Re: progress display during port de/activation

On Sunday August 11 2024 14:52:37 Clemens Lang wrote: > >Feel free to contribute a macports.conf option in a pull request. I'm preparing a PR that includes all my tweaks to the progress reporting feature and introduces 3 config variables to customise it. As a FWIW now that will hopefully attrac

Re: platform mismatch error

Hello Eric, I know why I am getting this error now. The terminal was in arm64 but I was using a software built for x86_64 arm64. I must now find the way to compile it in arm64 only. Bests. Raoul > On 15 Aug 2024, at 17:18, Eric Hoch wrote: > > Hi Raoul, > > Am 15.08.24 um 09:34 schrieb R

Re: platform mismatch error

Hi Raoul, Am 15.08.24 um 09:34 schrieb Raoul MEGELAS On 15 Aug 2024, at 09:14, Ryan Carsten Schmidt wrote: On Aug 14, 2024, at 12:46, Raoul MEGELAS wrote: As rosetta was not the problem, I tried something else. 1. Run the script posted here to remove all macports files. Downloaded macports f

Re: Re/ platform mismatch

Hello Franco It is exactly what is happening!!! Many thanks you solved my issue. BESTS Raoul > On 15 Aug 2024, at 10:19, Franco Vaccari wrote: > > Could it be that in your troubled account you have a copy of the Terminal app > marked to run under Rosetta? If you ask to show it in Finder from

Re: Re/ platform mismatch

Could it be that in your troubled account you have a copy of the Terminal app marked to run under Rosetta? If you ask to show it in Finder from its icon in the Dock, does it point to /Applications or to another location? If you look at the Terminal process in Activity Monitor, what is its kind?

Re/ platform mismatch

Hello, A little bit more. I Created a new administrator user account. Macports works fine on it. This means than I have an error in my own account., and only that. Please how to narrow the error search Is there a macport command to return all it send? Thanks Raoul

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 => Architectures in the f

Re: platform mismatch error

> On 15 Aug 2024, at 09:14, Ryan Carsten Schmidt > wrote: > > On Aug 14, 2024, at 12:46, Raoul MEGELAS wrote: >> >> As rosetta was not the problem, >> I tried something else. >> 1. Run the script posted here to remove all macports files. >> Downloaded macports for Sonoma 14. >> Installed i

Re: platform mismatch error

On Aug 14, 2024, at 12:46, Raoul MEGELAS wrote: > > As rosetta was not the problem, > I tried something else. > 1. Run the script posted here to remove all macports files. > Downloaded macports for Sonoma 14. > Installed it. > > Run install some port > Mismatch version! Are you using the Apple

Re: Platform mismatch error

Hello, Please see below Bests Raoul > On 15 Aug 2024, at 00:48, Joshua Root wrote: > > 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). >>

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

Hello, As rosetta was not the problem, I tried something else. 1. Run the script posted here to remove all macports files. Downloaded macports for Sonoma 14. Installed it. Run install some port Mismatch version! Ok. I logged in another account on the same machine. Installing some port gives t

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 Aug 14, 2024, at 03:10, Franco Vaccari wrote: > > 2) On my system, not all the directories listed in the sudo rm -rf command > existed. I would remove them one by one to be sure each existing one is > properly removed No need. rm will remove any of the directories that exist and it does not

Re: Platform mismatch error

Hi, Thanks, I will check this. Ciao > On 14 Aug 2024, at 10:10, Franco Vaccari wrote: > > Two comments: > > 1) the two dscl commands appear commented with # in your list. If that’s the > case, they weren’t executed > > 2) On my system, not all the directories listed in the sudo rm -rf com

Re: Platform mismatch error

Two comments: 1) the two dscl commands appear commented with # in your list. If that’s the case, they weren’t executed 2) On my system, not all the directories listed in the sudo rm -rf command existed. I would remove them one by one to be sure each existing one is properly removed Ciao Fra

Re: Platform mismatch error

Hello Franco, Here is exactly what I did: sudo port -fp uninstall installed # remove user and group # sudo dscl . -delete /Users/macports # sudo dscl . -delete /Groups/macports sudo rm -rf \ /opt/local \ /Applications/DarwinPorts \ /Applications/MacPorts \ /Library/LaunchDaemons/o

Re: Platform mismatch error

Hi Raoul, just to be sure, did you remove MacPorts following the steps described in Ciao Franco > On 14 Aug 2024, at 08:13, Raoul MEGELAS wrote: > > Hello macports, > > Still the same error: > As the subject says, > Platform m

RE: platform mismatch error

Hi, One precision: Os 14.6.1 in menu system about For memory Mac Studio M1 Max. Now: in terminal: name -a Darwin 23.6.0 T6000 arm64. Hope this help.

Re: Portindex fails (2.10.0)

Seems to be related to https://trac.macports.org/ticket/70511 > On 14 Aug 2024, at 00:23, Gerben Wierda wrote: > > I have three Macs, two of which running Sonoma. On one I have updated to > 2.10.0 without trouble. All three systems are configured in the same way > (obviously not…) > > When I

Re: resizing window when using "bc" in interactive mode

tion for SIGWINCH is to do nothing; > i.e. only programs that catch it are even aware of it. That would usually be > programs like text editors that do full-window text handling, and probably > need to re-fetch the current size and redraw on window size change. > Right. It is clearly a b

Re: resizing window when using "bc" in interactive mode

i'm sure i'm running stock zsh as the login shell. On Tue, Aug 13, 2024 at 7:37 AM matt henschel wrote: > > It happens in 'screen' and 'tmux' too. I don't think it did it in all > sonoma's but I cant remember. > > > > On Sun, Aug 11, 2024 at 8:23 AM matt henschel wrote: > > > > I forgot to mak

Re: resizing window when using "bc" in interactive mode

It happens in 'screen' and 'tmux' too. I don't think it did it in all sonoma's but I cant remember. On Sun, Aug 11, 2024 at 8:23 AM matt henschel wrote: > > I forgot to make a joke about augmented reality AI calculators and stock > prices

SOLVED: Re: Strange warning/file when doing a selfupdate

this using macports 2.10.0, macOS Sonoma 14.6.1 on an Intel MacBook Pro, late > 2019. Anyone know what this means? > > Kind regards, > Bas > > ------- > Date: Mon, 12 Aug 2024 09:44:14 -0400 > From: Bill Cole > To: Bas Jansen via macports-us

Re: Strange warning/file when doing a selfupdate

> On Aug 12, 2024, at 09:44, Bill Cole > wrote: > > On 2024-08-12 at 08:14:54 UTC-0400 (Mon, 12 Aug 2024 14:14:54 +0200) > Bas Jansen via macports-users > > is rumored to have said: > > Hi, > > When doing a self update via Terminal, I get the following warning:

  1   2   3   4   5   6   7   8   9   10   >