Migrating After Sonoma Install

[Michael Newman via macports-users]

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:00AM. When I went to bed at 
9:00PM it was still cranking away. I have no idea how long it actually took. 
But, at least 10 hours. This also amazes me.

On the other hand, my M1 MBA also has 13 in requested.txt and 148 in 
myports.txt. On this machine the post-Sonoma migration took about six hours. 
Still a long time, but somewhat less amazing.

Thanks to everyone who makes all this stuff possible.

Mike Newman
Korat, Thailand

smime.p7s
Description: S/MIME cryptographic signature

Warning: Error parsing file...

[Michael Newman via macports-users]

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 reading file
Warning: Error parsing file /opt/local/bin/msgcomm: Error opening or reading 
file


What should I do about this?

Mike Newman
Korat, Thailand

py310-markdown - Failed to fetch signature for archive

[Michael Newman via macports-users]

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
--->  Attempting to fetch py310-markdown-3.3.7_0.darwin_21.noarch.tbz2 from 
https://packages.macports.org/py310-markdown
--->  Attempting to fetch py310-markdown-3.3.7_0.darwin_21.noarch.tbz2.rmd160 
from https://packages.macports.org/py310-markdown
Error: Failed to archivefetch py310-markdown: Failed to fetch signature for 
archive: The requested URL returned error: 503
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-markdown/py310-markdown/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port py310-markdown failed

No idea what to do about this, but the error is preventing other outdated ports 
from upgrading.

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

[Michael Newman via macports-users]

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: 
> 
> 
> The executive summary for end users is that this is something that the port's 
> maintainer needs to look into, so you can file a ticket about it, but it may 
> or may not indicate a significant problem.
> 
> - Josh
> 

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

[Michael Newman via macports-users]

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 "Wimplicit" used before and wondered what it meant. When I 
searched I got:

Your search - -Wimplicit - did not match any documents.

Can someone please explain what this warning is about and just what "Wimplicit" 
means?

Mike Newman
Korat, Thailand

Re: ffmpeg unexpectedly uninstalled

[Michael Newman via macports-users]

I'm using the -f option because I copied it from some recommendation I read 
somewhere. I'm not smart enough to figure things like this out myself so I 
usually rely on what I find by searching. For years I just ran:

sudo port selfupdate
sudo port upgrade outdated

But then I read somewhere that to remove unneeded junk I should also run:

sudo port -f clean --all all
sudo port -f uninstall inactive
sudo port uninstall leaves

I guess I found out that was wrong. What should I run when I do my periodic 
selfupdate?

And, yes, I'm sure there was not another version of ffmpeg installed. I have a 
shell script that runs daily which uses ffmpeg. When I ran the script after 
updating macports there was an error message about there being no 
/opt/local/bin/ffmpeg. After I installed ffmpeg the script ran OK.

> On Jan 4, 2022, at 08:05, Chris Jones  wrote:
> 
> 
> 
>> 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 
> that might not be a good idea. Generally speaking you should not use it as a 
> matter of course, and only when you really need to, for some specific reason.
> 
>> 
>> 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
>> --->  Uninstalling ffmpeg @4.4.1_1+gpl2
>> --->  Cleaning ffmpeg
>> 
>> So, I reinstalled and tried:
>> 
>> MrMuscle:~ mnewman$ sudo port -f uninstall inactive
>> Password:
>> Error: No ports matched the given expression
>> 
>> I checked the "requested" ports here from a file I created for the Big Sur 
>> migration:
>> 
>> MrMuscle:~ mnewman$ ls -la /Users/mnewman/Desktop/requested.txt
>> -rwxrwxrwx@ 1 mnewman  staff  359 Jun  8  2021 
>> /Users/mnewman/Desktop/requested.txt*
>> MrMuscle:~ mnewman$ grep ffmpeg /Users/mnewman/Desktop/requested.txt
>> ffmpeg
>> 
>> So, ffmpeg is definitely a requested port.
>> 
>> I'm baffled. What's going on here?
> 
> Are you sure you don’t still have a version of ffmpeg installed ? The above 
> only temoved inactive ports, it did not uninstall any active ports.
> 
>> 
>> Mike Newman
>> Korat, Thailand
>> 

ffmpeg unexpectedly uninstalled

[Michael Newman via macports-users]

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
--->  Uninstalling ffmpeg @4.4.1_1+gpl2
--->  Cleaning ffmpeg

So, I reinstalled and tried:

MrMuscle:~ mnewman$ sudo port -f uninstall inactive
Password:
Error: No ports matched the given expression

I checked the "requested" ports here from a file I created for the Big Sur 
migration:

MrMuscle:~ mnewman$ ls -la /Users/mnewman/Desktop/requested.txt
-rwxrwxrwx@ 1 mnewman  staff  359 Jun  8  2021 
/Users/mnewman/Desktop/requested.txt*
MrMuscle:~ mnewman$ grep ffmpeg /Users/mnewman/Desktop/requested.txt
ffmpeg

So, ffmpeg is definitely a requested port.

I'm baffled. What's going on here?

Mike Newman
Korat, Thailand

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

[Michael Newman via macports-users]

> 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

[Michael Newman via macports-users]

> 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 `sudo port sync` t make sure your ports 
> are fully up to date….

Axe:~ mnewman$ sudo port sync
Password:
--->  Updating the ports tree
Error: Synchronization of the local ports tree failed doing rsync
port sync failed: Synchronization of 1 source failed


> On Oct 13, 2021, at 19:30, Christopher Jones  wrote:
> 
> Please run `port info librsvg rust` and post what that returns.

Axe:~ mnewman$ port info librsvg rust
librsvg @2.52.1_1 (graphics, gnome)
Variants: quartz, universal, x11

Description:  GNOME implementation of rsvg.
Homepage: https://wiki.gnome.org/Projects/LibRsvg

Extract Dependencies: xz
Build Dependencies:   pkgconfig, rust, cargo
Library Dependencies: glib2, cairo, pango, gdk-pixbuf2, libxml2, vala,
  gobject-introspection
Platforms:darwin
License:  (GPL-2+ or LGPL-2+)
Maintainers:  Email: dev...@macports.org, GitHub: dbevans
  Email: masc...@macports.org, GitHub: mascguy
  Policy: openmaintainer
--
rust @1.55.0_3 (lang, devel)
Sub-ports:rust-compiler-wrap, rust-src

Description:  Rust is a curly-brace, block-structured expression
  language. It visually resembles the C language family, but
  differs significantly in syntactic and semantic details.
  Its design is oriented toward concerns of "programming in
  the large", that is, of creating and maintaining
  boundaries -- both abstract and operational -- that
  preserve large-system integrity, availability and
  concurrency.
Homepage: https://www.rust-lang.org

Build Dependencies:   git, cmake, cctools, python39, openssl, pkgconfig, ninja,
  gmake
Library Dependencies: libffi, libgit2, openssl
Platforms:darwin
License:  (MIT or Apache-2) and BSD and zlib and NCSA and Permissive
Maintainers:  Email: g...@macports.org, GitHub: g5pw
  Email: herby.gil...@gmail.com, GitHub: herbygillot
  Policy: openmaintainer

Error: Failed to build librsvg: command execution failed

[Michael Newman via macports-users]

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/main.log
 for details.

I looked at the log, but it's above my pay grade.

Log is here: https://pastebin.com/ncBFApfH 

