Upgrade Xcode on Big Sur buildbot?

[Zhenfu Shi]

Can we have Xcode/CLT 13.1 or 13.2 on our Big Sur buildbot? 13.0 has a swift 
bug: https://github.com/apple/swift-corelibs-foundation/issues/3198 possibly 
affecting all ports using swift. An example: mpv fails to build because of 
this: https://build.macports.org/builders/ports-11_arm64-builder/builds/111255.

Zhenfu

qt6-qtwebengine missing icudtl.dat in Resources folder

[Zhenfu Shi]

Hi all,
I’m trying to upgrade my port sigil (an epub editor) to the next major version 
(see https://github.com/macports/macports-ports/pull/20359), and also use qt6 
instead of qt5. Right now it builds fine, but will crash on launch 
(SIGTRAP/SIGILL) because icudtl.dat is missing. qt5-qtwebengine does have this 
file installed. I tried fiddling a bit but couldn’t find out a way to install 
the file.Can anyone please help?

Thanks all,
Zhenfu

Re: Read environment variables from a file in launchd?

[Zhenfu Shi]

Thanks, that is a nice workaround.

Zhenfu

> On Jul 17, 2023, at 16:00, Rainer Müller  wrote:
> 
> On 17/07/2023 20.58, Zhenfu Shi wrote:
>> I’m looking for a way to import environment variables for a process started 
>> by launchd. systemd on Linux has EnvironmentFile key which allows env vars 
>> to be read from a file, can launchd do something similar?
>> I’m asking this because my cloudflared port has command line options 
>> hardcoded into its launchd script which gets overwritten on every upgrade. 
>> If I can somehow make those options read in from another file I can make 
>> them configuable to the users.
> 
> Unfortunately, I do not think this is easily possible with launchd.
> 
> The only solution I can think of would be to wrap it with a shell script. Or 
> use an external start script that reads the arguments from a file.
> 
> ProgramArguments
> 
>/bin/sh
>-c
>source /opt/local/etc/foo/options && exec /opt/local/bin/foo 
> $FOO_OPTIONS
> 
> 
> 
> Rainer

Read environment variables from a file in launchd?

[Zhenfu Shi]

Hi all,
I’m looking for a way to import environment variables for a process started by 
launchd. systemd on Linux has EnvironmentFile key which allows env vars to be 
read from a file, can launchd do something similar?
I’m asking this because my cloudflared port has command line options hardcoded 
into its launchd script which gets overwritten on every upgrade. If I can 
somehow make those options read in from another file I can make them 
configuable to the users.

Thanks,
Zhenfu

Re: iTerm2

[Zhenfu Shi]

I remember JOSM is an example, it does binary install on all systems.

Zhenfu

> On Jun 22, 2023, at 20:06, Mark Anderson  wrote:
> 
> iTerm2 is getting increasingly hard to support building using macports to 
> where I'm not even using the build - I've just been trying to fix it. The big 
> issue is that building it on the latest box with the latest Xcode works 
> great, but the developer rightly assumes that they can just send that binary 
> out to everyone and if you can't build it, well, download the binary.
> 
> So I'm wondering what exactly to do. We could download the binary for all but 
> the latest Xcodes/Macs or if you force it with a source build flag? I think 
> that might be the answer.
> 
> I'm open to any suggestions or input. Also, I'm not sure how to do binary 
> installs, are there examples? Java comes to mind for some reason.
> 
> —Mark
> ___
> Mark E. Anderson mailto:m...@macports.org>>
> MacPorts Trac WikiPage 
> GitHub Profile 
> 

Re: Notability reqiurement for submitted ports?

[Zhenfu Shi]

Thanks Ryan! It’s already up and I’ll be maintaining it.

Zhenfu

> On Nov 1, 2022, at 18:24, Ryan Schmidt  wrote:
> 
> 
> 
> On Oct 31, 2022, at 14:22, Zhenfu Shi wrote:
> 
>> Hi all,
>> I’m thinking about submitting a small utility written in C++ to MP that is 
>> really useful to only a small group of people (that is, rhythm gamers). Is 
>> there any notability requirements for submitted ports, like they have in 
>> Homebrew?
> 
> Nope! I would say feel free to submit a port for it, and if you want to 
> maintain it, that's even better.
> 

Notability reqiurement for submitted ports?

[Zhenfu Shi]

Hi all,
I’m thinking about submitting a small utility written in C++ to MP that is 
really useful to only a small group of people (that is, rhythm gamers). Is 
there any notability requirements for submitted ports, like they have in 
Homebrew?

Thanks,
Zhenfu

Re: Nodejs 16.16+: error:0308010C:digital envelope routines::unsupported

[Zhenfu Shi]

Thanks for the info, for now --openssl-legacy-provider fixed the build for 
filebrowser.
I have a PR open for nodejs16 adding an openssl11 variant, but I’ll probably 
change it to just ping to openssl11 instead.

Zhenfu

> On Aug 19, 2022, at 08:41, David Gilman  wrote:
> 
> When I did some sleuthing on this topic, which resulted in
> https://trac.macports.org/ticket/65515 , this was my finding:
> 
> - node before 17 doesn't really support openssl 3, resulting in the
> error you and I are seeing.
> https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V17.md#2021-10-19-version-1700-current-bethgriggs
> - node 16.17 added --openssl-legacy-provider, which allows for openssl
> 3 to work on node 16. However, this is an ugly breaking change:
> everyone needs to tweak their CLIs or export this through NODE_OPTIONS
> envvar.
> - for compatibility, node 16 and before should just build against
> openssl 1.1 by default. This is the combination that's being used by
> pretty much everyone out there.
> 
> On Thu, Aug 18, 2022 at 10:32 PM Zhenfu Shi  wrote:
>> 
>> Hi all,
>> Can someone please help me getting this error figured out? This error has 
>> been occurring since Nodejs 16.16 update and borked the build of my 
>> filebrowser port on all systems. Apparently it’s OpenSSL related, but all 
>> the workarounds I found failed in a way or another. Upstream said they could 
>> not reproduce this and our nodejs might have issues.
>> 
>> Build log: 
>> https://build.macports.org/builders/ports-12_x86_64-builder/builds/39078/steps/install-port/logs/stdio
>> Ticket: https://trac.macports.org/ticket/65691
>> Upstream issue: https://github.com/filebrowser/filebrowser/issues/2029
>> 
>> Thanks,
>> Zhenfu
> 
> 
> 
> -- 
> David Gilman
> :DG<

Nodejs 16.16+: error:0308010C:digital envelope routines::unsupported

[Zhenfu Shi]

Hi all,
Can someone please help me getting this error figured out? This error has been 
occurring since Nodejs 16.16 update and borked the build of my filebrowser port 
on all systems. Apparently it’s OpenSSL related, but all the workarounds I 
found failed in a way or another. Upstream said they could not reproduce this 
and our nodejs might have issues.

Build log: 
https://build.macports.org/builders/ports-12_x86_64-builder/builds/39078/steps/install-port/logs/stdio
 

Ticket: https://trac.macports.org/ticket/65691 

Upstream issue: https://github.com/filebrowser/filebrowser/issues/2029 


Thanks,
Zhenfu

macOS 13/Xcode 14 requiring code signing of all apps even on x86

[Zhenfu Shi]

Hi all,
It’s probably too early to talk about this but I would like to share something 
I found playing with the newest beta OS.
When trying to get iTerm2 port to build on macOS 13, Xcode spits out error "An 
empty identity is not valid when signing a binary for the product type [type]”. 
Previously to avoid signing problems, I or someone else had the identity 
removed, effectively disabling code signing. This apparently no longer works, 
and I had to use the adhoc signing identity “-“ for it to build.
This could affect a number of ports that are using Xcode to build apps, so I 
figured people here should know.

Zhenfu

Re: Git Gui missing? how to fix?

[Zhenfu Shi]

That file is part of git, you can just deactivate and reactivate git and MP 
will place the missing file back from the archive.
But that file will most likely go missing again some time later. No idea why 
but would be great if there’s a permant solution.

Zhenfu

> On Mar 28, 2022, at 11:47, John Douglas Owens via macports-dev 
>  wrote:
> 
> My linking-error scan has recently started flagging the following:
> 
> ---> Scanning binaries for linking errors
> Warning: Error parsing file /opt/local/share/git-gui/lib/Git 
> Gui.app/Contents/MacOS/Wish: Error opening or reading file
> 
> There is no /opt/local/share/git-gui/lib/Git Gui.app/ in my install. 
> (MacPorts 2.7.2, macOS 12.3, ARM). 
> 
> This doesn't hurt anything to not have this file, but it'd be nice to remove 
> the warning. Tips? (Any way to reinstall Git Gui?)
> 
> JDO

Re: Tcl text processing: Python 3.10 variants

[Zhenfu Shi]

Thanks. I’ll try if I can to your latter suggestion later, the portfile also 
uses this line with ${python.version} so it might not be that easy.

Zhenfu

> On Mar 21, 2022, at 16:13, Joshua Root  wrote:
> 
> On 2022-3-22 06:51 , Zhenfu Shi wrote:
>> Hi all,
>> I’m trying to add Python 3.10 variant to a few ports, but one of them (mpv) 
>> uses `set python_branch [join [split ${ver} {}] ".”]` to convert branch 
>> strings to version strings, resulting in “310” being converted to “3.1.0”. 
>> Can anyone advise how to change this line so it gives “3.10” without 
>> breaking compatibility with older Python versions?
> 
> Something like this works:
> 
> [string index $ver 0].[string range $ver 1 end]
> 
> However, it would be more reliable for mpv to start with versions containing 
> dots and strip them out when needed; something like:
> 
> set python.versions [list 3.8 3.9 3.10]
> foreach ver ${python.versions} {
>set ver_nodot [string map {. ""} $ver]
>...
> }
> 
> - Josh

Tcl text processing: Python 3.10 variants

[Zhenfu Shi]

Hi all,

I’m trying to add Python 3.10 variant to a few ports, but one of them (mpv) 
uses `set python_branch [join [split ${ver} {}] ".”]` to convert branch strings 
to version strings, resulting in “310” being converted to “3.1.0”. Can anyone 
advise how to change this line so it gives “3.10” without breaking 
compatibility with older Python versions?

Thanks,
Zhenfu

Re: Recent OpenSSL changes and CA certs

[Zhenfu Shi]

The axel port is also affected, it can't download anything that is https after 
this change.

Zhenfu

> On Oct 13, 2021, at 00:58, Aaron Madlon-Kay  wrote:
> 
> Hi all.
> 
> I know there are some important changes being made to the OpenSSL
> ports. Today I updated my ports and now have the following installed:
> 
> % port installed name:openssl
> The following ports are currently installed:
>  openssl @1.1_0 (active)
>  openssl10 @1.0.2u_2 (active)
>  openssl11 @1.1.1l_2 (active)
> 
> Apparently as a result of this, my Ruby environment (managed by rbenv
> + ruby-build, both available as ports) seems to no longer be able to
> connect to HTTPS hosts.
> 
> By some trial and error, I managed to find that symlinking the certs
> installed by the curl-ca-bundle port into the new "real" home of
> OpenSSL solved the problem:
> 
> sudo ln -s /opt/local/share/curl/curl-ca-bundle.crt
> /opt/local/libexec/openssl11/etc/openssl/cert.pem
> 
> Can anyone point me to a better solution?
> 
> I note that the Ruby OpenSSL module (built under the old OpenSSL port
> regime) is linked to /opt/local/lib/{libssl,libcrypto}.1.1.dylib. If I
> rebuild Ruby after updating to the new port regime, it is linked to
> /opt/local/libexec/openssl11/lib/{libssl,libcrypto}.1.1.dylib. Either
> way, SSL connections fail unless I symlink cert.pem as above. There
> are no apparent breakages in the linking itself.
> 
> Thanks,
> Aaron

PortIndex wasn't updated for 4 days?

[Zhenfu Shi]

Hi all,
I've been noticing that no ports have been upgraded on my systems for a few 
days, and checking rsync.macports.org/macports/release/tarballs/ 
 confirms that, the index 
was last updated on Feb 15. Just wondering what’s going on?

Zhenfu

mpv/waf: Nonexistent swift dylib got linked

[Zhenfu Shi]

Hi all,
When trying to upgrade mpv to 0.33.0 I ran in to the problem described in 
this ticket: https://trac.macports.org/ticket/61319 
 That is, this non existent dynamic 
library (/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib) got linked in mpv 
executable, causing port to rebuild this port in an attempt to fix it and 
eventually bail out. mpv works & play stuff just fine without this library.
   WIP PR: https://github.com/macports/macports-ports/pull/9213 
, thanks for any help.

Zhenfu

Re: Fetch problem on 10.11 and earlier (acpica)

[Zhenfu Shi via macports-dev]

> On Oct 18, 2020, at 21:33, Ryan Schmidt  wrote:
> 
> 
> 
>> On Oct 18, 2020, at 20:25, Zhenfu Shi wrote:
>> 
>> 
>> 
>>> On Oct 18, 2020, at 21:07, Ryan Schmidt wrote:
>>> 
>>> 
>>> 
>>> On Oct 18, 2020, at 20:04, Zhenfu Shi wrote:
>>> 
>>>> So in the future I need to find another site that mirrored the newest 
>>>> source and put it in (before the fix is implemented)?
>>> 
>>> Ideally yes.
>>> 
>>>> Also unrelated, how do I send messages from @macports.org address like you 
>>>> all could do? I currently have to have two addresses in the mailing list 
>>>> so I could send messages in.
>>> 
>>> That's just a matter of configuring your email client to offer an 
>>> additional "From" address that you can select from when you compose a 
>>> message. In Mail.app (on 10.13) that's in Preferences: Accounts: (your 
>>> account): Account Information: Email Address: Edit Email Addresses.
>>> 
>> Doesn’t seem to work with iCloud mail so I'm trying gmail. If this gets 
>> through then it’s working :P
> 
> It gets through, but shows your gmail address as the from address. I don't 
> think gmail supports customizing the from address anymore either.
> 
> With more ISPs introducing such restrictions, as well as problems we've seen 
> sending mail to some servers, we've been wondering if we need to offer an 
> smtp server or even an imap server, but I don't think we're very enthusiastic 
> about either of those.
> 
> 

