Re: ftgl and gl2ps won't install

[Ryan Schmidt]

On Feb 10, 2021, at 14:59, Murray Eisenberg wrote:

> Is there any hope of soon getting ftgl and gl2ps to build (under Big Sur 11.1 
> with MacPorts — I’m using 2.6.99 — and Xcode CLT 12.5)?
> 
> I need the former to get gnuplot and then maxima. the latter to get octave.
> 
> See https://trac.macports.org/ticket/61210 and 
> https://trac.macports.org/ticket/61671. 

I think we got those two fixed now.

Re: MacPorts bash on Big Sur as default shell

[Peter West]

I set my default shell to /bin/bash.

I kept the contents of my .profile as they were, making sure to export all of 
the variables I wanted, and bracketed them with tests like so:

eval profile_read=\$${USER}_profile_read
if [ -n "$profile_read" ]
then {
echo `date` "~/.profile already read" >>/tmp/$USER.init_scripts
return
}
fi

…and…

eval export ${USER}_profile_read=true
echo `date` "~/.profile sourced" >>/tmp/$USER.init_scripts

if [ -x "/opt/local/bin/bash" ]; then
[ "$BASH" != "/opt/local/bin/bash" ] && exec /opt/local/bin/bash
fi


Peter


—
Peter West
p...@ehealth.id.au
“Martha, Martha, you are anxious and troubled about many things, but one thing 
is necessary.”


> On 11 Feb 2021, at 7:35 am, Mike Summers via macports-users 
>  wrote:
> 
> I'm not able to get MacPorts bash working in Terminal as the default shell.
> 
> This is fresh install of Big Sur 11.2 on a new machine, fresh install of 
> MacPorts. Only bash and bash-autocomplete are installed
> 
> Setting the shell in either the Terminal preferences or for my user to 
> /opt/local/bin/bash always leaves me in /bin/bash 
> 
> The "best" workaround so far is to start in zsh which has the PATH set 
> correctly and exec bash from there.
> 
> My old machine where has been through many upgrades including Big Sur "just 
> works", 
> 
> I've run out of ideas, I'd appreciate pointers.

Re: Debugging restore_ports.tcl

[Ryan Schmidt]

On Feb 9, 2021, at 21:26, Eric Gallager wrote:

> With git at least, there's a built-in command (`git bisect`) to assist
> with cases like this; would it be possible to add a similar feature to
> the restore_ports.tcl script?

That seems out of scope for what the script is meant to do.

It might be more productive for us to change the instructions to recommend that 
users install only the ports they requested, rather than all previously 
installed ports.

Re: Access to workdir on the build server?

[Ryan Schmidt]

On Feb 10, 2021, at 11:14, Rainer Müller wrote:

> Your suspicion is correct, all buildbots run on case-sensitive filesystems.
> Direct access is not possible and it is wiped directly after the build as disk
> space is a rare resource for this setup.
> 
> You can already see it when inspecting the tarball directly:
> 
> $ tar tf 76e6ecda942f9e328efde7883ad75aed7290b632.tar.gz
> KeePassKit-76e6ecda942f9e328efde7883ad75aed7290b632/
> ...
> 
> I am not sure if there is a canonical way to solve this with the github port
> group, but I think it could work to set the worksrcdir with the right
> capitalization:
> 
> worksrcdirKeePassKit-${version}

Don't do that. Instead, correct the github.setup line. It currently reads:

github.setup MacPass keepasskit 76e6ecda942f9e328efde7883ad75aed7290b632

The third word should be KeePassKit not keepasskit to match the capitalization 
on the GitHub web site.

Re: I am getting "the MacOS 11.2 SDK does not appear to be installed" warning — have manually installed Xcode 12.4 command-line tools

[Ryan Schmidt]

On Feb 10, 2021, at 01:02, Gregory Dodwell wrote:

> I have also followed all of the other recommendations outlined on the 
> Macports webpage for the same issue ... to no avail once I start running 
> "sudo port install ..." commands. 
> 
> M1 Macbook Pro; OS 11.2.1; Macports v2.6.4.
> 
> I run from my general account as a sudoer.
> 
> I have downloaded the Xcode 12.4 command line tools from Apple Developer, and 
> have run the recommended licence activation commands as privileged user. I 
> still get the warning ...

Ignore this message for now, since there is no released version of Xcode that 
contains the 11.2 SDK. In the future, when you once again have a version of 
Xcode that contains an SDK version that matches your OS version, pay attention 
to it again. A future version of MacPorts will change how it checks for your 
SDK and will allow minor version matches.