A bug report (#56192 ) was opened on 
this but closed:  Resolution: → fixed

Quite a few ports depend on librsvg:

Axe:~ mnewman$ port echo depends:librsvg | wc -l
  65

I have no idea what to do next.

Mike Newman
Korat, Thailand

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

[Michael Newman via macports-users]

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

It was found in the following logs:

lynx2.8.9rel.1/config.log
clamav-0.103.2/config.log
anholt-libepoxy-d51a358/config.log
ghostpdl-9.54.0/config.log
graphviz-2.40.1/config.log
gst-libav-1.16.2/config.log
gst-plugins-bad-1.16.2/config.log

I have no idea what a "Wimplicit-function-declaration" is. I tried to search 
around, but was unable to enlighten myself. I gather it has something to do 
with C; about which I know nothing. If this warning is explained somewhere, 
please provide me with a link.

Do I need to do something about these, or are they ignorable?

Mike Newman
Korat, Thailand

Warning: cltversion:....

[Michael Newman via macports-users]

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 the instructions here:

https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 


This is the iMac:

MrMuscle:volumes mnewman$ touch 
/tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
MrMuscle:volumes mnewman$ softwareupdate -l
Software Update Tool
Finding available software
Software Update found the following new or updated software:
* Label: Command Line Tools for Xcode-12.4
Title: Command Line Tools for Xcode, Version: 12.4, Size: 440392K, 
Recommended: YES,
MrMuscle:volumes mnewman$ rm 
/tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
MrMuscle:volumes mnewman$ softwareupdate -l
Software Update Tool
Finding available software
No new software available.
MrMuscle:volumes mnewman$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 12.4.0.0.1.1610135815
volume: /
location: /
install-time: 1622628917
groups: com.apple.FindSystemFiles.pkg-group

But it doesn't seem to "stick" and the next time it shows up again.

What am I doing wrong?

Mike Newman
Korat, Thailand

Re: Warning: All compilers are either blacklisted or unavailable

[Michael Newman via macports-users]

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

> 
> File a bug report and provide as much information as possible about your OS 
> version, Xcode version, and which compiler got used.

As always, thank you for the clear and comprehensive explanation written in 
such a way that even I can understand it. 

Happy New Year

Mike Newman
Korat, Thailand

Warning: All compilers are either blacklisted or unavailable

[Michael Newman via macports-users]

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 selfupdate/upgrade. Both of the latter ran without 
error, but the clean produced many like the following:

--->  Cleaning wxsvg
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option

I’m not sure how to deal with this. There’s no indication that any ports failed 
to build, but the presence of the warning bothers me. I don’t see any recent 
list mentions of this issue.

Is there anything that I should do?

(Sorry for the New Year’s Eve interruption.)

Mike Newman
Korat, Thailand

Re: Failed to build graphviz: command execution failed

[Michael Newman via macports-users]

> 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 you need the little 
"touch" trick.

Thanks.

Re: Failed to build graphviz: command execution failed

[Michael Newman via macports-users]

> 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. Graphviz built after updating the command line tools.

I'm still not sure why this didn't work:

MrMuscle:~ mnewman$ xcode-select --install
xcode-select: error: command line tools are already installed, use "Software 
Update" to install updates

But, after doing that, Software Update didn't find any updates available. 

My browser history shows that after graphviz failed to build I visited:

> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> 
But my bash history doesn't go back far enough to show me what went wrong the 
first time I tried that.

Thanks again for your help. As you may have discovered, I need primary school 
level instructions.

Mike

Re: Failed to build graphviz: command execution failed

[Michael Newman via macports-users]

> 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 instance of 
graphviz related tickets, the details of which are beyond my ability to 
comprehend.

When graphviz builds, I get this warning:

Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot 
determine the version.
Warning: cltversion: For a possible fix, please see: 
https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

So, I run this:

MrMuscle:~ mnewman$ xcode-select --install
xcode-select: error: command line tools are already installed, use "Software 
Update" to install updates

But, that doesn't fix the "MacPorts cannot determine the version" warning. 

Xcode is at Version 11.7 (11E801a)

The details:

--->  Computing dependencies for graphviz
--->  Fetching archive for graphviz
--->  Attempting to fetch 
graphviz-2.40.1_3+pangocairo+x11.darwin_19.x86_64.tbz2 from 
http://jog.id.packages.macports.org/macports/packages/graphviz
--->  Attempting to fetch 
graphviz-2.40.1_3+pangocairo+x11.darwin_19.x86_64.tbz2 from 
https://kmq.jp.packages.macports.org/graphviz
--->  Attempting to fetch 
graphviz-2.40.1_3+pangocairo+x11.darwin_19.x86_64.tbz2 from 
http://nue.de.packages.macports.org/graphviz
--->  Building graphviz
Error: Failed to build graphviz: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_graphviz/graphviz/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

The log file referred to is rather large (almost 1MB) and incomprehensible to 
me.

I don't know how to proceed from here.

Failed to build graphviz: command execution failed

[Michael Newman via macports-users]

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
gupnp-igd
  libnice
gstreamer1-gst-plugins-bad
libproxy
  glib-networking
libsoup
  gstreamer1-gst-plugins-good
  neon
librsvg
  ffmpeg
chromaprint

I use both gstreamer and ffmpeg regularly.

Does this mean that these may stop working until the graphviz problem is fixed?

If so, what can I do?

Mike Newman
Korat, Thailand

Re: Is It Safe To Use reclaim?

[Michael Newman via macports-users]

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 reminder until I have a better grasp of MacPorts. 
(Which, given my age and cognitive ability is probably never.)

Thanks again for your time.

Re: Is It Safe To Use reclaim?

[Michael Newman via macports-users]

> 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 unrequested has 461 items; most of which I don't 
recognize. Lynx is there and I know I want that. But the first port listed is 
a52dec. I don't know what that is, or what it does or whether or not I want it. 
I also see atk, automake, bison, harfbuzz, and many others which mean nothing 
to me.

Sure, I can do some research to figure out what each of these does, but then I 
will still have no idea whether or not I want them. Did I request some in the 
distant past? Am I still using them? No idea.

It seems to be a very daunting task. 

Is It Safe To Use reclaim?

[Michael Newman via macports-users]

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 that I have 
actually requested have been so flagged:

MrMuscle:~ mnewman$ port installed | grep lynx
  lynx @2.8.9rel.1_1+ssl (active)
MrMuscle:~ mnewman$ port installed requested | grep lynx
MrMuscle:~ mnewman$ 

I know that I can use setrequested to flag a port, but how can I know on which 
ports I need to do that?

The only way I can think of is to manually go through the list of installed 
ports, try to recognize the ones I've requested, check to see if they are so 
flagged and, if not, manually flag them.

Is there an easier way?

Mike Newman
Korat, thailand

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

[Michael Newman via macports-users]

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 package manager had all 
available packages and where broken packages were fixed quickly, that might 
work.

Unfortunately, this is not the case.

I have been using ffmpeg from MacPorts daily for several years. It broke with 
the release of Catalina. A ticket has been filed (59750). But, I can’t wait for 
it to get fixed. I need it every day. The only alternative I could find was 
avconv, which MacPorts doesn’t have. I don’t know how long it will be before 
ffmpeg works again.

However, I do have some experience. I used to use sunwait. It broke. I filed a 
ticket (51700). It took two years before sunwait was fixed. In the meantime, I 
had to find an alternative.

I’m not trying to be critical here. I understand the situation. This is all 
done by volunteers who have way more smarts and ability than I have. 

The reality is that people are going to use more than one package manager if 
the need arises. 

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

[Michael Newman via macports-users]

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 MacPorts does then remove the ports it said it would remove if 
> you allow it to do 
> so.

No, you’re absolutely right. The scary thing is how stupid and sloppy I seem to 
be.

On the other hand, the list of ports to be removed was huge. How am I to know 
if it’s OK to remove something like popt?

> And more generally, remove anything you have in /usr/local.

Isn’t that where Homebrew installs its stuff? I prefer to use MacPorts, but 
sometimes I need something that doesn’t have a port, like avconv, growlnotify 
and others.

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

[Michael Newman via macports-users]

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? I try: 

  port list installed 

and find that there are only two ports: lynx which I installed yesterday and 
curl which I had just installed.

What happened? Well, just before installing lynx I did a selfupdate and 
upgrade. At the end of the upgrade I was invited to do a reclaim. So, I did. 
Now, admittedly, reclaim presented me with a huge long list of stuff it was 
going to remove.  Whenever I look at all the ports on my machine I only 
recognize a handful; most are things I know nothing about and never requested, 
they’re just stuff that the ports I want depend on. Fair enough. 

However, it would be nice if reclaim warned you that it was working with an 
empty or near empty requested file.

I’m sure that as part of the Catalina migration I did:

  sudo port unsetrequested installed
  xargs sudo port setrequested < requested.txt

Either I forgot, or it didn’t work. In any event, apparently every installed 
port was removed.

Fortunately, I still had the myports.txt file, so I was able to use:

  sudo ./restore_ports.tcl myports.txt

And get everything back.

I find it a little scary that a few simple mistakes can cause such havoc.

Mike Newman
Korat, Thailand

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

[Michael Newman via macports-users]

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. So, I installed it via MacPorts. But, when I 
first ran it I got the Bad CPU error.

That seemed wrong since I had just installed it so I tried both locate lynx and 
which -a lynx. But both of those only found: /usr/local/bin/lynx.

This was even more confusing.

As suggested, I deleted the old version of lynx and now both which and locate 
find the MacPorts version.

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

[Michael Newman via macports-users]

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
Nothing to upgrade.
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

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

[Michael Newman via macports-users]

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 for linking errors
--->  No broken files found.
--->  No broken ports found.

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

[Michael Newman via macports-users]

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/ticket/59390 

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

[Michael Newman via macports-users]

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

It seems to be a MacPorts issue.

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

[Michael Newman via macports-users]

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

[Michael Newman via macports-users]

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 is a bug in ffmpeg.
> 
> Sent from my iPhone

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

[Michael Newman via macports-users]

I’m not positive, but I believe it was built from source. This is what I got 
when I removed and reinstalled it:

MrMuscle:bin mnewman$ sudo port install ffmpeg
--->  Computing dependencies for ffmpeg
--->  Fetching archive for ffmpeg
--->  Attempting to fetch ffmpeg-4.2.1_2+gpl2.darwin_19.x86_64.tbz2 from 
http://lil.fr.packages.macports.org/ffmpeg
--->  Attempting to fetch ffmpeg-4.2.1_2+gpl2.darwin_19.x86_64.tbz2 from 
http://cph.dk.packages.macports.org/ffmpeg
--->  Attempting to fetch ffmpeg-4.2.1_2+gpl2.darwin_19.x86_64.tbz2 from 
http://jog.id.packages.macports.org/macports/packages/ffmpeg
--->  Fetching distfiles for ffmpeg
--->  Verifying checksums for ffmpeg
--->  Extracting ffmpeg
--->  Applying patches to ffmpeg
--->  Configuring ffmpeg
--->  Building ffmpeg
--->  Staging ffmpeg into destroot
--->  Installing ffmpeg @4.2.1_2+gpl2
--->  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 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.
>> 
>> However, after migrating MacPorts to the Catalina version, it fails:
>> 
>> ./skyvideo.sh: line 38:  5438 Donecat $ipath
>>  5439 Segmentation fault: 11  | /opt/local/bin/ffmpeg -f image2pipe 
>> -framerate 10 -vcodec mjpeg -i - -vcodec libx264 -preset veryslow 
>> -hide_banner -loglevel panic -r 10 -crf 28 -y -pix_fmt yuv420p "$vfile" >> 
>> "$log"
> 
> Is this a premade binary or built from source? If it's a binary you should 
> try building from source.
> 
> I'm not sure MacPorts provides a binary of ffmpeg.
> 
> Andrew

ffmpeg Fails After MacPorts Migration to Catalina Version

[Michael Newman via macports-users]

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
  5439 Segmentation fault: 11  | /opt/local/bin/ffmpeg -f image2pipe 
-framerate 10 -vcodec mjpeg -i - -vcodec libx264 -preset veryslow -hide_banner 
-loglevel panic -r 10 -crf 28 -y -pix_fmt yuv420p "$vfile" >> "$log"

Version information:

MrMuscle:bin mnewman$ port -v
MacPorts 2.6.2
MrMuscle:bin mnewman$ ffmpeg -version
ffmpeg version 4.2.1 Copyright (c) 2000-2019 the FFmpeg developers

The MacOS Problem Report is here:

https://pastebin.com/G6cN0t7Y 

I had saved a pre-migration version of ffmpeg that I know worked, but it now 
fails in the same way.

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

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 

https://pastebin.com/8sJafzKa 

This is before I did the reclaim that removed clamav.

> On Nov 9, 2019, at 09:40, Ryan Schmidt  wrote:
> 
> 
> 
> On Nov 8, 2019, at 20:31, Chris Jones  wrote:
> 
>> On 9 Nov 2019, at 1:39 am, Ryan Schmidt wrote:
>> 
>>> If you ran `sudo port install clamav`, and it was not already installed, 
>>> MacPorts should have marked it as requested. If clamav was automatically 
>>> installed as a dependency of something else, then it would not have been 
>>> marked requested.
>> 
>> That sounds like something we should fix to me. Is it not reasonable to 
>> expect the port in this case, even if it was previously installed as a 
>> dependency, to still be marked as requested in this case, as that is what 
>> the user did by asking for it to be installed. The fact it already was 
>> shouldn’t matter in terms of marking it as requested ?
> 
> If you mean that running `sudo port install` on a port that is already 
> installed should mark it as requested, then that's 
> https://trac.macports.org/ticket/55085.
> 

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

> 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 ...
> 
> Then `sudo port reclaim` will be able to uninstall them, if they're not 
> needed for anything else you've installed. Reclaim won't uninstall things it 
> thinks you want.
This set a little trap for me. For some reason, clamav, which I did request, 
was not shown as requested. So, when I ran reclaim, it was removed. I was 
puzzled at first when freshclam started to fail. I’ve reinstalled clamav now 
and all is well. Is there some reason why clamav would not be flagged as 
requested?

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

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 portname2 ...
> 
> Then `sudo port reclaim` will be able to uninstall them, if they're not 
> needed for anything else you've installed. Reclaim won't uninstall things it 
> thinks you want.

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

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.80 GiB) that are no longer needed and can be 
> deleted.
> [l]ist/[d]elete/[K]eep: d
> Deleting...
> This appears to be the first time you have run 'port reclaim'. Would you like 
> to be reminded to run it every two weeks? [Y/n]: y