Yeah it got to you but was rejected by the list. I’ll just use my current 
configuration for now.

Zhenfu

Re: Fetch problem on 10.11 and earlier (acpica)

[Zhenfu Shi via macports-dev]

> On Oct 18, 2020, at 11:48, Ryan Schmidt  wrote:
> 
> 
> 
> On Oct 17, 2020, at 19:34, Joshua Root wrote:
> 
>> On 2020-10-18 11:25 , Zhenfu Shi via macports-dev wrote:
>>> Hi all,
>>> 
>>> I’m trying to update acpica port to the latest version, but it seems
>>> like curl on 10.11 and earlier systems have problem taking to the
>>> server: Details
>>> <https://build.macports.org/builders/ports-10.11_x86_64-watcher/builds/38766>
>>> The last version is hosted on one other site other than the official
>>> site, which I believe is the workaround. Will installing macports curl
>>> as a build dep solve this?
> 
> No, adding a curl dep won't help. MacPorts downloads using the libcurl that 
> was linked with MacPorts when MacPorts was installed. It does not use a curl 
> executable nor can it use the libcurl in the curl port (unless configured to 
> do so when MacPorts was installed).
> 
>>> If not is there a way to fix this, other than
>>> hosting the file somewhere else?
>> 
>> Normally this wouldn't be a problem since the file would be mirrored to
>> distfiles.macports.org, but the system that does the mirroring couldn't
>> fetch it either:
>> <https://build.macports.org/builders/jobs-mirror/builds/208765/steps/mirror/logs/stdio>
>> 
>> Ryan might need to look into this one.
> 
> Mirroring did not work because mirroring currently happens on a machine 
> running 10.11. 10.11 is the last version officially supported on Xserve, and 
> since we store our data on the Xserve's RAID, I did not want to risk that 
> updating to a newer OS might make the RAID stop working, or worse stop 
> working correctly.
> 
> I worked around the problem by adding another download location to the acpica 
> port:
> 
> https://github.com/macports/macports-ports/commit/fcf6f6aa122dc2d113a41132ca1ae3da08df3db4
> 
> Note that I had fixed this once before:
> 
> https://github.com/macports/macports-ports/commit/418d0c03b7fa8f360f655c8e7af88fd19e85aa7a
> 
> As I redesign our buildbot setup for buildbot 2, my plan is to move the 
> buildmaster and mirroring to a separate VM running the latest OS version, 
> which should fix this problem. Until then, please make sure that the port 
> includes a viable second download location.
> 
> 

