Re: Packaging buildbot-www

On May 29, 2019, at 06:21, Rajdeep Bharati wrote: > On Wed, May 29, 2019 at 1:12 AM Rainer Müller wrote: > >> Out of curiosity, where does this screenshot come from? > > It's present in the UI: https://nine.buildbot.net/#/about >> To me it looks like all of these (minified) JavaScript libra

Re: `port select python` and qtwebengine

On Jun 2, 2019, at 10:03, René J.V. Bertinwrote: > I just learned that the QtWebEngine build process has a hard dependency on > python 2 and cannot be configured to use a specific python interpreter > exclusively. In other words, it fails if a user apparently used `port select > python` to m

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On May 31, 2019, at 17:27, Rajdeep Bharati wrote: > On Sat, Jun 1, 2019 at 2:01 AM Mojca Miklavec wrote: > >> What does >> port installed '*buildbot*' >> say? > > It's giving None of the specified ports are installed. It should show you all ports that are installed whose names contain th

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On May 29, 2019, at 13:29, Mojca Miklavec wrote: > As an intermezzo I want to explain one thing. Initially we had one single job > (which could run for days), and it built all the ports in a single job. > However one could not infer any information about what worked and what failed > without

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On Jun 2, 2019, at 11:30, Rajdeep Bharati wrote: > One thing is that when I install the new py37-buildbot, the command that I > get to use is `buildbot-3.7`. > What changes do I need to make in the port to use the command `buildbot`? As Rainer explained in https://github.com/macports/macport

Re: `port select python` and qtwebengine

On Jun 2, 2019, at 12:06, Joshua Root wrote: > On 2019-6-3 01:59 , Ryan Schmidt wrote: >> As a side note, as I understand it, it is a user error to make "python" a >> symlink to Python 3; it should always be Python 2. Going forward, use a >> "python2"

Re: `port select python` and qtwebengine

On Jun 3, 2019, at 04:20, René J.V. Bertin wrote: > > Would it be possible (and acceptable) to prevent the kind of build failure > we're talking about here by setting up a temporary symlink to a sanctioned > python interpreter in a build-specific tmp directory and prepend that > directory to

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On Jun 3, 2019, at 15:51, Mojca Miklavec wrote: > > On Sun, 2 Jun 2019 at 18:46, Ryan Schmidt wrote: > >> Buildbot is a program that we want to use for its own sake, so its port name >> should not begin with "py-" and it should be in a primary category that &

Re: upt-macports project update and feedback request

On Jun 5, 2019, at 21:36, Karan Sheth wrote: > 1. The naming convention of Python ports > For upt to be able to process dependencies correctly and add missing packages > recursively, it is important to have a consistent naming scheme for ports. > Currently, that is not completely the case, al

Re: upt-macports project update and feedback request

On Jun 6, 2019, at 21:11, Renee Otten wrote: > Looking at your comments I must admit I am a little confused, but that is > probably because I am not understanding some (basic) MacPorts things > correctly… For example, I didn’t realize (probably never tried) that “port > info py-sphinx” and "por

Re: openssl source install with trace mode bugged

On Jun 6, 2019, at 17:23, Rainer Müller wrote: > On 03.06.19 15:50, Mihir Luthra wrote: >> I noticed that on a “new" MacPorts installation, if we try to install >> openssl with flags -st, it will fail. >> >> Problematic lines in main.log with debug on are :- >> >> :info:configure darwintrac

Re: Peculiar perl version issue

On Jun 12, 2019, at 10:26, Bruce Miller wrote: > [This is motivated by the LaTeXML port, > but is a general question about perl portgroup] > > A colleague suggested the clever shebang line > #!/usr/bin/env perl > as a way to easily allow testing against different > versions of perl, running i

Re: Peculiar perl version issue

On Jun 12, 2019, at 13:41, Bruce R Miller wrote: > On 6/12/19 1:14 PM, Ryan Schmidt wrote: >> On Jun 12, 2019, at 10:26, Bruce Miller wrote: >> >>> So, apparently the perl portgroup replaces shebang >>> lines that it recognizes with a call to the specific &

