Re: Framing the MacPorts discussion

On May 19, 2021, at 10:01, David Gilman wrote: > but maybe the right mindset here is to do the best with what we've got. We do, and have, for over ten years.

Re: Becoming a legal entity and accepting donations

On May 17, 2021, at 06:13, Mojca Miklavec wrote: > On Mon, 17 May 2021 at 10:39, Ruben Di Battista wrote: >> >> Just as a side note, here in France I just created a non-profit association >> for a project I'm working on related to the organization of an event, and >> the process is almost free

Re: Buildbot hardware (was: Re: Framing the MacPorts discussion)

On May 19, 2021, at 12:38, Andrew Janke wrote: > I have a small stack of Mac Minis I got to use as a buildbot farm for > Octave.app; I might be able to have them pull double duty for MacPorts > depending on your change volume. On May 20, 2021, at 08:10, Enrico Maria Crisostomo wrote: > I've g

Re: Homebrew Disables OSXFuse ports

On May 17, 2021, at 21:00, Perry E. Metzger wrote: > On 5/17/21 19:06, Ryan Schmidt wrote >>>> Meh. They have different priorities than we do. No reason for us to follow >>>> what they do. >>> In this instance, though, I think their reasoning is correct. >

Re: Protobuf3-cpp update woes; strategy to avoid broken dependent ports?

On May 21, 2021, at 06:59, Christopher Nielsen wrote: > We need to figure out a better way to deal with updates to ‘protobuf3-cpp’, > as every time this port is updated, all dependent ports are broken. (Apart > from a handful that folks manually rev-bump along with it.) > > The problem is th

Re: Why is binary avoided for Xcode MPI wrappers?

On May 21, 2021, at 09:00, Eric Borisch wrote: > > On Thu, May 20, 2021 at 10:56 PM Ryan Schmidt wrote: > >> rev-upgrade only checks library linkage. If you're saying that this software >> links with a library inside Xcode, and that the install name of that l

Re: iTerm2 Question

On May 22, 2021, at 17:21, Jason Liu wrote: > If I'm not mistaken, to get a .app to show up in the /Applications/MacPorts > folder, you need to place the .app into ${destroot}$prefix/Applications at > some point during the destroot phase. If the build system does not install the app for you, yo

Re: bash and bashdb ports

On May 23, 2021, at 12:22, Giuseppe 'ferdy' Miceli wrote: > > On 21 May 2021, at 21:05, Rainer Müller wrote: >> On 21/05/2021 14.48, Giuseppe 'ferdy' Miceli wrote: >>> could someone be so kind to enlighten me about the bash port? >>> >>> if i am not mistaken the bash50 sub-port is obsolete and co

Re: MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

On May 24, 2021, at 10:13, Christopher Nielsen wrote: > Has there been any thoughts/interest in implementing another level (or two) > of debug output, providing more detail than we get at Debug? That would allow > us to optionally output more diagnostic info in various areas, such as our > port

Re: MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

On May 26, 2021, at 04:53, Georges Martin wrote: >> I personally find debug mode too verbose already and think we should reduce >> the amount of information produced by debug mode. > > I don’t know enough about Tcl logging but in Python you can have separate, > hierarchical loggers for each maj

Re: MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

On May 26, 2021, at 06:07, Christopher Nielsen wrote: > Great question! > > One of the key things this would allow us to do, is reduce our current Debug > output, by outputting less-important details at Debug2 or Debug3. For > example, if we don’t want to see some of the ui_debug messages fr

Re: MacPorts 2.7.1 - Availability for GitHub CI Jobs, as well as Buildbots?

On May 27, 2021, at 02:34, Joshua Root wrote: > On 2021-5-27 08:52 , Christopher Nielsen wrote: >> While I realize MacPorts 2.7.1 was just released, is there an ETA on when it >> will be available for both CI, as well as our buildbots? >> There’s certainly no rush. But the bug fix for issue 56793

Re: BigSur buildbot building software that will only run on 11.3+ ?