I’m so good about updating and upgrading regularly. I can’t believe I missed 
this.

Still learning.

Mike

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

I have no idea why I have postgreSQL:

MrMuscle:~ mnewman$ sudo port dependents postgresql84
postgresql84-server depends on postgresql84
MrMuscle:~ mnewman$ sudo port dependents postgresql84-server
postgresql84-server has no dependents.

I didn’t request it. I don’t use it.

When I list requested 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>> kirjoitti 6.11.2019 kello 3.39:
>> 
>> Error: Failed to configure postgresql84, consult 
> 
> Hi,
> if you need PostgreSQL, this version has been EOL’d already for many years, 
> current version is 12. Documentation for upgrade here: 
> https://www.postgresql.org/docs/current/pgupgrade.html 
> <https://www.postgresql.org/docs/current/pgupgrade.html>…
> 
> 
> !
> ! Jyrki
> 

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

Thanks Ryan.

I have reactivated boost.

The config log is here: 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 not smart enough to play with MacPorts….
> 
> Normally things work pretty well. Sometimes you'll encounter errors. 
> Unfortunately we'll have to deal with them on a case by case basis!
> 
> 
>> 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: sudo port -f deactivate boost
>> Error:
>> Error: Then try again. You can reactivate boost again later.
>> 
>> I deactivated boost as instructed and ran upgrade outdated again.
>> 
>> This time mysql built OK, but I got:
> 
> Ok great. Don't forget to reactivate boost. (sudo port activate boost)
> 
> 
>> Error: Failed to configure postgresql84, consult 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
>> Error: Failed to configure postgresql84: configure failure: command 
>> execution failed
>> 
>> The config.log file referred to is just under 1000 lines long. Is there 
>> anything in particular I should look for?
> 
> Please show us this file. You could file a bug report in our issue tracker 
> and attach it. Or you could upload it to a paste service (perhaps 
> https://paste.macports.org ) and send us the URL.
> 

mysql57, boost and postgresql84

[Michael Newman via macports-users]

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: sudo port -f deactivate boost
Error:
Error: Then try again. You can reactivate boost again later.

I deactivated boost as instructed and ran upgrade outdated again.

This time mysql built OK, but I got:

Error: Failed to configure postgresql84, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
Error: Failed to configure postgresql84: configure failure: command execution 
failed

The config.log file referred to is just under 1000 lines long. Is there 
anything in particular I should look for?

Re: postgresql83-server - Further Woes

[Michael Newman via macports-users]

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.

> On Nov 4, 2019, at 21:29, Ryan Schmidt  wrote:
> 
> Well MacPorts isn't the program that's complaining, DetectX is. So I'd ask 
> the developer of DetectX.

Re: postgresql83-server - Further Woes

[Michael Newman via macports-users]

I have a license for and use DetectX Swift.

I wrote to the developer. Phil’s full reply is below. I am a bit wary about 
simply telling DetectX to ignore this. Something is going on and I want to know 
what it is.

I’ve written Phil back to let him know what I learned from this list.

(I am grateful for the help I receive here.)

>> Hi Mike
>> 
>> 
>> If DetectX is throwing that alert, double-check the following locations to 
>> see if the file exists:
>> 
>> ~/Library/LaunchAgents
>> /Library/LaunchAgents
>> /Library/LaunchDaemons
>> 
>> If it doesn't appear in one of those three locations, then it's likely that 
>> macports is writing the file there as a temporary item and then deleting it.
>> 
>> There's a couple of options for stopping this behaviour.
>> 
>> First, in DetectX Preferences, you can turn off the Folder Observer function 
>> in the Obsever tab.
>> 
>> Alternatively, in the same preferences tab, you can leave Folder Observer 
>> and add "org.macports" to the "Ignore Keywords" list.
>> 
>> [image removed]
>> 
>> Let me know if you need any further help.
>> 
>> 
>> Best
>> 
>> 
>> Phil
>> @sqwarq

> On Nov 4, 2019, at 06:27, Al Varnell  wrote:
> 
> Recommend you contact the Developer at  >. Phil has been a colleague of mine for several 
> years and very responsive. Operates out of Australia.
> 
> You should be aware that if you are actually using the older DetectX rather 
> thanDetectX Swift, it's not going to be supported beyond next 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 
> definition updates until June 1st, 2020.
> 3. It is no longer possible to buy registration keys for the older versions 
> of DetectX.
> 
> -Al-
> 
>> On Nov 3, 2019, at 13:33, Michael Newman > > wrote:
>> 
>> Thank you.
>> 
>> I asked the developers of DetectX and this is what they said:
>> 
>>> If DetectX is throwing that alert, double-check the following locations to 
>>> see if the file exists:
>>> 
>>> ~/Library/LaunchAgents
>>> /Library/LaunchAgents
>>> /Library/LaunchDaemons
>>> 
>>> If it doesn't appear in one of those three locations, then it's likely that 
>>> macports is writing the file there as a temporary item and then deleting it.
>> 
>> The plist file definitely does not exist:
>> 
>> MrMuscle:Volumes mnewman$ sudo launchctl list | grep 'org\.macports\.'
>> Password:
>> 81   0   org.macports.dnsmasq
>> -0   org.macports.clamd
>> 89   0   org.macports.mysql57-server
>> 
>> So, I find myself stuck in the middle. Is it a DetectX problem or a MacPorts 
>> problem?
>> 
>> I don’t know.
>> 
>>> On Nov 3, 2019, at 21:38, Ryan Schmidt >> > wrote:
>>> 
>>> 
>>> 
>>> On Nov 3, 2019, at 04:46, Michael Newman wrote:
>>> 
 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.
 
 DetectX doesn’t tell me where the plist is located or what process changed 
 it; just that it has been changed. Over and over again.
 
 Perhaps this is a bug in DetectX, but I have no way of knowing that.
>>> 
>>> You could ask the developers of DetectX. If it's complaining to you about a 
>>> file that doesn't appear to be on your disk, I don't know what else to 
>>> suggest, except:
>>> 
>>> Maybe back when you had postgresql83-server installed, you loaded the 
>>> plist, and now that it's gone, the system is trying to load it every 10 
>>> seconds, and maybe DetectX is noticing that. You could check your Console 
>>> to see if there are any mentions of issues with MacPorts launchd plists.
>>> 
>>> You can list all the MacPorts launchd plists you've loaded with:
>>> 
>>> sudo launchctl list | grep 'org\.macports\.'
>>> 
>>> If you see anything there that you don't want loaded, and the plist file 
>>> still exists, you can unload it with:
>>> 
>>> sudo launchctl unload -w /Library/LaunchDaemons/org.macports.whatever.plist
>>> 
>>> If the plist is no longer on disk, you can make launchd forget about it 
>>> with:
>>> 
>>> sudo launchctl remove org.macports.whatever
>>> 
>> 
>> 
> 

Re: postgresql83-server - Further Woes

[Michael Newman via macports-users]

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.

DetectX doesn’t tell me where the plist is located or what process changed it; 
just that it has been changed. Over and over again.

Perhaps this is a bug in DetectX, but I have no way of knowing that.

> On Nov 3, 2019, at 17:28, Al Varnell  wrote:
> 
> 
> At this point, you have solved the mystery and should simply go back to work 
> and forget about it. DetectX did it's job and so have you.
> 
> -Al-

Re: postgresql83-server - Further Woes

[Michael Newman via macports-users]

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/org.macports.postgresql83-server.plist
/Volumes/Clorox2/_CCC SafetyNet/2019-10-30 (October 30) 
01-00-52/opt/local/etc/LaunchDaemons/org.macports.postgresql83-server/org.macports.postgresql83-server.plist

I think the first one is a symbolic link to the second.

So, I’m stuck. I can tell DetectX to ignore this, but that seems more like a 
coverup than a solution.

> On Nov 3, 2019, at 16:51, Ryan Schmidt  wrote:
> 
> MacPorts creates plists for ports that are meant to act as servers when you 
> install those ports. The plists are removed, along with all of the port's 
> other files, when the port is uninstalled.
> 
> You can use find or locate to try to determine whether a 
> org.macports.postgresql83-server.plist file still exists even after you have 
> uninstalled the port.

postgresql83-server - Further Woes

[Michael Newman via macports-users]

Periodically DetectX generates the following message:

=
Items:  org.macports.postgresql83-server.plist
Some background launch items have just been changed on your mac which can 
affect its security
=

I had previously uninstalled postgresql83-server and can’t find 
org.macports.postgresql83-server.plist in any of the following directories:

~/Library/LaunchAgents
/Library/LaunchAgents
/Library/LaunchDaemons

DetectX support suggested:

"... it's likely that macports is writing the file there as a temporary item 
and then deleting it."

Is that a reasonable explanation? If so, how do I stop MacPorts from creating 
this plist?

If it’s not a reasonable explanation, is there something I should do?

Mike Newman
Korat, Thailand

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

"Dominic Reich" mailto:domi...@mm.st>> wrote:

> You should be able to print without any additional software (except the 
> driver that macOS retrieves from its Servers). But you won't need any 
> package from MacPorts for printing.
> 
> Besides that, postgresql83-server is a database. You won't need a 
> database to print stuff.

This is going to be long, boring and somewhat irrelevant. If you’re busy, move 
on to the next thread.

Bottom line is that when you have an old, ignorant and naive person like me 
trying to use something like MacPorts, this stuff is going to happen.

Let’s examine the timeline.

On Tuesday morning the first thing I did was print a mailing label I needed to 
return a failed disk drive to Western Digital for warranty replacement. That 
print job executed without issue.

The next thing I did was to update MacPorts. That’s when I got the error 
message on postgresql83. After exchanging a few messages with other members of 
this list I decided to delete postgresql83. That was sometime after lunch. 
After that I didn’t do anything on the iMac. I watched some TV, read a novel, 
worked in the garden, had a beer for happy hour and ate dinner. (I’m retired.)

The next morning the first thing I did was try to print something. I’m both 
surprised and shocked that the print system has simply disappeared. In my mind 
I associate the last thing I did on Tuesday (delete postgresql83) with the 
first thing I tried to do on Wednesday morning (print something). So I assume 
(wrongly, I guess) that deleting postgresql83 had something to do with the 
disappearance of the printing system. What else could it have been? I’m the 
only one who uses this computer and I didn’t do anything between deleting 
postgresql83 on Tuesday afternoon and trying to print something on Wednesday 
morning.

Anyway, I apologize for the error. As always, I appreciate the help and advice 
I receive here.

Mike Newman
Korat, Thailand

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

>> On Oct 22, 2019, at 16:00, Ryan Schmidt > > wrote:
>>> 
>>> Yes, looks like nothing depended on postgresql83-server.
> 
> Except the Mac printing system.

I managed to get the printers back by resetting the printer system.

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 16:00, Ryan Schmidt  > wrote:
>> 
>> Yes, looks like nothing depended on postgresql83-server.

Except the Mac printing system.

After deleting postgresql83-server I can no longer print.

My printer has disappeared from the "Printers & Scanners System" Preferences 
and when I try to add the printer again, all the printer drivers have 
disappeared.

It’s hard for me to understand how the Mac printing system could depend on a 
database server installed via MacPorts, but it appears that’s the case.

I tried to reinstall postgresql83, but that failed with the same error that 
started this thread: Error: Failed to configure postgresql83: configure 
failure: command execution failed

Any ideas as to how to fix this?

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

On Oct 22, 2019, at 16:00, Ryan Schmidt  wrote:
> 
> Yes, looks like nothing depended on postgresql83-server.
> 
> 
>> Any way of finding out why this got installed in the first place? It didn't 
>> seem to have any dependencies, so why was it there?
> 
> It was installed either because you requested that it be installed, or 
> because some other port that you installed depended on it at one time.
> 
> You can see the ports that you directly requested to be installed using:
> 
> port installed requested
> 
> If the list is inaccurate (if ports are listed that you don't specifically 
> want), you can unmark them using:
> 
> sudo port unsetrequested thePortName
> 
> You can remove ports that you did not request and that are no longer needed 
> by other ports, as well as perform other cleanup activities, by running:
> 
> sudo port reclaim

Thank you very much for your help. I appreciate your taking the time to explain 
things so clearly.

Mike

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 13:45, Ryan Schmidt  wrote:
> 
> 
> 
> On Oct 22, 2019, at 00:50, Michael Newman wrote:
> 
>>> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote:
>>> 
 Michael Newman kirjoitti 22.10.2019 kello 7.19:
 
 I have no idea. I don’t even know what it is. It must have been installed 
 by some other port that I requested.
>>> 
>>> Hi,
>>> can you find out, what it was you requested. I looked at the port 
>>> collection and found some that are not actively maintained at the moment 
>>> depending on too old versions of postgres. If you can find that, I can try 
>>> to update that port. Then, it will take a few moments, especially if the 
>>> port is otherwise outdated.
>> 
>> How would I find out? I got this error message for the first time after 
>> updating to the most recent MacPorts release. I haven’t installed anything 
>> new in quite some time. 
> 
> PostgreSQL is a database server. If you don't think you need it (or any 
> port), try uninstalling it. ("sudo port uninstall postgresql83"). MacPorts 
> will either let you uninstall it, or it will tell that uninstalling it will 
> break some other port. If it does the latter, look at the variants of the 
> other port ("port variants theOtherPortsName") and see if there is a variant 
> for using a newer postgresql instead. If so, reinstall the port using that 
> other variant. ("sudo port install theOtherPortsName +postgresql12" for 
> example.) If not, let us know what the other port is.

