Re: Fix: My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

On May 22, 2024, at 16:25, Gerben Wierda wrote: > > I was able to circumvent this autoconf failure by installing gettext before > installing dovecot, I don't know if that is the best solution, but ot works > (as in, it now installs). Yes that is the solution and I committed it here:

Re: livecheck and curl 8.7.1

> On Apr 20, 2024, at 22:12, Fred Wright wrote: > > there was a case a couple of years ago where MacPorts decided to prefer > python.org to the mirrors (at my location), and the fetch (on 10.9) would > hang in a way that wasn't subject to a timeout, so it never gave up and never > moved on

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

On Apr 5, 2024, at 13:03, Riccardo Mottola wrote: > > Odd/Even was an old practice, possibly not followed anymore. It was an old practice of GNOME abandoned in 2020. Graphviz, Cairo, Pango, Pixman, Glib2 are examples, from ports I maintain(ed). The MacPorts "gnome" livecheck recipe still

Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror

On Apr 5, 2024, at 03:52, Riccardo Mottola wrote: > > I propose to keep even versions, because they are stable ones Do you have a source for this claim? It's the first I've heard of it. As far as I know, all gcc version numbers are stable.

Re: how to handle 'internal' logs for failed builds

On Apr 4, 2024, at 17:29, Joshua Root wrote: > > Do that on a branch, make some change to the affected port as well, and push > to your fork and let CI run. That presumes it will fail in CI. If it succeeds in CI but fails on buildbot, suspect a case sensitivity issue.

Re: New port for ldc2

On Mar 24, 2024, at 15:52, P Padil wrote: > I’m trying to develop a new port for the d-lang ldc package (see attached), > but I’m having a hard time deciphering the macports guide as to how to > install something like this. It is a binary distributed in a tar.xz file > which has the bin, lib,

Re: Unable to build Xcode projects using SwiftPM in MacPorts sandbox

On Mar 23, 2024, at 23:00, Zero King wrote: > > I think it could be base's sandbox that prevented writes to the home > directory, where SwiftPM stores its cache. If disabling sandboxing in macports.conf makes it work, then your suspicion is probably correct. MacPorts sets the HOME

Re: Unable to access macports-infrastructure.git

