[maintainer update] remind 5.3.6 -> 5.3.7

2025-05-08 Thread Martin Ziemer
This patch updates remind from 5.3.6 to 5.3.7. Tested on amd64. Index: Makefile === RCS file: /cvs/ports/misc/remind/Makefile,v diff -u -p -r1.87 Makefile --- Makefile28 Apr 2025 15:40:15 - 1.87 +++ Makefile8 May 202

UPDATE: sysutils/firmware/amd and sysutils/firmware/amdgpu

2025-05-08 Thread Rafael Sadowski
Update amd firmware to 20250410. Tested with the following setup: amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x400 irq 7, 184 pins amdgpu0 at pci6 dev 0 function 0 "ATI Hawk Point" rev 0xd0 amdgpu0: IP DISCOVERY GC 11.0.1 12 CU rev 0x0c More testes welcome; OK? Rafael diff --git a/sysutils/fi

Update: PostgreSQL 17.5

2025-05-08 Thread Jeremy Evans
Update to the latest PostgreSQL version, released today. Release notes at: https://www.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1321-released-3072/ Fixes CVE-2025-4207: PostgreSQL GB18030 encoding validation can read one byte past end of allocation for text that fails validation

Re: Mirroring distfiles for installed ports/packages

2025-05-08 Thread Morgan Aldridge
On Wed, May 7, 2025 at 14:52 H. Hartzer wrote: > > Stuart Henderson wrote: > > pkg_info -Pa > > > > One way to do it is write the pkgpaths to a file and "cd /usr/ports; > > SUBDIRLIST=/tmp/pkgpaths make fetch" (that wouldn't pull in distfiles > > for dependencies though). > > Thank you! For some

[update] audio/portmidi 217 to 2.0.4

2025-05-08 Thread Raphael Graf
The diff below updates audio/portmidi to 2.0.4. (I have already submitted this update some time ago, see https://marc.info/?l=openbsd-ports&m=168824866808246) The project has moved to github and the version numbering scheme has changed. A list of changes is here: https://github.com/PortMidi/portmi

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Stuart Henderson
On 2025/05/08 18:31, Theo Buehler wrote: > > Extra: gfortran.8 pthread.27 python3.12.0 quadmath.3 > > These come from the python and fortran modules (and pthread may be > extra but it will come back with COMPILER_LIBCXX anyway). Harmless. > > > WANTLIB += ${COMPILER_LIBCXX} > > This should be a

Re: [fix] www/anubis v1.17.1p0

2025-05-08 Thread Stuart Henderson
On 2025/05/08 18:52, Christoph Liebender wrote: > Am 07.05.25 um 16:48 schrieb Stuart Henderson: > > > > On 2025/05/02 17:51, Christoph Liebender wrote: > > > Hi @ports, > > > > > > I recently submitted a patch to update www/anubis to v1.17.0 that also got > > > applied to 7.7-stable. Turns out t

Re: [fix] www/anubis v1.17.1p0

2025-05-08 Thread Christoph Liebender
Am 07.05.25 um 16:48 schrieb Stuart Henderson: On 2025/05/02 17:51, Christoph Liebender wrote: Hi @ports, I recently submitted a patch to update www/anubis to v1.17.0 that also got applied to 7.7-stable. Turns out that the build produces an executable that does not work correctly. Cause being

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Theo Buehler
On sparc64 I ran into a weird build error. ../numpy/_core/src/umath/string_buffer.h:40:45: error: macro "getchar" passed 2 arguments, but takes just 0 getchar(const unsigned char *buf, int *bytes); ^ ../numpy/_core/src/umath/string_buffer.h:40:1: erro

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Theo Buehler
> Extra: gfortran.8 pthread.27 python3.12.0 quadmath.3 These come from the python and fortran modules (and pthread may be extra but it will come back with COMPILER_LIBCXX anyway). Harmless. > WANTLIB += ${COMPILER_LIBCXX} This should be added. Previously we had COMPILER_LANGS=c but that broke s

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Johannes Thyssen Tishman
2025-05-08T04:32:09+0200 Theo Buehler : > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > numpy 1.x in the tree is a blocker for updating quite a few ports. > > > > The main blocker for the update used to be boost. But now that we have > > boost 1.87 I think it's a good time t

Re: UPDATE: x11/emwm & x11/emwm-utils 1.2 -> 1.3

2025-05-08 Thread Lucas Gabriel Vuotto
On Sun, May 04, 2025 at 07:11:37PM -0500, izzy Meyer wrote: > Hello, Stuart and Lucas pushed me to switch x11/emwm-utils to use > authenticate(3) instead of SUID root in [1]. > > Well, this diff attached does this. I could not figure out how to get > the shutdown and reboot stuff sorted. My user i

Re: devel/git: used one thread by default

2025-05-08 Thread Kirill A . Korinsky
On Thu, 08 May 2025 11:32:00 +0200, Klemens Nanni wrote: > > 08.05.2025 11:33, Kirill A. Korinsky пишет: > > rovert@ had noticed that git out of the box uses as many threads as the > > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > > example that ld.lld with -Wl,--thr

Re: devel/git: used one thread by default

2025-05-08 Thread Stuart Henderson
On 2025/05/08 11:57, Stefan Sperling wrote: > On Thu, May 08, 2025 at 09:32:00AM +, Klemens Nanni wrote: > > 08.05.2025 11:33, Kirill A. Korinsky пишет: > > > rovert@ had noticed that git out of the box uses as many threads as the > > > system has CUPs. claudio@ had pointed that it is quite bad

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Theo Buehler
On Thu, May 08, 2025 at 10:46:12AM +0100, Stuart Henderson wrote: > On 2025/05/08 19:20, Jonathan Gray wrote: > > On Thu, May 08, 2025 at 04:32:09AM +0200, Theo Buehler wrote: > > > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > > > numpy 1.x in the tree is a blocker for updati

Re: devel/git: used one thread by default

2025-05-08 Thread Stefan Sperling
On Thu, May 08, 2025 at 09:32:00AM +, Klemens Nanni wrote: > 08.05.2025 11:33, Kirill A. Korinsky пишет: > > rovert@ had noticed that git out of the box uses as many threads as the > > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > > example that ld.lld with -Wl,--

Re: devel/git: used one thread by default

2025-05-08 Thread Klemens Nanni
08.05.2025 12:57, Stefan Sperling пишет: > I prefer a config override to patched executables. > Config files are easier to figure out for users who become curious about > observed differences in behaviour. Exactly. > For years now we have been overriding configuration file defaults in the > devel

devel/git: used one thread by default

2025-05-08 Thread Kirill A . Korinsky
Klemens, Benoit, rovert@ had noticed that git out of the box uses as many threads as the system has CUPs. claudio@ had pointed that it is quite bad idea and use an example that ld.lld with -Wl,--threads=1 reduces the configure time by 15% and system time by 40%. So, here the diff which replaces 0

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Stuart Henderson
On 2025/05/08 10:09, Theo Buehler wrote: > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > The main blocker for the update used to be boost. But now that we have > > boost 1.87 I think it's a good time to update numpy to the 2.x series. The > > diff below gets us to 2.0.2. >

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Stuart Henderson
On 2025/05/08 19:20, Jonathan Gray wrote: > On Thu, May 08, 2025 at 04:32:09AM +0200, Theo Buehler wrote: > > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > > numpy 1.x in the tree is a blocker for updating quite a few ports. > > > > > > The main blocker for the update used to

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Jonathan Gray
On Thu, May 08, 2025 at 04:32:09AM +0200, Theo Buehler wrote: > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > numpy 1.x in the tree is a blocker for updating quite a few ports. > > > > The main blocker for the update used to be boost. But now that we have > > boost 1.87 I th

Re: devel/git: used one thread by default

2025-05-08 Thread Claudio Jeker
On Thu, May 08, 2025 at 09:32:00AM +, Klemens Nanni wrote: > 08.05.2025 11:33, Kirill A. Korinsky пишет: > > rovert@ had noticed that git out of the box uses as many threads as the > > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > > example that ld.lld with -Wl,--

Re: devel/git: used one thread by default

2025-05-08 Thread Stuart Henderson
On 2025/05/08 10:33, Kirill A. Korinsky wrote: > Klemens, Benoit, > > rovert@ had noticed that git out of the box uses as many threads as the > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > example that ld.lld with -Wl,--threads=1 reduces the configure time by 15% >

Re: devel/git: used one thread by default

2025-05-08 Thread Klemens Nanni
08.05.2025 11:33, Kirill A. Korinsky пишет: > rovert@ had noticed that git out of the box uses as many threads as the > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > example that ld.lld with -Wl,--threads=1 reduces the configure time by 15% > and system time by 40%. >

Re: rtorrent crashes

2025-05-08 Thread Klemens Nanni
08.05.2025 11:50, Anthony J. Bentley пишет: > The stack dump was disabled by kn's recent commit, but I doubt that > caused this crash. It's very annoying that rtorrent neither prints a > stack trace nor leaves a corefile behind though, can we fix that? I only disabled libexecinfo since it wasn't e

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Theo Buehler
On Thu, May 08, 2025 at 09:30:34AM +0100, Stuart Henderson wrote: > On 2025/05/08 10:09, Theo Buehler wrote: > > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > > > The main blocker for the update used to be boost. But now that we have > > > boost 1.87 I think it's a good time to

Re: devel/git: used one thread by default

2025-05-08 Thread Klemens Nanni
08.05.2025 11:33, Kirill A. Korinsky пишет: > Klemens, Benoit, > > rovert@ had noticed that git out of the box uses as many threads as the > system has CUPs. claudio@ had pointed that it is quite bad idea and use an > example that ld.lld with -Wl,--threads=1 reduces the configure time by 15% > and

Re: rtorrent crashes

2025-05-08 Thread Anthony J. Bentley
Jan Stary writes: > This is current/amd64 with > > libtorrent-0.14.0p0v0 BitTorrent library written in C++ > rtorrent-0.10.0p0v0 ncurses BitTorrent client based on libTorrent > > Upon starting rtorrent, I get the following error messages > > Caught internal_error: SocketFd::close() called on an inv

Re: [update] numpy 1.x -> numpy 2.x

2025-05-08 Thread Theo Buehler
On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote: > The main blocker for the update used to be boost. But now that we have > boost 1.87 I think it's a good time to update numpy to the 2.x series. The > diff below gets us to 2.0.2. Hits an ICE on aarch64: ../numpy/_core/src/umath/l

Re: reimport math/coq as math/rocq

2025-05-08 Thread Stuart Henderson
It needs a quirks $stem_extensions entry to cover the renaming, and compcert BDEP needs changing. -- Sent from a phone, apologies for poor formatting. On 8 May 2025 00:23:55 Daniel Dickman wrote: The coq project has been renamed to rocq. I'd like to reimport it as math/rocq before doing mor

Re: [Update] wayland/foot 1.22

2025-05-08 Thread yaydn
On Wednesday, May 7th, 2025 at 20:08, Volker Schlecht wrote: > I arrived at a slightly different diff (didn't look into why there's > differences) but foot 1.22.3 seems to work ... > I defer to your diff. It looks better in the patches/patch-meson_build section. Built and tested using your diff