Did I do the right thing?

MrMuscle:~ mnewman$ sudo port uninstall postgresql83
Password:
The following versions of postgresql83 are currently installed:
 1) postgresql83 @8.3.23_2
 2) postgresql83 @8.3.23_3 (active)
Enter option(s) [1-2/all]: all
--->  Uninstalling postgresql83 @8.3.23_2
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break: postgresql83-server @8.3.23_0
Continue? [y/N]: y
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating postgresql83 @8.3.23_3
--->  Cleaning postgresql83
--->  Uninstalling postgresql83 @8.3.23_3

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki  wrote:
> 
>> Michael Newman  kirjoitti 22.10.2019 kello 7.19:
>> 
>> I have no idea. I don’t even know what it is. It must have been installed by 
>> some other port that I requested.
> 
> Hi,
> can you find out, what it was you requested. I looked at the port collection 
> and found some that are not actively maintained at the moment depending on 
> too old versions of postgres. If you can find that, I can try to update that 
> port. Then, it will take a few moments, especially if the port is otherwise 
> outdated.

How would I find out? I got this error message for the first time after 
updating to the most recent MacPorts release. I haven’t installed anything new 
in quite some time. 

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 11:06, Wahlstedt Jyrki  wrote:
> 
> Hi,
> just being curious, why postgresql83? It was EOL’d several years ago, so it 
> is obsolete. If you want PostgreSQL, the current version is postgresql12.