> On Mar 12, 2024, at 19:46, Dave Allured wrote: > >  > I am getting an unusual builder error that is blocking my recent port update > on all of the builders. Go to console view on build.macports.org, find port > `gjs-devel`, and look at the stdio logs below the commit message. > > `fatal:

Re: jupytext port build cannot find jlpm

On Mar 12, 2024, at 10:00, Jonathan Stickel wrote: > > command not found: jlpm > > Recommendations for how to resolve this issue? One solution is to figure out where this program is being called in the source code, then patch it to use the program name as it appears in MacPorts (e.g. in this

Re: FYI, Ryan's email is bouncing...

> Email sent to ryandesign at macports.org goes to macports at ryandesign.com, > which then bounces. Hopefully Ryan is still seeing this, or someone knows how > to get in touch with him. My email provider deleted my forwarding rules and I didn't notice right away so this was broken for about 2

Re: { darwin any } ports getting reinstalled after OS upgrade

On Sep 27, 2023, at 06:09, Christopher Jones wrote: > > That just means they are *supported* on any drawn version. Each version > still have its own build. But that's just what "any" means: they build identically on any OS version. That's why only one single archive gets produced for these

Re: { darwin any } ports getting reinstalled after OS upgrade

On Sep 27, 2023, at 05:57, Nils Breunese wrote: > > I noticed that ports that use ‘platform { darwin any }’ get reinstalled > during this process, and ‘port outdated’ shows ‘(platform darwin 22 ≠ 23)’. > Does MacPorts really need to reinstall these ports if they’re marked as being > suitable

Re: Qt 5.10 skipped?

> On Aug 30, 2023, at 19:40, Jason Liu wrote: > > I just noticed that Qt 5.9 and Qt 5.11 are available in MacPorts, but not Qt > 5.10. Was there a specific reason why 5.10 was skipped, or was it just that > no one got around to it before 5.11 was released? Certainly qt 5.10.x existed in

Re: Buildbots down?

On Feb 6, 2023, at 14:09, Fred Wright wrote: > On Thu, 2 Feb 2023, Ryan Schmidt wrote: >> On Feb 2, 2023, at 18:25, Herby G wrote: >>> >>> There haven't been any builds for recent commits to master on Github in >>> over 24 hours at the moment of writing this.

Re: configure step downloading resources - supported on buildbots?

On Feb 6, 2023, at 05:46, René J.V. Bertin wrote: > Exploring Audacity's latest code I notice it requires the conan package > manager nowadays, for building "vendored" libraries. A number of those aren't > in MacPorts. > > From what I've seen this downloaded stuff goes into `build.dir` but I

Checksum mismatches for ports fetching from GitHub updated January 30, 2023

Last week we received four tickets about unusual checksum mismatches for distfiles that download automatically-generated tarballs from GitHub: https://trac.macports.org/ticket/66796 (bsdmake) https://trac.macports.org/ticket/66804 (libgit2) https://trac.macports.org/ticket/66805 (rav1e)

Re: Buildbots down?

On Feb 2, 2023, at 18:25, Herby G wrote: > > There haven't been any builds for recent commits to master on Github in over > 24 hours at the moment of writing this. > > https://build.macports.org/ is also failing to load. > > Can someone take a look? Unfortunately, Winter Storm Mara delivered

Re: macOS 13 builds down?

On Jan 28, 2023, at 07:59, Jimmy Yuen Ho Wong wrote: > On Sat, Jan 28, 2023 at 1:57 PM Jimmy Yuen Ho Wong wrote: > >> I've just upgraded to to macOS 13 from macOS 12 and noticed most of the >> ports I'm reinstalling are building from source. It looks like no ports for >> Ventura have ever been

Re: Request to re-run buildbots for a few ports

On Nov 28, 2022, at 14:34, Kirill A. Korinsky wrote: > May I ask anyone with access to reschedule build for ports: scalapack and > papilo? Jeremy scheduled a rebuild of scalapack on 10.7 which succeeded. Looks like it had already succeeded on the other workers before. I scheduled a rebuild of

Re: Notability reqiurement for submitted ports?

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 >

Re: having the "+test" or "+tests" variant propagate causes unexpected builds

On Oct 28, 2022, at 21:33, Daniel J. Luke wrote: > > I don't think implementation difficulty is the barrier here - but that all > variants should just have the same behavior. > > In my mind, the real problem is the need for +test variants, there should be > a way to just use the test phase -

Re: Removed ports still listed on ports.macports.org

On Oct 30, 2022, at 01:06, Mojca Miklavec wrote: > V ned., 30. okt. 2022 01:02 je oseba Nils Breunese napisala: >> Hi, >> >> The openjdk port was removed on August 25th after it had been obsoleted a >> while ago (https://github.com/macports/macports-ports/pull/15910), but I >> just noticed

Re: Disabled key in launchd plists

On Sep 17, 2022, at 04:58, René J.V. Bertin wrote: > > Ryan Schmidt wrote on 20220916::21:30:28 re: "Re: Disabled key in launchd > plists" > >> My reading of the documentation is that the system will start any launchd >> plists at system startup time that

Re: Disabled key in launchd plists

On Sep 15, 2022, at 14:48, René J.V. Bertin wrote: > Ryan Schmidt wrote on 20220915::13:36:25 re: "Re: Disabled key in launchd > plists" > >> Yes, to all of that, but none of that really relates to the question you >> asked about the Disabled key. > > I

Re: Disabled key in launchd plists

On Sep 15, 2022, at 11:01, René J.V. Bertin wrote: > > On Thursday September 15 2022 10:07:24 Ryan Schmidt wrote: >> Apple's default value of Disabled is false, which means (according to the >> documentation I read) that the service will be started automatically the >&

Re: Disabled key in launchd plists

On Sep 15, 2022, at 08:24, René J.V. Bertin wrote: > I've noticed that most of the launchd plists installed by ports have > `Disabled: true`. There are a select few that don't, among which the mariadb > server. I have that port installed, and yet no mariadb launchd job loaded > which suggests

Re: Upgrading py-poetry-core and pep517

On Sep 11, 2022, at 12:40, David Gilman wrote: > > There's a new release of poetry and py-poetry-core and poetry. I have > the PR ready at https://github.com/macports/macports-ports/pull/16088 > . However, I am unable to get it to cleanly upgrade from an older > version of py-poetry-core. > > I

Re: include files for cgxCADTools

On Aug 7, 2022, at 19:06, Ryan Schmidt wrote: > configure.cxxflags-append -std=c++11 In fact, the Makefile already had -std=c++11, but your patchfile removed it. So don't remove it.

Re: include files for cgxCADTools

On Aug 6, 2022, at 09:47, Mark Brethen wrote: > See log file for errors I’m getting with using build.env instead of > build.args. The log has errors like this: Os -arch x86_64 -Wall -I../../FbdReader/inc -I/opt/local/include/opencascade -c FbdReader.cpp -o FbdReader.o make: Os: No such

Re: include files for cgxCADTools

On Aug 6, 2022, at 12:14, Mark Brethen wrote: > > It builds successfully when I blacklist Apple’s clang. It used clang++ 14, which I think defaults to a newer language standard. So don't blacklist Apple clang. Instead, specify what language standard you want, per my previous message.

Re: include files for cgxCADTools

On Aug 6, 2022, at 12:09, Mark Brethen wrote: > Here’s the log file when using build.args instead of build.env and compiling > with Apple’s clang. Different failure this time. You're getting warning about C++11 features: /opt/local/include/opencascade/Standard_Handle.hxx:75:19: warning:

Re: MacPorts custom installation prefix and precompiled binaries

On Aug 7, 2022, at 08:05, Steven Smith wrote: > Someday, one hopes that there will be a cleanup of all the tcl code that > breaks for prefix paths with spaces and non-ascii characters, but that’s > aspirational, not reality. Many ports use build systems like autoconf that do not support paths

Re: SPOOLES MT routines

On Aug 5, 2022, at 17:45, Mark Brethen wrote: > Note that the pre-build approach is overriding the makefile cflags, makefile > was patched to cflags += , etc. How do I prevent this? Setting variables like CFLAGS as arguments (e.g. build.args) overrides anything specified in the Makefile.

Re: Help with New Port - M2VDownsizer

On Aug 5, 2022, at 18:14, Robert Kennedy wrote: > I have been playing around with CFLAGS += -Xarch_ppc -faltivec in my > Makefile, as suggested by Josh. > > I noticed that if I include CFLAGS += -Xarch_ppc -faltivec in my Makefile, > the output from the clang compiler gets garbled but the

Re: Issues with config.h

On Aug 5, 2022, at 16:43, Robert Kennedy wrote: > > I have also patched config.h to address the ARCH issue. It now reads: > > #ifndef LINUX >   #if defined(__ppc__) || defined(__ppc64__) > #define ARCH_PPC >   #elif defined(__i386__) > #define

Re: Issues with config.h

Early in config.h it says: #ifndef LINUX #if defined(__ppc__) || defined(__ppc64__) #define ARCH_PPC #elif defined(__i386__) #define ARCH_X86 #endif #else #define ARCH_X86 #endif So, on non-Linux systems, it sets ARCH_PPC when building

Re: include files for cgxCADTools

On Aug 5, 2022, at 15:26, Mark Brethen wrote: > > I don’t see these errors when building with macports-clang, only Apple’s > clang. Ok. Certainly, different compilers can behave differently. I didn't try to see what the actual error was, since it was jumbled. If you have an non-jumbled error

Re: Issues with config.h

On Aug 4, 2022, at 08:36, Robert Kennedy wrote: > e.g. > ./config.h:29:9: warning: 'HAVE_STDINT_H' macro redefined > #define HAVE_STDINT_H > ^ > ./config.h:42:9: note: previous definition is here > #define HAVE_STDINT_H 1 The config.h file clearly does define HAVE_STDINT_H (empty)

Re: include files for cgxCADTools

On Aug 4, 2022, at 13:19, Mark Brethen wrote: > I’m seeing this error when generate all the header dependencies for > FbdReader. This is confusing, which file has the error? Error messages from several different files are being jumbled together due to parallel building. You can make it less

Re: SPOOLES MT routines

On Aug 5, 2022, at 14:32, Mark Brethen wrote: > > pre-build { > set cflags "${configure.cflags} [get_canonical_archflags cc]" > set ldflags "${configure.ldflags} [get_canonical_archflags ld]" > > # workaround for Rank mismatch between actual argument > set ver [regsub -all

Re: CalculiX is using libstdc++ (this installation is configured to use libc++)

On Jul 27, 2022, at 07:41, Mark Brethen wrote: > > As the source does not use configure, I pass the compiler args: > > pre-build { >build.args-appendCXX=${configure.cxx} \ > CC=${configure.cc} > } > > For reasons I don’t understand, If I don’t put it in a

Re: openGL Framework

On Jul 23, 2022, at 05:38, Mark Brethen wrote: > > if I switch to X11 server, should I remove /opt/X11 along with Xquartz.app? If you are using the MacPorts xorg-server's X11.app and aren't using any other parts of XQuartz (such as its libraries) for any things outside of MacPorts, then sure,

Re: fetch timeout

On Jul 26, 2022, at 11:25, Mark Brethen wrote: > > The mp curl no longer downloads from the target website, wias-berlin.de; web > download still works. The only changes were an Xcode update and reinstalling > commandlinetools and macports for big sur. You'll have to talk to the administrators

Re: What to do with Mono (and msbuild) on ARM64?

On Jul 3, 2022, at 18:22, Mojca Miklavec wrote: > One of the projects that I'm working on requires mono as a build dependency. > At the moment mono is broken on ARM64 in MacPorts (I suspect that it > works under HomeBrew). > > I fixed it: >

Re: How about a MacPorts "system" (generic) python port?

On Jul 15, 2022, at 03:04, Chris Jones wrote: > we already have a solution to this, for users that 'just want a python3' > > > sudo port select python3 python310 > > replacing python310 with your preferred version. > > I see no need for what you propose above in addition. He wants something

Re: openGL Framework

On Jul 19, 2022, at 17:18, Mark Brethen wrote: > I’m also confused about the two x11 window environments (xorg-server vs > xquartz). I’m assuming Xquartz libraries, etc are in /opt/local, what about > xorg? XQuartz is a standalone package that installs a complete X11 system, including the X11

Re: fetch timeout

On Jul 15, 2022, at 09:55, Chris Jones wrote: > On 15/07/2022 3:49 pm, Mark Brethen wrote: >> -rw-r--r--1 root wheel 346545 Jan 1 2020 cert.pem > > The above could be your problem, as that is very old, 2.5 years or so now. It > actually pre-dates the public release of macOS 11, which

Re: bazel 4.2 and 3.7 no longer building with native clang

On Jul 13, 2022, at 11:46, Steven Smith wrote: > How does one reconfigure the bazel Portfile to use a previous version of > clang that has a chance of working to build previous versions of bazel, which > are in turn necessary to build the tensor flow packages. If certain compilers that

Re: Using on macOS 10.13 with clang++-mp-13

On Jul 3, 2022, at 13:38, Ken Cunningham wrote: > You can (sometimes) use macports-libcxx to get past this. This however > introduces two versions of libc++.dylib into the softare mixture, and this > sometimes causes errors due to incompatibilities between libc++ versions (ODR > errors). If

Re: Compiler Selection

On Jul 3, 2022, at 13:39, Mark Brethen wrote: > > According to the wiki: > >> The compiler is chosen with the following precedence: >> >> • If configure.compiler is set in the Portfile, then that is the >> compiler that is used. >> • If the user sets default_compilers, the compiler

Re: A bunch of failures with nodejs on the builders

On Jul 2, 2022, at 19:11, Marc Wilson wrote: > > I’ve not heard of this before, and have never experienced it, despite having > two different Mac on 12.x and before that, on 11.x. Macs running macOS 12 do not seem to be affected presumably because they're already running macOS 12; there would

Re: A bunch of failures with nodejs on the builders

On May 5, 2022, at 07:59, Christopher Nielsen wrote: >> In addition, as you may know, a bug in recent macOS causes it to download >> the 12+ GB macOS Monterey installer periodically which would have left it >> with only 8 GB available. > > I recently discovered this behavior as well. > > My

Re: Frotz build targets

On Jun 27, 2022, at 17:47, Nils Breunese wrote: > > I don’t maintain any ports with GUI’s myself, but I believe flavors like x11, > sdl, etc. are usually provided as variants of a port instead of as subports. > You can also specify conflicts between variants if there are any to avoid > users

Re: openGL Framework

On Jun 30, 2022, at 07:50, Mark Brethen wrote: > > I noticed that -framework OpenGL exists in /System/Library/Frameworks. Is > there an OpenGL framework port that I should be using? The MacPorts equivalent of the OpenGL framework is the mesa port.

Re: Frotz build targets

On Jun 26, 2022, at 17:39, Mark Brethen wrote: > > Attaching a Portfile that uses variants—downside is you can only install one. > Maybe that is sufficient? I couldn’t find any documentation for using > subports. What would you like to know about subports? Have you looked at any existing

Re: Frotz build targets

On Jun 26, 2022, at 14:23, Mark Brethen wrote: > But is there an interest in building for X11 anymore? I do not know about frotz, but in MacPorts ports in general, yes, there is still interest in X11. Ports that have optional X11 components can make them available in an +x11 variant.

Re: Python+MacOS Versions

On Jun 24, 2022, at 19:47, Joshua Root wrote: > On 2022-6-25 05:47 , Jeremy Lavergne wrote: >> Does anyone happen to know what versions of Python each MacOS shipped with? >> * I'm specifically hoping to find when python3.8 began being pre-installed >> on MacOS to update a PSPP build-dep that's

Re: Difference between build_arch and configure.build_arch, universal_archs and configure.universal_archs (was: Re: +universal for x864+arm64 on Macintel)

On Jun 15, 2022, at 16:49, Joshua Root wrote: > $universal_archs contains exactly what is set in macports.conf (so does > $build_arch). ${configure.universal_archs} is the archs that will actually be > built with +universal, and may differ from the macports.conf value due to the >

Re: GitHub Actions macOS-10.15 image deprecation

On Jun 15, 2022, at 23:24, aeiouaeiouaeiouaeiouaeiouaeiou wrote: > > https://github.com/actions/virtual-environments/issues/5583 > > > GitHub Actions is starting the deprecation process for macOS 10.15. While > > the image is being deprecated, You may experience longer queue times during > >

Re: help with a regex please

On Jun 19, 2022, at 16:34, Fred Wright wrote: > I don't know specificlly about reinplace, but here's an example with sed: reinplace is sed -i "" https://github.com/macports/macports-base/blob/master/src/port1.0/portutil.tcl#L951-L953

Re: +universal for x864+arm64 on Macintel

On Jun 14, 2022, at 12:33, René J.V. Bertin wrote: > On Monday June 13 2022 04:34:46 Ryan Schmidt wrote: > >> The standard universal variant has no content. (Universal support is >> implemented by adding the return value of procedures like >> [get_canonical_archflags cc

Re: +universal for x864+arm64 on Macintel

On Jun 13, 2022, at 15:40, Chris Jones wrote: > On 13 Jun 2022, at 1:06 pm, René J.V. Bertin wrote: > >> Ryan Schmidt wrote on 20220613::04:34:46 re: "Re: +universal for x864+arm64 >> on Macintel" >> >>> As far as I know, the SDK would also n

Re: +universal for x864+arm64 on Macintel

On Jun 13, 2022, at 04:29, René J.V. Bertin wrote: > > On Monday June 13 2022 02:48:06 Ryan Schmidt wrote: >> (and if MacPorts does not create a universal variant automatically in this >> case then the port should do so itself) > > Doh, I should have thought about that.

Re: MacPorts Status

On Jun 11, 2022, at 09:07, Jordan wrote: > First of all thank you for your work! I use MacPorts exclusively for a few > different reasons and am looking to contribute to the project. I am starting > to spin up maintaining a few ports after a long break from macOS (mostly > because until M1

Re: +universal for x864+arm64 on Macintel

On Jun 13, 2022, at 02:58, Chris Jones wrote: > I assume you have tried removing these two line from your portfile ? > > You're pointing to the `universal_variant no` line and

Re: +universal for x864+arm64 on Macintel

On Jun 10, 2022, at 11:23, René J.V. Bertin wrote: > When I tried to test the new +universal variant of a x864_64 + arm64 port > (port:VLC) installing from official DMGs on my 10.9.5 Mac I discovered that > the variant wasn't added because the port only supported the current build >

Re: Fastly Mirrors Throttled to 1 MB/sec?

On Jun 6, 2022, at 08:54, Christopher Nielsen wrote: > > Over the past few months, I’ve found that downloads from > ‘packages.macports.org’ and ‘distfiles.macports.org’ are consistently > throttled at 1 megabyte/second. And while that isn’t an issue for smaller > payloads, it significantly

Re: Reason for rpath usage on arm64

On May 30, 2022, at 01:01, Ken Cunningham wrote: > ah yes, your question was arm64-specific so that led to the gcc assumption. > > the way the cmake PG configures cmake breaks testing on all archs and systems. It worked for me on Catalina x86_64 but not on Big Sur arm64, and I was trying to

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 15:31, Daniel J. Luke wrote: > On May 24, 2022, at 3:56 PM, Ryan Schmidt wrote: >> I wouldn't recommend anyone begin writing any code until it is discussed how >> the feature should work. That should avoid spending time writing code that >> won't work.

Re: Reason for rpath usage on arm64

On May 24, 2022, at 10:22, Ken Cunningham wrote: > >> Does anyone know why things seem to be using rpath on arm64 builds > > Basically, it comes down to the fact that Apple has disallowed > DYLD_LIBRARY_PATH to work on newer systems. > So gcc is installing it’s libraries with the @rpath

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 14:08, Daniel J. Luke wrote: > On May 24, 2022, at 12:07 PM, Ryan Schmidt wrote: >> I'm not convinced that I would be happy to see such a feature. Just a >> moment's consideration shows how many different parts of MacPorts would need >> modifications to

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 24, 2022, at 09:35, Daniel J. Luke wrote: > - MacPorts could grow a feature by which a port could specify that it needs > to get rebuilt if something it depends on gets rebuilt (this would probably > require another identifier along with epoch-version-revision or would require > some

Reason for rpath usage on arm64

Does anyone know why things seem to be using rpath on arm64 builds? For example: https://trac.macports.org/ticket/64204 The de-facto standard for things installed with MacPorts has been not to use rpath, since MacPorts predates the existence of rpath, and since things have worked fine without

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 23, 2022, at 18:35, Jim DeLaHunt wrote: > 1. port curl-ca-bundle is a subport of port curl[2], > 2. it looks to me like port curl-ca-bundle only got updated about 7 times in > the last 43 months[3] > 3. it looks as if port curl-ca-bundle updates a file within curl, >

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 23, 2022, at 21:16, Chris Jones wrote: > On 23 May 2022, at 9:59 pm, Steven Smith wrote: >  >>> What has changed between the time that the buildbot built the package and >>> the time that the user installs it? >> >> The certs in curl-ca-bundle are updated regularly to clear out expired

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 22, 2022, at 13:43, Steven Smith wrote: > A standard install command grabs pre-built stuff from > https://packages.macports.org/privoxy-pki-bundle. This pre-built stuff is > inevitably stale because it inevitably contains expired certs. Again, why is it the case that what we built on

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 21, 2022, at 12:40, Steven Smith wrote: > Is there a way to achieve the second objective: prevent MacPorts from > building and caching its own copy of the port contents, which for this port > will inevitably be filled with expired certificates? > > Right now, avoiding this issue

Re: cargo.crates_github doesn't work anymore in the cargo_fetch PG

On May 18, 2022, at 07:26, Vadym-Valdis Yudaiev wrote: > Looks like after some changes `cargo.crates_github` broke. The @harens > thought the `cargo._old_macos_compatibility` option was to blame. I do think > it broke even earlier. > >

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 17, 2022, at 15:31, Steven Smith wrote: >> Whenever the curl-ca-bundle port is updated to a new version, the >> privoxy-pki-bundle port's revision should be increased so that it rebuilds >> with the new bundle. > > > Thank you. > > This is the part that I was hoping is automatic,

Re: privoxy-pki-bundle not Behaving as Desired – Request for Assistance

On May 12, 2022, at 18:04, Steven Smith wrote: > > I tried to write privoxy-pki-bundle to have these two basic behaviors: > > • Updates to the file ${prefix}/share/curl/curl-ca-bundle.crt via port > curl-ca-bundle will force reinstallation of the CA file >

Re: A bunch of failures with nodejs on the builders

On Apr 25, 2022, at 07:54, David Gilman wrote: > > There were a handful of pushes of new nodejs versions (at least nodejs > 18 through 15) in the past week and a bunch of binary builders failed. > Some of these look ephemeral and just need xcode reinstalled or > whatever. I'd appreciate it if the

go ports fetching dependencies at build time

Question regarding this commit: https://github.com/macports/macports-ports/commit/2c8bec5807d23120038f39d292a7e1cad625707d Here, a port tfmigrate was updated from 0.3.2 to 0.3.3 and changed to allow it to fetch dependencies at build time. What transpired between 0.3.2 and 0.3.3 that made it

Re: Location to store binaries

On Apr 17, 2022, at 08:45, Marcus Calhoun-Lopez wrote: > I have been careful to submit all changes upstreams. > So far, most of them have been merged already. > The only changes I have not submitted are the ones that apply to systems > prior to 10.7, which Rust does not support. > These patches

Re: Location to store binaries

On Apr 16, 2022, at 10:36, Marcus Calhoun-Lopez wrote: > Right now, I put them in a release section of a fork of Rust: > https://github.com/MarcusCalhoun-Lopez/rust/releases > > Could a similar fork be created under the auspices of the MacPorts project? Yes, it could be. We haven't done that

Re: macOS 12 x86_64 buildbot weirdness

On Apr 8, 2022, at 10:06, Herby Gwrote: > Something weird might be going on with the macOS 12 x86_64 buildbot > > Two builds of the same latest Rust fail with completely different errors: > > 1. >

Re: revision control downloads

On Mar 23, 2022, at 16:31, Rainer Müller wrote: > On 22/03/2022 22.23, Ryan Schmidt wrote: > >> As I said we do already and have for a long time strongly discouraged using >> revision control systems for downloads. > > As these days most web frontends allow to down

Re: revision control downloads

On Mar 22, 2022, at 13:08, Daniel J. Luke wrote: > On Mar 21, 2022, at 9:20 PM, Ryan Schmidt wrote: >> Ports that fetch their sources from a revision control system do not enjoy >> the protection of checksums. Although ports that fetch source from a >> revision control sys

Re: Codesigning everything and combatting malicious code

On Mar 21, 2022, at 23:02, Joshua Root wrote: > We could ad-hoc codesign everything, which would not improve security at all, > but would get GateKeeper to ease up a bit on restrictions on incoming network > connections and the like. > Assurance that binaries have not changed after being

Codesigning everything and combatting malicious code

Sorry, this got long. I want to move a discussion to the macports-dev list that began with a user's question to macports-mgr. This user ran a third-party utility which reported that some files installed by MacPorts were not codesigned and asked if it was a concern. I replied that the files

Re: python2.7 pip install fails with SSLError

On Mar 17, 2022, at 14:49, Steven Smith wrote: >> macOS 12.3 removes /usr/bin/python > > This package encapsulates everything in a virtualenv, so that wasn’t the > issue. In case anyone runs into something similar, my logs say this the > removal of /usr/local/lib/.Python is the issue: > >>

Re: python2.7 pip install fails with SSLError

On Mar 17, 2022, at 14:37, Steven Smith wrote: > Thanks everyone for your responses and suggestions. > > Short story: I used the existing `sudo port install calendar-contacts-server` > and … it works! > > Even though this project is old and archived, I’m not aware of any open > source that

Re: python2.7 pip install fails with SSLError

On Mar 17, 2022, at 04:39, Chris Jones wrote: > Does the port *have* to use python 2.7 ? Is it not compatible with python 3.x > ? See https://github.com/apple/ccs-calendarserver/issues/537 where Steven asked upstream for guidance on migrating to Python 3. There was no reply. The project is no

Re: python2.7 pip install fails with SSLError

On Mar 14, 2022, at 20:18, Jim DeLaHunt wrote: > On 2022-03-14 17:09, Steven Smith wrote: >> I’m trying to update calendar-contacts-server to macOS 12.3. This requires >> installing a bunch of stuff with python2.7’s pip. >> I’m hitting an SSLError at the command: >>> /opt/local/bin/python2.7 -m

Re: OpenSSH 8.9p1 deprecated variants cleanup feedback request

Just a brief reply, I agree that we don't usually want to be in the business of forever maintaining patches, so they should be sent to the upstream developers for inclusion, and if they refuse them, then we either keep maintaining the patches (if they are valuable and someone wants to continue

Re: LLVM port mp-llvm-* select groups mislinks certain programs

On Mar 14, 2022, at 14:02, Christopher Jones wrote: > You can easily see the issue with > >> sudo port -d select llvm mp-llvm-13 > > the linkage starts out in sync, but then starts to diverge.. > > > DEBUG: ln -sf /opt/local/bin/llvm-symbolizer-mp-13 > /opt/local/bin/llvm-symbolizer > DEBUG:

Re: LLVM port mp-llvm-* select groups mislinks certain programs

On Mar 14, 2022, at 00:28, 조성빈 wrote: > Hello, > > I’m not sure who to CC so just sending it to the dev list: > > it seems that the mp-llvm-* select groups of the llvm-12, llvm-13 (and > possibly > more?) ports mislink certain programs. Could you describe exactly what is mislinked? > I

Re: /usr/bin/python will be removed in macOS 12.3!

On Feb 24, 2022, at 12:35, Bjarne D Mathiesen wrote: > "#!/usr/bin/env python" might not be a problem > iff > the macports python is also installed as a prerequisite > the ${PATH} variable includes '/opt/local/bin' The /opt/local/bin/python symlink will only exist if the user has

Re: Patch ./configure, or use autogen.sh instead?

On Feb 21, 2022, at 16:32, Jim DeLaHunt wrote: > But I also thought, why not also patch the m4 macros which generate the > configure script? It keeps the codebase on the user's machine consistent. It > keeps the patches in the MacPorts repository. What harm could it do? > > I'm glad you

Re: /usr/bin/python will be removed in macOS 12.3!

On Feb 19, 2022, at 11:06, Gerben Wierda wrote: > But how does one (a) find out the dependency exists and (b) make sure the > software finds python from MacPorts? General-purpose answers to either question are not possible. Each affected port will need to be investigated and fixed in its own

Re: Patch ./configure, or use autogen.sh instead?

On Feb 17, 2022, at 14:10, Jim DeLaHunt wrote: > > On 2022-02-16 23:12, Jason Liu wrote: >> autogen.sh is quite often just a wrapper around autoreconf -i. If you run >> 'autoreconf --install' (which is what 'use_autoreconf yes' runs), in >> many/most cases it's equivalent to running autogen.sh.

  1   2   3   4   5   6   7   8   9   10   >