Re: Xcode INSTALL_PATH and framework paths

On Jun 13, 2019, at 02:01, Aaron Madlon-Kay wrote: > I am working on a portfile for Sequel Pro (https://sequelpro.com/) and > am reaching the limits of my understanding of the Xcode build system. > > Sequel Pro contains several framework subprojects, which get built > along with the main target.

Re: Xcode INSTALL_PATH and framework paths

On Jun 13, 2019, at 09:37, Aaron Madlon-Kay wrote: > Now I have another issue: after installation the port is flagged as broken > with the following message. > >> sequelpro-devel is using libstdc++ (this installation is configured to use >> libc++) > > As I understand it, the reason is that

Re: Suggestion to slightly simplify pypi ports

On Jun 23, 2019, at 02:52, Mojca Miklavec wrote: > I would like to suggest providing simplification for the following four lines: > > namepy-foo > version 1.2.3 > master_sitespypi:[string index ${python.rootname} > 0]/${python.rootname} > distname

Re: Deprecating support for ports

On Jun 23, 2019, at 16:42, Adam Mercer wrote: > I work as part of the LIGO project and for a while now we've used > MacPorts to provide support for our collaboration members running our > software under macOS. For various reasons we are in the process of > switching over to Conda as this allows

Re: Suggestion to slightly simplify pypi ports

On Jun 23, 2019, at 05:02, Mojca Miklavec wrote: > I guess this then changes my question into: how could we get rid of > these two rows? > >master_sitespypi:[string index ${python.rootname} > 0]/${python.rootname} >distname${python.rootname}-${version} > > We still

Re: Docker container with MacPorts

On Jun 25, 2019, at 02:52, Mojca Miklavec wrote: > And I ended up with a totally stupid error: > > $ port info > Error: Current platform "linux 4" does not match expected platform "linux 5" > Error: If you upgraded your OS, please follow the migration > instructions: https://trac.macports.org/

Re: macOS 10.15 Read Only root

On Jun 29, 2019, at 19:53, Mark Anderson wrote: > Do we have any plans with how to deal with 10.15 not allowing us to create > /opt if it doesn’t exist? Or does /opt just come with the file system? I > can’t remember. macOS does not come with an /opt directory. I was not aware that macOS Catal

Re: flang port

On Jul 8, 2019, at 14:37, Jack Howarth wrote: >Since the legacy header support for avoiding the availability attribute > has been dropped from the 10.15 SDK... > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835 > > and it is unclear when and if the missing availability attribute supp

Re: Setting up port builds on Azure using master branch of macports

On Aug 1, 2019, at 10:50, Blair Zajac wrote: > On Aug 1, 2019, at 2:01 AM, Mojca Miklavec wrote: > >> Is anyone willing to set up one Azure build instance running macports >> master when building the ports? >> >> This could help us spot any potential issues with our code in the >> master bran

Re: build failure - odd compiler selection

On Aug 5, 2019, at 14:02, Christopher Jones wrote: > OK, I’ve worked out what was going on. > > The problem is the port uses the cxx11 port group, which internally sets the > whitelist to include *only* macports-clang-5.0. This is then used instead of > the fallback list below to pick a compile

Re: 10.7 buildbot disk space issues

On Aug 12, 2019, at 09:56, Chris Jones wrote: > Hi, > > Looks like the 10.7 bot is low on disc space again.. > > > > cheers Chris As you can see from the cleanup step's output,

Re: Is the buildbots filesystem case-sensitive?

On Aug 14, 2019, at 13:04, Ruben Di Battista wrote: > I’m hitting strange file not found errors on the paraview build on the > buildbots, but not locally nor on Azure; so I was wondering: do they run on a > case sensitive filesystem? Yes. P.S: Please make sure you write to our new list add

Re: 10.7 buildbot disk space issues

On Aug 14, 2019, at 08:28, Christopher Jones wrote: >> As you can see from the cleanup step's output, there was 21GiB of space >> available when the build failed. >> >> https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/108375/steps/cleanup/logs/stdio >> >> How much

Re: Retiring ports.php

On Aug 15, 2019, at 09:06, Mojca Miklavec wrote: > On Thu, 15 Aug 2019 at 15:27, Joshua Root wrote: >> >> I think ports.macports.org is already clearly superior to ports.php, so >> we should change the Available Ports link to point there. However, we >> should not remove ports.php so as not to

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 18, 2019, at 03:56, Dmitri Zaitsev wrote: > 3. What kind of build error is that and how to deal with it? Rust does not build on an OS X version as old as you are using. Software developers frequently remove support for older operating systems from their projects, on the assumption tha

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 19, 2019, at 05:22, Chris Jones wrote: >> It could be that switching to the latest compiler would help. You can >> try building with >> sudo port -v build rust configure.compiler=macports-clang-7.0 >> or something like that (I'm not 100% sure if the command is exactly >> right as I'm

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 20, 2019, at 02:19, Dmitri Zaitsev wrote: > Just trying to understand it better, does it mean when I attempted to access > those file, their mirroring had been initiated but it took many hours before > the completion? Is it documented somewhere? When a change to a port is committed, o

Re: Preparing for 2.6.0 beta

On Aug 23, 2019, at 22:45, Joshua Root wrote: > I think we're pretty close to being ready to make a new stable branch > and tag a beta. Clemens is going to make one more change related to > Xcode checking; are there any other changes that really need to go in > before the beta? It would be nic

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 08:55, Joshua Root wrote: > On 2019-8-24 21:59 , Mojca Miklavec wrote: > >> I would be grateful for addressing these: >> >> https://trac.macports.org/ticket/50448 > > Way too late to do anything about that in base. The plan is as described > in comment 16. I didn't reali

Re: 10.6.8 i386 buildbot offline

On Sep 7, 2019, at 09:17, Ken Cunningham wrote: > just a heads-up that this buildbot appears to have been offline a couple of > days now Thanks for letting me know. I've fixed it.

Re: https://build.macports.org/ down ?

I was also having trouble accessing it. The "kernel_task" and "master" processes were using over 50% CPU each, which didn't seem normal. So I restarted the server. Seems ok now. (Where "slow" must unfortunately be classified as "ok".) -Ryan > On Sep 15, 2019, at 07:44, Chris Jones wrote: > >

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 12, 2019, at 03:46, René J.V. Bertin wrote: > I hope I didn't ask this before: > > Is there a way to let command line options like the ones in the subject apply > to all ports on the command line, instead of only to the one given just > before of the option in question? I would guess

Re: [guide] 5.3 missing keywords

On Aug 31, 2019, at 07:31, Bjarne D Mathiesen wrote: > A description of the "build.dir" & "configure.dir" keywords are missing > > I only discovered these keywords by accident by looking in a Portfile > for help with exactly these issues : changing into a directory before a > python install >

Re: libraw updates because fetch gives 404

On Aug 26, 2019, at 04:25, Christopher Jones wrote: > On 26 Aug 2019, at 8:49 am, Riccardo Mottola wrote: > >> Hi, >> >> since yesterday I am trying to update... but... >> >> Is something wrong with our mirrors? > > The mirrors themselves seem fine. Just looks like the 0.19.5 update dist fi

Re: Port variants for deps

On Sep 15, 2019, at 22:31, Eric F (iEFdev) wrote: > What would be better (ie good “portiqette”)… Adding subports (keeping the > variants), or replacing variants with subports? Provide only one way for a user to install a feature. Convert variants to subports, if appropriate. Usually if a va

Re: scope of configure.optflags, configure.compiler etc. command line variables

I don't want to discuss this at great length, but I'll answer these questions: On Sep 16, 2019, at 02:22, René J.V. Bertin wrote: > On Sunday September 15 2019 20:25:59 Ryan Schmidt wrote: > >> Setting such options on the command line is intended as a debugging >

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 17, 2019, at 03:08, René J.V. Bertin wrote: > I continue to think that compiler choice and options should be something the > user can set the default for, without having to replace the standard system > compiler drivers (/usr/bin/clang{,++}) with wrapper scripts. As you know, we don't

Re: Port variants for deps

On Sep 16, 2019, at 17:01, Eric F (iEFdev) wrote: > On 9/16/19 23:20 , Ryan Schmidt wrote: >> On Sep 15, 2019, at 22:31, Eric F (iEFdev) wrote: >> >>> What would be better (ie good “portiquette”)… Adding subports (keeping the >>> variants), or

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 17, 2019, at 03:26, René J.V. Bertin wrote: > On Monday September 16 2019 16:26:12 Ryan Schmidt wrote: > >> There should be no need for you to specify anything ccache-related on the >> command line. You can enable ccache globally in macports.conf. Individual >&

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 23:20, Joshua Root wrote: > On 2019-8-25 03:00 , Mojca Miklavec wrote: >> Would it be possible to set up at least one builder with 10.6 running >> MacPorts master, building all ports with libc++ (apparently default by >> now in master), just not uploading the archives to the

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 12:00, Mojca Miklavec wrote: > Independent from the stdlibc++ vs. libc++ question I still believe > that it would be really nice to be able to easily include/exclude the > set of macOS versions. Say that we organize the meeting with very poor > internet connectivity (which i

Re: Preparing for 2.6.0 beta

On Sep 19, 2019, at 20:45, Joshua Root wrote: > On 2019-9-20 11:38 , Ryan Schmidt wrote: >> >> >> On Aug 24, 2019, at 23:20, Joshua Root wrote: >> >>> On 2019-8-25 03:00 , Mojca Miklavec wrote: >>>> Would it be possible to set up at least on

Re: Preparing for 2.6.0 beta

On Sep 19, 2019, at 21:22, Mojca Miklavec wrote: > On Fri, 20 Sep 2019 at 03:38, Ryan Schmidt wrote: >> >> >> >> On Aug 24, 2019, at 23:20, Joshua Root wrote: >> >>> On 2019-8-25 03:00 , Mojca Miklavec wrote: >>>> Would it be pos

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 20, 2019, at 02:23, René J.V. Bertin wrote: >> Storing a separate cache for each port would quickly eat up a lot of disk >> space. > > Evidently, but > - ccache doesn't use more space than needed > - the ccache directory compresses extremely well with afsctool, a background > cleanup

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

On Sep 19, 2019, at 23:40, Ken Cunningham wrote: > the documentation that comes along with many ports often seems like a heavy > and arguably needless burden: > I vote we expect ports to not include anything but a few man pages. > Everything else should be either left out, or an optional var

Re: Publishing links to non-encrypted websites for MacPorts downloads

On Sep 25, 2019, at 00:43, Mojca Miklavec wrote: > I already mentioned this in the past, but I would like to repeat. > When someone opens our homepage and wants to download MacPorts using > Safari on, say, 10.6, the download link from GitHub doesn't work, and > it's not trivial for users to fin

Re: Publishing links to non-encrypted websites for MacPorts downloads

On Sep 26, 2019, at 00:04, Mojca Miklavec wrote: > On Thu, 26 Sep 2019 at 06:26, Ryan Schmidt wrote: > >> On Sep 25, 2019, at 00:43, Mojca Miklavec wrote: >> >>> I already mentioned this in the past, but I would like to repeat. >>> When someone open

Re: 2.6.0 features

On Oct 5, 2019, at 07:14, Joshua Root wrote: > It has now been the customary 2 weeks since the release of MacPorts > 2.6.0, so the new features can be freely used in portfiles. In particular: > > * New compiler selection options. You can specify required C or C++ > standard versions, and/or sp

Re: 2.6.0 features

On Oct 5, 2019, at 08:37, Ken Cunningham wrote: > I have come across several ports where variant c++ standards are needed, like > gnu++11 for example, so perhaps setting the std automatically could lead to > troubles... Yeah. I had assumed that the MacPorts base feature had been implemented

Re: implementation of configure.env-append

On Oct 6, 2019, at 14:05, Ken Cunningham wrote: > I think I have tried this enough ways to be close, but I just want to be > certain. > > I want to *append* a value onto an existing environment variable from a > Portfile. I don’t want to overwrite what is there in the environment variable >

Re: CatalinaProblems added

On Oct 8, 2019, at 06:10, MacPorts Wiki wrote: > Page "CatalinaProblems" was added by jmroot > Content: > Ensure you have Xcode 11.0 or greater installed and selected (e.g. `sudo > xcode-select -s /Applications/Xcode.app/Contents/Developer`), and that you > have the command line tools instal

Re: Upgrade cctools unexpectedly failing

On Oct 8, 2019, at 10:34, Chris Jones wrote: > On 08/10/2019 6:52 am, Ken Cunningham wrote: >>> I wonder if the SDK path is >>> baked into llvm-config-mp-7.0? >> Yep -- sheesh. Is there no end to this? >> Ken >> $ llvm-config-mp-7.0 --cflags >> -I/opt/universalnew/libexec/llvm-7.0/include -pipe -O

Re: Upgrade cctools unexpectedly failing

On Oct 8, 2019, at 20:44, Joshua Root wrote: > On 2019-10-9 02:48 , Ryan Schmidt wrote: >> If we used the "MacOSX.sdk" (instead of the versioned one) the fact that it >> gets baked into things wouldn't be a problem*. We should do this, but it >> will

Re: CatalinaProblems added

On Oct 8, 2019, at 20:22, Joshua Root wrote: > On 2019-10-9 02:34 , Ryan Schmidt wrote: >> >> >> On Oct 8, 2019, at 06:10, MacPorts Wiki wrote: >> >>> Page "CatalinaProblems" was added by jmroot >>> Content: >> >>> En

Re: implementation of configure.env-append

On Oct 9, 2019, at 12:04, Ken Cunningham wrote: > On Tue, Oct 8, 2019 at 1:59 AM Ryan Schmidt wrote: > >> No... it's the other way around... >> >> If you want to modify LDFLAGS, do so by modifying configure.ldflags. >> MacPorts will set the LDFLAGS e

Re: implementation of configure.env-append

On Oct 9, 2019, at 10:57, Ken Cunningham wrote: > On Tue, Oct 8, 2019 at 9:25 AM Blair Zajac wrote: > >> Maybe the MacPorts could raise an error if one attempts to set a variable >> like LDFLAGS outside of configure.* ? Yes, MacPorts could do that. I don't think anybody's tried to write code

Re: Lazarus port

On Oct 11, 2019, at 09:13, Karl-Michael Schindler wrote: > Hi. > > I am working on the Portfile for Lazarus, an integrated IDE for FreePascal > similar to Delphi. Besides some smaller issues, which I am sure I can > address, a major issue shows up that was suggested to present here for > di

Re: Perl module Privileges::Drop Portfile Fails to Build on Azure

On Oct 12, 2019, at 10:20, Steven Smith wrote: > I see that the build is trying to download CPAN stuff Add the needed dependencies so that that does not happen.

Re: pymol crashing under Qt on Catalina

On Oct 16, 2019, at 17:36, Jack Howarth wrote: > > ps Do the binary servers retain the older versions of the python27 packages? > I am tempted to walk back through them and see if I can find a version that > still works. I recently ran a cleanup script that deleted most of the old archives. Her

Re: 10.15 builder

On Oct 17, 2019, at 08:07, Jack Howarth wrote: >I noticed that https://build.macports.org/builders doesn't show a 10.15 > builder yet. Is there a schedule for when one will become available? I have not started setting up a Catalina build worker yet. I may need to archive the recently-ret

Re: Index Broken on 10.5

On Oct 19, 2019, at 16:55, Fred Wright wrote: >> That's probably not actually the index being broken, but a circular >> dependency. See . >> >> The issue causing the circular dependency is that all the system >> compilers are blacklisted by whatever port

Re: replacing OpenGL with MoltenVK

On Oct 21, 2019, at 12:19, Jack Howarth wrote: > > Are there any plans for using the MoltenVK package in MacPorts as a > replacement for the macOS OpenGL support that is slated for depreciation? I haven't heard of any such plans.

How to handle ports that are still broken because of the icu upgrade

icu was recently updated to a new major version. As a result its install_name changed and anything that links with it needs to be rebuilt against the new version. All ports that declare a dependency on icu already had their revisions increased for this reason. So if you are encountering a port

Re: How to handle ports that are still broken because of the icu upgrade

On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: > On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: >> Or does the port use libxml2? If so, it may be using a bad method of finding >> libxml2. One bad method of finding libxml2 is using the xml2-config script. > > Should w

Re: How to handle ports that are still broken because of the icu upgrade

On Oct 23, 2019, at 09:20, Daniel J. Luke wrote: > On Oct 23, 2019, at 9:58 AM, Ryan Schmidt wrote: >> On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: >>> On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: >>>> Or does the port use libxml2? If so, it may be using

Command line tools installed on Mojave buildbot worker

I have now installed the command line tools for Xcode 10.3 on the Mojave buildbot worker. The Xcode version remains at 10.3. So if we need to revbump any ports so that they get rebuilt with command line tools SDK paths instead of Xcode SDK paths, that can now be done.

Re: Lazarus port

On Oct 12, 2019, at 02:34, Karl-Michael Schindler wrote: > Hallo > > Am 12.10.2019 um 03:56 schrieb Ryan Schmidt: > >> I am not familiar with Lazarus but it sounds like a very strange program >> indeed if it requires its own files to be modified at runtime. Normally

Re: "Error: poppler cannot be built while another version of poppler is active." Why?

On Oct 29, 2019, at 20:49, Thomas R. Murphy wrote: > This essentially makes port upgrade outdated require manual intervention when > a rev-bump of poppler comes by. Until this problem in the poppler build system is fixed, you can still have unattended upgrades of outdated ports by writing a

Re: OpenBLAS fixed in Xcode 11.2

On Oct 31, 2019, at 20:34, Joshua Root wrote: > On 2019-11-1 11:49 , Jack Howarth wrote: >> Although it wasn't fixed in Xcode 11.2 beta 2, the -fcheck-stack >> issues with OpenBLAS's test suite are fixed in the final Xcode 11.2 >> released today. >> Jack > > Good to hear. Ryan, c

Re: 10.15 builder offline ?

On Nov 2, 2019, at 07:04, Christopher Jones wrote: > Looks like the 10.15 builder has gone down ? > > https://build.macports.org/waterfall It was requested that I update its Xcode to 10.2, and 10.15.1 is available. I'm doing those updates.

Re: OpenBLAS fixed in Xcode 11.2

On Oct 31, 2019, at 21:51, Ryan Schmidt wrote: > On Oct 31, 2019, at 20:34, Joshua Root wrote: > >> On 2019-11-1 11:49 , Jack Howarth wrote: >>> Although it wasn't fixed in Xcode 11.2 beta 2, the -fcheck-stack >>> issues with OpenBLAS's test

Re: 10.15 builder offline ?

On Nov 2, 2019, at 07:33, Ryan Schmidt wrote: > On Nov 2, 2019, at 07:04, Christopher Jones wrote: > >> Looks like the 10.15 builder has gone down ? >> >> https://build.macports.org/waterfall > > It was requested that I update its Xcode to 10.2, and 10.15.1 is

Re: OpenBLAS fixed in Xcode 11.2

e has now been removed? > Jack > > On Sat, Nov 2, 2019 at 11:43 AM Ryan Schmidt wrote: > > > On Oct 31, 2019, at 21:51, Ryan Schmidt wrote: > > > On Oct 31, 2019, at 20:34, Joshua Root wrote: > > > >> On 2019-11-1 11:49 , Jack Howarth wrote: >

Re: OpenBLAS fixed in Xcode 11.2

On Nov 3, 2019, at 03:52, Chris Jones wrote: > Hi, > > On 2 Nov 2019, at 4:56 pm, Ryan Schmidt wrote: > >> Josh told me when Mojave was released that we weren't installing the CLT >> anymore on the builders. >> >> Then when Xcode 11 came along

freedesktop.org domain expired

The freedesktop.org domain name has expired and is in a pending deletion state with its registrar. This affects a couple hundred of our ports. They are aware of it and are working to get it renewed. https://www.reddit.com/r/linuxquestions/comments/dqxuj3/freedesktoporg_down/ Meanwhile, if you n

Re: FUNDING files

On Nov 4, 2019, at 00:40, Joshua Root wrote: > How would everyone feel about adding FUNDING.yml files to our repos? > > > > Full disclosure: I've been accepted into the GitHub Sponso

Re: FUNDING files

On Nov 4, 2019, at 09:43, Joshua Root wrote: > On 2019-11-5 02:23 , Ryan Schmidt wrote: >> >> >> On Nov 4, 2019, at 00:40, Joshua Root wrote: >> >>> How would everyone feel about adding FUNDING.yml files to our repos? >>> >>> <http

Re: 10.15 builder offline ?

On Nov 5, 2019, at 03:02, Chris Jones wrote: > > Ryan, can you make sure the builder has this update ? Note that 'Software > Update' might not automatically do it, if the package receipts for the CLT > where removed (as they have been on the two machines I have access to running > 10.15) whe

Re: OpenBLAS fixed in Xcode 11.2

On Nov 8, 2019, at 20:03, Joshua Root wrote: > On 2019-11-9 10:28 , Jack Howarth wrote: >> I just noticed a really bizarre aspect to this Xcode 11 bug. If you >> build gmp manually from source with the default compiler flags in use... >> >> ./configure >> make >> make check >> >> the t-powm test

Re: OpenBLAS fixed in Xcode 11.2

On Nov 3, 2019, at 05:39, Jack Howarth wrote: > On Sun, Nov 3, 2019 at 4:55 AM Ryan Schmidt wrote: > >> The fact that the CLT SDK is now preferred is another reason why we want to >> go back to requiring the CLT. After Xcode 11 was released and Mojave users >> upgra

Re: keeping software forks under MacPorts repo?

On Nov 9, 2019, at 10:54, Ken Cunningham wrote: > In #57751 Michael and I have been talking about how keeping up the patchset > for qt4 would probably be easier with our own fork of it, with our patches > added on. > > QT4 has a github repo here and we could fork that

Re: keeping software forks under MacPorts repo?

On Nov 9, 2019, at 11:00, Mojca Miklavec wrote: > > But we would probably want to > prefix the repository names (something like "fork_qt", "fork_llvm") to > clearly distinguish them from our main repositories. I wouldn't necessarily suggest doing that. We're not forking in order to diverge from

Re: Four pending PRs for 4+ days

On Nov 11, 2019, at 14:54, Remko Scharroo wrote: > I have submitted four pull requests 4+ days ago, and they have not been > approved. Only one was commented on asking to wait of the maintainer to > respond. All four already passed the maintainer timeout. And the maintainer > (@tenomoto) has

Re: CI pipilene has a "sudo" problem

On Nov 11, 2019, at 15:07, Helmut K. C. Tessarek wrote: > Subject says it all. > > Travis fails with: The command "sudo ./runner" exited with 1. https://trac.macports.org/ticket/59666

Re: CI pipilene has a "sudo" problem

On Nov 12, 2019, at 21:38, Renee Otten wrote: > I think having a working Travis CI and/or Azure pipelines is important. Of course. > As a temporary workaround for the current issues [1], I suggest to commit the > change in PR 5767 [2]. I intend to merge that PR tomorrow morning (i.e., in >

Re: [MacPorts] #59699: ksh93: Update to latest version

On Nov 16, 2019, at 11:10, joerg van den hoff wrote: > On 16.11.19 13:14, MacPorts wrote: >> #59699: ksh93: Update to latest version >> -+ >> Reporter: jghub | Owner: ryandesign >> Type: update | Status: closed >> Priority:

Adding py38 subports? Mind the dependencies

There have been a lot of commits adding py38 subports to python module ports, when those ports' dependencies don't yet have py38 subports. Of course, this will fail to build. If you're going to add a python version to a port, please make sure its dependencies exist. This is a more specific cas

Re: File Doesn't Appear in Release tarball, but is in GitHub master

On Nov 17, 2019, at 14:37, Steven Smith wrote: > I have a weird error with the recently merged macos-fortress port. > > sudo port selfupdate > sudo port install macos-fortress > > throws an error because the file ${filespath}/hosts.orig doesn’t exist. > > I see this file on GitHub: > https:

Developer mode

I wonder if we should add a "developer mode" to MacPorts -- something that developers could enable in macports.conf. I feel that currently we print some information that is meant for developers and is not helpful to regular users -- such as the "reinplace didn't change anything" or "all compile

Re: Developer mode

> On Nov 18, 2019, at 14:32, Ralph Seichter wrote: > * Ryan Schmidt: > >> I wonder if we should add a "developer mode" to MacPorts -- something >> that developers could enable in macports.conf. > > I for one would like to be able to peek into what is ha

Re: Xcode Portgroup for XCWorkspace

On Nov 28, 2019, at 13:47, Mark Anderson wrote: ' > Does the Xcode portgroup have anyway to build an Xcode project that uses a > workspace? These are pretty common if you're using cocoapods. I don't see it, > but I want to check that I'm not totally missing something before I try and > add it

Re: Developer mode

On Nov 19, 2019, at 18:21, Ralph Seichter wrote: > * Ryan Schmidt: > >> We might also add a way for a developer to indicate for which ports >> developer mode should be turned on. A developer might wish, for >> example, to be notified of issues relating to the ports

Re: py38-pytorch fails to build in buildbot

On Dec 1, 2019, at 06:23, Steven Smith wrote: > I’m working on porting AllenNLP models in > https://github.com/macports/macports-ports/pull/5862 . > > The build bot fails building py38-pytorch, which I haven’t modified within > this PR. I have verified that the Python version 3.7 build of th

Initial builds on 10.15 buildbot worker

Hi Josh, I noticed you forced some builds on the 10.15 builder. Note that I have a list of all ports that I have been working my way through in a somewhat random order ever since I set the builder up, building a couple hundred or so ports at a time, whenever the builder is not busy. I currently

Re: Initial builds on 10.15 buildbot worker

On Dec 9, 2019, at 09:27, Joshua Root wrote: > On 2019-12-9 16:23 , Ryan Schmidt wrote: >> Hi Josh, >> >> I noticed you forced some builds on the 10.15 builder. Note that I have a >> list of all ports that I have been working my way through in a somewhat >>

Re: AWS SAM CLI - Looking for help

On Dec 17, 2019, at 13:38, Jackson Isaac wrote: > You would need to create py-ports for any > missing dependency packages e.g., tomlkit. Note that pypi2port (which can be installed using MacPorts) can help you generate those portfiles.

Re: How to Git Clone Subrepo for Build (opencv-python)

On Dec 10, 2019, at 15:35, Steven Smith wrote: > The opencv-python package needs to clone a subrepo of opencv4 as part of the > build. See: > > https://pypi.org/project/opencv-python/ > https://github.com/skvark/opencv-python > > How should this be done within a Portfile? Effectively, `git c

<    7   8   9   10   11   12   13   14   15   16   >