I have no idea. I don’t even know what it is. It must have been installed by 
some other port that I requested. 

MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

I have no idea what to do about this. The error message includes:

Error: Failed to configure postgresql83, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/work/postgresql-8.3.23/config.log
Error: Failed to configure postgresql83: configure failure: command execution 
failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/main.log
 for details.

I looked at the log files referred to, but they are way above my ability level.

Re: mpv, ffmpeg seg fault in macOS catalina

[Michael Newman via macports-users]

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 ffmpeg stop working?
> 
> As long as you follow the migration guide correctly, no.
> 
> https://trac.macports.org/wiki/Migration 
> 
> 

Re: mpv, ffmpeg seg fault in macOS catalina

[Michael Newman via macports-users]

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

Re: sudo port selfupdate Doesn't Seem To Work

[Michael Newman via macports-users]

Yes. That was it. It failed because I had not yet accepted the Xcode license.

Once I did that 2.6.1 was actually installed and I was able upgrade installed 
ports.

Thank you.

> On Oct 6, 2019, at 07:26, Joshua Root  wrote:
> 
> Michael Newman wrote:
>> What’s going on here?
>> 
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.5.4 installed,
>> MacPorts base version 2.6.1 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is outdated, installing new version 2.6.1
>> Installing new MacPorts release in /opt/local as root:wheel; permissions 0775
>> 
>> MrMuscle:~ mnewman$ sudo port selfupdate
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.5.4 installed,
>> MacPorts base version 2.6.1 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is outdated, installing new version 2.6.1
>> Installing new MacPorts release in /opt/local as root:wheel; permissions 0775
>> 
>> It seems that 2.6.1 never actually gets installed.
> 
> You're likely running into this bug:
> 
> 
> Using the -v or -d flag to get more verbose output will show you what's
> actually happening, e.g. 'sudo port -d selfupdate'.
> 
> - Josh

