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
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
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
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
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
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
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 happe
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/ticket/577
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.
>
>
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 (which
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
>
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 archive
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
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,
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
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.
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
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?
>>
>> (
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
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
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
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.
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
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
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
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.
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
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:
>
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
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.
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
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
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
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
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
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
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.
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 caches a
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.
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 got
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-
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
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
>>> ? linux r
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
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.
&g
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.
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
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
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
>
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...
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) e
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
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
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
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
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:
>
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.
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 doesn't d
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,
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
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
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
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
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
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
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
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
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.
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
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
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
>
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
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
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
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
On Feb 13, 2021, at 04:21, Chris Jones wrote:
> On 13 Feb 2021, at 9:06 am, Ryan Schmidt wrote:
>
>> Apple helpfully recreated the CoreSimulator directory again today. I'm not
>> going to delete it again unless we have a plan for how to prevent it from
>> b
On Feb 11, 2021, at 19:19, Ryan Schmidt wrote:
> On Feb 11, 2021, at 18:45, 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.
On Feb 12, 2021, at 20:57, Ruben Di Battista wrote:
> Hello, I was exploring a bit how to build the CI system for old platforms and
> the first step was to virtualize old macOS version. I'd like to do it using
> KVM. I was following this: https://github.com/kholia/OSX-KVM, but trying to
>
On Jan 31, 2021, at 11:05, harens wrote:
> I completely agree that Homebrew is currently winning at publicity.
What should the MacPorts community be doing do publicize MacPorts better?
> I think vocalising the points of Saagar Jha’s article Thoughts on macOS
> Package Managers would be
On Feb 7, 2021, at 09:59, Ken Cunningham wrote:
> On Feb 7, 2021, at 03:17, Clemens Lang wrote:
>
>> Hi Ken,
>>
>>> On Sat, Feb 06, 2021 at 11:35:58PM -0800, Ken Cunningham wrote:
>>> although I was concerned about getting this pattern right before we
>>> had too many of these to fix, it does
On Feb 6, 2021, at 11:55, Lothar Haeger wrote:
> The latest version of FileZilla fails to build on my Catalina system and the
> developer states, it requires the latest BigSur SDK to compile (though the
> final binary should be running on macOS 10.11 and newer):
>
> →
On Feb 6, 2021, at 09:17, Ken Cunningham wrote:
> those are the small things.
>
> I stopped when the broad strokes, as it is now, were a unworkable disaster.
I don't understand which aspects are an unworkable disaster. As I said, based
on what you've said so far, it seems like everything
On Feb 6, 2021, at 04:15, Ken Cunningham wrote:
> try the sagemath one if you like. It's all set, for a newish system at
> present:
>
> https://github.com/kencu/myports/blob/master/binary/sagemath-binary/Portfile
>
> It is a stress test, for sure -- and I fully admit you may know simple
On Feb 6, 2021, at 02:14, Ken Cunningham wrote:
> On Feb 5, 2021, at 10:04 PM, Ryan Schmidt wrote:
>
>> That sounds like what Craig is saying: that meson is now adding a compiler
>> flag that old compilers don't understand. Meson should check whether a
>> compile
On Feb 6, 2021, at 02:28, Ken Cunningham wrote:
>>> This kind of port just repackages the DMG into many tgz archives.
>>>
>>> It’s wasteful. People want them.
>>>
>>> What we should have instead of this is some kinda tech that
>>>
>>> 1. downloads the DMG
>>> 2. installs the app
>>> 3. records
On Feb 4, 2021, at 11:26, Ken Cunningham wrote:
> wait, I could have missed the issue...if meson is now adding a default
> argument to all checks that means it can never build anything with the
> default compilers on <10.10, that would be something we should consider
> fixing in meson, even
On Feb 5, 2021, at 13:00, Ken Cunningham wrote:
> With no plan, we’ll just keep getting more and more of these.
I'm not aware of a huge influx of these, but I'm also not really paying
attention to the PR queue. And I'm not intending to get drawn into this
discussion of binary ports again.
On Feb 3, 2021, at 03:29, Eric Borisch wrote:
> This seems off.
>
> Hwloc’s own page talks about the availability of pre-compiled packages, and
> its demos focus on determining what threads to bind to (on OSes where
> explicit binding is possible; last I checked it wasn’t on OSX) if you
On Feb 3, 2021, at 01:12, Ken Cunningham wrote:
>> But if "his system will never see that port could be universal" then how
>> could he "download and install that port +universal" in the first place?
>
> that is the crux of it, indeed.
>
> Should our poor soul, who cannot build the port
On Feb 1, 2021, at 09:49, Christopher Nielsen wrote:
> Given how long the various openmpi-* subports take to build, it would be
> beneficial to publish binaries for our users.
>
> This is currently disabled in the Portfile, with a brief mention that it’s
> due to ‘hwloc’... and the tight
On Feb 2, 2021, at 11:18, Ken Cunningham wrote:
> One port needed +universal has some tricks in it, and requires
> "merger_must_run_binaries". That port cannot be built universal on an Intel
> system (which can't run arm64) but can be built universal on an arm64 system
> (which can run
On Feb 2, 2021, at 18:27, Craig Treleaven wrote:
> In the dav1d PR, CI didn’t produce results for the older OS versions. I
> thought the CI system was just being grumpy.
Our CI system uses publicly available build infrastructure from GitHub, which
only offers build machines running current
On Jan 27, 2021, at 06:32, Mojca Miklavec wrote:
> Maybe GitLab runner isn't able to run on the oldest macOS that we
> support, but if you run it on the host just to fire up a VM, that
> might be ok.
>
> I see that GitLab supports CI on top of GitHub repository:
>
>
On Jan 25, 2021, at 11:37, Clemens Lang wrote:
> I personally wouldn't have a problem with optional CI steps running on
> other people's machines, as long as that's for pull requests and we
> don't use the results anyhere but to post status information to GitHub.
There would be an advantage
On Jan 25, 2021, at 10:02, Ruben Di Battista wrote:
> If I configured a server I own to run CI jobs for old systems (I was thinking
> about using a custom Gitlab runner libvirt
> https://docs.gitlab.com/runner/executors/custom_examples/libvirt.html for
> that and maybe), it's gonna be
On Jan 25, 2021, at 10:03, Andrew Janke wrote:
> On 1/25/21 10:31 AM, Ryan Schmidt wrote:
>> On Jan 25, 2021, at 01:55, Joshua Root wrote:
>>
>>> On 2021-1-25 18:48 , Andrew Janke wrote:
>>>> How do you download the installers for Big Sur and for older vers
On Jan 25, 2021, at 01:55, Joshua Root wrote:
> On 2021-1-25 18:48 , Andrew Janke wrote:
>> How do you download the installers for Big Sur and for older versions of
>> macOS? I've always had to go through the App Store to download installers,
>> and what it makes available for me is
On Jan 24, 2021, at 17:52, Ruben Di Battista wrote:
> I think that one of the selling points of Macports, at least for me, is
> providing ports for legacy systems. So on the ports I maintain, I try to fix
> build issues on old systems. The problem is that it’s very difficult to do it
>
On Jan 21, 2021, at 02:04, Bjarne D Mathiesen wrote:
> Ken Cunningham wrote:
>> It builds on 10.4 to 10.14 at least; dunno about 10.15, although gcc5
>> seems to build there. Haven't tried.
>
> Doesn't work on my 10.15
Normally it would be helpful to provide more information. In this case we
On Jan 21, 2021, at 02:06, Bjarne D Mathiesen wrote:
> php80-imagick can be installed directly from git :
> ( https://github.com/Imagick/imagick/issues/358 )
Yes, but if you actually read that issue, you'll find that the author is not
ready to declare that code as the PHP 8-compatible release
201 - 300 of 1515 matches
Mail list logo
