Re: fun fact about ICU +universal

On Feb 14, 2021, at 20:11, Fred Wright wrote: > On Sun, 14 Feb 2021, Ken Cunningham wrote: > >> The i386/x86_64 universal build looks fine too, so far, with all the >> muniveral stuff out. >> >> Now -- have to see why it was ever put in there in the first place, I guess. > > One of the typic

Re: fun fact about ICU +universal

On Feb 15, 2021, at 07:42, Ken Cunningham wrote: > Yeah, the real downside of the muniversal PG is that once it has been > chucked in to fix a build, for whatever reason it may have been once upon a > time, convincing everyone you DON'T need it after that is much harder than if > you never use

Re: Very Large Number of Python ports Don't Exist in ${python.default_version } (py39)

On Mar 1, 2021, at 09:49, Joshua Root wrote: > Once that's done, there's no problem adding lots of them in a single commit. It can be difficult to get approval from a large number of maintainers for a single PR. If you're going to submit a PR that does a mass update for this that affects por

Re: Very Large Number of Python ports Don't Exist in ${python.default_version } (py39)

On Mar 2, 2021, at 09:25, Steven Smith wrote: > The approach of other Python package managers (conda, pip) is to simply use > whatever the installed version is and presume that the package will build and > work. If it doesn’t, post an issue. > > Currently, keeping MacPorts Python ports up-to

Re: Looking to resolve Qemu on AppleSilicon build failure

On Mar 4, 2021, at 00:16, Blake Garner wrote: > Building with the vnc variant is failing for me at the configure step. I was > able to resolve a previous ld error by reinstalling xcode cli tools. Doesn't > look like that is the issue with the attached errors. > > ProductName:macOS > Pro

Re: Dovecot Update Fails to Build in CI, Trace Mode

On Mar 4, 2021, at 11:51, Steven Smith wrote: > The dovecot build downloads several text files from https://dovecot.org/ > using wget. (For some reason this doesn’t break trace mode). Does trace mode usually prevent network access? I don't recall. > Is it preferred to just let the project’s

Re: Looking to resolve Qemu on AppleSilicon build failure

On Mar 4, 2021, at 11:39, Blake Garner wrote: > > I'll get another bug open for this. Hopefully, I can isolate the vnc variant > build issue from the existing PR to fix the other arm64 build issue. The > original bug I opened didn't get much response until it was discussed on the > dl. By all

Re: INSTALL_PATH with spaces

On Mar 5, 2021, at 10:35, Janosch Peters wrote: > I am working on a new port and I am struggling to set the INSTALL_PATH to > "/$HOME/Library/Application Support/MacPass“. This is what I tried: I would abandon this attempt because a port shouldn't be installing anything in a user's $HOME. Po

Re: How to trigger port rebuild for arm64

On Mar 9, 2021, at 13:02, Dave Allured wrote: > I work very occasionally on port fixes for arm64. I tried to trigger > rebuilds of dependent ports on the arm64 buildbot, using simple revbumps. > For example, port geos was updated and built successfully on Feb. 15. I then > submitted a rev

Re: Octave port: website search results, 6.2.0, and Tablicious

On Mar 9, 2021, at 03:18, Andrew Janke wrote: > Octave 6.2.0 is out; released on Feb 20. Looking at > https://ports.macports.org/port/octave/summary, it seems like the MacPorts > port is still on 6.1.0. When can we expect it to update to 6.2.0? Anything I > can do to help out with that process?

Re: How to trigger port rebuild for arm64

On Mar 9, 2021, at 22:06, Dave Allured wrote: > While the ports website is not updating, is there an easy way for me to > access build logs for new builds that fail for specific ports? It's not > critical but would help me stay on track. Nope. If the build happened within the past day or so

Re: How to trigger port rebuild for arm64

On Mar 9, 2021, at 23:49, Joshua Root wrote: > Maintainers are supposed to get an email with a link to the build when ports > fail, which makes it a lot easier, but for some reason that has never worked > for some subset of maintainers on the current buildbot setup. And now that we've added

