cad/opencascade build failure

2024-04-15 Thread Andrea Venturoli
Hello. Since switching to 2024Q2 I am no longer able to build this in poudriere (for 13.2). Log follows. Any hint? bye & Thanks av. % cat 132amd64-default.log =>> Building cad/opencascade build started at Mon Apr 15 21:01:30 CEST 2024 port directory: /usr/ports/cad/opencascade packa

Re: Package a second port (gitlab-ee instead of gitlab-ce)

2024-04-15 Thread Matthias Fechner
Am 15.04.2024 um 14:13 schrieb Dag-Erling Smørgrav: You can use “www/gitlab@all” to build all flavors of www/gitlab. even short, thanks a lot! Does maybe anyone know where all the flavor features are documented. Was not able to find a man page for, maybe there is something else to learn about

Unmaintained FreeBSD ports which are out of date

2024-04-15 Thread portscout
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this po

Re: holding rust at a particular version

2024-04-15 Thread Jamie Landeg-Jones
void wrote: > On Mon, Apr 15, 2024 at 12:00:39PM -0500, Matthew D. Fuller wrote: > >On Mon, Apr 15, 2024 at 02:33:33PM +0100 I heard the voice of > >void, and lo! it spake thus: > >> Is it possible, either within poudriere or using traditional ports, > >> to not have ports building fetching lates

New port for ActivityPub server snac

2024-04-15 Thread Matthew Phillips
Hello, I've created a new port for the ActivityPub server snac. snac is an interesting project because it implementations an ActivityPub server in a minimalist way; written in portable C and uses the filesystem for data storage. Here's the homepage to learn more: https://codeberg.org/grunfink/snac

Re: holding rust at a particular version

2024-04-15 Thread Piotr Smyrak
On Mon, 15 Apr 2024 14:33:33 +0100 void wrote: > Is it possible, either within poudriere or using traditional ports, > to not have ports building fetching latest rust? > > rust 1.76 is already installed. 1.77 is in the ports tree. > 1.76 is the latest for -current on arm64 on the pkg builders. >

Re: holding rust at a particular version

2024-04-15 Thread void
On Mon, Apr 15, 2024 at 12:00:39PM -0500, Matthew D. Fuller wrote: On Mon, Apr 15, 2024 at 02:33:33PM +0100 I heard the voice of void, and lo! it spake thus: Is it possible, either within poudriere or using traditional ports, to not have ports building fetching latest rust? rust 1.76 is already

Re: holding rust at a particular version

2024-04-15 Thread Chris
On 2024-04-15 09:58, Dimitry Andric wrote: On 15 Apr 2024, at 18:48, Chris wrote: On 2024-04-15 09:31, Moin Rahman wrote: On Apr 15, 2024, at 6:27 PM, Chris wrote: On 2024-04-15 06:33, void wrote: Is it possible, either within poudriere or using traditional ports, to not have ports building

Re: holding rust at a particular version

2024-04-15 Thread Matthew D. Fuller
On Mon, Apr 15, 2024 at 02:33:33PM +0100 I heard the voice of void, and lo! it spake thus: > Is it possible, either within poudriere or using traditional ports, > to not have ports building fetching latest rust? > > rust 1.76 is already installed. 1.77 is in the ports tree. > 1.76 is the latest fo

Re: holding rust at a particular version

2024-04-15 Thread void
On Mon, Apr 15, 2024 at 09:48:22AM -0700, Chris wrote: I'm sorry to hear this. For the sake of clarity; Is this just my ignorance for rust? I have no difficulty accomplishing this task with other targets -- perl, php, *SQL,... So long as the *chosen* version is still available within the ports

Re: holding rust at a particular version

2024-04-15 Thread Dimitry Andric
On 15 Apr 2024, at 18:48, Chris wrote: > > On 2024-04-15 09:31, Moin Rahman wrote: >>> On Apr 15, 2024, at 6:27 PM, Chris wrote: >>> On 2024-04-15 06:33, void wrote: Is it possible, either within poudriere or using traditional ports, to not have ports building fetching latest rust? >>>

Re: holding rust at a particular version

2024-04-15 Thread Chris
On 2024-04-15 09:31, Moin Rahman wrote: On Apr 15, 2024, at 6:27 PM, Chris wrote: On 2024-04-15 06:33, void wrote: Is it possible, either within poudriere or using traditional ports, to not have ports building fetching latest rust? rust 1.76 is already installed. 1.77 is in the ports tree. 1.7

Re: holding rust at a particular version

2024-04-15 Thread Moin Rahman
> On Apr 15, 2024, at 6:27 PM, Chris wrote: > > On 2024-04-15 06:33, void wrote: >> Is it possible, either within poudriere or using traditional ports, >> to not have ports building fetching latest rust? >> rust 1.76 is already installed. 1.77 is in the ports tree. >> 1.76 is the latest for -cu

Re: holding rust at a particular version

2024-04-15 Thread Chris
On 2024-04-15 06:33, void wrote: Is it possible, either within poudriere or using traditional ports, to not have ports building fetching latest rust? rust 1.76 is already installed. 1.77 is in the ports tree. 1.76 is the latest for -current on arm64 on the pkg builders. if I go into the ports t

holding rust at a particular version

2024-04-15 Thread void
Is it possible, either within poudriere or using traditional ports, to not have ports building fetching latest rust? rust 1.76 is already installed. 1.77 is in the ports tree. 1.76 is the latest for -current on arm64 on the pkg builders. if I go into the ports tree and build something needing ru

Re: Package a second port (gitlab-ee instead of gitlab-ce)

2024-04-15 Thread Dag-Erling Smørgrav
Matthias Fechner writes: > thanks, I fixed it now by adding just the following two lines into my > pkglist (as I do not build all ports on my local poudriere and I do > not want to interfere with my other builds): > > www/gitlab > www/gitlab@ee You can use “www/gitlab@all” to build all flavors of