On May 31, 2021, at 10:19, Ken Cunningham wrote: > In this ticket > > https://trac.macports.org/ticket/63003 > > it has been suggested by a knowledgable contributor that this issue: > > xcrun: error: unable execute utility "/opt/local/libexec/llvm-11/bin/clang" > because it requires a newer ve

Re: MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

On May 26, 2021, at 08:38, Christopher Nielsen wrote: > I’m referring to debug output like the following, in this cases taken from > one of our builtbot logs. Some of these are generated by base, while others > are generated by the portgroups themselves. > > While I’m not necessarily advocat

Re: 2.7 features and CI

On Jun 7, 2021, at 19:34, Joshua Root wrote: > It's been well over the usual 2 weeks we normally wait before using features > introduced in a new release. But CI is stuck on 2.6.4 and will fail for ports > that use the new features. Of course we should really get CI updated to the > new vers

Re: Freenode IRC

On Jun 15, 2021, at 13:19, Joshua Root wrote: > Given Freenode's announcement that they are switching to new software and not > carrying over the existing services database with all the channel and nick > registrations, this is a good time to complete our exit. Please remove the > bridging to t

Re: Buildbots Down?

On Jun 22, 2021, at 08:57, Christopher Nielsen wrote: > Sorry, I meant the buildbot watchers and workers, not the jobs themselves. The commit that added the p5.32 ports causes ~1800 build requests to be created per worker. Buildbot isn't designed for there to be thousands of pending build reque

Re: live check fetch failures

Please write to list addresses at lists.macports.org, not the old addresses at the other hostname that were deprecated at the end of 2016. Some users' email server setups have such restrictive security settings that they are not able to read the emails if they are forwarded from the old address

Re: live check fetch failures

On Jun 19, 2021, at 05:12, Christopher Jones wrote: > Hi, > > I’ve been noticing recently a number of ports are failing to live check, with > errors like > >> port -d live libogg > DEBUG: Changing to port directory: > /Users/chris/Projects/MacPorts/ports/multimed

Re: list ports that depend on a given port

