Re: py39-nbconvert fails to build on Catalina

On Sep 8, 2022, at 08:49, Artemio González López wrote: > I got the following error when trying to build py39-nbconvert on a 2014 27” > iMac running the latest version of Catalina (10.15.7). The error I got (from > main.log) is the following: > > :info:build Executing: cd &g

py39-nbconvert fails to build on Catalina

I got the following error when trying to build py39-nbconvert on a 2014 27” iMac running the latest version of Catalina (10.15.7). The error I got (from main.log) is the following: :info:build Executing: cd "/opt/local/var/macports/

Re: catalina full disk access

grade outdated"), then the authorization goes away even though the binary is still listed as authorized in System Preferences. Can you try removing the item's authorization in System Preferences and then re-adding it? > The behavior has also seen some changes under different OS versions. What are > you using? Subject line says Catalina.

Re: catalina full disk access

This isn’t specific to MacPorts, but is a more general issue with recent versions of macOS and “Full Disk Access”. What I’ve found is that any binaries you add to Full Disk Access won’t actually be authorized. Authorized applications seem to need a bundle identifier. The behavior has also seen

catalina full disk access

from cron i run a bash job that runs a bash job that runs rsnapshot from an external usb disk to another external usb disk. gcp -al (called from rsnapshot) fails with operation not permitted. it runs fine from ssh from iterm on another mac. /usr/sbin/cron /opt/local/bin/bash /opt/local/bin/rsnap

Re: No user or group to remove on macOS Catalina

