FreeBSD ports you maintain which are out of date

2025-01-11 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your 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. If any ports have already been updated, you

[Bug 283950] devel/qt6-base: segfaults after update to 6.8.1

2025-01-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283950 Jesper Schmitz Mouridsen changed: What|Removed |Added CC||j...@freebsd.org --- Co

[Bug 283997] devel/qt6-5compat fails during configure step on 14.2-RELEASE

2025-01-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283997 --- Comment #2 from George Mitchell --- Correction: I did get qt6-base, qt6-languageserver, qt6-svg, qt6-shadertools, and qt6-declarative to compile last night. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 283997] devel/qt6-5compat fails during configure step on 14.2-RELEASE

2025-01-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283997 --- Comment #1 from George Mitchell --- Same failure happens in the configure step on other qt6 components as well. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 283997] devel/qt6-5compat fails during configure step on 14.2-RELEASE

2025-01-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283997 Bug ID: 283997 Summary: devel/qt6-5compat fails during configure step on 14.2-RELEASE Product: Ports & Packages Version: Latest Hardware: Any OS: Any

maintainer-feedback requested: [Bug 283997] devel/qt6-5compat fails during configure step on 14.2-RELEASE

2025-01-11 Thread bugzilla-noreply
Bugzilla Automation has asked freebsd-kde (group) for maintainer-feedback: Bug 283997: devel/qt6-5compat fails during configure step on 14.2-RELEASE https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283997 --- Description --- This happened both on versions 6.7.3 and 6.8.1. I upgraded my base