Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Nuno Teixeira
Hello Mark! Note: I do not know why, but aarch64 does not get MULTILIB to > also span armv7 (aarch32). So aarch64 might not have this > problem being visible as stands. I confirm that aarch64 doesn't have this problem. main-n275011-dbedcc169f70 poudriere-devel PKG_NO_VERSION_FOR_DEPS=yes `pkg

Re: Strange version inconsistency in Samba t* utils (e.g. talloc)

2025-02-01 Thread Tatsuki Makino
Hello. The following two lines exist in INDEX-*. tdb-1.4.9,1|/usr/ports/databases/tdb|/usr/local|Trivial Database|/usr/ports/dat... tdb-1.4.10,1|/usr/ports/databases/tdb1410|/usr/local|Trivial Database|/usr/port... I haven't checked which one takes precedence, but I guess it's bad that packa

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Guido Falsi
On 01/02/25 22:56, Baptiste Daroussin wrote: On Sat 01 Feb 22:40, Baptiste Daroussin wrote: On Fri 31 Jan 19:13, Baptiste Daroussin wrote: On Fri 31 Jan 18:18, Guido Falsi wrote: On 27/01/25 10:56, Nuno Teixeira wrote: Hello Rainer, > Wouldn't this be the right time to get Bapt@ involved?

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Guido Falsi
On 01/02/25 16:24, Mark Millard wrote: On Feb 1, 2025, at 03:04, Nuno Teixeira wrote: Hello Mark! Note: I do not know why, but aarch64 does not get MULTILIB to also span armv7 (aarch32). So aarch64 might not have this problem being visible as stands. I confirm that aarch64 doesn't have this

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Baptiste Daroussin
On Sat 01 Feb 22:40, Baptiste Daroussin wrote: > On Fri 31 Jan 19:13, Baptiste Daroussin wrote: > > On Fri 31 Jan 18:18, Guido Falsi wrote: > > > On 27/01/25 10:56, Nuno Teixeira wrote: > > > > Hello Rainer, > > > > > > > > > Wouldn't this be the right time to get Bapt@ involved? After all, he >

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Mark Millard
On Feb 1, 2025, at 03:04, Nuno Teixeira wrote: > Hello Mark! > > Note: I do not know why, but aarch64 does not get MULTILIB to > also span armv7 (aarch32). So aarch64 might not have this > problem being visible as stands. > > I confirm that aarch64 doesn't have this problem. This suggests the

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Mark Millard
On Feb 1, 2025, at 07:52, Guido Falsi wrote: > On 01/02/25 16:24, Mark Millard wrote: >> On Feb 1, 2025, at 03:04, Nuno Teixeira wrote: >>> Hello Mark! >>> >>> Note: I do not know why, but aarch64 does not get MULTILIB to >>> also span armv7 (aarch32). So aarch64 might not have this >>> problem

How can i prevent blueprint-compiler from generating pycache files thus causing build_fs_violation

2025-02-01 Thread Yusuf Yaman
Hello, I am trying to port a third-party Signal messaging app which has buil dependency on devel/blueprint-compiler and the port builds fine but i am getting build_fs_violation error in poudriere testport even though I have that PYTHONDONTWRITEBYTECODE=1 set in MAKE_ENV variable in Makefile. H

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Baptiste Daroussin
On Fri 31 Jan 19:13, Baptiste Daroussin wrote: > On Fri 31 Jan 18:18, Guido Falsi wrote: > > On 27/01/25 10:56, Nuno Teixeira wrote: > > > Hello Rainer, > > > > > > > Wouldn't this be the right time to get Bapt@ involved? After all, he > > > has > > > > worked intensively on the pkg updates. >

Unmaintained FreeBSD ports which are out of date

2025-02-01 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: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-02-01 Thread Mark Millard
Guido Falsi wrote on Date: Sat, 01 Feb 2025 22:36:12 UTC : > On 01/02/25 22:56, Baptiste Daroussin wrote: > > . . . >>> 32bits libs, they are actually needed. for reported ports, I think the >>> PKG_NO_VERSION_FOR_DEPS=yes does not work yet with newer pkg version. > > And I was wrong about the

Strange version inconsistency in Samba t* utils (e.g. talloc)

2025-02-01 Thread Kevin Oberman
For several days 'pkg version reports that all three of the ports are old: talloc-2.4.1 < needs updating (index has 2.4.2) tdb-1.4.9,1< needs updating (index has 1.4.10,1) tevent-0.15.0 < needs updating (index has 0.16.1) How