Re: Subtleties of Modifying post-configure

On Mar 14, 2021, at 19:58, Steven Smith wrote: > I need to run some post-configure steps in a cmake Portfile. > > I’m running into two these issues: > > Issue 1: > > cmake already has some post-configure code. How do I add stuff to whatever > cmake already has? Not post-configure-append, I see

Re: the whole world is renaming the git default branch to main...

On Mar 14, 2021, at 13:50, Blair Zajac wrote: > +1 for renaming. > > https://github.com/github/renaming > https://sfconservancy.org/news/2020/jun/23/gitbranchname/ Thanks for making us aware of this issue. I had no idea. Ken, maybe next time start with the links that explain what you're talking

Re: depends_run and activation

On Mar 14, 2021, at 07:51, René J.V. Bertin wrote: > Supposing runtime dependencies are stored in the registry, Yes of course. > wouldn't it be possible and a good idea to give at least a warning if any are > missing when you (re)activate a port? It shouldn't warn; it should install or activat

Re: depends_run and activation

On Mar 15, 2021, at 08:45, René J.V. Bertin wrote: > > Hmmm, then I don't understand why yesterday this didn't work for me. Trying > now with (an older version of) paracode as in your example gives a similar > result. In my case however: > > {{{ >> sudo port activate paracode > ---> Computing

Re: depends_run and activation

On Mar 17, 2021, at 05:19, René J.V. Bertin wrote: > On Tuesday March 16 2021 23:12:12 Ryan Schmidt wrote: > >> There is no such thing as a "too-new version". There is only one version of >> a port available in the ports tree -- the current version. > > Sure,

Re: depends_run and activation

On Mar 17, 2021, at 06:38, René J.V. Bertin wrote: > On Wednesday March 17 2021 05:28:29 Ryan Schmidt wrote: > >> I don't believe we can do that because I don't believe that information is >> stored in the registry. > > Probably not, given that MacPort doe

Re: Ports for buildbot 3

On Mar 20, 2021, at 08:39, Mojca Miklavec wrote: > Hi, > > Buildbot 3 (that is slightly incompatible with buildbot 2) has > recently been released. > > We currently ship: > - buildbot-0.8, buildbot-slave-0.8 > - buildbot, buildbot-worker (+ dependencies) that provide version 2 > > So we are

Re: Problem with Objective-C import on the build server

On Mar 22, 2021, at 15:12, Janosch Peters wrote: > What am I doing wrong? You forgot to increase the MacPass port's revision when you modified it to install the headers.

Re: 11_x86 build - build failures due to 'no space on device'

On Feb 11, 2021, at 04:21, Christopher Jones wrote: > I am seeing some large builds fail due to drive space issues > > https://build.macports.org/builders/ports-11_x86_64-builder/builds/21466/steps/install-port/logs/stdio > error: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefa

Re: 11_x86 build - build failures due to 'no space on device'

On Mar 23, 2021, at 11:23, Christopher Jones wrote: > As it happens I’ve been working on the bazel builds a bit, and discovered an > option to disable local build caching. To quote the manual > > --[no]use_action_cache > > This option is enabled by default. If disabled, Bazel will not use its l

Please double-check that PRs build before merging

PR CI checks are being marked as successful even when they failed. https://trac.macports.org/ticket/62530 Please take an extra moment to view the PR CI logs or try to build the port (including all subports) before merging a PR to avoid merging something that does not build. (If anyone knows ho

Re: ARM64 Github CI

On Mar 24, 2021, at 17:50, Joshua Root wrote: > we would have to set up a self-hosted runner. People have expressed interest in this (for x86_64) every now and then over the years, but as of now we have no ability to do this. Software would need to be written to allow this to happen. And then w

Re: macOS11 arm builder offline ?

On Mar 26, 2021, at 12:13, Chris Jones wrote: > I’ve noticed the macOS11 arm builder has been offline for a short while now. > Just curious if there is some issue with it ? It doesn't exist at the moment. We were using an Apple Developer Transition Kit machine for this builder, and Apple has re

Re: ARM64 Github CI

On Mar 28, 2021, at 18:04, Fred Wright wrote: > On Fri, 26 Mar 2021, Ryan Schmidt wrote: >> On Mar 24, 2021, at 17:50, Joshua Root wrote: >> >>> we would have to set up a self-hosted runner. >> >> People have expressed interest in this (for x86_64) every

Re: Built archive not uploaded

On Mar 27, 2021, at 20:51, Jason Liu wrote: > On Sat, Mar 27, 2021 at 1:44 PM Mojca Miklavec wrote: > >> I didn't try to look into details, but note that the 10.15 builder has >> more than 500 jobs in the backlog, so it might also be just a matter >> of time. > > Thanks for pointing this out...

Re: Existing fix for py-scipy shared objects with incorrect @rpath/libmkl_rt.dylib?

On Mar 28, 2021, at 10:30, Steven Smith wrote: > Re: https://trac.macports.org/ticket/62578 > > Is there a python or Portfile one-liner fix for the incorrect @rpath issues > in py-scipy’s shared objects? > > We can code up an exhaustive search of the build for all the .so's and use > install_n

Re: map download link to distname

On Apr 5, 2021, at 14:43, Jonathan Stickel wrote: > I'm working on updating the graphviz portfile. Huh, I thought an update had already been submitted months ago. > The new download link is: > > https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download > > I can get Macports to

Re: Desolate Condition

On Apr 5, 2021, at 13:04, Karl-Michael Schindler wrote: > 2) Put the command 'port install PACKAFE_NAME' to a prominent position. https://github.com/macports/macports-webapp/issues/144

Re: Misconceptions about binaries (was: Re: Desolate Condition)

On Apr 3, 2021, at 19:21, Wowfunhappy wrote: > > I know it's just one data point, but I thought the replies I got on this > Hacker News comment today were interesting. I can understand why he/she got > confused, and I wonder if there's anything MacPorts could do to make it > clearer. https:/

Re: map download link to distname

On Apr 5, 2021, at 16:33, Jonathan Stickel wrote: > On 4/5/21 14:17, Ryan Schmidt wrote: >> On Apr 5, 2021, at 14:43, Jonathan Stickel wrote: >>> I'm working on updating the graphviz portfile. >> Huh, I thought an update had already been submitted months ago. >

Re: What's our audience - and how do we serve them best

On Apr 5, 2021, at 17:16, Bjarne D Mathiesen wrote: > As I see it, we've got several problems/issues : > > 1) what's our audience : > ? newbies > ? experienced > ? nerds > ? linux refugees > each of these needs different kinds of handholding > > 2) how does one use macports in daily

Re: What's our audience - and how do we serve them best

On Apr 5, 2021, at 20:42, Bjarne D Mathiesen wrote: > Ryan Schmidt wrote: >> On Apr 5, 2021, at 17:16, Bjarne D Mathiesen wrote: >>> >>> 1) what's our audience : >>> ? newbies >>> ? experienced >>> ? nerds >>> ? li

