qt6 the default qt on -current?

2023-08-09 Thread void
Hello list, How can I build making qt6 the default Qt? I'm using poudriere to build. I can see that for some ports there's a 'uses: qt6' that goes in the port. What I was looking for was a default string I can use with a poudriere make.conf like there is for python or perl. ty --

Re: Has the update procedure changed?

2023-08-09 Thread Miroslav Lachman
On 09/08/2023 08:22, Kevin Oberman wrote: I don't see how you get this from the man page. "Compares only files known to be                  essential to the success of {build|install}world, i.e.,                  /etc/group and /etc/master.passwd. If it is potentially updating files that MIGH

Re: Has the update procedure changed?

2023-08-09 Thread Matthias Apitz
El día miércoles, agosto 09, 2023 a las 12:40:31 +0200, Miroslav Lachman escribió: > On 09/08/2023 08:22, Kevin Oberman wrote: > > > I don't see how you get this from the man page. > > "Compares only files known to be > >                  essential to the success of {build|install}world, i.e.,

Re: Has the update procedure changed?

2023-08-09 Thread Tomoaki AOKI
On Tue, 8 Aug 2023 23:22:32 -0700 Kevin Oberman wrote: > On Mon, Aug 7, 2023 at 9:12 AM Matthias Apitz wrote: > > > El día lunes, agosto 07, 2023 a las 08:51:55a. m. -0700, Kevin Oberman > > escribió: > > > > > On Sun, Aug 6, 2023 at 9:51 AM Tim Kellers wrote: > > > > > > > > > > > > > > > On

Re: Bhyve NIC Passthru broken

2023-08-09 Thread Santiago Martinez
Hi there! I'm seeing the same, but at the end the machine end crashing. Seems that a complete power-off/on of the hardware clears it, until it random happen again when loading vmm and doing passthru. With 13.1p7 it was solid. I'm adding  Micheal as he probably know who is the right person to

Re: qt6 the default qt on -current?

2023-08-09 Thread Jan Beich
Please, use ports@ list next time. Every supported FreeBSD version uses the same ports/ tree. Not supported FreeBSD versions require a time machine i.e., rolling back the ports/ tree to a date before EOL. void writes: > How can I build making qt6 the default Qt? When everything in ports support

Re: 14.0 boot failure

2023-08-09 Thread Graham Perrin
On 09/08/2023 07:10, Kevin Oberman wrote: I closed the ticket. I wasn't aware of a ticket, thanks for the update. Yesterday's 09c20a293280 boots fine for me.

Re: qt6 the default qt on -current?

2023-08-09 Thread void
On Wed, Aug 09, 2023 at 04:47:36PM +0200, Jan Beich wrote: Please, use ports@ list next time. Every supported FreeBSD version uses the same ports/ tree. Not supported FreeBSD versions require a time machine i.e., rolling back the ports/ tree to a date before EOL. OK. I didn't think the query be

Re: Has the update procedure changed?

2023-08-09 Thread Tomoaki AOKI
On Wed, 9 Aug 2023 05:50:05 -0700 David Wolfskill wrote: > On Wed, Aug 09, 2023 at 09:38:22PM +0900, Tomoaki AOKI wrote: > > ... > > > > Please correct me if I'm missing something. > > I use source update for years and not using bsdinstall nor > > freebsd-update. > > > > Does bsdinstall (and/or

Re: ZFS deadlock in 14

2023-08-09 Thread Kevin Bowling
Possibly https://github.com/openzfs/zfs/commit/2cb992a99ccadb78d97049b40bd442eb4fdc549d On Tue, Aug 8, 2023 at 10:08 AM Dag-Erling Smørgrav wrote: > > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4 >

aarch64 (not armv7) kyua run on main [so: 14]: sys/net/if_lagg_test:status_stress got "Fatal data abort" panic

2023-08-09 Thread Mark Millard
The context is on a Windows Dev Kit 2023, using a bectl based boot/root disk: # uname -apKU FreeBSD CA78C-WDK23-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT aarch64 1400094 #9 main-n264643-0befc55cdf4b-dirty: Wed Aug 9 14:23:48 PDT 2023 root@CA78C-WDK23-ZFS:/usr/obj/BUILDs/main-CA78C-dbg-clang/usr

poudriere && --MAKE_ENV-- section

2023-08-09 Thread Matthias Apitz
If I look into the log of a job run in poudriere, from where the section --MAKE_ENV-- OPENSSLBASE=/usr/local OPENSSLDIR=/usr/local/openssl ... --MAKE_ENV-- is pulled in? It is not (my) definition from the jail's make.conf. I have the problem, that a given port (lang/python27) does not compile