On Nov 27, 2021, at 02:22, Pieter van Oostrum wrote: > chilli.names...@gmail.com writes: > >> To uninstall macports entirely, I use the three commands below in a script >> (which I assume I got >> from the manual, but it's been awhile, I do not recall), but they work just >> as well one at a ti

Re: No user or group to remove on macOS Catalina

I don't consider /Applications/MacPorts part of the installation. And deleting binaries I built would be like... not only uprooting the tree, but destroying the fruit as well. That said, you have fair point. > On Nov 27, 2021, at 03:22, Pieter van Oostrum wrote: > > "chilli.names...@gmail.com

Re: No user or group to remove on macOS Catalina

"chilli.names...@gmail.com" writes: > To uninstall macports entirely, I use the three commands below in a script > (which I assume I got > from the manual, but it's been awhile, I do not recall), but they work just > as well one at a time: > > sudo port -vfp uninstall --follow-dependencies inst

Re: No user or group to remove on macOS Catalina

I would say the big benefit of MacPorts over Brew is that it feels more secure, mainly because it doesn’t do everything as an unprivileged user. André-John Sent from my phone. Envoyé depuis mon téléphone. > On 26 Nov 2021, at 19:50, Dave Horsfall wrote: > > On Fri, 26 Nov 2021, Ryan Schmid

Re: No user or group to remove on macOS Catalina

On Fri, 26 Nov 2021, Ryan Schmidt wrote: > You're right, it's best to pick one package manager and uninstall the > other, to avoid them conflicting with one another. If you have any > feedback about ways that MacPorts could improve, please let us know. I'm not sure how I came across MacPorts, b

Re: No user or group to remove on macOS Catalina

To uninstall macports entirely, I use the three commands below in a script (which I assume I got from the manual, but it's been awhile, I do not recall), but they work just as well one at a time: sudo port -vfp uninstall --follow-dependencies installed sudo port -vfp uninstall all sudo rm -r

Re: No user or group to remove on macOS Catalina

e other, to avoid them conflicting with one another. If you have any feedback about ways that MacPorts could improve, please let us know. On my Catalina system: $ /usr/bin/dscl . -search /Users name macports macportsdsAttrTypeNative:name = ( macports ) If you don't get th

No user or group to remove on macOS Catalina

Hello, I am following the steps from https://guide.macports.org/chunked/installing.macports.uninstalling.html to remove mac ports from my machine (it is currently functioning but I want to migrate to homebrew and I've heard they do not coexist). The second step states that I need to remove the user

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

I contacted NLNet Labs, they updated their certs which made NSD fetch on Mojave work again for me. Somewhere during my tests accidentally OpenSSL was activated on my machine (a destroot on nsd 4.3.8 maybe?), which killed all the installed ports that were dependent on an opensll 1.1.1 dylib (whi

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

On Sun, 7 Nov 2021, Bill Cole wrote: So I wonder how widespread this problem is? The problem in this case is not the existence of the cert in the CA bundle, but the fact that this particular expired cert was used in an alternative validation path and the logic of verification for multi-path

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

On 2021-11-07 at 16:29:30 UTC-0500 (Mon, 8 Nov 2021 08:29:30 +1100 (EST)) Dave Horsfall is rumored to have said: On Sun, 7 Nov 2021, Bill Cole wrote: I have my own Mojave machines working without a problem after removing the bad certificate from /etc/ssl/cert.pem. The one that starts like t

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

On Sun, 7 Nov 2021, Bill Cole wrote: I have my own Mojave machines working without a problem after removing the bad certificate from /etc/ssl/cert.pem. The one that starts like this: [...] Intrigued, I checked my own: mackie:~ dave$ grep "Not After" /etc/ssl/cert.pem Not A

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

o I suspect that is the Mojave-doesn’t-get-root-cert-updates problem. So, I tried to do a port fetch on Catalina, and there it works and the distribution is downloaded. It is strange, though, because Safari on both Catalina (other machine) and Mojave say the cert is fine. Still, it is most li

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

;>>> On Nov 6, 2021, at 5:43 AM, Ryan Schmidt wrote: >>>> >>>> >>>> >>>>> On Nov 6, 2021, at 05:39, Gerben Wierda wrote: >>>>> >>>>> I was looking at updating nsd (for which I am maintaining and it is h

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

On Nov 7, 2021, at 00:03, Kastus Shchuka wrote: > > On the other hand, it's plain dumb why it works for me. As you can see below, > org.macports.fetch does not use HTTPS, it downloads over HTTP. Certificates > are just irrelevant for that. > > I am not sure what part of macports.conf control

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

-4.3.8.tar.gz does not exist in >>> /opt/local/var/macports/distfiles/nsd >>> :notice:fetch ---> Attempting to fetch nsd-4.3.8.tar.gz from >>> https://www.nlnetlabs.nl/downloads/nsd/ >>> :debug:fetch Fetching distfile failed: SSL certificate problem: certi

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

h >>>> time) >>>> >>>> But fetching failed on macOS Mojave (where I have my MacPorts setup). >>>> >>>> :debug:fetch Executing org.macports.fetch (nsd) >>>> :info:fetch ---> nsd-4.3.8.tar.gz does not exist in >&g

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

macOS Mojave (where I have my MacPorts setup). >>>> >>>> :debug:fetch Executing org.macports.fetch (nsd) >>>> :info:fetch ---> nsd-4.3.8.tar.gz does not exist in >>>> /opt/local/var/macports/distfiles/nsd >>>> :notice:fetch --->

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

>>> :info:fetch ---> nsd-4.3.8.tar.gz does not exist in >>> /opt/local/var/macports/distfiles/nsd >>> :notice:fetch ---> Attempting to fetch nsd-4.3.8.tar.gz from >>> https://www.nlnetlabs.nl/downloads/nsd/ >>> :debug:fetch Fetching distfil

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

nlnetlabs.nl/downloads/nsd/ >> :debug:fetch Fetching distfile failed: SSL certificate problem: certificate >> has expired >> >> Now, my main MacPorts dev/use machine is macOS Mojave so I suspect that is >> the Mojave-doesn’t-get-root-cert-updates problem. So, I tried to do

Re: port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

; > Now, my main MacPorts dev/use machine is macOS Mojave so I suspect that is > the Mojave-doesn’t-get-root-cert-updates problem. So, I tried to do a port > fetch on Catalina, and there it works and the distribution is downloaded. > > It is strange, though, because Safari on bo

port cannot fetch because of expired cert, but cert is OK according to Safari, curl (question related to Mojave / Catalina)

suspect that is the Mojave-doesn’t-get-root-cert-updates problem. So, I tried to do a port fetch on Catalina, and there it works and the distribution is downloaded. It is strange, though, because Safari on both Catalina (other machine) and Mojave say the cert is fine. Still, it is most likely th

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

Thank you Bjarne, this is great to know especially for those of us lagging somewhat and getting ourselves more acquainted with the new volume formats of Catalina and Big Sur, with Monterrey in the works. I would not be surprised if Apple included the opt directory in /System/Volumes/Data thanks in

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

Tabitha McNerney wrote: > Hi all, > > I haven't installed a fresh MacPorts system in quite some time but will > soon be doing so on a few Macs one running Catalina and the other Big > Sur. Starting with Catalina, the root volume / is read-only so how do > the MacPorts

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

wrote: > On Jun 25, 2021, at 21:03, Tabitha McNerney wrote: > > > On a fresh Catalina or Big Sure system, if you cd to root / then sudo > then try mkdir /opt or something else such as mkdir /hello the system won't > allow it, I get this: > > > > mkdir: /hello:

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

On Jun 25, 2021, at 21:03, Tabitha McNerney wrote: > On a fresh Catalina or Big Sure system, if you cd to root / then sudo then > try mkdir /opt or something else such as mkdir /hello the system won't allow > it, I get this: > > mkdir: /hello: Read-only file system >

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

On a fresh Catalina or Big Sure system, if you cd to root / then sudo then try mkdir /opt or something else such as mkdir /hello the system won't allow it, I get this: mkdir: /hello: Read-only file system note: the MacBook I just tried this on also has FileVault enabled and its got one of

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

On Jun 25, 2021, at 18:07, Tabitha McNerney wrote: > Hi all, > > I haven't installed a fresh MacPorts system in quite some time but will soon > be doing so on a few Macs one running Catalina and the other Big Sur. > Starting with Catalina, the root volume / is rea

MacPorts and /opt/local on Catalina and Big Sur read only volumes

Hi all, I haven't installed a fresh MacPorts system in quite some time but will soon be doing so on a few Macs one running Catalina and the other Big Sur. Starting with Catalina, the root volume / is read-only so how do the MacPorts package installers set things up such that /opt/local can r

Re: does osxfuse and encfs work in 10.15 (catalina)?

On Apr 9, 2021, at 07:33, Uwe Brauer wrote: > I started to use a macbook air running catalina (10.15) and installed > first of all fink. > > It took some time to install encfs and osxfuse (currently version 2.7) > however when I want to use encfs on a specific dir

does osxfuse and encfs work in 10.15 (catalina)?

Hi I started to use a macbook air running catalina (10.15) and installed first of all fink. It took some time to install encfs and osxfuse (currently version 2.7) however when I want to use encfs on a specific directory I obtain , [+] | EncFS Password: | /opt/sw/lib/osxfusefs.fs

Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

am running an extensive MacPorts (with postfix, dovecot, nginx, minion, >> etc.) on my macOS Server, which is still running macOS Mojave. >> >> On one of the other Macs, running macOS Catalina, I run a backup unbound >> caching nameserver. This also offers me a way to do some

Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

of the other Macs, running macOS Catalina, I run a backup unbound > caching nameserver. This also offers me a way to do some minimal testing of > the MacPorts setup on a more recent version of macOS (as a preparation for > upgrading the Mojave system when Apple stops supporting it) > &

Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

> wrote: > > I am running an extensive MacPorts (with postfix, dovecot, nginx, minion, > etc.) on my macOS Server, which is still running macOS Mojave. > > On one of the other Macs, running macOS Catalina, I run a backup unbound > caching nameserver. This also offers me

How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

I am running an extensive MacPorts (with postfix, dovecot, nginx, minion, etc.) on my macOS Server, which is still running macOS Mojave. On one of the other Macs, running macOS Catalina, I run a backup unbound caching nameserver. This also offers me a way to do some minimal testing of the

Re: Catalina: accepting incoming connections on unbound does not survive a reboot

On 14 Jan 2021, at 18:50, Tom wrote: Have you tried Lulu or Little Snitch? I've used both on various versions through 10.14. It is my understanding that due to Apple exempting their own software from the Network Extension Framework, both are hobbled on 10.15+, but that with 11.2 they will b

Re: Catalina: accepting incoming connections on unbound does not survive a reboot

preferences pane and supposedly this still can be done on Catalina (see https://www.dummies.com/computers/macs/macbook/how-to-customize-your-macbooks-catalina-firewall/) but I have not tried that and it may not work for software that is not packaged as a macOS application. You definitely should disable

Catalina: accepting incoming connections on unbound does not survive a reboot

unbound. System administrator user name and password are given and incoming connections are then accepted. But after a reboot I have to do this again. This worries me. My main server (stilll on Mojave until I have enough confidence in MacPorts under Catalina to upgrade) must be able to survive

Re: Any reason not to update to Xcode 12.2 on Catalina?

fixed many >> ports already, there are many many more that have yet to be identified and >> fixed. > > Im on: > Catalina 10.15.7, with Xcode 12.2 (12B45b). > "pkgutil --pkg-info=com.apple.pkg.CLTools_Executables | grep version" gives > "version: 1

Re: Any reason not to update to Xcode 12.2 on Catalina?

ied and fixed. Im on: Catalina 10.15.7, with Xcode 12.2 (12B45b). "pkgutil --pkg-info=com.apple.pkg.CLTools_Executables | grep version" gives "version: 12.2.0.0.1.1604628099" I have encountered "This problem". It was in the port "man" (that I don't actually

Re: Any reason not to update to Xcode 12.2 on Catalina?

On Mon, Nov 16, 2020 at 06:45:17PM -0600, Ryan Schmidt wrote: > On Nov 16, 2020, at 17:32, raf wrote: > > > On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote: > > > >> You should definitely never run with a mismatched set of Xcode and its > >> command line tools. Either update the c

Re: Any reason not to update to Xcode 12.2 on Catalina?

On Nov 16, 2020, at 17:32, raf wrote: > On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote: > >> You should definitely never run with a mismatched set of Xcode and its >> command line tools. Either update the command line tools to the Xcode >> 12.2 version or downgrade Xcode to whatever

Re: Any reason not to update to Xcode 12.2 on Catalina?

On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote: > You should definitely never run with a mismatched set of Xcode and its > command line tools. Either update the command line tools to the Xcode > 12.2 version or downgrade Xcode to whatever it was before. Using Xcode > 11.x and match

Re: Any reason not to update to Xcode 12.2 on Catalina?

atic updates on users, which is often great, but in the case of Xcode and its command line tools it's not always desirable. > Now one of my Macs is running Catalina, with XCode 12.2, but without having > upgraded the Command Line Tools. And I ran "sudo port selfupdate; sudo por

Re: Any reason not to update to Xcode 12.2 on Catalina?

On Nov 12, 2020, at 23:08, Richard L. Hamilton wrote: > One or two times past, an Xcode version around the time of a new OS release > has been a problem on the older OS. > > I don't see anything likely to be that way with Xcode 12.2 (and MacPorts) on > Catalina,

Any reason not to update to Xcode 12.2 on Catalina?

One or two times past, an Xcode version around the time of a new OS release has been a problem on the older OS. I don't see anything likely to be that way with Xcode 12.2 (and MacPorts) on Catalina, but I'm looking for alternative opinions; reverting is a nuisance. I'm in no hu

Re: Catalina xcode-select --install and MacPorts installation

Thanks. Maybe there is something about the mobile device management setup my employer uses that changes how the installations work. On 10/29/20, 03:44, "Ryan Schmidt" wrote: On Oct 28, 2020, at 02:31, Fielding, Eric J (US 329A) wrote: > I just upgraded my MacBoo

Re: Catalina xcode-select --install and MacPorts installation

On Oct 28, 2020, at 02:31, Fielding, Eric J (US 329A) wrote: > I just upgraded my MacBook to Catalina 10.15.7 from 10.14.6 and I installed > the latest Xcode 12.1. I started Xcode and agreed for it to install required > components. When I tried to run “xcode-select –install” it as

Catalina xcode-select --install and MacPorts installation

I just upgraded my MacBook to Catalina 10.15.7 from 10.14.6 and I installed the latest Xcode 12.1. I started Xcode and agreed for it to install required components. When I tried to run “xcode-select –install” it asked me to agree to the license for the command-line tools and tried to install

Re: Xcode 12 on Catalina?

> I've been putting off the upgrade to XCode 12 for a while, since I kinda > got burned by the upgrade from 10 to 11. I haven't seen any reports of > problems with the new version, but I thought I'd ask -- any reason not to > upgrade at this point? It seems the most frequently encountered issue so

Re: Xcode 12 on Catalina?

I had a problem recently that may have been due to Xcode 12, with the convertlit port, where the code was missing some include files and declarations that really should have been there. That was fixed, and I'm ok since then with Xcode 12 on Catalina. There may have been some earlier pro

Xcode 12 on Catalina?

I've been putting off the upgrade to XCode 12 for a while, since I kinda got burned by the upgrade from 10 to 11. I haven't seen any reports of problems with the new version, but I thought I'd ask -- any reason not to upgrade at this point? Thanks, Richard

Re: freeciv SDL - blank screen on Mojave/Catalina

On Nov 23, 2019, at 10:37, Dennis van der Burg wrote: > Since upgrading to Mojave, when doing a fresh MacPorts install and then > installing freeciv (SDL client) and clicking on the Apps>MacPorts>Freeciv > icon, only a blank screen opens instead of a screen with the game running in > it. >

Xcode 11.5 on Catalina FYI

While I haven't yet updated many ports with it, so far I've seen no problems with Xcode 11.5 on Catalina. In other words, as yet I don't regret updating to it. :-)

Re: upgrade to osx 10.15 catalina

ode releases >> with catalina and assorted package specific problems simply not being >> solvable right now. >> I have looked at the mail archive and macports webpage but have not found a >> clear recommendation or statement what the current situation (as of jan >> 2020

Re: upgrade to osx 10.15 catalina

last months of problems with subsequent macports upgrade, recommendations to use previous xcode releases with catalina and assorted package specific problems simply not being solvable right now. I have looked at the mail archive and macports webpage but have not found a clear recommendation or

upgrade to osx 10.15 catalina

I had to upgrade to 10.15 (wanted to postpone this further but ...) and recall that there were many reports over the last months of problems with subsequent macports upgrade, recommendations to use previous xcode releases with catalina and assorted package specific problems simply not being

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

There are two recent tickets which, I believe, involve the same error: ffmpeg and ffmpeg-devel immediately crash with segfault 11 when input is mp4: https://trac.macports.org/ticket/59750 ffmpeg @4.2.1 crash using -vcodec libx264: https://trac.macports.org

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

These work: /usr/local/bin/avconv -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; /usr/local/bin/ffmpeg -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; This doesn’t: /opt/local/bin/ffmpeg -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; Both ffmpegs are version 4.2.1

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

> On 2019-12-13, at 23:51, Michael Newman via macports-users > wrote: > > I tried uninstalling all ports and reinstalling again. That didn’t work. > > I did manage to get my time-lapse videos working with avconv. I tested a similar ffmpeg command and it fails with the same segfault. This is

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

I tried uninstalling all ports and reinstalling again. That didn’t work. I did manage to get my time-lapse videos working with avconv.

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

I saved the version of ffmpeg that was built before I migrated and which worked fine before migration. It also now fails with the same error message. So, I think there’s something else going on here > On Dec 14, 2019, at 08:16, Andrew Udvare wrote: > > It's built so it seems more likely this

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

ent from my iPhone >> >>>> On Dec 13, 2019, at 18:28, Michael Newman via macports-users >>>> wrote: >>> >>> I’ve been using ffmpeg daily for several years to generate time lapse >>> videos from a series of JPEGs. >>> >>&g

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

m my iPhone > >> On Dec 13, 2019, at 18:28, Michael Newman via macports-users >> wrote: >> >> I’ve been using ffmpeg daily for several years to generate time lapse >> videos from a series of JPEGs. >> >> After I updated my 2017 iMac to Catalina, it st

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

Sent from my iPhone > On Dec 13, 2019, at 18:28, Michael Newman via macports-users > wrote: > > I’ve been using ffmpeg daily for several years to generate time lapse videos > from a series of JPEGs. > > After I updated my 2017 iMac to Catalina, it still worked

ffmpeg Fails After MacPorts Migration to Catalina Version

I’ve been using ffmpeg daily for several years to generate time lapse videos from a series of JPEGs. After I updated my 2017 iMac to Catalina, it still worked. However, after migrating MacPorts to the Catalina version, it fails: ./skyvideo.sh: line 38: 5438 Donecat $ipath

Re: problem migrating to catalina

Please remember to write to our new mailing list addresses at lists.macports.org, not the old address you used which was deprecated at the end of 2016. The error in the log you attached is: :info:build dyld: Library not loaded: /opt/local/lib/libcrypto.1.0.0.dylib :info:build Referenced from:

Re: 32bit Docker containers in Catalina

On Nov 28, 2019, at 11:04, Ces VLC wrote: > Should I be beware of difficulties at running 32bit Linux containers in the > macports docker in Catalina, or should the Catalina hypervisor be fine at > virtualizing 32bit code? I know that the developers of Wine are having to do

Re: problem migrating to catalina

Chris, Thanks for the suggestion about bzip2. I have compresse with bzip2 and am attaching herewith. Comer On Thu, Nov 28, 2019 at 1:06 PM Chris Jones wrote: > > > > > On 28 Nov 2019, at 3:39 pm, Comer Duncan wrote: > > > > I've migrated to catalina and am ha

Re: problem migrating to catalina

> On 28 Nov 2019, at 3:39 pm, Comer Duncan wrote: > > I've migrated to catalina and am having problem with building pango. > I've attached an edited version of the main.log, as the whole file was > deemed too big. Please take a look and let me know what you think.

32bit Docker containers in Catalina

Hi! Should I be beware of difficulties at running 32bit Linux containers in the macports docker in Catalina, or should the Catalina hypervisor be fine at virtualizing 32bit code? Thanks! César PS: Just found mingw-w64 just updated to 7.0.0 yay! Thanks a million Mojca!!

problem migrating to catalina

I've migrated to catalina and am having problem with building pango. I've attached an edited version of the main.log, as the whole file was deemed too big. Please take a look and let me know what you think. Thanks very much! Comer Duncan duncan.migrate.to.cataline.summaryerrors D

Catalina X11 xterm - cannot access ~/.Trash and /Volumes/* - Full Disk Access

Trying to get access in xterm to ~/.Trash and /Volumes/*, but Catalina is blocking access. * In SysPref/Sec&Priv/Privacy/Full Disk Access, remove "Terminal". * Run Terminal, try "ls ~/.Trash" - "Operation not permitted" * Back to Full Disk Access, "Terminal&

Re: Catalina installation problems

hand » on a terminal session? >>> An other way: is it a proxy between your PC and MacPorts? Global or >>> specific to MacPorts (file « /opt/local/etc/macports/macports.conf » and « >>> proxy » key)? >>> >>>> Le 26 nov. 2019 à 11:20, Tarik Cicic >&g

Re: Catalina installation problems

your PC and MacPorts? Global or specific >> to MacPorts (file « /opt/local/etc/macports/macports.conf » and « proxy » >> key)? >> >>> Le 26 nov. 2019 à 11:20, Tarik Cicic >> <mailto:tarik.ci...@gmail.com>> a écrit : >>> >>> Hi, >>

Re: Catalina installation problems

rts for years, and for first time have problems >> installing, after upgrade to MacOS 10.15 Catalina. >> >> Gray-MBP:~ tarik$ sudo port -d selfupdate >> Password: >> DEBUG: Copying /Users/tarik/Library/Preferences/com.apple.dt.Xcode.plist to >> /opt/loc

Re: Catalina installation problems

i, > > I have been using Macports for years, and for first time have problems > installing, after upgrade to MacOS 10.15 Catalina. > > Gray-MBP:~ tarik$ sudo port -d selfupdate > Password: > DEBUG: Copying /Users/tarik/Library/Preferences/com.apple.dt.Xcode.plist to > /op

Catalina installation problems

Hi, I have been using Macports for years, and for first time have problems installing, after upgrade to MacOS 10.15 Catalina. Gray-MBP:~ tarik$ sudo port -d selfupdate Password: DEBUG: Copying /Users/tarik/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library

freeciv SDL - blank screen on Mojave/Catalina

Since upgrading to Mojave, when doing a fresh MacPorts install and then installing freeciv (SDL client) and clicking on the Apps>MacPorts>Freeciv icon, only a blank screen opens instead of a screen with the game running in it. Has anyone else seen this too? Any ideas how to solve this? This pack

Re: Catalina ante portas - wine, wine-bottler LTSpice

On Oct 22, 2019, at 10:30, Christoph Kukulies wrote: > My macOS wants to update (Mojave->Catalina 10.15). > > I’ve heard wine emulator based programs will cease working. > > Has anyone heard there will be an escape for this situation? This is the latest informat

Re: Catalina ante portas - wine, wine-bottler LTSpice

Stay in 10.14 actually. The update message of OSX is just an incitation not an obligation. And all 10.14 update are stil here, just under Catalina suggest. > Le 22 oct. 2019 à 17:30, Christoph Kukulies a écrit : > > My macOS wants to update (Mojave->Catalina 10.15). > &g

Catalina ante portas - wine, wine-bottler LTSpice

My macOS wants to update (Mojave->Catalina 10.15). I’ve heard wine emulator based programs will cease working. Has anyone heard there will be an escape for this situation? Best regards, Christoph Kukulies

Re: mpv, ffmpeg seg fault in macOS catalina

Thanks. I’ve used the migration process many times in the past, so no worries. I appreciate your taking the time to reply. > On Oct 19, 2019, at 10:08, Chris Jones wrote: > >> If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts >> for Catalina will f

Re: mpv, ffmpeg seg fault in macOS catalina

> On 18 Oct 2019, at 11:30 pm, Michael Newman via macports-users > wrote: > > I’m sorry, but I don’t understand most of what was written in this thread, > but I do have a simple question: > > If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts

Re: mpv, ffmpeg seg fault in macOS catalina

I’m sorry, but I don’t understand most of what was written in this thread, but I do have a simple question: If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts for Catalina will ffmpeg stop working? > On Oct 18, 2019, at 19:00, Gill Bates <mailto:smo...@shaw.ca&g

Re: mpv, ffmpeg seg fault in macOS catalina

Thanks all for the explanations and workaround. From: "Mojca Miklavec" To: "smogus" Cc: "macports-users" Sent: Friday, October 18, 2019 5:02:55 AM Subject: Re: mpv, ffmpeg seg fault in macOS catalina V čet., 17. okt. 2019 22:58 je oseba Gill Bates &l

Re: mpv, ffmpeg seg fault in macOS catalina

Hi, Workaround is to either blacklist the compiler which has this option turned on by default (which is what Chris replied) or in fact use a flag to disable this. But disabling this flag is not needed for non-broken compilers, so it's probably better to just blacklist the compiler, and the la

Re: mpv, ffmpeg seg fault in macOS catalina

V čet., 17. okt. 2019 22:58 je oseba Gill Bates napisala: > I recently updated to catalina (10.15) and Xcode (11.1), installed > MacPorts from source (2.6.1) and had it build mpv and its dependencies. > However, mpv (and ffmpeg for example) do not run apparently related to some >

Re: mpv, ffmpeg seg fault in macOS catalina

a good idea. For ‘Part B’ difficult to say as long as Xcode has issues (which I understand as off 11.1 it does). Until those are addressed hard to say if the project themselves also have issues to address. Chris > On 17 Oct 2019, at 9:58 pm, Gill Bates wrote: > > I recently updat

mpv, ffmpeg seg fault in macOS catalina

I recently updated to catalina (10.15) and Xcode (11.1), installed MacPorts from source (2.6.1) and had it build mpv and its dependencies. However, mpv (and ffmpeg for example) do not run apparently related to some new default compiler option enforcing 16 byte stack alignment? See: [ https

PortAuthority, MacPorts GUI for Catalina

I'd like to take a moment to re-introduce my GUI for MacPorts, PortAuthority, now updated for Catalina. PortAuthority makes it easy to install thousands of Unix software packages for macOS.  PortAuthority's familiar three-pane interface lets you get started doing what you want to d

Re: Xfce4 Won't Launch in macOS Catalina

> On Oct 12, 2019, at 10:30 PM, Chris Jones wrote: > > Most likely some command that previously worked is now failing to run, and > you need to first figure out what that is. Are there any crash reports, in > Console, that might help ? Have you checked to see if its any of the specific > pos

Re: Xfce4 Won't Launch in macOS Catalina

if its any of the specific possible causes mentioned in those pop ups ? Cheers Chris >> On 13 Oct 2019, at 1:39 am, Emily Jackson wrote: > I recently upgraded from Mojave to Catalina and redid my MacPorts > installation. I used Xfce4 as a WM under Mojave, but now I can’t get it

Xfce4 Won't Launch in macOS Catalina

I recently upgraded from Mojave to Catalina and redid my MacPorts installation. I used Xfce4 as a WM under Mojave, but now I can’t get it to launch while running Catalina. I have attached screen shots of the errors I get. I can use quartz-wm with X11, but I would like to get Xfce4 working

Re: The state of Catalina...

On Oct 10, 2019, at 18:05, Carlo Tambuatco wrote: > After some difficulties caused by upgrading to XCode 11, I'm sure a lot of > people are weary of upgrading to Catalina just yet, so could someone give a > timeframe for when it should be >95% safe for most macports users

  1   2   >