Thank you. So in the future I need to find another site that mirrored the 
newest source and put it in (before the fix is implemented)?
Also unrelated, how do I send messages from @macports.org address like you all 
could do? I currently have to have two addresses in the mailing list so I could 
send messages in.

Zhenfu

Fetch problem on 10.11 and earlier (acpica)

[Zhenfu Shi via macports-dev]

Hi all,

I’m trying to update acpica port to the latest version, but it seems like curl 
on 10.11 and earlier systems have problem taking to the server: Details 

The last version is hosted on one other site other than the official site, 
which I believe is the workaround. Will installing macports curl as a build dep 
solve this? If not is there a way to fix this, other than hosting the file 
somewhere else?

Thanks,
Zhenfu

waf.python configurable?

[Zhenfu Shi via macports-dev]

Hi all,
I’m working on mpv portfile but I couldn’t find a way to change {waf.python}, 
the python executable needed for waf. It’s currently failing to configure on 
buildbots. In https://trac.macports.org/ticket/57927 
 the original maker of waf portgroup 
said it is configurable. Anyone knows how?

Thanks,
Zhenfu

Re: Best way to get submodules into extracted source?

[Zhenfu Shi via macports-dev]

Thank you. this indeed works for transmission-x11 but not for transmission, 
because the release tarball only has some of the submodules. Maybe I’ll ask the 
dev to see if he can provide a complete one.