sudo port selfupdate Doesn't Seem To Work

[Michael Newman via macports-users]

What’s going on here?

--->  Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.6.1
Installing new MacPorts release in /opt/local as root:wheel; permissions 0775

MrMuscle:~ mnewman$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.6.1
Installing new MacPorts release in /opt/local as root:wheel; permissions 0775

It seems that 2.6.1 never actually gets installed.

Re: Problems With Mysql57

[Michael Newman via macports-users]

> On Jul 28, 2019, at 05:53, Ryan Schmidt  wrote:
> 
> Looking at the port select code, it just tries to create each symlink in 
> turn. There isn't any special error handling code to deal with the case that 
> a symlink can't be created; if that happens, an error will occur and MacPorts 
> will exit. Any symlinks that were already successfully created will remain on 
> disk. This would leave you with an incomplete or possibly even inconsistent 
> set of symlinks. 

Thanks for taking the time to check that. 

I trust it will get fixed. I’m not that guy to do that. I’m just a user.

Re: Problems With Mysql57

[Michael Newman via macports-users]

> On Jul 27, 2019, at 11:16, Ryan Schmidt  wrote:
> 
> `port select` is a convenience that places symlinks in /opt/local/bin. If 
> `port select` doesn't work, you won't be able to call the programs by their 
> convenient shortened names, but you can still call them by their absolute 
> paths wherever the port put them. You can find out where the port put them by 
> using `port contents mysql57`. For example, if you had wanted to run 
> `mysqld_safe`, you would instead run `/opt/local/lib/mysql57/bin/mysqld_safe`.

Thanks for the clarification. Oddly, the symlink seems to have been created in 
spite of the port select failure:

lrwxr-xr-x 1 root wheel38 Jul 25 08:59 mysqld_safe -> 
/opt/local/lib/mysql57/bin/mysqld_safe

The reason I’m a bit wary is that in my previous installation of MySQL there 
was a symlink that pointed to the correct MySQL (5.7). But, the Launch Daemon 
was trying to start this: /usr/local/mysql/bin/mysqld_safe --user=mysql, which 
failed every ten seconds and created the massive (150 million line) error file 
in the directory for MySQL 5.6.

I’m assuming that the symlink was created when I initially installed MySQL 
(5.6) but wasn’t updated when it was upgraded to 5.7. 

I’d like for that not to happen again. 

Re:Re: Problems With Mysql57

[Michael Newman via macports-users]

> On Jul 26, 2019, at 19:00, Christopher Chavez wrote:
> 
> Not sure about your other issues, but the `port select` problem was
> reported a while ago:
> 
> https://trac.macports.org/ticket/58197 
> 
Yes, I’m aware of that. But, I don’t understand the consequences. Is the port 
select problem fatal, or can I go ahead and try to use MySQL?

Background: I originally installed the System Preferences version of MySQL 
years ago in order to set up an XBMC media library. I stopped using XBMC and 
didn’t give MySQL another thought. Just the other day I was diagnosing another 
problem when I noticed that there was an entry every ten seconds in the System 
Log saying that launchd had tried and failed to run mysqld. As a result, the 
mysql.err file had grown to over 11 GB and had over 150 million lines of error 
messages. The fatal error seemed to be:

2019-07-20 01:09:54 16104 [ERROR] Can't open the mysql.plugin table. Please run 
mysql_upgrade to create it.

I tried to do that, but it didn’t work. So, I decided to completely delete 
MySQL and reinstall the MacPorts version. 

Perhaps that was a bad idea.

Problems With Mysql57

[Michael Newman via macports-users]

This was previously reported in March 2019, but nothing since then:

https://lists.macports.org/pipermail/macports-users/2019-March/046514.html 


Here are the errors:

  mysql57-server has the following notes:
If this is a new install you might want to run:

$ sudo /opt/local/lib/mysql57/bin/mysqld --initialize --user=_mysql
$ /opt/local/lib/mysql57/bin/mysql_secure_installation

MrMuscle:~ mnewman$ sudo /opt/local/lib/mysql57/bin/mysqld --initialize 
--user=_mysql
2019-07-25T00:47:20.692646Z 0 [Warning] TIMESTAMP with implicit DEFAULT value 
is deprecated. Please use --explicit_defaults_for_timestamp server option (see 
documentation for more details).
2019-07-25T00:47:20.693843Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 
'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They 
will be merged with strict mode in a future release.
2019-07-25T00:47:20.693849Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not 
set.
2019-07-25T00:47:20.703194Z 0 [Warning] Setting lower_case_table_names=2 
because file system for /opt/local/var/db/mysql57/ is case insensitive
2019-07-25T00:47:21.013714Z 0 [Warning] InnoDB: New log files created, LSN=45790
2019-07-25T00:47:21.045721Z 0 [Warning] InnoDB: Creating foreign key constraint 
system tables.
2019-07-25T00:47:21.104765Z 0 [Warning] No existing UUID has been found, so we 
assume that this is the first time that this server has been started. 
Generating a new UUID: c29dee88-ae75-11e9-820c-2e3fb0b57b48.
2019-07-25T00:47:21.124478Z 0 [Warning] Gtid table is not ready to be used. 
Table 'mysql.gtid_executed' cannot be opened.
2019-07-25T00:47:21.126793Z 1 [Note] A temporary password is generated for 
root@localhost: yCsGrKUda7&-

MrMuscle:~ mnewman$ /opt/local/lib/mysql57/bin/mysql_secure_installation

Securing the MySQL server deployment.

Enter password for user root:
Error: Can't connect to local MySQL server through socket 
'/opt/local/var/run/mysql57/mysqld.sock' (2)

MrMuscle:~ mnewman$  sudo port select mysql mysql57
Selecting 'mysql57' for 'mysql' failed: could not create new link 
"/opt/local/man/man1/mysql-stress-test.pl.1.gz": target 
"/opt/local/share/man/mysql57/man1/mysql-stress-test.pl.1.gz" doesn't exist


I have no idea what to do next.

Re: Migration Woes - Can’t Install Xcode Command Line Tools

[Michael Newman via macports-users]

> `xcode-select --install` presents you with a dialog box through which you can 
> initiate either an installation of Xcode or an installation of the command 
> line tools. If you want to do both, initiate `xcode-select --install` a 
> second time after you've finished doing the first one.

Thanks for the explanation. "xcode-select --install" finally worked after 
failing all day yesterday and the day before. As of this moment the reinstall 
part of the migration seems to be working as expected. 

Migration Woes - Can’t Install Xcode Command Line Tools

[Michael Newman via macports-users]

This on a 2010 MBA that I only visit once a month. This visit I finally bit the 
bullet and upgraded from Mavericks to High Sierra. That upgrade wasn’t 
flawless, but it’s working. I also installed a compatible version of Xcode from 
the App Store.  Now I’m stuck trying to install the command line tools. Earlier 
today I kept getting network errors and now every time I try it gets stuck on 
"Finding Software". 

I have not yet installed the appropriate version of MacPorts nor have I 
uninstalled my installed ports. (They all seem to be working.)

I’ll only be here a few more days, but I hesitate to proceed until I install 
the command line tools. 

What should I do if I’m unable to install the command line tools before I go 
back home?



Aside: To be honest, it’s not clear to me if I have to separately install the 
command line tools if I have already done a full install of Xcode. The 
migration instructions say:
"After a major system change, update the development tools by ​installing the 
latest version of Xcode. Open the Xcode application once after installation and 
follow any prompts. Install the command line tools package as well (run 
xcode-select --install)."

This implies that you need to install the command line tools separately from 
Xcode.

But, when you run Xcode-select —install, the resulting dialog seems to indicate 
that installing Xcode also installs the command line tools. 