Re: map download link to distname

On Apr 6, 2021, at 10:44, Rainer Müller wrote: > On 06/04/2021 01.39, Ryan Schmidt wrote: >> Regarding the specific download link you mentioned, >> https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download, I see >> that link on the graphviz

Re: 11_x86 build - build failures due to 'no space on device'

On Mar 23, 2021, at 11:04, Ryan Schmidt wrote: > On Feb 11, 2021, at 04:21, Christopher Jones wrote: > >> I am seeing some large builds fail due to drive space issues >> >> https://build.macports.org/builders/ports-11_x86_64-builder/builds/21466/steps/install-

Re: 11_x86 build - build failures due to 'no space on device'

On Apr 8, 2021, at 07:25, Ryan Schmidt wrote: > We now have 21GB free. 31GB free after rebooting. For some reason fseventsd was taking 14GB of memory. The VM only has 8GB of real memory so a lot of swap was being used. This is probably also the explanation for why that builder has gotte

Re: macmini colo m1

On Apr 8, 2021, at 14:13, Blake Garner wrote: > Hey I saw this offer of free access to m1 mini hardware from macmini colo for > opensource projects. Not sure about who/what qualifies in regards to macports > but figured I'd pass it along. > > https://www.macstadium.com/opensource Thanks. W

Re: 11_x86 build - build failures due to 'no space on device'