MacPorts bash on Big Sur as default shell

[Mike Summers via macports-users]

I'm not able to get MacPorts bash working in Terminal as the default shell.

This is fresh install of Big Sur 11.2 on a new machine, fresh install of
MacPorts. Only bash and bash-autocomplete are installed

Setting the shell in either the Terminal preferences or for my user to
/opt/local/bin/bash always leaves me in /bin/bash

The "best" workaround so far is to start in zsh which has the PATH set
correctly and exec bash from there.

My old machine where has been through many upgrades including Big Sur "just
works",

I've run out of ideas, I'd appreciate pointers.

ftgl and gl2ps won't install

[Murray Eisenberg]

Is there any hope of soon getting ftgl and gl2ps to build (under Big Sur 11.1 
with MacPorts — I’m using 2.6.99 — and Xcode CLT 12.5)?

I need the former to get gnuplot and then maxima. the latter to get octave.

See https://trac.macports.org/ticket/61210 
 and 
https://trac.macports.org/ticket/61671 
. 
---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 
Rockville, MD 20850-6667Mobile (413)-427-5334

Re: Access to workdir on the build server?

[Rainer Müller]

Hello Janosch,

thank you for contributing these ports for MacPass!

I think this topic would have been better on the macports-dev@ mailing list, as
it reaches more developers that can help with writing Portfiles.

On 10/02/2021 13.44, Janosch Peters via macports-users wrote:
> I am currently investigating a build failure of the new port keepasskit
> .

First of all, this port must be updated with a proper versioning scheme. You
cannot use the git commit hash, because the version must have a defined sort
order. Hashes are "arbitrary" values and with just two hashes, there is no way
to tell which one is newer. This is important as with the current versioning
scheme the port might never show up as outdated. The port would only be upgraded
if the next hash happens to be sorted alphabetically after the current one.

Normally tagged releases should be preferred, but apparently there are no recent
tags that are suitable for MacPass and KeePassKit.

For repositories without tags, a common option would be to use the date of the
commit in MMDD format. Or if this will return to "normal" version numbers at
some point, start from the last tagged release 2.4.7 and add an increment as a
suffix, such as 2.4.7-snapshotMMDD or similar.

https://guide.macports.org/#reference.portgroup.github.distfile

To correct this you will also have to increment the 'epoch' of the port, as that
is the only way to ensure the new version number format will upgrade all
existing installation.

> The problem only occurs on the build server, not on my local machine:
> 
> Error: Failed to extract keepasskit: error renaming
> "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_security_keepasskit/keepasskit/work/phc-winner-argon2-b31aa322566a8559403d419b2e9cd3f57957e394"
> to
> "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_security_keepasskit/keepasskit/work/keepasskit-76e6ecda942f9e328efde7883ad75aed7290b632/Argon2":
> no such file or directory
> 
> The full logfile is here:
> https://build.macports.org/builders/ports-11_x86_64-builder/builds/19836/steps/install-port/logs/stdio
> 
> Is there a way to inspect the workdir on the build server? I have a suspicion
> that this is a problem with case-sensitiveness but to be sure I would need to
> inspect the workdir.

Your suspicion is correct, all buildbots run on case-sensitive filesystems.
Direct access is not possible and it is wiped directly after the build as disk
space is a rare resource for this setup.

You can already see it when inspecting the tarball directly:

$ tar tf 76e6ecda942f9e328efde7883ad75aed7290b632.tar.gz
KeePassKit-76e6ecda942f9e328efde7883ad75aed7290b632/
...

I am not sure if there is a canonical way to solve this with the github port
group, but I think it could work to set the worksrcdir with the right
capitalization:

worksrcdirKeePassKit-${version}

Rainer

Access to workdir on the build server?

[Janosch Peters via macports-users]

I am currently investigating a build failure of the new port keepasskit 
.
 The problem only occurs on the build server, not on my local machine:

Error: Failed to extract keepasskit: error renaming 
"/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_security_keepasskit/keepasskit/work/phc-winner-argon2-b31aa322566a8559403d419b2e9cd3f57957e394"
 to 
"/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_security_keepasskit/keepasskit/work/keepasskit-76e6ecda942f9e328efde7883ad75aed7290b632/Argon2":
 no such file or directory

The full logfile is here: 
https://build.macports.org/builders/ports-11_x86_64-builder/builds/19836/steps/install-port/logs/stdio

Is there a way to inspect the workdir on the build server? I have a suspicion 
that this is a problem with case-sensitiveness but to be sure I would need to 
inspect the workdir.