I remain confused. 


Mike Newman
Korat, Thailand


-- 
www.mgnewman.com

Re: Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

[Michael Newman via macports-users]

On Jun 18, 2019, at 20:31, Ulrich Wienands  wrote:

> Hmm... per EveryMac.com , the 2009 MacBook Air only 
> goes up to 10.11. This agrees with my experience; my 2009 MBP also tops out 
> at 10.11.

I’m sorry, it’s actually a late 2010 MBA. On June 10th the App Store downloaded 
and attempted to install High Sierra. I have no idea why Apple pushed this to 
my machine two years after it was released. From the Console log:

Jun 10 04:48:26 Axe.local softwareupdated[240] : SWU: downloading "macOS High 
Sierra,  "
Jun 10 04:49:14 Axe.local softwareupdated[240] : SWU: installing "macOS High 
Sierra,  "

According to the System log the installation failed:

Sandbox denied authorizing right 
'system.install.app-store-software.standard-user' for authorization created by 
'/System/Library/CoreServices/Software 
Update.app/Contents/Resources/SoftwareUpdateConfigData'

The App Store app actually shows that it was installed, even though it was not.

> If the machine really only runs shell scripts, why would you bother upgrading?

This is a remote machine to which I need to log in now and then. It is behind a 
double NAT so I can’t SSH into it. Back To My Mac never worked. The only 
solution I’ve found that is both cheap (free) and reliable is Chrome Remote 
Desktop. But, support for Mavericks will go away soon.

I’d be happy to find a remote login solution that works with Mavericks.

So far I have stuck with Mavericks because it runs just fine and, until now, I 
had no compelling reason to upgrade.

Mike

Re: Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

[Michael Newman via macports-users]

> On Jun 18, 2019, at 19:00, Chris Jones  > wrote:
> 
> Yes. You always have to follow the migration guide when updating to a 
> new major OS.

Thanks. I have no problem with that. Done it many times in the past. But, there 
is still one thing I don’t fully understand.

My next visit to this site may be a brief one. If I only have time to do the 
MacOS upgrade, but not the MacPorts migration, will the MacPorts binaries that 
I have already installed continue to work under the new OS, or is there a 
chance that some will fail?

Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

[Michael Newman via macports-users]

I have an old 2009 MacBook Air (2GB RAM) which is running MacOS 10.9.5 
(Mavericks). I’m now getting warnings from Apple, Google (Remote Desktop) and 
DropBox (among others) that this version of the OS will no longer be supported 
"real soon now".

I have an installer for High Sierra (10.13) which Apple downloaded to my 
machine and attempted but failed to install. (All this was done without my 
permission.)

This machine doesn’t do too much except run a bunch of shell scripts that power 
a webcam and some other shell scripts that keep me connected to a captive 
portal Internet connection. These shell scripts depend on many MacPorts 
installations.

I have a couple of questions:

Will this old machine actually run 10.13 without blowing up?
If I install 10.13 over 10.9, will I have to uninstall and reinstall MacPorts?

I have been diligent about keeping MacPorts updated. I visit the location where 
this machine is located only a few days per month, but always do an upgrade 
soon after arriving.

TIA

Mike Newman
Korat, Thailand

Re: How To Troubleshoot MacPorts

[Michael Newman via macports-users]

> On Apr 12, 2019, at 23:50, Ryan Schmidt  wrote:
> 
> We explain some of this in our Guide, but I'll try to give an overview.

Wow. That was incredibly helpful and very well done. You know how to write for 
people who don’t know as much as you do. That’s an uncommon skill in this 
field. You might think about incorporating much of that in the Introduction 
section of the MacPorts Guide. 

Thanks for taking the time to write it. 

Mike Newman
Korat, Thailand. 

Re: How To Troubleshoot MacPorts

[Michael Newman via macports-users]

> On Apr 12, 2019, at 06:19, Ryan Schmidt  wrote:
> 
> It's difficult to answer a question this broad. But I can tell you a little 
> about how I answer port build failure bug reports or posts on the list.

Thank you for taking the time to write such an interesting and informative 
post. 

I suppose the root of my problem is that while I have a basic understanding of 
how to use MacPorts, I have very little knowledge about how it actually works. 

For example, I’ve been confused as to why some ports generate a config log and 
some don’t. You explained that. 

I suppose the takeaway from your post is that I should take more time to study 
other threads and learn from them. My failure is to only read this list when I 
have a problem of my own to solve. That’s a poor strategy for learning. 

Thanks again for taking the time to write. 

Mike Newman
Korat, Thailand. 

Hoe To Troubleshoot MacPorts

[Michael Newman via macports-users]

I’ve been using MacPorts for many years now. While I understand the basics, I 
often run into problems that I cannot solve. Without exception, I have been 
able to post those problems here and get near-immediate solutions. For that I 
am grateful. 

On the other hand, I would ver much like to learn how to deal with these issues 
on my own. Usually, the solutions I’m offered are easy to follow, but nearly 
impossible to understand. I know what I’m doing,  But I don’t know why. 

Where can I turn to learn about the inner workings of MacPorts? What the 
different log files are and what they mean? How to figure out what went wrong 
and how to fix it? 

I've looked at the "How To" page, But that seems aimed at users more advanced 
than I and with needs and interests different from my own. 

Any ideas?

TIA

Mike Newman
Korat, Thailand. 


-- 
www.mgnewman.com

Failed to configure libraw

[Michael Newman via macports-users]

MacPorts Version: 2.5.4 MacOS 10.0.5 MacBook Air 2010What to do? I looked at the two referenced log files, but they mean nothing to me. --->  Configuring libraw
Error: Failed to configure libraw, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libraw/libraw/work/LibRaw-0.19.2/config.log
Error: Failed to configure libraw: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libraw/libraw/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

config.log
Description: Binary data


main.log
Description: Binary data
-- www.mgnewman.com

Re: Rust - Failed to Build

[Michael Newman via macports-users]

> On Mar 6, 2019, at 13:35, Ryan Schmidt  wrote:

> Rust is a programming language. The rust port provides a Rust compiler. You 
> need a Rust compiler if you want to compile software written in the Rust 
> language.



> Now that the librsvg you use has been downgraded to a version that no longer 
> requires rust, you can uninstall rust. You can safely try to uninstall any 
> port anytime you like. If it is required by another port you have installed, 
> MacPorts will let you know and will prevent the uninstallation.
> 
> MacPorts is a volunteer organization. The reason why nobody has fixed the bug 
> you mentioned is that nobody has volunteered to do so. It looks like there is 
> a suggestion in the bug report that raising the ulimit might help. If anybody 
> would like to attempt to integrate a solution for this into the rust portfile 
> and submit a pull request, that would be great.

Thank you for taking the time to write such a detailed and informative 
explanation. I learned a lot.

Rust - Failed to Build

[Michael Newman via macports-users]

I am aware that there is a bug report on this issue: 
https://trac.macports.org/ticket/57058 

However, I have some different questions. This on a 2010 MBA running 10.9.5, 
Xcode 6.2

I first noticed this failure about six months ago. I chose to ignore it because:

I saw the bug report and figured it would get fixed, eventually
The failure of Rust to build seemed to have no effect on my installed Ports

After six months:

The bug has not been fixed
The failure of Rust to build still has no effect on my Ports

However, I’m concerned. If the bug is never fixed, will this cause problems in 
the future? 

For example, one of the commenters on the bug report states: "I don't care 
about rust per se, but it's a dependency for FFMPEG, which I *do* want." But, I 
run ffmpeg every four minutes, 24/7 on this machine and the lack of Rust seems 
to have had no effect at all on building or running ffmpeg.

Why do I even have Rust? I didn’t install it, so something I did install must 
have depended on it at some time. But, it seems that none of my currently 
installed Ports depend on it. Can I just get rid of it or is some other course 
of action warranted?