On Apr 8, 2021, at 13:05, Nils Breunese wrote: > Ryan Schmidt wrote: > >> Both copies of the simulator caches came back again. I filed FB9072613 with >> Apple about this. We were down to 3GB free disk space which isn't a good >> place to be. I deleted the cac

Re: 11_x86 build - build failures due to 'no space on device'

On Apr 8, 2021, at 16:04, Jason Liu wrote: >> For some reason fseventsd was taking 14GB of memory. > > Not really surprising, for a machine being used as a builder. The constant > creation and deletion of files when compiling software is bound to be > generating a ton of file system events. It

Re: 11_x86 build - build failures due to 'no space on device'

On Apr 9, 2021, at 14:10, Chris Jones wrote: > On 9 Apr 2021, at 7:20 pm, Ryan Schmidt wrote: > >> On Apr 8, 2021, at 13:05, Nils Breunese wrote: >> >>> Ryan Schmidt wrote: >>> >>>> Both copies of the simulator caches came back again. I file

Re: Github CI Broken

On Apr 12, 2021, at 11:53, Herby G wrote: > PR checks are failing across multiple pull requests in macports-ports. > > On both Github Actions and Azure Pipelines, we're seeing the following when > CI is trying to install MacPorts: > > > curl: (22) The requested URL returned error: 403 Forbid

Re: Github CI Broken

On Apr 12, 2021, at 17:10, Mark Anderson wrote: > We could also host them using the releases system on github. But releases of what? I do not want to attach the getopt file to the releases of any MacPorts repository because getopt is not our project and it does not change on the schedule of

License GPL-2 conflicts with OpenSSLException

https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/55652/steps/gather-archives/logs/stdio > "hydrogen" is not distributable because its license "GPL-2" conflicts with > license "OpenSSLException" of dependency "qt5-qtbase" Does this make sense or is there an error in the scrip

Re: OpenSSL GPL conflict (was: Re: License GPL-2 conflicts with OpenSSLException)

On Apr 16, 2021, at 20:33, Fred Wright wrote: > On Fri, 16 Apr 2021, Ryan Schmidt wrote: > >> https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/55652/steps/gather-archives/logs/stdio >> >>> "hydrogen" is not distributable becau

Re: License GPL-2 conflicts with OpenSSLException

On Apr 16, 2021, at 20:21, Joshua Root wrote: > On 2021-4-17 11:16 , Ryan Schmidt wrote: >> https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/55652/steps/gather-archives/logs/stdio >>> "hydrogen" is not distributable because its license "G

Re: OpenSSL GPL conflict

On Apr 16, 2021, at 21:25, Fred Wright wrote: >> I'm not aware of the Oracle / Google ruling. > > They ruled in favor of Google, meaning that copying Oracle's Java header > files to use in conjunction with Google's Java implementation did not > constitute a violation of Oracle's copyright.

Re: License GPL-2 conflicts with OpenSSLException

On Apr 16, 2021, at 21:30, Joshua Root wrote: >> And is this really true that a GPL-2 program like Hydrogen is not >> distributable if it links with a GPL-3 / LGPL-3 library like Qt5? > > Yep. That's why the FSF has always recommended licensing under version n or > later of the GPL rather than

Re: Publicizing MacPorts

On Apr 18, 2021, at 07:28, Steven Smith wrote: >>> I completely agree that Homebrew is currently winning at publicity. >> >> What should the MacPorts community be doing do publicize MacPorts better? > > The new M1 architecture is a perfect opportunity to champion MacPorts’s > strengths: > >

Re: FileZilla: current version requires SDK 11

On Apr 21, 2021, at 10:55, Lothar Haeger wrote: > Sorry for the long delay, busy times had me loose this topic out of sight a > bit. > >> Would it help if we had a port in MacPorts that installed the macOS 11 SDK? > > I'm not sure about that, since I have XCode 12.4 (which afaik includes the