> On May 22, 2020, at 15:42, Joshua Root  wrote:
> 
> On 2020-5-23 05:16 , Zhenfu Shi via macports-dev wrote:
>> Hey guys,
>> I’m trying updating transmission(-x11) to just-released version 3.0, but it 
>> uses a lot of 3rd party submodules. I found the macports guide reads "the 
>> best distfile candidate (if available) is a distfile from GitHub releases”, 
>> so I’d like to know what’s the best way to put submodules into the extracted 
>> tarball, without using `fetch.type git` and `git submodule update —init`. 
>> Would be great if there’s a port already doing this so I could learn from it.
> 
> GitHub's auto-generated tarballs do not contain submodules, which is
> just one of the many reasons why projects should upload proper release
> tarballs. Fortunately, transmission does this, so it's just a matter of
> setting `github.tarball_from releases` and `use_xz yes`.
> 
> - Josh

Best way to get submodules into extracted source?

[Zhenfu Shi via macports-dev]

Hey guys,
I’m trying updating transmission(-x11) to just-released version 3.0, but it 
uses a lot of 3rd party submodules. I found the macports guide reads "the best 
distfile candidate (if available) is a distfile from GitHub releases”, so I’d 
like to know what’s the best way to put submodules into the extracted tarball, 
without using `fetch.type git` and `git submodule update —init`. Would be great 
if there’s a port already doing this so I could learn from it.

Thanks in advance!

Need help diagnosing weird build error of mpv on Catalina

[Zhenfu Shi via macports-dev]

Hi guys, 
I am having trouble making mpv build on Catalina with MacPorts. There seems to 
be some sort of dependency conflict preventing the build. There are ways to 
avoid the error, but I can’t figure out how to add a (proper) fix in the 
portfile. The WIP PR is here: 
https://github.com/macports/macports-ports/pull/7080 , it contains more info.

Thanks in advance!

Review request

[Zhenfu Shi via macports-dev]

Hi, can anyone please review my PRs? Two of them have been lingering for more 
than half a month.
https://github.com/macports/macports-ports/pull/7001 

https://github.com/macports/macports-ports/pull/6901 

https://github.com/macports/macports-ports/pull/6832 


Thanks!