On Jun 4, 2021, at 16:29, Joshua Root wrote: > Probably this (remember that it's matching the text in each depends_* field > in the PortIndex): port echo depends:':boost(\s|$)' Yeah that's what I usually use.

Re: python PortGroup and destroot.pre_args

On Jun 29, 2021, at 15:35, René J.V. Bertin wrote: > Hi, > > There's a strange side effect of the Python PG on `destroot.pre_args` (and > maybe other, related variables). Accessing the variable after including the > PG leads to > > {{{ > DEBUG: Sourced PortGroup python 1.0 from > /path/to//_r

Re: python PortGroup and destroot.pre_args

On Jul 2, 2021, at 05:51, René J.V. Bertin wrote: > On Friday July 02 2021 04:31:50 Ryan Schmidt wrote: > >> If I create a dummy portfile that includes the python portgroup then then >> immediately tries to print destroot.pre_args, it shows why it failed: > > Y

Re: Azure pipeline failing due to parse error

On Jul 5, 2021, at 00:45, Manoj Karthick wrote: > > Hi! I was updating the antibody port, PR: > https://github.com/macports/macports-ports/pull/11516 and the Azure Pipeline > check seems to be failing during portindex due to an error parsing an > unrelated port. > > See: > https://dev.azure

Re: Determine dependencies of another port

On Jul 15, 2021, at 05:26, Haren Samarasinghe wrote: > I'm trying to write an NPM portgroup, part of which involves setting the > correct version of npm and the corresponding version of nodejs as a > port's dependencies. An npm portgroup is a good idea if we ever want npm-based software to (r

Re: How to install an old port from the binary archive?

On Jul 31, 2021, at 08:52, Jimmy Yuen Ho Wong wrote: > The latest gcc11 port has disabled the jit and thus broke emacs-devel. I am > trying to install an older version of gcc11 from the default binary archive. > I can see the tarball clearly still exists on > `https://packages.macports.org/libg

Re: Need help debugging failed build on build server

On Jul 31, 2021, at 10:38, Janosch Peters wrote: > Hi, > > I am trying to add a new port called MacPassHTTP to macports: > https://github.com/macports/macports-ports/pull/10162 > > On the build server I get the following error: > > Installing dependency (15 of 15) 'MacPass' with variants '' (r

Re: BuildBot Certificate Invalid

On Aug 9, 2021, at 07:37, Herby G wrote: > Getting a DATE INVALID for the SSL certificate for build.macports.org Sorry about that, I forgot to renew the certificates before I went out of town. I did renew the certificates shortly thereafter and re-sent the GitHub change notifications so everyth

Re: fluent-bit failing to build

On Aug 1, 2021, at 08:11, Herby G wrote: > > fluent-bit is failing to build on pretty much everything except Big Sur and > Catalina: https://ports.macports.org/port/fluent-bit/details/ You should file a bug report in Trac. :) I see you're one of the maintainers of the port but that's still the

Re: Haskell Stack Ports on Apple Silicon

On Aug 12, 2021, at 15:28, Ken Cunningham wrote: > It was reverted / replaced though. I was told that MacPorts did this > automatically now (MacPorts would fall back and install the Intel binary on > arm64) so it was not needed to do this any longer. As far as I could tell, this applies to indi

Re: Haskell Stack Ports on Apple Silicon

; supported_archs x86_64 >> >> https://github.com/macports/macports-ports/blob/4e94528cf34ba0ac86ee26d8f33b43351214/lang/stack/Portfile#L31 >> >> >>> On Aug 13, 2021, at 5:27 AM, Ryan Schmidt wrote: >>> >>> As far as I could tell, this applies to individual ports, but not to a >>> port's dependencies. See: >>> >>> https://trac.macports.org/ticket/63092 >> >

Re: Haskell Stack Ports on Apple Silicon

On Aug 13, 2021, at 10:58, Steven Smith wrote: > > If the Macports-compiled stack runs on arm64, then the prebuilt download will > too. > > The issue as far as I can tell from the internet is that stack will generate > x86_64 binaries, even if running on an M1. > https://www.haskell.org/ghc/bl

Re: New Port harfbuzz-devel/harfbuzz-devel-icu; Path-Style Dependency Now Needed

On Aug 30, 2021, at 17:27, Christopher Nielsen wrote: > Folks, > > As part of the overarching GIMP upgrade effort, we’re juggling updates to a > number of foundational ports. One of those is ‘harfbuzz’, which is still > pending via PR 11948 (https://github.com/macports/macports-ports/pull/11948

Re: kibana submission node version conflict issue

On Sep 2, 2021, at 05:12, Steven Smith wrote: > How can this node version conflict be resolved? The node ports should be fixed so that they do not conflict with one another.

Re: Portfile dependencies relying on specific variant

On Oct 5, 2021, at 05:36, Frank Dean wrote: > > I've submitted a pull request [1] for a new Portfile, `mod_tile`, but the > checks are failing because this port requires the `mapnik` port to be > installed with a non-default variant, `+postgis`. Similarly, it requires the > `osm2pgsql` port to ha

Re: get a compiler version?

On Oct 3, 2021, at 16:02, Sergey A. Osokin wrote: > On Mon, Oct 04, 2021 at 04:27:19AM +1100, Joshua Root wrote: >> On 2021-10-4 03:20 , Sergey A. Osokin wrote: >>> I've found that www/unit builds, primarily unit-perl* and unit-ruby >>> modules, fail when it runs with clang13. And that's because

Re: [NEW] www/unit

On Sep 29, 2021, at 04:50, Sergey A. Osokin wrote: > 2. added php module, commented out at the moment, PHP embed SAPI is > required to build Unit's PHP module, here's the I wasn't aware of the existence of the PHP embed SAPI, but now that I am, I should be able to add this to the php ports.

Re: Should CI/buildbot report rev-upgrade errors?

On Oct 11, 2021, at 14:01, Eric Gallager wrote: > On Mon, Sep 6, 2021 at 7:59 PM Aaron Madlon-Kay wrote: >> >> On Tue, Sep 7, 2021 at 4:42 AM Eric Gallager via macports-dev >> wrote: >>> >>> I agree that this behavior would be helpful, however, doing so would >>> require keeping the results

Re: Monterey install .pkg and website updates?

On Oct 25, 2021, at 13:19, Perry E. Metzger wrote: > macOS Monterey is officially out. I note that we don't yet have instructions > for installing MacPorts on it at https://www.macports.org/install.php and we > don't seem to have install .pkg files yet. > > I've never either built the .pkg for

Re: incr revision / portindex

On Oct 29, 2021, at 01:06, Joshua Root wrote: > On 2021-10-29 10:03 , Daniel J. Luke wrote: >> Hi macports-dev, >> Looks like the change in 10aaad9b10e7350e76676ebdb5acfc950b800273 caused >> behavior I didn't expect on my Monterey system. Since I'm using a git >> checkout for my portfiles on tha

Re: Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

On Oct 31, 2021, at 05:30, Nils Breunese wrote: > I’ve just reported this issue via Feedback Assistant. I’ve been using Macs > since 2004, but actually didn’t know about Feedback Assistent. Feedback Assistant is the recent rebranding of the old Apple bug reporter at https://bugreport.apple.c

Re: Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

On Oct 31, 2021, at 02:42, Nils Breunese wrote: > Apart from adding that link to the MacPorts warning message, would it be a > good idea to let that wiki page more explicitly state that this is caused by > a macOS bug and that we recommend reporting this issue to Apple via the > Feedback Ass

Re: Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

> On Oct 31, 2021, at 02:35, Nils Breunese wrote: > > I also remember MacPorts used to refer to the URL that explains how to fix > this. Could that link be added to the warning message again, so users will > know what to do? You're probably thinking of the message the the cltversion portgrou

Re: GitHub Sponsors

On Nov 10, 2021, at 12:11, Perry E. Metzger wrote: > Should we turn on the GitHub Sponsors functionality for the project on GitHub? > > It doesn't cost us anything to do it, and the money raised could be used to > do things like buying hardware for builds and such. MacPorts is not a legal or

Re: rmd160 deprecated with openssl 3

On Nov 9, 2021, at 13:28, Chris Jones wrote: > we should review our use of rmd160 in macports Yes. I filed https://trac.macports.org/ticket/63885 to cover this.

Re: [10.6.8] mysql57 5.7.36 fails to configure

Build failures should be reported by filing a bug report in the issue tracker.

Re: GitHub Sponsors

On Nov 10, 2021, at 14:01, Perry E. Metzger wrote: > On 11/10/21 14:59, Ryan Schmidt wrote: >> On Nov 10, 2021, at 12:11, Perry E. Metzger wrote: >> >>> Should we turn on the GitHub Sponsors functionality for the project on >>> GitHub? >>> >>

Re: GitHub Sponsors

On Nov 10, 2021, at 14:02, Ryan Schmidt wrote: > > On Nov 10, 2021, at 14:01, Perry E. Metzger wrote: > >> On 11/10/21 14:59, Ryan Schmidt wrote: >>> On Nov 10, 2021, at 12:11, Perry E. Metzger wrote: >>> >>>> Should we turn on the GitHub Sponsors

Re: Question regarding builders and require_active_variants

On Nov 16, 2021, at 10:48, Jason Liu wrote: > When using `require_active_variants` in a Portfile, are the builders smart > enough to then install dependencies using the required variants? No. The build will fail with the same message that a user would see. On Nov 17, 2021, at 10:23, Christophe

Re: Policy on `obsolete` ports...

On Nov 19, 2021, at 15:05, Perry E. Metzger wrote: > Howdy! As things stand, we don't explicitly say much in our rules about > whether people can remove obsolete ports after a year even without a port > maintainer's say-so. We also have circumstances where people leave > "maintainer" lines i

Re: Policy on `obsolete` ports...

On Nov 19, 2021, at 17:02, Dave Allured wrote: > Perry, you said "remove". I would like to have obsolete ports moved to an > inactive permanent reference archive, preferably somewhere in the ports code > base, rather than permanently removed. This would mainly be for possible > resurrection a

Re: build.macports.org currently down?

On Nov 26, 2021, at 09:50, Christopher Nielsen wrote: > It looks like ‘build.macports.org’ is current inaccessible. Is anyone else > seeing the same thing? Yes. There appears to have been a power outage which depleted the UPS battery and everything turned off. I am currently running disk first

Re: build.macports.org currently down?

On Nov 26, 2021, at 12:14, Ryan Schmidt wrote: > On Nov 26, 2021, at 09:50, Christopher Nielsen wrote: > >> It looks like ‘build.macports.org’ is current inaccessible. Is anyone else >> seeing the same thing? > > Yes. There appears to have been a power outage which

Re: build.macports.org currently down?

On Nov 30, 2021, at 10:43, Christopher Nielsen wrote: > >> The RAID is fine. Buildmaster and some workers are back up. I'll work on >> getting the remaining workers back online tonight (in a few hours). (Each >> has to be checked and cleaned up manually first.) > > > Ryan, do you think we’ll b

Re: 10.15 Xcode version: Buildbot, vs. GitHub CI

On Dec 1, 2021, at 09:18, Christopher Nielsen wrote: > > * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? > Or are there certain ports/situations that necessitate remaining with 11.7? Because there are a variety of scenarios where a build fails if the OS version and

Re: Question about `platforms` and `${os.platform}`

On Dec 10, 2021, at 15:07, Jason Liu wrote: > A conversation in one of my PRs has brought up an interesting question that > I've been wondering about for a long time. In Portfiles, whenever I've had a > test for `${os.major} <= xx`, I've typically always added an additional check > for darwi

Re: Question about `platforms` and `${os.platform}`

On Dec 11, 2021, at 16:41, Jason Liu wrote: > Then would it be easier (or even kosher) to simply wrap the majority of the > Portfile inside of a single > > if {${os.platform} eq "darwin"} { The shorthand way to do that is: platform darwin { > and be done with it, instead of needing to add on

Re: Question about `platforms` and `${os.platform}`

On Dec 11, 2021, at 18:42, Jason Liu wrote: > On Sat, Dec 11, 2021 at 5:46 PM Ryan Schmidt wrote: >> I wouldn't expect you to need to write more than a couple such conditionals >> in a portfile so I wouldn't expect it to be that inconvenient. > > Actually, I find

Re: fetch phase: sourceforge with 302 redirects?

On Dec 16, 2021, at 15:24, Jason Liu wrote: > Is there any way to get MacPorts to follow redirects during the fetch phase? MacPorts always does so already. But SourceForge has a bug in at least one of their mirror servers where redirects are not working correctly. Therefore, refer to the Avo

Re: Question about `platforms` and `${os.platform}`

On Dec 13, 2021, at 20:41, Christopher Chavez wrote: >> Before you mentioned the AppKit overhaul some time ago and started >> addressing it in your ports, I had never heard of it and I don't think >> anyone else's ports do anything about it. So either we have a lot of broken >> ports due to thi

Re: Acceptability of depends_build bin:…

On Dec 13, 2021, at 04:48, Christopher Chavez wrote: > I recently specified bin:node:… build dependency in qt5-qtwebengine. I would > not consider Node.js to be a lightweight dependency, so I thought it would be > preferable to allow using whichever is present, even a non-MacPorts one, > before

Re: security certificate

On Dec 22, 2021, at 08:40, Jerry wrote: > > Hi. I would like to ask a favor of someone who has access to a v10.7 and > v10.8 system. Could you please tell me if a security certificate[1] exists > on each system? It was created after v10.6 was released, but I am not sure > when it was added.

Change your ports' gettext dependencies!

Hi! If you maintain (or work on updating, or review a PR that updates) a port that depends on the gettext internationalization library (libintl.dylib): depends_lib-append port:gettext Please change it to: depends_build-append port:gettext depends_lib-append port:gettext-runtime This is necessa

Re: Change your ports' gettext dependencies!

On Dec 25, 2021, at 10:47, Ryan Schmidt wrote: > Hi! If you maintain (or work on updating, or review a PR that updates) a port > that depends on the gettext internationalization library (libintl.dylib): > > depends_lib-append port:gettext > > Please change it to: > &

Re: iTerm 2 Discussion

On Dec 29, 2021, at 10:24, Mark Anderson wrote: > From iTerm2 dev: "Running is supported on 10.14 but building is only ever > supported on the most recent released version of Xcode." > > This situation has caused me no end of trouble - I kinda wish I could have > the build bots build a version

Re: gcc11-devel and our buildbots

On Dec 30, 2021, at 17:41, Chris Jones wrote: > Hi > > Before arm came along the gccdevel ports indeed did not update that regularly. They did some years ago. Then for a time they didn't. > Normally in the run up to a new major release they might see more activity, > as we take a look as to if

Re: Detecting Apple Silicon (vs. legacy Intel)

On Dec 31, 2021, at 11:36, Chris Jones wrote: > > On 31 Dec 2021, at 5:13 pm, Vincent Habchi wrote: > >> finally put my hands on my brand new MacBook Pro 14”! (Well, not really >> mine, rather my company’s, but let’s pretend…) >> >> I was wondering if there is a simple scheme to detect on which

Re: perl 5.34 branch

On Jan 2, 2022, at 13:13, Vincent Habchi wrote: > On behalf of Christopher Chavez: > >> while trying to install ‘ffmpeg’ using perl5.34 as my base version, I >> stumbled on a slew of p5 ports which have not been updated to the 5.34 >> branch yet. >> >> I did that manually, and now I’m left

Re: license_noconflict ignored on builders?

On Jan 14, 2022, at 18:14, Jason Liu wrote: > Oh, was license_noconflict supposed to be used with the name of a port? I > thought it was supposed to specify a license that didn't conflict! See the documentation for license_noconflict at https://guide.macports.org/#reference.keywords

Re: 10.15 buildbot and nodejs17

On Jan 14, 2022, at 12:24, David Gilman wrote: > The buildbot for nodejs17 failed a few days ago: > > https://build.macports.org/builders/ports-10.15_x86_64-watcher/builds/24816 > > It looks like the other builders were OK with the job, so it isn't an > issue with the port. Digging into the log

Re: trace mode triggering issue in builds using CMake

On Jan 17, 2022, at 15:26, Christopher Chavez wrote: > Unless I should first wait for the cmake port maintainer to respond, I would > invite others especially those knowledgeable of trace mode internals to have > a look at https://trac.macports.org/ticket/64368 This is *very* interesting. I don

Re: [macports/macports-ports] abcde: switch to Perl 5.34 (PR #13720)

On Jan 20, 2022, at 23:04, Gabriel Rosenkoetter wrote: > > Probably belaboring the git history with this conversation further is > unnecessary. > > After some local frustrations (see also macports-user), I just ripped a CD > successfully with abcde reinstalled per Christopher's (minimal, of cou

Re: [macports/macports-ports] abcde: switch to Perl 5.34 (PR #13720)

On Jan 21, 2022, at 20:17, Gabriel Rosenkoetter wrote: > I was fishing for advice on what a "good enough" test here would be. > > Right now, I'm thinking dd(1) a few blocks constructed to look like a very > short audio CD into a file under [/var]/tmp, mount(8) that as a > pseudo-device, tell ab

Re: Acting on a subport in a development Portfile

On Jan 22, 2022, at 22:37, Georges Martin wrote: > Le 22 janv. 2022 à 21:31, Joshua Root a écrit : > >> sudo port build subport=thesubportname > > That's... awesome :-) Thanks, I didn't know that. For testing purposes, you can override most port variables that way.

Re: Adding to implicit function declaration whitelists [was: Re: How to suppress -Wimplicit-function-declaration warning, if really does not have the declaration?]

On Jan 28, 2022, at 23:15, Jim DeLaHunt wrote: > On 2022-01-26 02:59, Joshua Root wrote: > >> …In any case, we maintain lists of functions that are known not to exist on >> each macOS version, so the warning can be suppressed. They are in the ports >> tree here: >>

Re: "port upgrade" error message usability

On Jan 30, 2022, at 02:24, Andrew Janke wrote: > Hi, MacPorts developers, > > Long-time Homebrew user and recent MacPorts convert here. Welcome! I'm interested in your impressions of MacPorts as a Homebrew user and if you have any suggestions for changes we can make to make your MacPorts exper

Re: "port upgrade" error message usability

On Jan 30, 2022, at 03:30, Andrew Janke wrote: > On 1/30/22 4:04 AM, Ryan Schmidt wrote: >> On Jan 30, 2022, at 02:24, Andrew Janke wrote: >> >>> Hi, MacPorts developers, >>> >>> Long-time Homebrew user and recent MacPorts convert here. >> Welcome

Re: porturls (was: Re: "port upgrade" error message usability)

On Jan 30, 2022, at 09:15, Joshua Root wrote: > On 2022-1-30 21:12 , Ryan Schmidt wrote: >> I'm actually not sure what kind of file MacPorts is expecting to find at >> such a URL. I tried just a Portfile and a gzip-compressed tarball containing >> a Portfile an

Re: "port upgrade" error message usability

On Jan 30, 2022, at 23:16, Andrew Janke wrote: > On 1/30/22 10:16 AM, Julien Salort wrote: >> Le 30/01/2022 à 10:30, Andrew Janke a écrit : >> >>> I'm the primary maintainer for Octave.app (https://octave-app.org/), a >>> "native Mac app" distribution of GNU Octave >>> (https://www.gnu.org/so

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

It has been announced that /usr/bin/python will be removed in macOS 12.3, of which a beta is already out. If you have ports that use /usr/bin/python, please ensure that at minimum they are switched to use MacPorts python27 on macOS 12 and later. Better yet, see if you can switch them to use a M

Re: "port upgrade" error message usability

On Jan 31, 2022, at 13:18, Julien Salort wrote: > Le 31/01/2022 à 12:08, Ryan Schmidt a écrit : > >> The situation is: >> >> libgfortran.5.dylib was built with an install_name containing @rpath. (It >> was the choice of the developers of libgfortran (the devel

Re: Trace mode slow? Test this patch.

On Jan 30, 2022, at 12:25, Clemens Lang wrote: > > Hi developers, > > I recently noticed that trace mode was significantly slower on modern > macOS than it used to be, and found some time to investigate the root > cause. > > If you saw the same, please test the current master branch state with >

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

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

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

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

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

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

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

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

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

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

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

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

Re: OpenSSH 8.9p1 deprecated variants cleanup feedback request

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

Re: python2.7 pip install fails with SSLError

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

Re: python2.7 pip install fails with SSLError

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

Re: python2.7 pip install fails with SSLError

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

Re: python2.7 pip install fails with SSLError

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

Codesigning everything and combatting malicious code

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

Re: Codesigning everything and combatting malicious code

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

Re: revision control downloads

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

Re: revision control downloads

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

Re: macOS 12 x86_64 buildbot weirdness

On Apr 8, 2022, at 10:06, Herby Gwrote: > Something weird might be going on with the macOS 12 x86_64 buildbot > > Two builds of the same latest Rust fail with completely different errors: > > 1. > https://build.macports.org/builders/ports-12_x86_64-builder/builds/26275/steps/install-port/lo

Re: Location to store binaries

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

Re: Location to store binaries

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

go ports fetching dependencies at build time

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

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