Re: Buildbots down?

On Apr 21, 2021, at 11:36, Herby G wrote: > https://build.macports.org/ is unreachable. Maybe there was a temporary problem with my Internet connection? It was up when I checked it.

Re: Help Understanding Code Signing

On Apr 22, 2021, at 00:09, Marcus Calhoun-Lopez wrote: > I must admit that whan issues like code signing come up, I tend to > tune out, so please forgive me if this is well trodden territory. > > While working on the netgen, I added the following code to get the > destroot phase working (where

Re: emacs-app-devel build fail on master not detected by buildbot

On Apr 22, 2021, at 18:22, Nathaniel W Griswold wrote: > So are you guys just gonna point to the new commit and otherwise keep it the > same? I think maybe it should change. I'll just weigh in to say that the purpose of our buildbot setup (the way that it is currently conceived) is to build

Re: Buildbots down?

On Apr 22, 2021, at 01:49, Ryan Schmidt wrote: > On Apr 21, 2021, at 11:36, Herby G wrote: > >> https://build.macports.org/ is unreachable. > > Maybe there was a temporary problem with my Internet connection? It was up > when I checked it. I have seen intermittent fail

Re: emacs-app-devel build fail on master not detected by buildbot

On Apr 22, 2021, at 21:48, Dan Ports wrote: > To be clear, the problem here was that MacPorts uses the xcode-provided > git, and certain older systems have a version of git that's too old to > support the --shallow-since option, causing the port to break on > systems where it's buildable today.

Reminder: Pull request CI checks will break on May 1

The Bintray service will cease to exist on May 1. Our pull request CI checks rely on being able to download certain assets from Bintray, so unless we do something to fix this before then, our pull request CI checks will no longer work as of May 1. https://jfrog.com/blog/into-the-sunset-bintray-

Re: MacPorts 2.7.0-beta1 now available for testing

On Apr 24, 2021, at 13:19, Ken Cunningham wrote: > Started testing on 10.4 Intel: > > after upgrading /opt/local to the release-2.7 branch tip building from git > source I am seeing this, which I have not previously noticed: > > $ port > sqlite error: attempt to write a readonly database (15

Re: MacPorts 2.7.0-beta1 now available for testing

On Apr 24, 2021, at 22:46, Joshua Root wrote: > On 2021-4-25 12:36 , Ryan Schmidt wrote: >> On Apr 24, 2021, at 13:19, Ken Cunningham wrote: >>> then I build and install base in /opt/local like this: >>> >>> ./configure —with-curlprefix=/opt/bootstrap &g

Re: codesigning and app permissions for programs that need filesystem access

On Apr 24, 2021, at 10:49, Nathaniel W Griswold wrote: > I guess my intent in asking this was to ask: does macports ever ad-hoc > codesign packages? Is there ever a case that is necessary? Googling didn’t > yield much discussion about it. MacPorts does not contain any code to codesign anything

Re: MacPorts 2.7.0-beta1 now available for testing

On Apr 24, 2021, at 23:23, Ken Cunningham wrote: > On Apr 24, 2021, at 7:36 PM, Ryan Schmidt wrote: > >> Does only the first non-sudo `port` command fail? Does running the command >> with `sudo` once allow it to work without `sudo` a second time? >> >> (The

Re: MacPorts 2.7.0-beta1 now available for testing

On Apr 25, 2021, at 11:57, Ken Cunningham wrote: > Well, now I am a bit confused. I restarted the Tiger machine, and the problem > is back: > > $ uname -a > Darwin MacMini.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 > PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 >

Re: GitHub CI Jobs Failing During MacPorts Bootstrap

On Apr 27, 2021, at 09:37, Christopher Nielsen wrote: > force-push a change to re-initiate the CI process. Or close and reopen the PR using the GitHub web interface.

Re: GitHub CI Jobs Slower than Usual?

On Apr 25, 2021, at 08:46, Christopher Nielsen wrote: > Are the GitHub CI builds running much slower than usual? (At least, as > compared to a few weeks ago.) > > Installing of dependencies, in particular, is taking several hours. > > Does anyone have any thoughts/insight? Can you point me to

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 10:58, Christopher Nielsen wrote: > I’ve noticed this with all of my recent PRs. > > But here’s one from a few days ago, for NoMacs: > https://github.com/macports/macports-ports/pull/10781/checks?check_run_id=2427118047 > > Looking at the raw logs, with timestamps, illustrate

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 11:36, Christopher Nielsen wrote: > Ryan, from what I can see in the logs, qt5-qttools doesn’t appear to be > building. > > It looks like the published binary is being fetched: > > ---> Fetching archive for qt5-qttools > DEBUG: Executing org.macports.archivefetch (qt5-qttoo

Re: Reminder: Pull request CI checks will break on May 1

On Apr 23, 2021, at 07:08, Ryan Schmidt wrote: > The Bintray service will cease to exist on May 1. Our pull request CI checks > rely on being able to download certain assets from Bintray, so unless we do > something to fix this before then, our pull request CI checks will no longer

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 11:17, Ryan Schmidt wrote: > On Apr 27, 2021, at 10:58, Christopher Nielsen wrote: > >> Is this normal/expected? > > Nope, there is a problem for me to fix on the server. I see lots of "403 > Forbidden" requests to the private archives,

Re: openmpi-* subports, and publishing of binaries

On Apr 27, 2021, at 17:10, Christopher Nielsen wrote: > As a follow-up to this thread, I recently noticed that we’ve been publishing > binaries for port hwloc for quite some time. And openmpi is utilizing that > library, apparently without any issues. (Confirmed by the dependencies of the >

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 16:50, Christopher Nielsen wrote: >> How do I access this log for a PR build? > To get the detailed logs, you have to download the zipped log archive. Start > by navigating here: > > https://github.com/macports/macports-ports/pull/10781/checks?check_run_id=2427118047 > >

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 17:24, Ryan Schmidt wrote: > I know there is a bug in base where the same host is tried twice, but I > haven't seen it happen three times before. > > https://trac.macports.org/ticket/57719 Ok yes that is the bug. Each of the archive_site_local entries (w

Re: openmpi-* subports, and publishing of binaries

On Apr 27, 2021, at 18:15, Christopher Nielsen wrote: > [My previous reply looks like it may be stuck in the mailman queue, and/or > rejected. So re-sending with additional info.] > > Well, the investigation is all on me, barring a definitive answer from > someone more knowledgable. > > But

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 18:07, Ryan Schmidt wrote: > On Apr 27, 2021, at 17:24, Ryan Schmidt wrote: > >> I know there is a bug in base where the same host is tried twice, but I >> haven't seen it happen three times before. >> >> https://trac.macports.org/ticke

Re: GitHub CI Jobs Slower than Usual?

On Apr 27, 2021, at 18:21, Ryan Schmidt wrote: > On Apr 27, 2021, at 18:07, Ryan Schmidt wrote: > >> On Apr 27, 2021, at 17:24, Ryan Schmidt wrote: >> >>> I know there is a bug in base where the same host is tried twice, but I >>> haven't seen it

Re: build.macports.org down?

On Apr 29, 2021, at 09:48, Christopher Nielsen wrote: > I’m currently trying to check the builder logs, but build.macports.org isn’t > responding. Is it down? Yes, it is down. There was a thunderstorm and a power outage. Builds were happening on all builders at the time, so I need to manuall

Re: MacPorts 2.7.0-beta1 sqlite error: attempt to write a readonly database

On Apr 29, 2021, at 10:32, Joshua Root wrote: > It appears that SQLite version 3.35.5 as installed by the sqlite3 port > deletes a database's -wal and -shm files at least some of the time when > closing. SQLite version 3.28.0 as shipped as /usr/bin/sqlite3 on Catalina > does not. The existen

Re: GitHub discussions

On Apr 30, 2021, at 14:08, Mark Anderson wrote: > For some of our more long running discussions should we try and leverage > GitHub’s discussion feature? I know that for instance the past Perl > discussion and the Binary only discussion can be hard to wade through on the > list. Might be a good

Re: GitHub discussions

On May 1, 2021, at 17:46, Gregory Anders wrote: > One potential solution might be something like public-inbox.org [1]. This > would provide an easy-to-access archive without fragmenting discussion > further. Why would an archive created with public inbox be easier to use than the archives w

Re: MacPorts 2.7.0-beta2 now available for testing

On May 2, 2021, at 10:19, Joshua Root wrote: > On 2021-5-1 20:05 , Andrew Udvare wrote: >> Any chance this can get in to the final release? >> https://github.com/macports/macports-base/pull/225 > > Most likely not for 2.7.0. Typically only regression fixes are merged to the > branch during the b

Re: Ports updated without maintainer notification?

On May 7, 2021, at 01:59, Jason Liu wrote: > I've run across a situation that has left me confused. I started updating > some of the portfiles for which I'm the maintainer, and then I noticed that > the portfiles seem to have already been updated in git. However, I can't find > any PRs for s

Re: Ports updated without maintainer notification?

On May 8, 2021, at 14:26, Jason Liu wrote: > Running port -d sync results in the updated ports now showing up in the list > of outdated ports. I was under the impression that port selfupdate ran port > sync as a part of the self-update process? Or am I mistaken, and port sync > needs to be adde

Re: python port notes suggest to "select" one -- but do we want that

On May 8, 2021, at 13:40, Ken Cunningham wrote: > Sat am ponder: > > I just updated python and saw the note displayed to select a python if you > want it the default. > > However we/I spend lots of time undoing this kind of thing, asking people to > unselect everything, when their builds in

Re: compiler_wrapper portgroup

On May 7, 2021, at 12:13, Chris Jones wrote: > Hi, > > It solves a number of problems, but mostly it boils down to not all build > systems or projects supporting the standard rules we use in macports for > passing flags erc. to the underlying compilers. Legacy support PG for > instance requ

MacOSX11.sdk

I notice that the Xcode 12.5 CLT (but not Xcode 12.5) now contains a MacOSX11.sdk symlink pointing to the MacOSX11.3.sdk. If MacPorts used MacOSX11.sdk when available instead of the more-specific version number, it would reduce some of the problems we have from baked-in SDK paths in some ports.

Re: Buildbot Performance

On May 12, 2021, at 07:41, Christopher Nielsen wrote: > > On 2021-05-12-W, at 08:32, Christopher Nielsen wrote: > >> Looking at the build times for various ports, it varies significantly. >> >> I was curious, are we overcommitting virtual CPUs vs. the number of >> available physical cores on ou

Re: Buildbot Performance

On May 14, 2021, at 07:12, Christopher Nielsen wrote: > Since we’re overcommitting on CPU, I’m wondering if it would make sense to > reduce the vCPUs in each VM to 4? In addition to reducing any swapping, that > might also reduce the hypervisor context-switching overhead, and improve > build ti

Re: Buildbot Performance

On May 16, 2021, at 09:48, Christopher Nielsen wrote: > In terms of the ratio of vCPUs to GB of RAM, 1:1 isn’t totally unreasonable. > However, we should also reserve 2 GB of RAM for the OS, including the disk > cache. So perhaps 6 vCPUs would be a better choice. MacPorts base hasn't ever co

Re: Homebrew Disables OSXFuse ports

On May 16, 2021, at 21:49, Mark Anderson wrote: > Given some of our recent back and forth, I found this interesting: > https://github.com/Homebrew/homebrew-core/pull/74812 Meh. They have different priorities than we do. No reason for us to follow what they do.

Re: Becoming a legal entity and accepting donations (was: Re: Buildbot Performance)

On May 16, 2021, at 14:46, Mark Anderson wrote: > I keep wondering if we became like a not-for-profit If we could get someone > like MacStadium or Amazon or something to donate server time to us. Or accept > donations from Github sponsorship. I could look into what that would take, > although i

Re: Buildbot Performance

On May 16, 2021, at 17:57, Daniel J. Luke wrote: > On May 16, 2021, at 10:48 AM, Christopher Nielsen wrote: >> I’d bet the hypervisor is spending more time on scheduling and pre-emption, >> than actual processing time. > > This is something we could actually measure, though, right? Then we do

Re: Buildbot Performance

On May 17, 2021, at 13:13, Jason Liu wrote: > Regarding CPU overcommitment: Are the virtual hosts doing any sort of CPU > pinning? Many virtualization products have the ability to specify which of > the pCPU cores a guest is allowed to use. As far as I can remember, products > like KVM and ESXi

Re: Buildbot Performance

On May 17, 2021, at 07:36, Christopher Nielsen wrote: > As for overcommitment: I’m simply suggesting that we reduce the number of > vCPUs per builder, from eight to six. And I'm suggesting that doing so will slow things down in those situations when only one or two VMs on a host are busy. I

Re: Buildbot Performance

On May 17, 2021, at 17:30, Christopher Nielsen wrote: > If you total up the memory allocated across all VMs, is there at least one or > two GB free for the hypervisor? The hypervisor reserves 4.x GB for itself.

Re: Buildbot Performance

On May 17, 2021, at 17:42, Christopher Nielsen wrote: > Also, I see two buildbot VMs with 9 GB of memory allocated: > > OS X El Capitan v10.11.6 (15G22010) > Xcode v8.2.1 (8C1002) > Apple LLVM version 8.0.0 (clang-800.0.42.1) > Architecture: x86_64 > C++ library: libc++ > CPU: 8 ⨉ 2.15 GHz > RAM:

Re: Homebrew Disables OSXFuse ports

On May 17, 2021, at 08:44, Perry E. Metzger wrote: > On 5/17/21 01:44, Ryan Schmidt wrote: >> On May 16, 2021, at 21:49, Mark Anderson wrote: >> >>> Given some of our recent back and forth, I found this interesting: >>> https://github.com/Homebrew/homebrew-

Re: llvm-9.0 on 10.6.8 shows red -- but it builds

On May 18, 2021, at 00:53, Mojca Miklavec wrote: > On Tue, 18 May 2021 at 07:15, Ken Cunningham wrote: >> >> People are quoting >> >> the lack of llvm-9.0 for SnowLeopard on macports as a sign of the demise

Re: Framing the MacPorts discussion

MacPorts is short-staffed in all areas, not just infrastructure. Our Buildbot system works. It produces all the binaries we are able to. Our buildbot system was already substantially redesigned when we took it over from Apple in 2016 and will be substantially redesigned again as we upgrade to t

Re: llvm-9.0 on 10.6.8 shows red -- but it builds

On May 18, 2021, at 04:35, Mojca Miklavec wrote: >>> That probably counts as a bug in the Tcl script that returns the list >>> of subports to be built. >> >> I'm not aware of a bug in that script. > > Do you have any clue or any alternative explanation why llvm-9.0 would > be missing on this lis

Re: Why is binary avoided for Xcode MPI wrappers?

On May 20, 2021, at 11:51, Eric Borisch wrote: > It was an issue where when the xcode versions were not aligned on the builder > and user that the resulting binary package did not work correctly. > > I really can't speak to if this is still an issue we would run into; we could > always try re-e

Re: Error: Failed to build snort

On May 19, 2021, at 19:22, Bjarne D Mathiesen wrote: > #=> port outdated > The following installed ports are outdated: > snort 2.9.17_0 < 2.9.17.1_0 > root@MacPro 02:05:26 /Library/LaunchDaemons > #=> port -cuNp upgrade snort > ---> Computing dependencies for snort > --->

Re: Framing the MacPorts discussion

On May 19, 2021, at 07:56, Bjarne D Mathiesen wrote: > Ryan Schmidt wrote: >> I personally am not comfortable adding other build machines to our buildbot >> system that I do not control. When I control the machines, I know what is >> installed on them and that they are set

<    4   5   6   7   8   9   10   11   12   13   >