Re: py311+-mysqlclient

[Craig Treleaven]

> On Jan 10, 2024, at 2:47 AM, Henning Hraban Ramm  wrote:
> 
> Am 09.01.24 um 22:32 schrieb Craig Treleaven:
>>> On Jan 9, 2024, at 3:55 PM, Henning Hraban Ramm  wrote:
>>> 
>>> Hi,
>>> 
>>> is there a reason there’s no py311 or py312 version of mysqlclient?
>>> 
>>> Hraban
>>> 
>> I created it for something I used to work on.  The other thing has gone by 
>> the wayside.  Our user stats didn’t show anybody else using it so I hadn’t 
>> really thought about it for some time.  Now that I look, I see that upstream 
>> has made some non-trivial updates.
>> 
>> https://ports.macports.org/port/py-mysqlclient/details/
>> 
>> I’ll have a go at updating it.  May take a few days.
> 
> Thank you!
> 
> I have MacPort’s Python 3.11 as my default Python. Additionally installed 
> 3.10 now and made a virtualenv with it where I needed mysqlclient (a local 
> test environment for a Django app that I wanted to check on different Python 
> versions); I couldn’t get mysqlclient (3.10) working, since the global one 
> isn’t available in the venv and pip can’t install it (I guess the mysql-dev 
> libs are missing). I symlinked the one from MacPorts’ Python framework into 
> the venv’s site-packages, and it works so far, but I don’t like such hacks, 
> since now my requirements.txt doesn’t work for the local installation any 
> more.
> 
> If you had hints how to resolve this situation better, I’d be glad. (I found 
> nothing helpful on the internet, search engine results just aren’t usable any 
> more…)
> 
> (I’m still on Mojave BTW.)

The update turned out to be a little more involved than I expected.  MacPorts 
has versions of MariaDB from 10.2 through 10.11.  I’m not following db stuff 
anymore and I haven’t got a clue what is considered ‘mainstream’ now.  I’ve set 
the py-mysqlclient port to default to MariaDB 10.9 in hopes that that version 
is relatively recent and yet stable enough to use.

Please either reply or file a ticket if you run into any problems.

Craig

Re: py311+-mysqlclient

[Craig Treleaven]

> On Jan 9, 2024, at 3:55 PM, Henning Hraban Ramm  wrote:
> 
> Hi,
> 
> is there a reason there’s no py311 or py312 version of mysqlclient?
> 
> Hraban
> 

I created it for something I used to work on.  The other thing has gone by the 
wayside.  Our user stats didn’t show anybody else using it so I hadn’t really 
thought about it for some time.  Now that I look, I see that upstream has made 
some non-trivial updates.  

https://ports.macports.org/port/py-mysqlclient/details/

I’ll have a go at updating it.  May take a few days.

Craig

Re: Apple Silicon Hardware and MacPorts

[Craig Treleaven]

> On Nov 14, 2023, at 10:04 PM, Alexander Newman via macports-users 
>  wrote:
> 
> I use Inkscape, R and Octave


https://ports.macports.org/port/inkscape/details/ 


https://ports.macports.org/port/R/details/ 


https://ports.macports.org/port/octave/details/ 


No personal experience, but each of these ports apparently has users running 
Apple Silicone machines.  They all have open Trac tickets, as well, but I 
didn’t look into the details.

Craig
(Our port information web pages appear to be less than well-known.)

Re: Request for support

[Craig Treleaven]

> On Mar 12, 2023, at 5:35 PM, Sarah Zinsmeister  
> wrote:
> 
> I actually thought this was a program to back up websites

As others have said, you can leave Macports installed without any risk.  Or 
uninstall it if you don’t intend to use it.

However, perhaps we can help you achieve the goal of backing up websites.  If 
you found this idea on the web, could you post a link so that we can help you 
work through what may be required?

Craig

Re: Request Alda and ABC packages exist on homebrew but do not exist as ports

[Craig Treleaven]

> On Feb 15, 2023, at 6:00 PM, Kenneth Wolcott  wrote:
> 
> abcmidi is the one ABC package that homebrew offers.

You mean...

https://ports.macports.org/port/abcMIDI/details/ 


Craig

Re: sc build failed

[Craig Treleaven]

> On Jan 7, 2023, at 2:21 AM, Kenneth Wolcott  wrote:
> 
> Hi;
> 
> I tried to install the sc port, building from source, on Mac Mini,
> Venturi 13.1, M1 chip.
> 
> The build failed.  Compressed log attached.

Please file a bug:

https://trac.macports.org/newticket?port=sc 


The source for sc is over 10 years old and appears to have numerous problems.  
There are a handful of forks available, see:

https://repology.org/project/sc/information

This fork might be promising but I haven’t done anything more than check the 
Readme:

https://github.com/n-t-roff/sc

Craig

Re: Can I use Macports for Gimp maintenance?

[Craig Treleaven]

> On Jul 3, 2022, at 5:57 AM, Lukas Oberhuber  wrote:
> 
> Given we support all the way back to 10.12, I'm worried about trying to get 
> that version of macos up and running reliably with the build tools. Homebrew 
> also doesn't go back that far, which is one of the main reasons I'm looking 
> at macports. It seems I've now got the bare bones working (thought it's hard 
> to tell if the right SDK was linked). In any case, thanks for your help!

One option might be to use Parallels or another virtualization system.  That 
way the host OS can be a current release and you can have older OS versions as 
guests.

Craig

Re: Port tree not syncing

[Craig Treleaven]

> On Jun 2, 2022, at 10:19 PM, Ryan Schmidt  wrote:
> 
> On Jun 2, 2022, at 20:44, Craig Treleaven wrote:
> 
>> I’m a port maintainer…but I’m having a user problem.  For some weeks now, 
>> ‘sudo port selfupdate’ has not been properly updating my local ports tree(s) 
>> on my main Mac.  About 2 weeks ago, I was going to post a question about 
>> this but then I ran ‘sudo port -d selfupdate’ and it seemed that all the 
>> missed updates were now caught up.  I put it down to gremlins in the ether 
>> but then I noticed recently that I had no outdated ports when I knew that 
>> there should be several.  I tried ’sudo port -d sync’ with the same result, 
>> ie no updates.
>> 
>> Obviously, ’sudo port selfupdate’ has worked flawlessly for me for quite a 
>> few years.  TTBOMK, I haven’t changed anything relevant on my side.  I’m 
>> overdue to update my OS version (I’m on 10.15.7).  
>> 
>> I’ve pasted the debug log from ’sudo port -d sync’ in case that shows 
>> something useful:
>> 
>> https://paste.macports.org/69b104de0e93
>> 
>> BTW, I have another older Mac that also has MacPorts installed.  ’sudo port 
>> selfupdate’ continues to work as expected on that machine.
>> 
>> Suggestions on what’s wrong and how to fix it?
> 
> From that log, looks like you have two sources configured: the standard rsync 
> one, which looks like it updated ok, and one you created at 
> file:///Users/craigtreleaven/mp/macports-ports, which looks like it contains 
> a full collection of ports and did not get updated on that sync.
> 
> Presumably file:///Users/craigtreleaven/mp/macports-ports is the one marked 
> as default in sources.conf so any ports present there (which is presumably 
> all of them) override those in the rsync tarball, which is why nothing is 
> shown as outdated. So there's no reason for your sources.conf to continue to 
> list the rsync tarball since those ports won't be used. You can delete the 
> things related to ports in /opt/local/var/macports/sources too. (The ones 
> related to base can stay, or will be recreated when you selfupdate.)
> 
> What is file:///Users/craigtreleaven/mp/macports-ports? Is it a git clone of 
> the macports-ports repository? Ours or your fork? What happens if you try to 
> update it with git manually? Is there an error? Or is perhaps a branch other 
> than master checked out?
> 

Hi Ryan:

I seem to have it fixed.  I guessed that PortIndex (in 
/Users/craigtreleaven/mp/macports-ports) might be damaged so I moved it aside 
temporarily and ran ’sudo port -d sync’.  After it chugged away, it reported a 
whole bunch of ports were outdated.  

In the past, I’ve had to blow away my git clone (not fork) from time to time 
when I messed up something.  That’s the reason I’ve kept both the standard 
MacPorts-installed tree and the git clone.  Is there any harm in having both?

Thanks,

Craig

Port tree not syncing

[Craig Treleaven]

Hi:

I’m a port maintainer…but I’m having a user problem.  For some weeks now, ‘sudo 
port selfupdate’ has not been properly updating my local ports tree(s) on my 
main Mac.  About 2 weeks ago, I was going to post a question about this but 
then I ran ‘sudo port -d selfupdate’ and it seemed that all the missed updates 
were now caught up.  I put it down to gremlins in the ether but then I noticed 
recently that I had no outdated ports when I knew that there should be several. 
 I tried ’sudo port -d sync’ with the same result, ie no updates.

Obviously, ’sudo port selfupdate’ has worked flawlessly for me for quite a few 
years.  TTBOMK, I haven’t changed anything relevant on my side.  I’m overdue to 
update my OS version (I’m on 10.15.7).  

I’ve pasted the debug log from ’sudo port -d sync’ in case that shows something 
useful:

https://paste.macports.org/69b104de0e93

BTW, I have another older Mac that also has MacPorts installed.  ’sudo port 
selfupdate’ continues to work as expected on that machine.

Suggestions on what’s wrong and how to fix it?

Thanks,

Craig

Re: PHP80

[Craig Treleaven]

> On May 5, 2022, at 2:13 PM, JEFFRY KILLEN  wrote:
> 
> Hello:
> 
> I am new to macports. My current interest to so install php on
> MacOS Monterey. But I do no see specific info on what PHP80
> installs. Is it just a CLI installation, or is there a module that can
> be used with localhost Apache?
> 
> If not for web server, is there a port that will install php. Or do I
> have to reinstall Apache with configuration for using php? It has
> been a while since I have had to negotiate these details.
> 
> Some 12 years ago I compiled and installed Apache with php 
> from source on a FreeBSD system.
> 
> Thanks for time and attention:
> JK

Hi:

Have you had a look at the howto page on for PHP?

https://trac.macports.org/wiki/howto/PHP 


Craig

Re: get_iplayer out of date

[Craig Treleaven]

cc’ing the maintainer…



> On Apr 7, 2022, at 11:56 AM, Mark Lucas  wrote:
> 
> The current MacPorts version of get_iplayer 3.27 is out of date. Recent 
> updates appear to include a number of significant changes, the current 
> version stands at 3.29
> Any chance of an update to the MacPorts package to the latest version?
> 
> Thanks
> Mark Lucas
> 

Re: Does MacPorts depend on Spotlight?

[Craig Treleaven]

> On Nov 18, 2021, at 9:47 AM, Eric Gallager via macports-users 
>  wrote:
> 
> On Thu, Nov 18, 2021 at 3:02 AM Ryan Schmidt  wrote:
>> 
>> MacPorts base doesn't do anything with Spotlight. It doesn't depend on it 
>> existing, nor does it tell Spotlight to index or not to index anything. 
>> MacPorts predates the existence of Spotlight.
>> 
>> As far as I know, ports don't depend on Spotlight having indexed the 
>> MacPorts prefix or the build directory. On the MacPorts buildbot machines, I 
>> exclude /opt/local and /Applications/MacPorts from the Spotlight index in 
>> order to reduce disk writes. As far as I know, this hasn't caused any build 
>> failures.
>> 
>> I do recall at least one port where we discovered that it was using `mdfind` 
>> (the command line utility for finding files using the Spotlight index) to 
>> find something it needed (Xcode, if I recall), and this failed for a user 
>> who had excluded either /Applications or maybe their whole disk from 
>> Spotlight or turned Spotlight off entirely, so I don't recommend doing that.
>> 
> 
> Didn't MacPorts start doing `chflags hidden` on
> /opt/local/var/macports at some point to stop Spotlight from indexing
> it? If it wasn't actually to stop Spotlight from indexing it, then why
> hide it? Also Fink makes Spotlight avoid its build directory by giving
> it a `.build` suffix; apparently a `.noindex` suffix ought to work,
> too; I've thought for a while that MacPorts should use one of these
> suffixes as well. Also Fink supplies a package that provides an
> importer that allows Spotlight to index its info files, which is
> something that I've wondered if it could be ported to MacPorts to
> create an `.mdimporter` for Portfiles, too:
> https://github.com/fink/fink-distributions/blob/4b95ece57eb9acdf68b7d4390914b59e16370bff/10.4/stable/main/finkinfo/devel/finkinfofile.info


There was some discussion of alternative ways to avoid indexing, all the way 
back in 2014:

https://www.mail-archive.com/macports-dev@lists.macosforge.org/msg26538.html 


Craig

Migration after hardware failure

[Craig Treleaven]

Hi:

My old computer, which was running OS X 10.10, failed and I’ve replaced it with 
anew iMac running 10.15.  The drive in the old system was fine so I pulled it 
out and mounted it in an external enclosure so I could recover my file using 
Migration Assistant.

Looking at the Migration instructions [1], I don’t quite fit any of the 
mentioned scenarios.  If I try to get a list of requested ports, it fails 
thusly:

$ port echo requested
Error: Current platform "darwin 19" does not match expected platform "darwin 14"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch

Do I just need to install the correct version of MacPorts for this OS or is 
there something else I should be doing?

[1] https://trac.macports.org/wiki/Migration

Thanks,

Craig

Re: configure error on compile ports

[Craig Treleaven]

> On Feb 14, 2021, at 1:22 PM, rmgls  wrote:
> ...
> :info:configure checking for gcc... /usr/bin/clang
> :info:configure checking for C compiler default output file name... 
> :info:configure configure: error: C compiler cannot create executables
> 
> some details:
> osx11.2. new macports (/opt/local entirely deleted first).
> gcc and clang correctly seated in /usr/bin and running fine.
> xcode up-to-date, and commandline tools installed!

Have you installed the Xcode command line tools and accepted the license?

https://www.macports.org/install.php

Craig

Re: How to cross compile Apple Silicon target under Intel Apple computer ?

[Craig Treleaven]

> On Jan 28, 2021, at 12:30 PM, Gilles Caulier  wrote:
> 
> 
> Of course as expected it stop after a long computation. It's about a
> ffmpeg dependency : gmp
> 
> [macports/tools] > clean gmp
> --->  Cleaning gmp
> [macports/tools] > install gmp
> --->  Fetching distfiles for gmp
> --->  Verifying checksums for gmp
> --->  Extracting gmp
> --->  Applying patches to gmp
> --->  Configuring gmp
> Error: Failed to configure gmp, consult
> /opt/digikam.org.arm64/var/macports/build/_opt_digikam.org.arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.2.1/config.log
> Error: Failed to configure gmp: configure failure: command execution failed
> Error: See 
> /opt/digikam.org.arm64/var/macports/logs/_opt_digikam.org.arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gmp/gmp/main.log
> for details.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port gmp failed
> 
> Are you agree that i open a generic file in bugzilla about digiKam
> deps broken with Silicon ?

Hmm, as of now, our user-submitted stats show that there are 14 installations 
of gmp on arm64:

https://ports.macports.org/port/gmp/stats?days=30_ago=0

I presume that is people with M1 Macs that have built and installed the 
software on that machine.

The gmp port has some interesting comments and code related to informing 
configure of the (build?) CPU in order to get the best performance from the 
compiled code:

https://github.com/macports/macports-ports/blob/master/devel/gmp/Portfile#L104

If I read this right (which is not at all assured), it looks like for 
non-universal builds, it is assuming that the build and target machines must 
have the same CPU.  Which is the opposite of your case.  Perhaps you would have 
more success if you tried to build everything universal?

