Re: Foiled Again

Thanks. nbsmtp is now installed. > On Oct 2, 2024, at 14:04, Ryan Carsten Schmidt > wrote: > > On Oct 2, 2024, at 00:13, Ryan Carsten Schmidt wrote: >> >>> On Oct 2, 2024, at 00:06, Michael Newman wrote: >>> >>> I did my best with the bug repor

Re: ffmpeg - Abort trap 6

ll do my best to file a report with Apple. Thanks for the help. > On Oct 3, 2024, at 11:14, Ryan Carsten Schmidt > wrote: > > On Oct 2, 2024, at 22:28, Michael Newman wrote: >> >> Sellotape:bin mnewman$ file /opt/local/lib/libavcodec.58.dylib >> /opt/local/lib/

Re: ffmpeg - Abort trap 6

on a 2019 Intel iMac upgraded to Sequoia (15.0) just two days ago. > On Oct 3, 2024, at 10:02, Ryan Carsten Schmidt > wrote: > > On Oct 2, 2024, at 20:50, Michael Newman wrote: >> >> Reason: tried: '/opt/local/lib/libavcodec.58.dylib' (not a mach-o file

Re: ffmpeg - Abort trap 6

ale 5. 9.100 / 5. 9.100 > libswresample 3. 9.100 / 3. 9.100 > libpostproc55. 9.100 / 55. 9.100 > > > > you might try doing this: > > sudo port -v rev-upgrade > > and of course, if you have not updated your ports lately, that would be step > 1 to

ffmpeg - Abort trap 6

Sorry to bother everyone again, I have a shell script that has been working fine for several years which uses ffmpeg to add audio to a video. It stopped working after migrating to the latest MacPorts. I can’t tell you the version of ffmpeg because: Sellotape:bin mnewman$ ffmpeg -version dyld[1

Re: Foiled Again

something that I really didn’t understand. Somehow it seems that tickets should generally be filed by people who actually know what they’re doing. -- https://www.mgnewman.com > On Oct 2, 2024, at 10:58 AM, Joshua Root wrote: > > Michael Newman wrote: > >> This morning I upg

Foiled Again

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

Re: Upgrade Dilemma

There already is a bug report (#70869). msmtp fails because building gas fails. > On Sep 30, 2024, at 09:20, Ryan Carsten Schmidt > wrote: > > On Sep 29, 2024, at 19:25, Michael Newman wrote: >> >> I’ve been migrating MacPorts both to new machines and as a result of

Upgrade Dilemma

I’ve been migrating MacPorts both to new machines and as a result of OS upgrades for many years now. It has always worked OK. The migration after the Sequoia upgrade on an MBA didn’t go so well; part of which was my fault. In the end I was able to migrate all ports except for msmtp. That parti

Re: Requested Ports

everyone’s time. On the plus side, I learned a lot and appreciate the help. Mike > On Sep 24, 2024, at 10:00, Joshua Root wrote: > > Michael Newman wrote: > >> I did what Arno suggested (thank you) and I now have a requested.txt file >> that, as far as I can tell, is a goo

Re: Requested Ports

ime. And your > TimeMachine requested.txt is the best you’ll get for the past. > > Any manually installed ports should already be marked as requested. > >> On Sep 23, 2024, at 06:05, Michael Newman via macports-users >> wrote: >> >> After yesterday’s partial

Requested Ports

After yesterday’s partially unsuccessful migration, I noticed that some ports that I had previously installed were missing after the migration, even though there was no error message during “sudo port migrate” on any of the missing ports. For example, I have several shell scripts that use “spong

Re: Migration Errors after Sequoia

Previously I reported. > On Sep 22, 2024, at 19:00, macports-users-requ...@lists.macports.org wrote: > > Attempting to migrate following Sequoia installation I got the following: > >Migration finished with errors. >The following ports could not be restored: > - ImageMagick > Sk

Re: Migration Errors after Sequoia

I’m sorry, but this is way beyond my ability. I have many questions. The guide to filing a ticket says "Clean and try again” • Does “clean” mean I should run "sudo port -f clean --all all” • Does “try again” mean I should run "sudo port migrate” again, or try to install each failed port separate

Migration Errors after Sequoia

This on a 15” M2 MBA 16/512 Attempting to migrate following Sequoia installation I got the following: Migration finished with errors. The following ports could not be restored: - ImageMagick Skipped because its dependency aom failed - ffmpeg Skipped because its dep

Migrating After Sonoma Install

Don’t worry. The migration went fine and, fingers crossed, everything works. However, it always amazes me how long this takes. I have only 13 ports in requested.txt. There are 148 ports in myports.txt. I get this, but I still find it amazing. On a 2019 Intel iMac, the migration started at 11:0

Warning: Error parsing file...

I recently had to reformat my boot drive, reinstall MacOS and restore from a CCC backup. After doing so I ran: sudo port -u upgrade outdated And received many warnings like this: ---> Scanning binaries for linking errors Warning: Error parsing file /opt/local/bin/msgcmp: Error opening or read

py310-markdown - Failed to fetch signature for archive

After: sudo port -u upgrade outdated Error: Failed to archivefetch py310-markdown: Failed to fetch signature for archive: The requested URL returned error: 503 Then: sudo port install py310-markdown ---> Computing dependencies for py310-markdown ---> Fetching archive for py310-markdown --->

Re: A simple request (MkHexGrid) turned into ...

On 2022-05-14, at 1:21 PM, Mojca Miklavec wrote: > On Sat, 14 May 2022 at 19:55, Michael wrote: >> On 2022-05-14, at 9:27 AM, Mojca Miklavec wrote: >>> On Sat, 14 May 2022 at 16:20, Michael wrote: >>>> >>>> So I thought I'd insta

Re: A simple request (MkHexGrid) turned into ...

On 2022-05-14, at 9:27 AM, Mojca Miklavec wrote: > On Sat, 14 May 2022 at 16:20, Michael wrote: >> >> So I thought I'd install a simple little hex map generator. Mkhexgrid. >> >> Hasn't been updated in years, should be simple, right? > ... > You can

Re: A simple request (MkHexGrid) turned into ...

ading it, and maybe one or two libraries. > > Marius > -- > Marius Schamschula > > > > >> On May 14, 2022, at 9:20 AM, Michael wrote: >> >> So I thought I'd install a simple little hex map generator. Mkhexgrid. >> >> Hasn't

A simple request (MkHexGrid) turned into ...

So I thought I'd install a simple little hex map generator. Mkhexgrid. Hasn't been updated in years, should be simple, right? Three versions of Python (37, 38, and 39) A full reinstall of X I mean, I can sort-of understand perl, one python, and ssl -- maybe it needed to rebuild something, and n

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

Thank you for the explanation. I tried to read the wiki page. Unfortunately, it is above my pay grade. I'll have to leave it to someone else to file a ticket. > On May 7, 2022, at 12:48, Joshua Root wrote: > > We have a wiki page with an in-depth explanation of what this warning means: >

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

When upgrading MacPorts this morning I noticed the following message wizzing by: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled: This right after: ---> Configuring xorg-libxcb I've never seen "Wimplic

Re: Changing the install location per OS version (was: During Migration to Arm64 mac, should I null out archs='x86_64' from installed ports list?)

On 2022-04-14, at 3:44 AM, Peter Serocka wrote: > A "meta-select" can easily provide /opt/local as symlink to the desired > default tree. Another tiny tool can set up $PATH for users at runtime, > providing the bin folders from multiple trees (PATH= ... > $(/opt/local/bin/mp_paths) ...) So

installing py310-jupyter fails: cannot import name 'StaticModule' from 'setuptools.config'

ortError: cannot import name 'StaticModule' from 'setuptools.config' (/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/setuptools/config/__init__.py) I've filed a ticket but was wondering if anyone on the list had any insight… thanks Mi

Re: Hello and my first question (regarding CMAKE_OSX_DEPLOYMENT_TARGET)

as spring for me will be very busy. Anyway, thanks again. I’ll be in touch. Kind regards, Michael > On 6 Oct 2021, at 00:09, Ryan Schmidt wrote: > > On Sep 28, 2021, at 05:09, Michael Monschau wrote: >> >> Background: >> I recently had the need to resort to some o

Re: certificate update for old Macs

On 2022-01-03, at 4:12 PM, Richard L. Hamilton wrote: > The only problem with that or anything similar, is that unless you go to > quite a lot of work to just download rather than install the PEM file, and > convert it into something human readable WITHOUT installing it, and > investigate ev

Re: ffmpeg unexpectedly uninstalled

>> On 3 Jan 2022, at 11:54 pm, Michael Newman via macports-users >> wrote: >> >> When I periodically update MacPorts I also run: >> >> sudo port -f uninstall inactive > > Why are you using the -f option here. That could force something to happen >

ffmpeg unexpectedly uninstalled

When I periodically update MacPorts I also run: sudo port -f uninstall inactive This seemed to work fine until last month when ffmpeg was uninstalled. I reinstalled and forgot about it. But, it happened again yesterday: ---> Deactivating ffmpeg @4.4.1_1+gpl2 ---> Cleaning ffmpeg ---> Unins

Re: provide latest OS root certificates via port?

So I found this advice online for updating certs without having to worry about trusting expired old certs. 1. Visit https://letsencrypt.org/certs/isrgrootx1.pem to download the certificate, and save it in the Documents folder. 2. Open Terminal, paste this command, and press enter: sudo securit

Re: provide latest OS root certificates via port?

As a user who spent a week trying to figure out what was going on with more and more sites not working, making less of the information out there available to figure out how to solve the expired cert, it was really painful to find out that this was "known in advance", and worse, this implies that

Re: Error: Failed to build librsvg: command execution failed

> On Oct 13, 2021, at 20:28, Christopher Jones wrote: > > In the meantime if you are in a hurry installing macports clang 11 should > also fix things. I wasn't in a hurry, but I wanted to try this. It worked. Thank you very much. Mike

Re: Error: Failed to build librsvg: command execution failed

> On Oct 13, 2021, at 18:12, Lenore Horner wrote: > > Do you have /opt/local/bin/clang-mp-11? Axe:~ mnewman$ ls /opt/local/bin/clang-mp-11 ls: /opt/local/bin/clang-mp-11: No such file or directory > On Oct 13, 2021, at 19:31, Christopher Jones wrote: > > oh, and to be sure please first run

Error: Failed to build librsvg: command execution failed

Old 2010 MacBook Air on: 10.13.6 MacPorts: 2.7.1 CLTools: 10.1.0.0.1.1539992718 Here's the error: Error: Failed to build librsvg: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_librsvg/librsvg/ma

Re: Let's Encrypt DST Root CA X3 Expiration

e out how to make that change. Can anyone help me? On 2021-10-02, at 8:25 PM, raf wrote: > On Sat, Oct 02, 2021 at 08:06:27PM -0700, Michael wrote: > >> So, first, I want to say "Thank you" for this bit: >> >>> • From View menu select "Show Expired Ce

Re: Let's Encrypt DST Root CA X3 Expiration

27;t this done?) And I cannot find any good reason for expiring root certs. They explicitly have much longer lifespans than anything else, and this isn't the first time that root certs have gone poof. Off the list topic now. Thanks for your help. On 2021-10-02, at 8:32 PM, Ryan Schmidt wrote:

Re: Let's Encrypt DST Root CA X3 Expiration

clue where to even begin looking. And yes, I know that quantum factoring will eventually permit all of these certs to be forged, but until then, why not allow them, and even after that point, why not allow me to allow them? On 2021-10-02, at 7:52 PM, Ryan Schmidt wrote: > On Oct 2, 2021, at 10:5

Hello and my first question (regarding CMAKE_OSX_DEPLOYMENT_TARGET)

2. how to force the rebuilding from source using cmake of the openssl libraries via 'port install' Many thanks for any answers that yo can provide Kind regards, Michael web: www.brainydata.com

Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration

Today I finally installed Big Sur and followed the MacPorts migration guide. I don't see any errors; no failures to build. However, I did get seven of these warnings: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentall

Warning: cltversion:....

This happens both on a 2017 iMac running Catalina and a 2010 MBA running High Sierra. Every time I run "sudo port upgrade outdated" I get the message about the command line tools: "Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot determine the version." I follow

Re: Build servers offline due to failed SSD

I’d really love to know more about what you’re saying here. Up until I just read what you wrote, I thought SSDs were the savior of HDDs. Michael A. Leonetti As warm as green tea > 3/7/21 午後5:26、Dave Horsfall のメール: > > On Sat, 6 Mar 2021, Dave C via macports-users wrote: > >&g

Re: Build servers going offline due to inclement weather

Best mailing list ever? Michael A. Leonetti As warm as green tea On 2/17/21 10:58 PM, Dave Horsfall wrote: On Wed, 17 Feb 2021, Richard Bonomo TDS personal wrote: I work in Nuclear Fusion, as that is really the only truly long-term (centuries, millennia) way to power a technically advanced

Re: Warning: All compilers are either blacklisted or unavailable

On Jan 1, 2021, at 01:47, Ryan Schmidt wrote: > If you see this warning when doing actions other than > configuring/building/installing (such as when cleaning) ignore it. Maybe we > shouldn't even display the warning in those cases, though I'm not sure if > there's a good way for us to do that

Warning: All compilers are either blacklisted or unavailable

Some months ago I upgraded the OS on a remote 2010 MacBook (the white one) to High Sierra (10.13.16). After the upgrade I did the recommended MacPorts migration without problems. I don’t visit this machine very regularly, so only recently remembered to run port clean all after doing a selfupdat

Re: Using X11 for an older program

On 2020-12-25, at 7:27 PM, Peter West wrote: > Thanks for that, Michael. > > God bless you. I do my best to bring humor wherever I can, no matter how silly it may seem. > -- > Peter West > p...@pbw.id.au > “The Word was made flesh, he lived among us…” > >&g

Re: Using X11 for an older program

On 2020-12-25, at 5:10 PM, Ken Cunningham wrote: > > Oh, you have nothing to lose trying it. > > If it doesn’t work, just set it back. > > you can’t break anything. It’s just a computer, and it does what you tell it > to do. You'd be amazed at how that's no longer true. My iPhone refuses t

Re: Using X11 for an older program

ovides. i.e. -- my choice is either an 8 year old apple build, or a current Macport build. (If I'm wrong here, please tell me.) > > K > >> On Dec 21, 2020, at 7:01 PM, Michael wrote: >> >> OK. Next question: Is there any reason I cannot install libpng versi

Re: Using X11 for an older program

of dynamic libraries that you don't get a single specific buggy version, but the latest non-buggy version? On 2020-12-21, at 6:55 PM, Ken Cunningham wrote: >> On 2020-12-21, at 10:55 AM, Michael wrote: > This >> should be a simple one. I hope. >>> >>> I

Re: Using X11 for an older program

On 2020-12-21, at 10:55 AM, Michael wrote: > This should be a simple one. I hope. > > I just installed a program that was compiled against the release version of > mac's X11. Crashes on startup with this: > > dyld: launch, loading dependent libraries > > Dyld

Using X11 for an older program

This should be a simple one. I hope. I just installed a program that was compiled against the release version of mac's X11. Crashes on startup with this: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: /opt/X11/lib/libpng15.15.dylib What symbolic links do I n

Confused about build dependencies here

Ok, this seems ... odd. I didn't know about Supertux until I saw it mentioned, and figured it seemed like a good game. > bash-3.2# port install supertux > ---> Computing dependencies for supertux > The following dependencies will be installed: > boost > clang-9.0 > clang_select > cmake > g

More old upgrade issues (was: Re: Libgcc: new version won't deactivate the old version)

On 2020-12-04, at 6:24 PM, Ryan Schmidt wrote: > On Dec 4, 2020, at 02:58, Christopher Jones wrote: > >> That particular message can only occur if you have not updated your ports in >> a very long time, as the change that made libgcc a stub port happened >> several years ago now If you d

Libgcc: new version won't deactivate the old version

> ---> Computing dependencies for libgcc > The following dependencies will be installed: libgcc10 > Continue? [Y/n]: y > ---> Activating libgcc10 @10.2.0_3 > Error: Failed to activate libgcc10: Image error: > /opt/local/include/gcc/c++/algorithm is being used by the active libgcc port. > Plea

Removing all non-requested ports?

What's the command to remove non-requested ports again?

Re: Failure to compile Poppler - 10.5

These should take care of the vast majority of the poppler / GO-I issues https://github.com/macports/macports-ports/pull/8779 https://github.com/macports/macports-ports/pull/8780 I might have overlooked something. Please test / verify! - MLD On Wed, Oct 14, 2020, at 6:06 AM, Ryan Schmidt wrote:

Re: GTK3 upgrade issue on Mojave

Hi Greg - You need to reinstall the "at-spi2-atk" port. For example: {{{ sudo port -f uninstall at-spi2-atk sudo port install at-spi2-atk sudo port clean gtk3 sudo port upgrade gtk3 }}} This worked for me recently. I hope it does for you too! - MLD On Wed, Oct 14, 2020, at 10:41 AM, Greg Earle wro

Re: Apple ARM binary codesign issue

Excellent! Thanks for the heads-up. I've downloaded this file and will get it installed and start testing later today. - MLD On Tue, Sep 29, 2020, at 2:47 PM, Gary Palter wrote: > Apple today released Xcode 12.2 beta 2 and the Release Notes state >> Apple Clang Compiler >> Resolved Issues >> *

Re: Apple ARM binary codesign issue

Let's try this again from my MP email so that it gets to lists ... sorry for duplicate emails! I've finally gotten to the point of working out a hack solution. One can -not- modify '/usr/bin' without a lot of effort. But, one can modify '/Applications/Xcode[-beta].app/Contents/Developer/Toolcha

Re: Apple ARM binary codesign issue

ntirely work with those built using 12.2beta? H Thx! - MLD On Tue, Sep 22, 2020, at 2:58 PM, Ryan Schmidt wrote: > > > On Sep 22, 2020, at 13:29, Michael Dickens wrote: > > > % codesign -v - --ignore-resources > > /opt/local/Library/Frameworks/Python.

Apple ARM binary codesign issue

There has been some discussion about the recent change Apple made for macOS 11.0beta7 for ARM Mac only (-not- Intel Mac at this time); we in MP-land had some on this PR < https://github.com/macports/macports-ports/pull/8328 >. As pointed out, a better venue for discussion would be these lists.

Re: Failed to build graphviz: command execution failed

> On Sep 4, 2020, at 07:27, Ryan Schmidt wrote: > > It's especially non-straightforward when Apple breaks things, like removing > the receipt of the command line tools periodically, which is what that > problem hotlist entry is about. OK, now I understand why what I tried didn't work and why y

Re: Failed to build graphviz: command execution failed

> On Sep 4, 2020, at 05:51, Ryan Schmidt wrote: > >> Warning: cltversion: For a possible fix, please see: >> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt >> > > Follow the instructions at that URL. Thank you. Graphvi

Re: Failed to build graphviz: command execution failed

> On Sep 3, 2020, at 22:01, Ryan Schmidt wrote: > > There have been a few other reports lately of graphviz build failures for > other reasons; if you're experiencing a graphviz build failure, see if one of > them applies. I spent some time searching around, but all I found were other instanc

Failed to build graphviz: command execution failed

I realize that there is a ticket on this (57137) that has been open for quite some time. However, this is the first time I've seen this error. What concerns me is this: MrMuscle:~ mnewman$ port rdependents graphviz The following ports are dependent on graphviz: vala gssdp gupnp

Port that converts heic/heif?

What port will convert heic/heif to png or mpg? I see (port search heif) that there is a library, but I could not find any program that used it --- This message was composed with the aid of a laptop cat, and no mouse

Re: Is It Safe To Use reclaim?

Thanks to all for the clearly written suggestions. At this point I don't understand most of this well enough to have any confidence that I won't mess things up worse than they already are. I'm not much concerned about storage, so I think my best course of action here is to disable the reclaim r

Re: Is It Safe To Use reclaim?

> On May 3, 2020, at 21:28, Ryan Schmidt wrote: > > Look at the output of "port installed unrequested". If you see any port in > that list that you actually do want, indicate that by running "sudo port > setrequested thePortName". This is easier said than done. The output of port installed un

Is It Safe To Use reclaim?

Late last year I ran reclaim for the first time. It was somewhat of a disaster because it removed ports that I actually wanted and I ended up having to completely reinstall MacPorts. Since then I have been afraid to use it again. As far as I can tell there is no way for me to be sure that ports

Re: swig4 vs swig

Hi Leo - We just merged in changes that swap which SWIG provides "bin/swig" ... so, if you update your ports, then SWIG4 will be providing this binary. Hopefully that addresses your issue! - MLD On Thu, Apr 2, 2020, at 12:57 PM, Singer, Leo P. (GSFC-6610) wrote: > Hi, > > I noticed that the "sw

Re: EXSi

> Did you try a current version of macOS on top of ESXi? I'd be curious if > anyone has tested this setup and how is the performance. What is ESXi? --- Entertaining minecraft videos http://YouTube.com/keybounce

Filing suit against legal abusers

On 2020-02-15, at 11:28 AM, Jeffrey Walton wrote: > Checkout Walton vs Network > Solutions filed in Montgomery County, MD. PLEASE, tell us more. --- Entertaining minecraft videos http://YouTube.com/keybounce

Re: Dependency untangling riddle

On 2020-02-05, at 11:31 AM, Vincent wrote: > > In my case, I delay the bump somewhat because I know most of my ports depend > not only on the language itself, but also on various py-xxx librairies, the > update of which often comes pretty late after the new Python version has been > release

Re: Git question

On 2020-01-09, at 2:33 PM, Steven Smith wrote: > Me too. We’re discussing MacPorts-relevant git commands in > https://github.com/macports/macports-ports/pull/6106 . > > Easiest, most destructive to local: > > # save all local files changed outside the git repo > > git fetch --all > git reset

Re: /usr/local/bin/lynx: Bad CPU type in executable

On Dec 23, 2019, at 21:06, Ryan Schmidt wrote: > > As far as I know, yes it does, by default, which is why, if you install them > to their default locations, you should only use one package manager and > uninstall the other to prevent conflicts. I supposed that in an ideal world where a single

Re: /usr/local/bin/lynx: Bad CPU type in executable

On Dec 22, 2019, at 22:04, Ryan Schmidt wrote: > Since reclaim prints a list of the ports it will remove, it seems like it's > up to you to verify that there isn't anything on the list that you want to > keep before confirming the action, and it should not be surprising or scary > to you that

Re: /usr/local/bin/lynx: Bad CPU type in executable

More of the story. When I got up this morning I found that a couple of scripts that I run overnight had failed with error 127. It seems that the scripts couldn’t find curl. So I checked, and sure enough, curl was missing. No worries, I can reinstall it. And then I wonder, what else is missing?

Re: /usr/local/bin/lynx: Bad CPU type in executable

On Dec 21, 2019, at 19:00, Bill Cole wrote: > > Is it possible that your /usr/local/bin/lynx is a relic of some ancient > time and a different machine? Yes. Here’s the whole story: I wanted to use the lynx trace facility and had forgotten that sometime in the distant past I had installed lynx.

/usr/local/bin/lynx: Bad CPU type in executable

Sorry. I used the wrong version of Lynx…. MacPorts Version: 2.6.2 macOS 10.15.2 I installed lynx today and received the error message: /usr/local/bin/lynx: Bad CPU type in executable Is there anything I can do about this? MacPorts is up to date: MrMuscle:~ mnewman$ sudo port upgrade outdated

/usr/local/bin/lynx: Bad CPU type in executable

MacPorts Version: 2.6.2 macOS 10.15.2 I installed lynx today and received the error message: /usr/local/bin/lynx: Bad CPU type in executable Is there anything I can do about this? MacPorts is up to date: MrMuscle:~ mnewman$ sudo port upgrade outdated Nothing to upgrade. ---> Scanning binaries

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

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

2 ---> Activating ffmpeg @4.2.1_2+gpl2 ---> Cleaning ffmpeg ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. > On Dec 14, 2019, at 06:49, Andrew Udvare wrote: > > > > Sent fro

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

Sharing free space?

> If you have room on your main disk and it is APFS-formatted, you can easily > create a new volume in Disk Utility that will share the free space, and if it > doesn't work out, you can delete the volume later. I'd like to know how to get two volumes to share free space if they are on the same

Re: mysql57, boost and postgresql84

I don’t know if it helps at all, but on October 24th I did the first steps of MacPorts migration in anticipation of installing Catalina. I never did install Catalina, but I saved the myports.txt and requested.txt files. They are here: https://pastebin.com/cxM85Dq6

Re: mysql57, boost and postgresql84

> On Nov 7, 2019, at 06:34, Ryan Schmidt > wrote: > > If `port installed requested` shows things that you don't actually want, tell > MacPorts by marking them as not requested: > > sudo port unsetrequested portname1 portname2 ... > >

Re: mysql57, boost and postgresql84

Thank you. I’m slowly (very slowly) beginning to pull all this together. > On Nov 7, 2019, at 06:34, Ryan Schmidt wrote: > > If `port installed requested` shows things that you don't actually want, tell > MacPorts by marking them as not requested: > > sudo port unsetrequested portname1 portnam

Re: mysql57, boost and postgresql84

On Nov 6, 2019, at 19:00, Chris Jones wrote: > You could also try rerunning > >> sudo port reclaim > > which does a number of tasks aimed at removing stuff you do not need. Thank you for that. It returned a massive list of unused and unneeded ports including this: > Found 1156 files (total 4.

Re: mysql57, boost and postgresql84

ports, there are always several that I don’t recognize, such as: boost, gcc7, mysql57-server, and nss. But, there they are. > On Nov 6, 2019, at 13:09, Wahlstedt Jyrki wrote: > > > >> Michael Newman via macports-users > <mailto:macports-users@lists.macports.org>

Re: mysql57, boost and postgresql84

Thanks Ryan. I have reactivated boost. The config log is here: https://pastebin.com/VdiZHn4k <https://pastebin.com/VdiZHn4k> Mike > On Nov 6, 2019, at 12:30, Ryan Schmidt wrote: > > > > On Nov 5, 2019, at 19:39, Michael Newman wrote: > >> Maybe I’m just

mysql57, boost and postgresql84

Maybe I’m just not smart enough to play with MacPorts…. This on an iMac still running Mojave. This morning I did selfupdate and upgrade outdated with the following result: Error: mysql57 cannot be built while boost is active. Error: Please forcibly deactivate boost, e.g. by running: Error: Error

Re: postgresql83-server - Further Woes

The only solution offered by the developer of DetectX was to tell DetectX to ignore changes to macports plist files. That seems to defeat the purpose of DetectX. DetectX is supposed to warn you of possible nefarious changes to your system. Choosing to ignore a possible problem is no solution.

Re: qt5-qt3d complains about system assimp missing

Did exactly this for ticket #59601. Michael A. Leonetti As warm as green tea On 11/4/19 3:59 PM, Ryan Schmidt wrote: On Nov 4, 2019, at 14:25, Michael A. Leonetti wrote: My qt5 installation keeps complaining about missing linking files so I am trying to reinstall and qt5-q3d complains about

qt5-qt3d complains about system assimp missing

3d/work/qt3d-everywhere-src-5.12.5" && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- -system-assimp :info:configure Exit code: 3 -- Michael A. Leonetti As warm as green tea

Re: postgresql83-server - Further Woes

May. He posted > the following to his Slack community late last week: > > 1. The older versions of DetectX (not DetectX Swift) are no longer being > offered for download on the Sqwarq site. > 2. The older versions will continue to receive maintenance updates and search > defin

Re: postgresql83-server - Further Woes

I have uninstalled the port, but DetectX keeps telling me that the plist has been changed. If it only happened once when I still had the port installed I’d say, yeah, problem solved. But when the plist keeps getting changed after the port has been uninstalled I have to wonder what’s happening.

Re: postgresql83-server - Further Woes

Thank you. Locate did not find this plist on the boot volume. It did find it in a Carbon Copy Cloner SafetyNet directory on a backup drive. MrMuscle:home mnewman$ locate org.macports.postgresql83-server.plist /Volumes/Clorox2/_CCC SafetyNet/2019-10-30 (October 30) 01-00-52/Library/LaunchDaemons

  1   2   3   >