Re: [MacPorts] #70187: qemu @9.0.0 aborts on Sierra

Probably need to `selfupdate`: `sudo port selfupdate`, then check for 9.0.1 On Tue, Jun 11, 2024 at 3:59 PM MacPorts wrote: > #70187: qemu @9.0.0 aborts on Sierra > +-- > Reporter: Randrianasulu | Owner: raimue > Type: defe

Re: There should be a requirement to check if a port exists before committing something right into the master

Is it a guarantee that the PortIndex is available to `port` everytime `port lint` is run? If so, would it be possible for us to use the port index to verify that one and only one port exists for the current port name? On Fri, May 31, 2024 at 8:35 AM Joshua Root wrote: > On 31/5/2024 21:22, Sergi

Re: Getting updated cargo.crates

You can check out `cargo2port` ( https://ports.macports.org/port/cargo2port/ ), and I have a similar utility here: https://github.com/herbygillot/cargo2ports On Thu, Nov 30, 2023 at 2:07 PM Austin Ziegler wrote: > I was opening a new PR to update a Rust dependency today and could not > figure ou

Re: More classes of maintainer

I think the challenge with base is that it's a Tcl codebase, which is a language most developers these days are less familiar with. Folks write Portfiles, yes, but they don't have to write proper Tcl too much as much of Portfile development is very declarative. I also understand the desire not to

Re: More classes of maintainer

I actually do think moving tickets and issues from Trac to GitHub Issues is a good idea, and would increase engagement for the project. On Thu, Nov 2, 2023, 10:19 Perry E. Metzger wrote: > > On 11/1/23 21:54, Joshua Root wrote: > > On 2/11/2023 12:32, Perry E. Metzger wrote: > >> As an aside, as

Re: Updating alpine

, 2023 at 3:47 AM contextnerror ​ wrote: > That fails even earlier, and on all of the files instead of just pine. > > > On Oct 4, 2023, at 10:22 PM, Herby G wrote: > > Attempt with `patch.pre_args -p0` > > On Wed, Oct 4, 2023 at 10:38 PM contextnerror ​ > wrote: >

Re: Updating alpine

Attempt with `patch.pre_args -p0` On Wed, Oct 4, 2023 at 10:38 PM contextnerror ​ wrote: > Thanks for that advice. > I tried to use the patch from > https://repo.or.cz/alpine.git/patch/701aebc00aff0585ce6c96653714e4ba94834c9c > This was with patch.pre_args -p1 applied as well. > It’s failing at

Re: [MacPorts] #66833: ipfs @0.18.1: Build failed - no files matched glob pattern

That is mostly because of the latest version's requirement on Go 1.20 which does not build on those older macOS versions. We might have to put an `if` statement that builds an older version of `ipfs` for those macOS versions. On Sat, May 20, 2023, 05:34 MacPorts wrote: > #66833: ipfs @0.18.1: Bu

Re: Pull Request # 17418 for totp-cli

Thanks Rob. Took a look and commented. On Wed, Feb 8, 2023 at 6:31 PM Robert Kennedy wrote: > Three weeks ago, I submitted a Pull Request for totp-cli. (see > https://github.com/macports/macports-ports/pull/17418). > But the PR has not been assigned to anyone for a review and merge. It is > a

Re: Buildbots down?

Got it, sorry to hear that :| Hoping that things get sorted out soon. On Thu, Feb 2, 2023 at 7:44 PM Ryan Schmidt wrote: > On Feb 2, 2023, at 18:25, Herby G wrote: > > > > There haven't been any builds for recent commits to master on Github in > over 24 hours at the

Buildbots down?

There haven't been any builds for recent commits to master on Github in over 24 hours at the moment of writing this. https://build.macports.org/ is also failing to load. Can someone take a look?

Re: The State of Rust in MacPorts Today

Thank you for the update, Marcus. I apologize for any harsh tone of mine in this conversation, and I hope that things are getting better on your end. I tested this PR on macOS 12.6.2 arm64 and it built successfully: $ rustc --version; cargo --version > rustc 1.66.0 (69f9c33d7 2022-12-12) (built f

Re: The State of Rust in MacPorts Today

Kevin Reid: > A suggestion: if this is done, the shim port would ideally work in the > same fashion as the "rustup" [1] Rust installation manager tool does. > A very solid idea. We need to focus on getting the rust-N ports into place to start. David Gilman: > The thing blocking me, and probably

The State of Rust in MacPorts Today

Hello all, Right now, Rust in MacPorts is severely out of date. It's about 5 versions behind the current release, which at the moment is at 1.65.0. In comparison, MacPorts Rust is currently at 1.61.0. As a core language underlying a lot of other ports, many of these ports cannot be updated to the

Re: go ports fetching dependencies at build time

The mechanism we use to vendor Go dependencies can be somewhat brittle and does not work very well in a number of instances. For some updates, new Go dependencies cause failures during extraction when attempting to capture them in go.vendors. Additionally, the key mechanism we currently use to ven

Re: latest git version no longer detected by base

As I mentioned in my original comment on the commit , the big change in Git 2.35.3 (and starting in 2.35.2) is a major behavior change to address CVE-2022-24765

Re: latest git version no longer detected by base ==> and it is a pain to use

I believe the *safe.directory *config option is what we'll want to configure to alleviate this: https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory On Sat, Apr 16, 2022 at 2:02 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > the new git is causing headach

Re: Location to store binaries

rap > compiler just be a port like everything else, and thus the binary hosting > is just the same as any other binary tarball macports distributes ? > > On 15 Apr 2022, at 11:16 pm, Herby G wrote: > >  > Since this would be adding a component that affects the build of a very > c

Re: Location to store binaries

Since this would be adding a component that affects the build of a very core build component to many MacPorts packages, perhaps a bit more care should be taken with where it will be stored. Maybe it makes sense for this new bootstrap compiler to live in a repository owned by the MacPorts Github or

Re: macOS 12 x86_64 buildbot weirdness

Update here: this turned out to have been an issue with Rust itself on macOS 12 x86_64: https://github.com/macports/macports-ports/pull/14523#issuecomment-1093011889 Fixed starting here: https://github.com/macports/macports-ports/pull/14532 On Fri, Apr 8, 2022 at 7:17 PM Ryan Schmidt wrote: > O

macOS 12 x86_64 buildbot weirdness

Hello, 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/logs/stdio 2. https://build.macports.org/builder

SecTrustEvaluateWithError on 10.12 and earlier?

The latest Go (1.17.6) isn't building on 10.12 and earlier due to missing SecTrustEvaluateWithError ( https://developer.apple.com/documentation/security/2980705-sectrustevaluatewitherror ) Here's the log from the 10.12 buildbot: https://build.macports.org/builders/ports-10.12_x86_64-builder/builds

Re: New project member: judaew

Welcome aboard, Judaew On Sun, Oct 10, 2021, 17:18 Haren S wrote: > Lots of great contributions to the project. Thanks for all your good work > :) > > - Haren > > 10 Oct 2021 17:49:28 Rainer Müller : > > > Please join us in welcoming the following new MacPorts project member: > > > > - Vadim-Val

BuildBot Certificate Invalid

Getting a DATE INVALID for the SSL certificate for build.macports.org

fluent-bit failing to build

fluent-bit is failing to build on pretty much everything except Big Sur and Catalina: https://ports.macports.org/port/fluent-bit/details/ /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_sysutils_fluent-bit/fluent-bit/work/fluent-bit-1.8.3/lib/mbedtls-2.26.0/library/cma

Re: Old Macports Site

The guide is here: https://guide.macports.org/ You'll get the same by clicking the *Documentation *tab on the current site. On Sun, Jun 6, 2021 at 2:31 PM Rainer Müller wrote: > Please use Reply All to keep the discussion on the mailing list. > > On 06/06/2021 19.59, Jonathan Moore wrote: > > w

Buildbots down?

https://build.macports.org/ is unreachable.

Re: Github CI Broken

iki/mark> > GitHub Profile <https://github.com/markemer> > > > > On Mon, Apr 12, 2021 at 2:18 PM Ryan Schmidt > wrote: > >> >> >> On Apr 12, 2021, at 11:53, Herby G wrote: >> >> > PR checks are failing across multiple pull requests

Github CI Broken

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 Forbidden

Re: [macports-ports] branch master updated: wuzz: run "go mod tidy" to fix broken build files

Hello Frank, Yes, you're right. Corrected in: https://github.com/macports/macports-ports/commit/09ea075bf9d9fefee0091ce22740446ea32d1b7b Thanks On Thu, Apr 1, 2021 at 7:41 PM Frank Schima wrote: > Hi Herby, > > On Apr 1, 2021, at 5:15 PM, Herby Gillot wrote: > > Herby Gillot (herbygillot) p

ARM64 Github CI

Any chance we can have macOS 11 ARM64 CI enabled for pull requests in the macports-ports repo? I'm aware it would create confusion as there are probably a lot of ports today that will fail outright on ARM64, so PRs that would pass the CI on all the x86_64 builders would get marked as failed due to

Re: New project member: harens

Congrats and welcome, Haren :) On Tue, Feb 23, 2021, 10:31 Rainer Müller wrote: > Please join us in welcoming the following new MacPorts project member: > > - Haren Samarasinghe (harens@, @harens) > > We look forward to continued excellent contributions from these new team > members. > > - Josh

Re: 99 bottles of beer on the wall...

Thank you for your vigilance on the PRs list, Ken. On Mon, Jan 25, 2021, 15:39 Ken Cunningham wrote: > the PR list is < 100 for the first time in a very very long time…. > > Keep ‘er going! > > K

Re: Github CI Issues

Yes, it does look like @jmroot's commit fixed the issue. CI started looking a lot healthier for previously failing PRs after rebasing them onto master after that commit. Thank you. On Wed, Jan 6, 2021 at 6:25 AM Ryan Schmidt wrote: > > > On Jan 5, 2021, at 20:43, Herby G wrote:

Github CI Issues

Hello all, For the last few days, CI runs in Github under both Github Actions & Azure Pipelines have been failing because port is rebuilding every dependency for a given port from scratch for some reason. This is causing CI builds to take hours to build a port that builds in a fraction of the tim

Re: Swift Package Manager

> Otherwise MacPorts could just run Artifactory or something to cache and serve dependencies and all would be good. Having MacPorts run asset servers or repositories for all the different languages and frameworks out there (like running Artifactory) would be immensely unsustainable. On Fri, Dec 1

macOS Instances Now Available On AWS

https://aws.amazon.com/blogs/aws/new-use-mac-instances-to-build-test-macos-ios-ipados-tvos-and-watchos-apps/ These aren't VMs as per the norm, but bare metal instances. Intel-based instances are available today, with Apple Silicon M1 coming in 2021. I imagine this will further increase the need f

Re: [MacPorts] #61267: Error in mysqld_safe from mysql8-server

r > > ps -ax | grep mysql > 39298 ttys0010:00.00 grep mysql > > Is the mysql8 server actually running?? > > Should there be a process found for mysqld? > > On 3 Oct2020, at 1:52 PM, Herby G wrote: > > Hello Murray, > > Instructions for setting up mysql8-se

Re: [MacPorts] #61267: Error in mysqld_safe from mysql8-server

Hello Murray, Instructions for setting up mysql8-server after installation with MacPorts are shown in the console right after installation. You can review these using 'port notes': $ port notes mysql8-server Then you would start the mysql8-server service using 'port load': $ sudo port load mys

Re: port "cask" -- installing prebuilt binaries

tegory than a list of blessed regexes for determining whether a port _might be_ binary only (as it's possible some other port may have "binary" in its name even though it may not be). On Thu, Aug 6, 2020 at 7:13 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > &

Re: port "cask" -- installing prebuilt binaries

ningham.web...@gmail.com> wrote: > > > On Aug 6, 2020, at 12:28 PM, Herby G wrote: > > > so far, name-suffix is winning on all fronts...with no downsides yet. > > I don't plan on pushing the issue, but I have to say that I don't agree. > > Using a name su

Re: port "cask" -- installing prebuilt binaries

> All that said, one more question. As I now understand it, the idea is to download a binary-only installer (from the publisher’s web site) and launch it. Someone still has to answer any and all dialogs that such installers always present. So, it fact, the administrator has to sit at the machine

Re: port "cask" -- installing prebuilt binaries

> so far, name-suffix is winning on all fronts...with no downsides yet. I don't plan on pushing the issue, but I have to say that I don't agree. Using a name suffix isn't clean, as you may include other non-binary ports that may happen to have the word "binary" in their name. A category allows y

Re: port "cask" -- installing prebuilt binaries

Adding my 2 cents to this as well (why not). I personally think a conservative approach makes sense here. We can keep the entirety of MacPorts structure exactly the way it is today, and add 3 things: - a "binary"/"binary_only" (or a new MacPorts specific name for these) as a *category*, ju

Request to close

Hello all, think we can close https://trac.macports.org/ticket/47279 Thank you.

Big Sur will be both 10.16 and 11.0

Not sure if this has been posted previously or elsewhere, but as the title says: https://eclecticlight.co/2020/07/21/big-sur-is-both-10-16-and-11-0-its-official/

Re: Cached distfile with the same name

Awesome, thank you Ryan. On Sat, Jun 27, 2020 at 1:30 PM Ryan Schmidt wrote: > > > On Jun 27, 2020, at 11:32, Herby G wrote: > > > I have a situation where a particular port is using a distfile of the > same name from version to version. > > > > So there&#x

Cached distfile with the same name

Hello all, I have a situation where a particular port is using a distfile of the same name from version to version. So there's currently an older version of the port's distfile cached in the MacPorts mirrors. Unfortunately, trying to update the port is failing since the distfile is first fetched