The log referred to in the error messages  
(/opt/digikam.org.arm64/var/macports/logs/_opt_digikam.org.arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gmp/gmp/main.log)
 should confirm if this was the problem.

If you need to file a ticket, have it refer to the port that is failing.  It is 
not especially relevant that you are trying to install it as part of the 
installation of DigiKam.  

Craig

Re: Desolate Condition

[Craig Treleaven]

Please be sure to copy the macports-users mailing list with your replies.

I’m not familiar with any of the desktop environments that you’ve listed.  I do 
note that we have around 300 entries each in the Gnome and KDE sections of our 
repository:

https://ports.macports.org/ports/category/kde/

https://ports.macports.org/ports/category/gnome/

We have many fewer entries for GNUStep and Xfce.  I would try picking one app 
in one of the categories and try to install it.  If you continue to have 
problems, post the details or file a support ticket (and attach the main.log).  
Someone can likely help if you give details on a specific problem.  Without 
those details, all we can do is guess.

Craig

> On Jan 26, 2021, at 7:57 PM, Tom  wrote:
> 
> Hi,
> 
> I have Xcode 12.3 installed. I am using it.
> FreeCAD is not so important.
> Important would be Gnome, KDE, Xfce, GNUStep. How can I build and start them?
> Xfce builds and starts, but does not seem to work correctly.
> 
>> On 26. Jan 2021, at 19:32, Craig Treleaven > <mailto:ctrelea...@cogeco.ca>> wrote:
>> 
>>> On Jan 26, 2021, at 12:02 PM, Tom >> <mailto:thomas.bodl...@web.de>> wrote:
>>> 
>>> I am using Big Sur 11.1
>>> Which macOS are you using?
>>> I am installing new ports.
>>> 
>>> tom@Toms-Mac-Pro ~ % port diagnose
>>> Warning: No Xcode version info was found for your OS version.
>>> Warning: found dylibs in your /usr/local/lib directory. These are known to 
>>> cause problems. We'd recommend  you remove them.
>>> 
>>> tom@Toms-Mac-Pro ~ % ls -l /usr/local/lib 
>>> total 2088
>>> drwxr-xr-x  3 root  wheel   96 Nov 20 22:29 docker
>>> drwxr-xr-x  3 root  wheel   96 Apr 28  2020 dtrace
>>> -rw-r--r--@ 1 root  wheel  1064880 Oct 16  2015 libgmp.a
>>> -rwxr-xr-x@ 1 root  wheel  864 Oct 16  2015 libgmp.la 
>>> <http://libgmp.la/>
>>> drwxr-xr-x  3 root  wheel   96 Apr 29  2020 node_modules
>>> drwxr-xr-x  2 root  wheel   64 Dec  2 21:42 pkgconfig
>>> 
>>> I tried to build for example: FreeCAD, Wine-Crossover, virt-manager, 
>>> Kopete, qt4-mac, Gnome, KDE, GNUStep
>>> 
>> 
>> The first issue is Xcode; it must be installed.  You must also agree to the 
>> Xcode license.  See:
>> 
>> https://www.macports.org/install.php <https://www.macports.org/install.php>
>> 
>> Next, it is impossible to predict if the things you have installed in 
>> /usr/local/lib will conflict or not.  But if you have an install failure, if 
>> can waste a lot of time if that turns out to be the problem.  I suggest 
>> (strongly) that you at least temporarily rename that directory while 
>> installing with MacPorts.
>> 
>> Big Sur may be another issue.  It is still quite new and changed enough 
>> things that it caused some of our ports to break.  Do you have an Intel or 
>> ARM Mac?  More details of Big Sur issues at:
>> 
>> https://trac.macports.org/wiki/BigSurProblems 
>> <https://trac.macports.org/wiki/BigSurProblems>
>> 
>> Finally, it appears that some o the ports you are trying to install may be 
>> broken at present.  Taking the first one you listed, FreeCAD, there is an 
>> open support ticket that might be the problem you are experiencing:
>> 
>> https://trac.macports.org/ticket/60039 
>> <https://trac.macports.org/ticket/60039>
>> 
>> Basically, FreeCAD depends on boost.  Boost was changed last year to default 
>> to a Python version that is incompatible with with FreeCAD.  However boost 
>> can be installed with an appropriate version.  Try:
>> 
>> sudo port clean freecad
>> sudo port install boost +python27
>> sudo port install freecad
>> 
>> If that still fails, the error messages will tell you where to find 
>> “main.log” which should identify the actual issue.
>> 
>> HTH,
>> 
>> Craig
>> 
> 
> Tom
> thomas.bodl...@web.de <mailto:thomas.bodl...@web.de>

Re: Desolate Condition

[Craig Treleaven]

> On Jan 26, 2021, at 12:02 PM, Tom  wrote:
> 
> I am using Big Sur 11.1
> Which macOS are you using?
> I am installing new ports.
> 
> tom@Toms-Mac-Pro ~ % port diagnose
> Warning: No Xcode version info was found for your OS version.
> Warning: found dylibs in your /usr/local/lib directory. These are known to 
> cause problems. We'd recommend  you remove them.
> 
> tom@Toms-Mac-Pro ~ % ls -l /usr/local/lib 
> total 2088
> drwxr-xr-x  3 root  wheel   96 Nov 20 22:29 docker
> drwxr-xr-x  3 root  wheel   96 Apr 28  2020 dtrace
> -rw-r--r--@ 1 root  wheel  1064880 Oct 16  2015 libgmp.a
> -rwxr-xr-x@ 1 root  wheel  864 Oct 16  2015 libgmp.la 
> drwxr-xr-x  3 root  wheel   96 Apr 29  2020 node_modules
> drwxr-xr-x  2 root  wheel   64 Dec  2 21:42 pkgconfig
> 
> I tried to build for example: FreeCAD, Wine-Crossover, virt-manager, Kopete, 
> qt4-mac, Gnome, KDE, GNUStep
> 

The first issue is Xcode; it must be installed.  You must also agree to the 
Xcode license.  See:

https://www.macports.org/install.php

Next, it is impossible to predict if the things you have installed in 
/usr/local/lib will conflict or not.  But if you have an install failure, if 
can waste a lot of time if that turns out to be the problem.  I suggest 
(strongly) that you at least temporarily rename that directory while installing 
with MacPorts.

Big Sur may be another issue.  It is still quite new and changed enough things 
that it caused some of our ports to break.  Do you have an Intel or ARM Mac?  
More details of Big Sur issues at:

https://trac.macports.org/wiki/BigSurProblems 


Finally, it appears that some o the ports you are trying to install may be 
broken at present.  Taking the first one you listed, FreeCAD, there is an open 
support ticket that might be the problem you are experiencing:

https://trac.macports.org/ticket/60039

Basically, FreeCAD depends on boost.  Boost was changed last year to default to 
a Python version that is incompatible with with FreeCAD.  However boost can be 
installed with an appropriate version.  Try:

sudo port clean freecad
sudo port install boost +python27
sudo port install freecad

If that still fails, the error messages will tell you where to find “main.log” 
which should identify the actual issue.

HTH,

Craig

Re: Desolate Condition

[Craig Treleaven]

> On Jan 24, 2021, at 6:05 PM, Tom  wrote:
> 
> MacPorts is in a desolate condition.
> Nearly nothing is building.
> Can somebody try to build everything and fix the errors?

If you could give us some more information, we might be better able to help.  
It sounds like MacPorts used to work for you but is not now?  Are you trying to 
upgrade existing ports or install new ports?  Etc.

Please try the command ‘port diagnose’.  It will run (for a surprising long 
time) and check a number of common issues that trip up users.  Please respond 
with any output.

Craig

Re: registry.db getting rather obese (> 600MB) and updates very slow. Anything to do?

[Craig Treleaven]

Hi:

I can’t help but I have the same issue as you—uninstalls take a long time.  My 
registry:

$ ls -la /opt/local/var/macports/registry/
total 1453344
drwxr-xr-x 7 root  wheel238 19 Jun 15:23 .
drwxr-xr-x@   17 root  admin578 28 Feb  2017 ..
-rw-r--r-- 1 root  wheel  0 19 Jun 15:20 .registry.lock
-rw-rw-r-- 1 root  wheel  0 20 Nov  2014 .turd_MacPorts
drwxr-xr-x  4088 root  wheel 138992 19 Jun 15:21 portfiles
drwxr-xr-x   234 root  wheel   7956 29 May 09:12 portgroups
-rw-r--r-- 1 root  wheel  744112128 19 Jun 15:23 registry.db

This is on a 2011 MacBook Pro (i7).

Craig

> On Jun 21, 2020, at 2:17 PM, Ken Cunningham  
> wrote:
> 
> On one of my systems, 10.5 PPC, things are taking a long time when 
> uninstalling a port - like 4-5 minutes of heavy tcl interpreter use.
> 
> The registry.db is pretty huge:
> 
> $ ls -la
> total 1286264
> drwxr-xr-x 7 root  admin238 21 Jun 11:06 .
> drwxr-xr-x@   15 root  admin510 18 Dec  2018 ..
> -rw-r--r-- 1 root  admin  0 21 Jun 10:59 .registry.lock
> -rw-rw-r-- 1 root  admin  0  1 Oct  2015 .turd_MacPorts
> drwxr-xr-x  2954 root  admin 100436 21 Jun 10:59 portfiles
> drwxr-xr-x   185 root  admin   6290 13 Jun 19:51 portgroups
> -rw-r--r-- 1 root  admin  658564096 21 Jun 11:06 registry.db
> 
> 
> As you can see, this install has been going along for 5 years, so I guess 
> some bitrot could occur. I’m sure I could blow out the installation and start 
> fresh, but that’s not terribly trivial on 10.5 PPC with no functional 
> buildbot. 
> 
> Is there something else I can do to put that registry.db on a diet?
> 
> Thanks,
> 
> Ken

Re: Mpv doesn't install

[Craig Treleaven]

> On May 12, 2020, at 12:00 PM, dan d.  wrote:
> 
> I tried to install mpv @0.31.0.  The binary install bombed which is sometimes 
> the case; likely there is no binary.
> 
> A install started; "make" but failed.
> 
> I'm using os10.10, might this have someting to do with it?

mpv is failing to build on the 10.10 buildbot as well:

https://ports.macports.org/port/mpv/summary

Check the main.log — does your issue match any of the 8 open trac tickets?

Craig

Re: help please

[Craig Treleaven]

> On May 15, 2019, at 12:58 AM, James Linder  wrote:
> 
> Error: Failed to install qt511-qtxmlpatterns: no destroot found at: 

Appears you’ve run into an intermittent problem with MacPorts that we’ve 
unfortunately never been able to track down and fix.

See:

https://trac.macports.org/wiki/ProblemHotlist#nodestrootfound

Just clean and try again.

Craig

Re: building octave fails

[Craig Treleaven]

> On Mar 10, 2019, at 10:47 PM, Ulrich Wienands  wrote:
> 
> Trying to build octave on OS X 10.10.6 Yosemite with Macports 2.4.3.
> 
> Sync'd port tree first
> 
> Then sudo port install octave... installs a bunch of dependencies but then 
> faiis with "invalid command name "startupitems".
> ...

Your MacPorts base software needs to be updated:

$ port version
Version: 2.5.4

Use ‘sudo port selfupdate’ or reinstall.

Craig