Note that I only visit this machine about once a month. And, it is behind a 
double NAT, so remote access is problematic. I won’t be there again until 
mid-April.

Michael Newman
Korat, Thailand

Re: myports.txt vs requested.txt

[Michael Newman via macports-users]

> On Oct 25, 2018, at 19:00, macports-users-requ...@lists.macports.org wrote:
> 
>> It doesn’t include many ports that are in myports.txt, such as curl, wget, 
>> and dnsmasq, all of which I know I specifically requested.
>> 
>> Why is that?
> 
> I guess MacPorts doesn't think you specifically requested them. A port is 
> marked as requested if you "sudo port install" it when it is not installed, 
> or "sudo port setrequested" it when it is installed.

So, just an unexplainable glitch, then? 

I have used setrequested to clean things up.

myports.txt vs requested.txt

[Michael Newman via macports-users]

I decided to compare the ports found in myports.txt with those in requested.txt.

I figured that every port in requested.txt should also be in myports.txt.

But, that’s not the case. Requested.txt contains only the following ports:

ImageMagick
clamav
ffmpeg
gstreamer010
gstreamer010-gst-plugins-base
gstreamer1
gstreamer1-gst-libav
gstreamer1-gst-plugins-bad
gstreamer1-gst-plugins-good
gstreamer1-gst-plugins-ugly
ipcalc
libsdl2
switchaudio-osx

It doesn’t include many ports that are in myports.txt, such as curl, wget, and 
dnsmasq, all of which I know I specifically requested.

Why is that?

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 19:00,Chris Jones wrote:
> 
> Do you create the requested list ? This is much shorter as it lists only 
> the ports your actively requested, not dependencies etc. My 
> recommendation is to go through this list, and just use it to identify, 
> by hand those you wish to reinstall. Then, reinstall these using 
> whatever the new default variants (plus whatever options you want) are.

Thank you. That worked very well for installing the missing ports.

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 19:48, Joshua Root  wrote:
> 
> Were there any failures shown in the output of restore_ports.tcl? Were
> the missing ports mentioned at all? Running it again will not do any
> harm since it will simply skip any ports in myports.txt that are already
> active; what happens if you do so?

There were many errors regarding obsolete ports and things like:

Error: p5.24-io has been replaced by p5.26-io

The script simply stopped running when it got here:

Unable to execute target 'install' for port 'texinfo': can't create directory 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texinfo":
 permission denied
while executing
"install_ports $operationList"
(file "./restore_ports.tcl" line 287)

Now that I look at the script output in more detail, I see that it never got to 
reinstalling most of the missing ports, such as ffmpeg and curl.

I’ve just now finished installing all of the missing requested ports.

I’ll run restore_ports.tcl again if you think it would be worthwhile.

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 16:21, Ryan Schmidt  wrote:
> 
>> Not by me. I’ve always installed ports with the simplest command: sudo port 
>> install [port]
> 
> Right, and doing so may, in some cases, cause dependencies to be installed 
> with the universal variant, and I was asking if that had happened for you.

From the myports.txt file I see that the following port was installed with 
+universal:

libcxx @5.0.1_2+universal

That’s it unless the myports.txt file isn’t definitive.

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 16:17, Ryan Schmidt  wrote:
> 
> Were any of the ports in myports.txt, by chance, installed with the 
> +universal variant? If so, you'll have to install them without the +universal 
> variant on Mojave and later.

Not by me. I’ve always installed ports with the simplest command: sudo port 
install [port]

> Other than that, if you don't know what a port is for, don't install it. 
> Install the ports you want to use and let MacPorts figure out what 
> dependencies are needed.

OK. Then I’m done. Thanks again.

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 15:31, Ryan Schmidt  wrote:
> 
>> Makes me thing something went seriously wrong with restore_ports.tcl.
> 
> Ok, pick one, try to install it, see what happens. If it fails, show us what 
> the error was.

Every one I’ve picked so far has installed without any errors.

But, I just picked a few that I recognize. I have no idea what most of the 
stuff on the list actually is. When I see something like this:

py26-cython 
py26-nose   
py26-numpy  
py26-setuptools 
py27-beaker 
py27-cairo  

I’m totally ignorant.

Bottom line? There’s just no way for me to know what I actually need to 
install. I suspect that stuff will fail and tell me why and I’ll install what’s 
needed to make it work again.

Thanks again for your time.

Re: Mojave and Migration

[Michael Newman via macports-users]

> On Oct 23, 2018, at 15:09, Ryan Schmidt  wrote:
>> Is there any way to find our without manually checking each and every port 
>> in myports.txt?
> 
> Sure, get a list of only the port names you want to know about. For example 
> you could do that using:
> 
> awk '{print $1}' myports.txt
> 
> Then ask MacPorts which of them aren't installed. For example:
> 
> port echo not installed and \( ImageMagick MPlayer \)
> 
> Or:
> 
> port echo not installed and \( $(awk '{print $1}' myports.txt) \)

Thank you. Unfortunately, the list is huge:

MrMuscle:~ mnewman$ port echo not installed and \( $(awk '{print $1}' 
myports.txt) \) | wc -l
 218

And includes things like curl, wget, gzip and others.

Makes me thing something went seriously wrong with restore_ports.tcl.

Mojave and Migration

[Michael Newman via macports-users]

I followed the migration instructions which are found here: 
https://trac.macports.org/wiki/Migration 


That sort of worked, except that some ports didn’t get reinstalled. For 
example, neither ImageMagick nor MPlayer were reinstalled. It was easy to 
manually install them, but now I’m wondering what else didn’t get reinstalled.

(I found out that ImageMagick didn’t get reinstalled because a script I wrote 
which uses convert failed. MPlayer was just a random check.)

Is there any way to find our without manually checking each and every port in 
myports.txt?

TIA

Re: 10.14 Mojave

[Michael Newman via macports-users]

> Chris Jones wrote:
> 
> MacPorts, for the most part, works fine on macOS10.14 now.

Does that mean that I can install Mojave and that installed ports will continue 
to run without my having to install a newer MacPorts from source and perform a 
migration?

ClamAV: freshclam vs. sudo freshclam

[Michael Newman via macports-users]

If I run freshclam as a non-privileged user, it runs fine with no warnings or 
error messages. Here’s the last line of the response:

Database updated (6622193 signatures) from db.TH.clamav.net 
 (IP: 104.16.188.138)

But, if I run sudo freshclam it fails with numerous errors, some of which are 
shown below. 

What do I need to do to fix this?

WARNING: Can't query current.cvd.clamav.net 
WARNING: Invalid DNS reply. Falling back to HTTP mode.
If-Modified-Since: Wed, 07 Jun 2017 21:38:10 GMT
Reading CVD header (main.cvd): nonblock_connect: connect(): fd=6 errno=64: Host 
is down
Can't connect to port 80 of host db.TH.clamav.net  
(IP: 104.16.186.138)
nonblock_connect: connect(): fd=6 errno=64: Host is down
Can't connect to port 80 of host db.TH.clamav.net  
(IP: 104.16.188.138)
Trying host db.TH.clamav.net  (104.16.187.138)...
nonblock_connect: connect(): fd=6 errno=64: Host is down
Can't connect to port 80 of host db.TH.clamav.net  
(IP: 104.16.187.138)
Trying host db.TH.clamav.net  (104.16.189.138)...
nonblock_connect: connect(): fd=6 errno=64: Host is down

WARNING: Can't read main.cvd header from database.clamav.net 
 (IP: )
Giving up on database.clamav.net ...
Update failed. Your network may be down or none of the mirrors listed in 
/opt/local/etc/freshclam.conf is working. Check 
https://www.clamav.net/documents/official-mirror-faq 
 for possible reasons.