Re: Making `port mpgk' create smaller packages

[Craig Treleaven]

> On Mar 10, 2019, at 12:00 PM, Mojca Miklavec  wrote:
> 
> Dear Werner,
> 
> On Sun, 10 Mar 2019 at 08:24, Werner LEMBERG wrote:
>> 
>> trying
>> 
>>  port mpkg lilypond-devel
>> 
>> creates a 1.5GByte bundle, which is far too large to be used for
>> distribution.  Is there a possibility to reduce the number of packages
>> that gets bundled?
>> 
>> As far as I can see, the main problem is that build and run
>> dependencies are intermixed in Portfiles: If `foo' is necessary for
>> building and running, it gets only listed in `depends_lib'.
> 
> That's a clear bug in a Portfile specification (rather than in MacPorts).
> 
> Any dependency that's not required for running should be
> depends_build[-append] and any dependency that's not required for
> building the port should be depends_run[-append]. There's also
> depends_test, depends_fetch, ... (maybe more).
> 
>> Is it possible to provide a finer granularity?  For example,
>> `lilypond-devel' needs `texlive' for building only but not for
>> running.
> 
> In that case just move it from depends_lib[-append] to
> depends_build[-append] (in a PR, probably)
> 
>> Or may `port
>> mpkg' gets a new command line option to specify a list of packages
>> that should be omitted (together with its dependencies).
> 
> I'm pretty sure there is a lot of room for improvement of port mpkg.
> Maybe open a ticket for base in our Trac? (Improvements to mpkg might
> potentially even be suitable for GSOC projects.)
> 
> Mojca

I notice that gcc8 is also shown as a run time dependency which may be adding 
to the bulk of the package.  

You may want to run port-depcheck.sh against lilypond-devel to see if it 
identifies and inconsistencies in the dependencies.  The script is provided by 
the port ‘macportsscripts’.

Possibly the wiki page I put together may have a helpful tip or two regarding 
making an installer:

https://trac.macports.org/wiki/howto/CreateInstallers

Craig

Re: Bringing a package under the hood of Xcode - maybe OT ?

[Craig Treleaven]

> On Jan 11, 2019, at 3:12 PM, Christoph Kukulies  wrote:
> 
> I have a downloaded a library (open source) - libartnet to be more precise. 
> It’s a typical UNIX package with configure and Makefile. It compiled smoothly 
> (./configure ; make ) as I tried out on macOS mojave x64 architecture.
> 
> I would like to port this to the iPhone architecture. How could I achieve 
> this? Is there a way to cross compile it under macOS?
> 
> How does one import such large packages to Xcode. Pointers or links welcome 
> as well.

It is this library, right:

https://www.openlighting.org/libartnet-main/

If so, the home page says: "libartnet is an implementation of the ArtNet 
protocol for Linux, Mac, iOS, & Windows (via mingw).”  So it appears you don’t 
need to “port this to the iPhone” since iOS is already supposed to be supported.

At some point, libartnet was brought to MacPorts:

$ port info libartnet
libartnet @1.0.7 (multimedia, net)
Variants: universal

Description:  implementation of the ArtNet protocol designed for POSIX 
systems
Homepage: http://www.nomis52.net/data/artnet/libartnet/

Platforms:darwin
License:  LGPL-2.1
Maintainers:  none

It appears our version is out of date and the project has moved to GitHub at 
some point.

Craig

Re: Using macports to create binary package

[Craig Treleaven]

Others will have to advise you on dylibbundler; it doesn’t do what I need so 
I’ve never used it.

Does your app provide a Mac gui?  Otherwise, it doesn’t make sense to create an 
app bundle.

Craig

> On Jul 20, 2018, at 11:03 AM, Manav Bhatia  wrote:
> 
> I typically do:
> 
> $ port install openmpi-clang hdf5 eigen boost 
> 
> before building my application. This installs (a lot of) dependencies, 
> including gcc. 
> 
> Thanks for pointing me to dylibbundler. I was not aware of that. I will look 
> into the details of this package. 
> 
> Will this be able to take ports installed in a default /opt/local location 
> and pack them in an app bundle? 
> 
> -Manav
> 
>> On Jul 20, 2018, at 9:53 AM, Craig Treleaven > <mailto:ctrelea...@macports.org>> wrote:
>> 
>>> On Jul 20, 2018, at 8:51 AM, Manav Bhatia >> <mailto:bhatiama...@gmail.com>> wrote:
>>> 
>>> Thanks. 
>>> 
>>> I saw some instructions related to octave that describes creations of an 
>>> app bundle that can be put anywhere: 
>>> https://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_MacPorts 
>>> <https://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_MacPorts>
>>> 
>>> One of the commands they used is install_name_tool: 
>>> install_name_tool -change /opt/local/libiconv.2.dylib 
>>> @executable_path/../lib/libiconv.2.dylib Octave-3.7.0+
>>> 
>>> So, if I only keep the specific header files and relevant dyld files, with 
>>> enough care something like this should be possible (?). 
>>> 
>>> -Manav
>>> 
>> 
>> Creating a Mac application bundle is a somewhat different objective from 
>> what I thought was your stated goal.  You haven’t said what you want to 
>> package.
>> 
>> If it is appropriate to package your app as an app bundle, then perhaps 
>> dylibbundler is what you need.  Check ‘port info dylibbundler’ and ‘port 
>> gohome dylibbundler’.
>> 
>> Craig
> 

Re: Using macports to create binary package

[Craig Treleaven]

> On Jul 20, 2018, at 8:51 AM, Manav Bhatia  wrote:
> 
> Thanks. 
> 
> I saw some instructions related to octave that describes creations of an app 
> bundle that can be put anywhere: 
> https://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_MacPorts 
> 
> 
> One of the commands they used is install_name_tool: 
> install_name_tool -change /opt/local/libiconv.2.dylib 
> @executable_path/../lib/libiconv.2.dylib Octave-3.7.0+
> 
> So, if I only keep the specific header files and relevant dyld files, with 
> enough care something like this should be possible (?). 
> 
> -Manav
> 

Creating a Mac application bundle is a somewhat different objective from what I 
thought was your stated goal.  You haven’t said what you want to package.

If it is appropriate to package your app as an app bundle, then perhaps 
dylibbundler is what you need.  Check ‘port info dylibbundler’ and ‘port gohome 
dylibbundler’.

Craig

Re: Using macports to create binary package

[Craig Treleaven]

> On Jul 20, 2018, at 12:41 AM, Manav Bhatia  wrote:
> 
> Hi, 
> 
>   I have an application code that uses several dependencies that I typically 
> install using macports. I am interested in creating an installer that can 
> include these dependencies in addition to my compiled code. The objective is 
> to be able to give it to other users so that they can use it on their 
> computer without having to install macports. 
>  
>   I have seen the instructions on macports: 
> https://guide.macports.org/chunked/using.binaries.html 
> 
> https://guide.macports.org/chunked/installing.macports.html#installing.macports.source.multiple
>  
> 
>  
> 
> 
You should also look at:

https://trac.macports.org/wiki/howto/CreateInstallers

>   There are a few points that are still unclear to me. 
> 
> — I have compiled macports from source with 
> —prefix=/my/home/director/macports , and I am installing relevant ports 
> there. If I create a package using macports, does it also need to exist in 
> the same location on some other users’s computer? Or can it be moved around 
> to any folder in the user’s directory. 
> 
> — I am suspecting that there is a way to set library paths/rpaths/etc. 
> relative to the package directory. (For example, 
> https://wincent.com/wiki/%40executable_path%2C_%40load_path_and_%40rpath 
> ). 
> Is this automatically done by the macports package builder?
> 
The packaged software will be delivered to exactly the same location as it was 
on your build machine.  I’ve packaged a digital video recorder application so I 
used the prefix ‘/opt/dvr’.  I suggest using something similar for your app.

> — can the precompiled binaries only be used for macports in /opt/local?  My 
> current installation process (to the non-standard directory) is compiling 
> from scratch. (NOTE: this is on Mac OS 10.13.6). 
> 
That is expected; it isn’t possible for MacPorts to re-locate from one install 
prefix to another.  There is no definitive list of the things that depend on 
the install location.  May include libraries, scripts, help files, etc.

You also need to determine what target operating systems you can and will 
support.  I found it helpful to set up VM’s with the oldest and newest OS 
versions and test deployment to each.  

>   I would greatly appreciate some guidance on these. 
> 
> Thanks,
> Manav
> 
Hope this helps; feel free to ask any other questions.

Craig

Re: Advice on distributing a project

[Craig Treleaven]

> On Jun 14, 2018, at 1:58 PM, Langer, Stephen A. (Fed) 
>  wrote:
> 
> On 6/13/18, 8:37 PM, "Craig Treleaven"  wrote:
> 
>> On Jun 13, 2018, at 6:35 PM, Rainer Müller  wrote:
>> 
>> On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
>>> (2) Package all of the compiled libraries and dependencies into a Mac-like 
>>> app and distribute binaries, but not a portfile.  Will "port pkg"  do this 
>>> if I write a portfile for the project?  Can I tell it to include the vtk 
>>> libraries that have been built outside of MacPorts?
>> 
>> You could use 'sudo port mpkg', which creates a single .pkg installer
>> that includes the files for the port and all of its dependencies. This
>> assumes that you have a port that provides the required vtk libraries.
>> It is not possible to include extra files that are not provided by a port.
>> 
>> If you are going to distribute this installer, please use a prefix other
>> than /opt/local for it, to avoid a collision for users that also use
>> MacPorts.
>> 
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fguide.macports.org%2F%23using.binaries.binary-packages=02%7C01%7Cstephen.langer%40nist.gov%7C13c0320a0b5d4cbf5f6008d5d18ef78f%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C1%7C636645334320959905=VhTttsZ3dydXb7vatIRiExciRimMpMa38%2Bj6zLNeTZE%3D=0
> 
>If you anticipate that some or all the users will have MacPorts installed, 
> creating an installer with MacPorts _may_ lead to problems even though you 
> use a non-default prefix when creating your installer.  That non-default 
> prefix is where your packaged software ends up on the user’s system.  If your 
> packaged software looks for utilities (or libraries) at run-time, the user’s 
> PATH could lead to version conflicts.  Hopefully this would not affect you 
> but it could lead to ‘wild-goose-chasing’ bugs.  Something to give thought to 
> before going down this path.
> 
>Re vtk, or any other dependency, you can create/modify any of the ports 
> for the deps so as to get the version you want.  See the guide section:
> 
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fguide.macports.org%2F%23development.local-repositories=02%7C01%7Cstephen.langer%40nist.gov%7C13c0320a0b5d4cbf5f6008d5d18ef78f%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C1%7C636645334320959905=uo57kLPv9JZjJnZDb9%2FTIVhAcqmojVI03kbfUhWjTJQ%3D=0
> 
>In addition to the guide section that Rainer linked, you might want to 
> review the following wiki page.  I’ve written up some tips and tricks…mostly 
> to aid my own memory.  Contributions encouraged!
> 
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.macports.org%2Fwiki%2Fhowto%2FCreateInstallers=02%7C01%7Cstephen.langer%40nist.gov%7C13c0320a0b5d4cbf5f6008d5d18ef78f%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C1%7C636645334320959905=5G7LcSLCO%2FSWO2W4b4TMIzWp2JOHMONoGWuHIjfnLq0%3D=0
> 
>If you get into the process and have questions or issues, don’t hesitate 
> to post to this mailing list.  I and others would be happy to try to help.
> 
>Craig
> 
> 
> Thanks for the advice.  If I make a new non-standardly located macports 
> directory on my system, build my program and all of its dependencies in that 
> directory (including dependencies that aren't packaged with macports), and 
> then package it with "port mpkg", is that guaranteed to avoid conflicts on 
> users' systems?  I'd be using both a non-default installation prefix in my 
> portfile, and also a non-default version of macports to build it.
> 

I can’t “guarantee” that there won’t be conflicts—I don’t know what you are 
trying to package!

If your software consists of a few C++ programs that link to libraries in the 
normal way, it is very likely that everything will be fine.  However, if you 
are packaging mostly scripts that call utilities (without a fully qualified 
path), there is the potential for breakage.

Then there are systems that look up plugins at run time, etc.

Suppose, for an extreme example, that a user had installed a few things with 
MacPorts several years ago.  They might have ancient versions of something 
(installed under /opt/local) where your package relies on an up-to-date version 
installed in your custom prefix (say /opt/fed).  The user’s PATH may still 
include /opt/local/bin and friends.  As long as all of the software you are 
packaging avoids using PATH to find things, it should be fine.  

HTH,

Craig

Re: Advice on distributing a project

[Craig Treleaven]

> On Jun 13, 2018, at 6:35 PM, Rainer Müller  wrote:
> 
> On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
>> (2) Package all of the compiled libraries and dependencies into a Mac-like 
>> app and distribute binaries, but not a portfile.  Will "port pkg"  do this 
>> if I write a portfile for the project?  Can I tell it to include the vtk 
>> libraries that have been built outside of MacPorts?
> 
> You could use 'sudo port mpkg', which creates a single .pkg installer
> that includes the files for the port and all of its dependencies. This
> assumes that you have a port that provides the required vtk libraries.
> It is not possible to include extra files that are not provided by a port.
> 
> If you are going to distribute this installer, please use a prefix other
> than /opt/local for it, to avoid a collision for users that also use
> MacPorts.
> 
> https://guide.macports.org/#using.binaries.binary-packages

If you anticipate that some or all the users will have MacPorts installed, 
creating an installer with MacPorts _may_ lead to problems even though you use 
a non-default prefix when creating your installer.  That non-default prefix is 
where your packaged software ends up on the user’s system.  If your packaged 
software looks for utilities (or libraries) at run-time, the user’s PATH could 
lead to version conflicts.  Hopefully this would not affect you but it could 
lead to ‘wild-goose-chasing’ bugs.  Something to give thought to before going 
down this path.

Re vtk, or any other dependency, you can create/modify any of the ports for the 
deps so as to get the version you want.  See the guide section:

https://guide.macports.org/#development.local-repositories

In addition to the guide section that Rainer linked, you might want to review 
the following wiki page.  I’ve written up some tips and tricks…mostly to aid my 
own memory.  Contributions encouraged!

https://trac.macports.org/wiki/howto/CreateInstallers

If you get into the process and have questions or issues, don’t hesitate to 
post to this mailing list.  I and others would be happy to try to help.

Craig

Re: upcoming removal of components from macOS Server: opportunity?

[Craig Treleaven]

> On Apr 16, 2018, at 7:39 PM, Richard L. Hamilton  wrote:
> 
> "In fall 2018, Apple will stop bundling open source services such as Calendar 
> Server, Contacts Server, the Mail Server, DNS, DHCP, VPN Server, and Websites 
> with macOS Server. Customers can get these same services directly from 
> open-source providers. This way, macOS Server customers can install the most 
> secure and up-to-date services as soon as they’re available."  
> https://support.apple.com/en-us/HT208312 
> 
> 
> For which of these (and others listed on the link) is there already a port, 
> esp. for the recommended (or most nearly identical) replacement?  How about 
> management GUIs?
> 
> Should there maybe also be a mention on a FAQ or wiki page of the collective 
> availability of easily installable alternatives via MacPorts?  If MacPorts is 
> able to provide replacements for most of the functionality, would further 
> publicity be appropriate?
> 
> Anything else that might be an opportunity to mitigate this annoyance that I 
> haven't mentioned?
> 

I got as far as finding Apple’s detailed documentation on the open source 
alternatives to the features that are being removed from Server.  

https://developer.apple.com/support/macos-server/macOS-Server-Service-Migration-Guide.pdf
 


Clearly, MacPorts would make it much easier to install a number of these 
software packages compared to the manual build processes outlined in the 
migration document.

A wiki page showing MacPorts alternatives might be a good start.  Some are 
obvious but in other cases there may be multiple packages that might suit a 
particular installation.  If the page contains the right keywords, it ought to 
be easy enough to find.

Craig

Re: problem with upgrading macport installed packages

[Craig Treleaven]

> On Apr 16, 2018, at 4:23 PM, Ryan Schmidt  wrote:
> On Apr 16, 2018, at 08:37, pagani laurent wrote:
> 
>> Here one such example :
>> 
>> […]
>> --->  Installing py36-six @1.11.0_0
>> --->  Activating py36-six @1.11.0_0
>> Error: Failed to activate py36-six: Image error: 
>> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc
>>  already exists and does not belong to a registered port.  Unable to 
>> activate port py36-six. Use 'port -f activate py36-six' to force the 
>> activation.
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-six/py36-six/main.log
>>  for details.
>> Error: Problem while installing py36-six
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> 
> Only MacPorts should install software in /opt/local, but MacPorts states 
> above that it did not install this file. So how did it get there? If you 
> don't know, the safest thing to do is uninstall MacPorts and all ports, 
> following the uninstallation instructions on the web site, and then reinstall 
> MacPorts and the ports you want.
> 

The unregistered files could possibly be from a badly-built installer package?  
Or the registry file got nuked at some point.

https://trac.macports.org/wiki/ProblemHotlist#xmlwf

Craig

Re: trying to install ATLAS

[Craig Treleaven]

> On Mar 15, 2018, at 8:29 AM, pagani laurent via macports-users 
>  wrote:
> 
> I reinstalled gcc5, both gcc5 and 7 are active but the result is the same.
> I desactivate gcc7 but Xcode gcc takes precedence upon Macports/gcc5 even 
> when I deactivate/reactivate the later.
> 

I’m not familiar with ATLAS but I think you need to choose one of the variants 
in order to build it with another compiler:

$ port variants atlas
atlas has the variants:
   gcc49: build using macports-gcc-4.9
 * conflicts with gcc5 mpclang37 perf
   gcc5: build using macports-gcc-5
 * conflicts with gcc49 mpclang37 perf
   mpclang37: use mp-clang-3.7 and gfortran
 * conflicts with gcc49 gcc5 perf
   nofortran: Forgo use of fortran compiler
   universal: Build for multiple architectures

Perhaps try

sudo port install atlas +gcc5

Also, some packages can take a very long time to build.  Adding the verbose 
flag can give you more feedback as the build progresses:

sudo port -v install atlas +gcc5

Craig

Re: running macports along with homebrew

[Craig Treleaven]

> On Feb 14, 2018, at 2:46 PM, Ken Cunningham  
> wrote:
> 
> 1. a one-line copy-paste install script that can be embedded into any webpage.

I could never understand that this is considered an advantage of Homebrew.  The 
idea of running a random script directly from a web page that purports to 
install useful software.  

Craig

Re: unknown +variant silently ignored

[Craig Treleaven]

> On Jan 3, 2018, at 2:34 PM, Jan Stary  wrote:
> 
> I just built "bitcoin +qt5", only to realize its "bitcoin +gui".
> While build the noneexistent +qt5 variant, the default variant
> was buit (which happens to be +daemon+wallet).
> 
> Is it intentional that a nonexistent variant is _silently_ ignored?
> Wouldn't it be less surprising if MP stopped with an error?
> Currently, a typo can result in something the user didnt want,
> eventhough it was easily avoidable.
> 
The variant specification is passed down to any dependencies that will be 
installed.  The current port can’t error out since that variant may be valid to 
one or more of the deps.  

Craig

Re: What's the push to require the latest Perl?

[Craig Treleaven]

> On Dec 31, 2017, at 11:46 PM, Bill Cole 
>  wrote:
> 
> Ah, so apparently the reason this met total silence was that it got 
> lost/dropped somewhere so only I thought it was posted. Odd...
> 
> Reposted message:
> 
> From: Bill Cole 
> To: macports-users@lists.macports.org
> Subject: What's the push to require the latest Perl?
> Date: Fri, 15 Dec 2017 18:00:20 -0500
> 
> In regards to https://trac.macports.org/ticket/55208 :
> 
> In doing pre-upgrade due diligence I ran across this:
> 
> # port rdeps p5.24-net-dns
> The following ports are dependencies of p5.24-net-dns @1.140.0_0:
>  perl5.24
> [...]
>  p5.24-net-libidn2
>libidn2
>  pkgconfig
>  autoconf
>xz
>  automake
>  libtool
>xattr
>  unzip
>  libunistring
>perl5
>texinfo
>  help2man
>perl5.26
>p5.26-locale-gettext
> 
> 
> That seems unhelpful... Why would help2man demand the absolute latest Perl? 
> Well, because the Portfile says it does. However, in the real world, help2man 
> is happy with any perl since 5.8.
> 
> Doing a 'port -y upgrade outdated' reveals that multiple ports are 
> threatening to demand perl5.26 if I try to upgrade them, like whois!? Because 
> it needs perl to build???
> 
> This is insanity. Can anyone convince me otherwise or even explain how this 
> hasn't led to an angry mob with torches and pitchforks? Because I have one of 
> each if anyone wants to join the revolt…

I’m not the best to explain the situation, but the issue basically comes down 
to manpower.  We have many thousands of ports and not all that many active 
maintainers.  It is felt that supporting multiple Perl versions drains 
resources that would be better spent keeping up to date.  Especially since 
older versions are no longer supported upstream or even receiving critical 
security fixes.

Since most users receive and install pre-compiled binaries, it doesn’t present 
a big burden when they upgrade.  Should a user be concerned about old versions 
wasting disk space, the port reclaim command is available to pare things down.

As the home page says: "We provide a single software tree that attempts to 
track the latest release of every software title (port) we distribute”.  Note 
the _latest release_ part.

Craig

Re: Security Update 11-29-2017

[Craig Treleaven]

Thanks for the report, but could you clarify?  Are the crashes with an 10.13.1 
host that has the Security Update applied?  Or an Updated 10.13.1 guest?  Are 
you saying that you were using dscl from the command line or that Parallels was 
calling it and crashing?

I presume this is under Parallels Desktop 13?  I have 13.2.0 (43213).

Craig

> On Nov 30, 2017, at 11:01 AM, S. L. Garwood  wrote:
> 
> Watch out for the update … it caused me some issues with Parallels Desktop. I 
> got repeated crashes in dscl - the command line directory services utility. 
> Apple must have plugged some thing Parallels was using. VMWare and VirtualBox 
> are fine.
> 
>> 
>> Date: Wed, 29 Nov 2017 20:51:32 +
>> From: Chris Jones 
>> To: Ryan Schmidt 
>> Cc: MacPorts Users 
>> Subject: Re: High Sierra security advisory: set your root account
>>  password
>> Message-ID: <01d969c9-5347-46fc-94ad-08b134033...@hep.phy.cam.ac.uk>
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Hi,
>> 
>> A security patch is now available, so the work around is no long needed. See
>> 
>> https://support.apple.com/en-gb/HT208315
>> 
>> Chris
>> 
>>> On 29 Nov 2017, at 12:42 am, Ryan Schmidt  wrote:
>>> 
>>> A vulnerability was discovered in macOS High Sierra (10.13, 10.13.1, 
>>> 10.13.2 beta) today that allows an attacker to gain root access to your 
>>> system if your root account is disabled and has no password set (which is 
>>> the default). If you are running High Sierra, please mitigate this attack 
>>> by enabling your root account and setting a strong password for it.
>>> 
>>> https://support.apple.com/en-us/HT204012
>>> 
>>> https://www.macrumors.com/2017/11/28/macos-high-sierra-bug-admin-access/
>>> 

Re: Questions on the update to Apache 2.4

[Craig Treleaven]

Minor further questions…I’m a real neophyte at web servers so be gentle!

It seems that mod_rewrite and mod_deflate are both commented out by default.  I 
believe they were both enabled in the prior version.  Is there any particular 
reason for the change?  

Is it safe to use an httpd.conf file from Apache 2.2 with the new version?  Or 
is it important to start with the new template and make necessary changes to it?

Craig

Re: buildbot build time

[Craig Treleaven]

> On Oct 25, 2017, at 7:45 PM, Mojca Miklavec  wrote:
> 
> On 25 October 2017 at 16:23, Ryan Schmidt wrote:
>> On Oct 25, 2017, at 03:28, db wrote:
>>> On 25 Oct 2017, at 07:35, Mojca Miklavec wrote:
 On 23 October 2017 at 10:40, db wrote:
> On 9 Oct 2017, at 12:46, Mojca Miklavec wrote:
>> That info is easy to read and collect from the buildbot. The keyword is: 
>> "to collect".
> I checked https://build.macports.org/json/help, but couldn't find it.
 For example:
 - 
 https://build.macports.org/json/builders/ports-10.13_x86_64-builder/builds/10627?as_text=1
 which corresponds to
 - 
 https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/10627
 
 The idea would be to write a script to iterate through all numbers
 from 1 on and store results somewhere.
 
 If you want the time estimate specifically, here might be the relevant
 information:
 
"name": "install-port",
 ...
"times": [
  1508901749.648058,
  1508901850.387383
]
 
 I guess the difference represents the seconds spent building the port.
>>> 
>>> Thanks. I was searching for "to collect" there and in base, to no avail.
> 
> "To collect" was not meant as a literate strings to search for, but as
> the main action that needs to be done.
> 
>>> Those are the start/end epochs that I need to subtract, for a single port.
>>> 
>>> How can I correlate portname to buildnumber?
> 
> You cannot at the moment.
> 
> What I envision is a script that would run once from number 1 on and
> then either daily or hourly to update for new builds. The script would
> then construct a database of builds and do some simple visualisation.
> The most important part would be to ask some simple app to return data
> about one particular port. I would expect it to return the list of all
> builds (including URLs) for that particular port, but most
> importantly, for each buildslave:
> - whether the last build succeeded or failed
>  - (if failed, whether it was a dependency or the port installation
> that failed)
> - commit timestamp / shasum & version of the port
> - whatever else seems relevant, potentially including the build time
> and size of the package
> 
>> I don't think scraping information from buildbot json files is the right way 
>> to collect this data. If we want to collect it, the buildbot scripts could 
>> be modified to do so.
> 
> I don't see any big difference. The important part would be to do it
> in the first place. How to do it most efficiently can be a subject for
> discussion, but parsing json files with a library seems the easiest
> approach to me, in particular because we are currently unable to
> modify the buildbot script to return us data about packages built in
> the past. We can always modify the build scripts later.
> 
>> But as I said before, I don't think the information is useful to collect.
> 
> Build time doesn't seem *the most* interesting part of information,
> but it is useful to know in any case.
> 
>> Besides the fact that the buildbot worker machines have different hardware 
>> specs than user hardware, not all of the buildbot workers run on the same 
>> hardware. A build will go faster on our High Sierra worker than on the 
>> Sierra worker, because the High Sierra worker has a faster processor. In 
>> addition, the buildbot workers are virtual machines, with multiple VMs 
>> running on a single host. So a build may be faster or slower depending on 
>> whether the other VMs that run on the same host are busy or not.
>> 
>> If all you want to do is display on a web site somewhere that a particular 
>> build of a port took a particular amount of time on our buildbot workers, 
>> ok. But I wouldn't try to use this information to, for example, modify 
>> MacPorts base to have it offer the user a prediction of how long the port 
>> will take to build on their system, because I don't think we can accurately 
>> predict that.
> 
> I would definitely not use it for that purpose. But having *some
> statistics* about which ports built and failed on which builder would
> be super super useful. What I miss most is quickly finding the build
> where a particular port failed to build. At the moment it's nearly
> impossible to find it.

If we’re going to do this, can we be a little more precise about “failed” 
builds?  

1) Any port that relies on a non-default variant “fails” on the buildbots.  All 
of my myth* ports will ALWAYS show a “failed” status on ALL of the buildbots 
for this reason.   I would rather that users were told that the build was “not 
attempted”.  Telling them that build “failed" isn’t helpful.

2) Any port that needs C++11 “fails” on the existing 10.7 and earlier buildbots.

3) Various ports have a pre-fetch block that checks the OS version and “fails” 
if it is not supported.

Assuming the above can be fixed, is the following a mock-up of the data we’d 
collect?  Each commit 

Re: Searching macports-users Archives

[Craig Treleaven]

> On Sep 4, 2017, at 9:43 AM, David Epstein  wrote:
> 
> Is there a way of searching Macports-users archive?
> They seem dauntingly large and unapproachable.
> 

http://www.mail-archive.com/macports-users@lists.macosforge.org/ 


Craig

Re: running macports along with homebrew

[Craig Treleaven]

> On Aug 31, 2017, at 9:46 AM, db <iams...@gmail.com> wrote:
> 
> On 31 Aug 2017, at 15:35, Craig Treleaven <ctrelea...@cogeco.ca> wrote:
>> What is it that you want that MacPorts does not provide?
> 
> As I said in my OP, missing ports and updated versions, cask...

Gentle reminders, regularily applied, tend to cure the ‘missing ports and 
updated versions’ issue.

Homebrew Casks appear to confuse many people, me included:

https://apple.stackexchange.com/questions/125468/what-is-the-difference-between-brew-and-brew-cask

AIUI, casks are supposed to help in two ways:  binary (only) packages and 
pre-compiled binaries.

MacPorts solved the second part several years ago.  As an aside, I think a lot 
of people using Homebrew never got this message.

For Homebrew, the binary-only Cask packages seem to be aimed at things like 
Google Chrome and similar.  I understand the attraction to having a command 
line way to check for and update my major packaged applications.  But, AFAICT, 
it is never going to work for purchased applications (Carbon Copy Cloner, 
Parallels Desktop, etc).  Given that I’m going to have to keep an eye out for 
such updates, it is not solving the whole problem.  And creates an opportunity 
for malicious software to be substituted, even temporarily.

Maybe I’m missing something important.

Craig

Re: running macports along with homebrew

[Craig Treleaven]

> On Aug 31, 2017, at 9:32 AM, db  wrote:
> 
> On 30 Aug 2017, at 10:16, Richard L. Hamilton  wrote:
>> the newer, safer convention is distinct subdirectories of /opt, for each 
>> package or set of commonly managed packages; thus, MacPorts by default uses 
>> /opt/local, XQuartz uses /opt/X11 (for the stuff that's not elsewhere), etc.
> 
> Is it a tacit convention? I couldn't find a source myself.
> 
> 
> Thank you all for the useful information. It seems only Umesh is actually 
> using homebrew though.

What is it that you want that MacPorts does not provide?  

Craig

Re: Mac port error

[Craig Treleaven]

> On Jun 22, 2017, at 12:13 PM, Simone Poli  wrote:
> 
> dear mac port users, I’ve just installed mac port, but no commando can be 
> executed on it, not even the sudo self update, no action is recognised:
> 
> MacBook-Pro-di-nicola-travaglia:/ SimonePoli$ port
> MacPorts 2.4.1
> Entering shell mode... ("help" for help, "quit" to quit)
> [/] > sudo 
> Error: Unrecognized action "port sudo"
> [/] > 
> 

Hi Simone:

Looks like you just need to enter your command on a single line in the 
Terminal.  Try:

sudo port selfupdate

Copy, then paste all three words into the Terminal and finally press Return.  
You will then be prompted to enter your password.  Enter your admin password; 
the same password that you used to install the MacPorts software.   You should 
then see some messages printed that describe the various steps that the 
‘selfupdate’ command goes through.  Some of the steps may take a minute or two 
to finish.  If all goes well, the command prompt in Terminal will be printed 
and will wait for you to enter the next command.

Official documentation is at:

https://guide.macports.org/#using


> I would like to ask also if the mac port platform could be used as a virtual 
> computer with the Lnux shell on it.


I’m not sure what you mean by this.  MacPorts makes several thousand software 
packages ("ports”) available on Mac OS X  Most of them were developed on the 
Linux operating system.  OS X is derived from unix, as is Linux, and therefore 
the operating systems share a fair bit in common.

If you could tell us more specifically what you want to do, perhaps we could 
suggest particular ports to install.

Craig

Re: Query on ffmpeg

[Craig Treleaven]

> On Apr 30, 2017, at 6:03 PM, Dave Horsfall  wrote:
> 
> Why is it that every week when I do the "port upgrade outdated" thing, 
> "ffmpeg" is invariably selected?  Is it really that unstable, or what?  
> It certainly ties up my poor little MacBook :-(

You can see the history of updates to the port at:

https://github.com/macports/macports-ports/commits/master/multimedia/ffmpeg

Not all of the changes will cause your installed version to be updated.  
Scanning the list, most of the updates are due to version updates of the 
underlying libraries like x265, libbluray, libdvdpsi, libvpx, etc.  Also, a new 
version of ffmpeg was released in March.

We’re not trying to be mean to your MacBook!  ;)  

Craig

Test to macports-users@lists.macports.org

[Craig Treleaven]

Message sometimes don’t go through for me; trying to determine why.

Craig

Re: Prevent MacPorts editing .bash_profile over and over again...

[Craig Treleaven]

AIUI, the following script is run to set up the user’s environment after the 
installer copies in all the payload files:

https://github.com/macports/macports-base/blob/master/portmgr/dmg/postflight.in#L90

Craig

> On Jan 29, 2017, at 9:13 AM, Barry  wrote:
> 
> I have been using the .pkg to reinstall MacPorts. I guess that does not check.
> 
> Barry
> 
> Barry
> 
> 
>> On 29 Jan 2017, at 02:52, Daniel J. Luke  wrote:
>> 
>> I think only the pkg installers do that - and they're supposed to not edit 
>> the $PATH if $prefix is already in there.
>> 
>> (ie if you upgrade using `port selfupdate` I don't think you have that 
>> problem).
>> 
>> Or am I mistaken?
>> 
 On Jan 28, 2017, at 4:56 PM, Barry  wrote:
 On 28 Jan 2017, at 16:37, Christopher Jones  
 wrote:
 Hi,
 
 It would be better yet if whatever it is that does this first checks to 
 see in the path it is about to add is already in the users PATH, and does 
 not add it again if already there…
>>> 
>>> That would be an improvement.
>>> 
>>> I would also like a way to say never edit my .bash_profile.
>>> Maybe a comment line specially formated.
>>> 
>>> # MacPorts: no-edit-path
>>> 
>>> Barry
>>> 
 Chris
 
> On 28 Jan 2017, at 4:31 pm, Barry Scott  wrote:
> 
> I want to be able to stop MacPorts Installation from editing my 
> .bash_profile.
> As it happens I already set all the env var that are needed my self.
> 
> Is there a “do-not-edit-bash-profile” settings somewhere?
> 
> So far I have 3 sets of the settings in the same file.
> 
> Barry
>> 
>> -- 
>> Daniel J. Luke
>> 
>> 
>> 
> 

Re: pan - start with script.app at the new Pan 0.141

[Craig Treleaven]

> On Jan 6, 2017, at 6:17 AM, FritzS - gmx  wrote:
> 
> Now with only
> do shell script "export PATH=\"/opt/local/bin:$PATH\" && pan“
> it works well.
> 
> PS: I am not a script guru - but now I understand this script line.

Apple has a comprehensive primer on shell scripting:

https://developer.apple.com/library/content/documentation/OpenSource/Conceptual/ShellScripting/ResultCodes,Chaining,andArgumentParsing/ResultCodes,Chaining,andArgumentParsing.html#//apple_ref/doc/uid/TP40004268-CH5-SW1

The only new element in the script is the ‘&&’ operator.  See the section on 
Chaining Execution at the above link.

Craig