https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283950

--- Comment #16 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=740d89cf91c1bd58fa7d9a826cdc1847fe667a99

commit 740d89cf91c1bd58fa7d9a826cdc1847fe667a99
Author:     Jason E. Hale <jh...@freebsd.org>
AuthorDate: 2025-02-02 07:50:09 +0000
Commit:     Jason E. Hale <jh...@freebsd.org>
CommitDate: 2025-02-02 08:32:19 +0000

    */*: Bump PORTREVISION for known Qt private API abusers

    Qt 6.8.2 edition.

    These ports directly use or link to a library that uses the Qt
    private API and must be rebuilt with every Qt update.

    Qt public API/ABI compatability is excellent, so most consumers don't
    need to necessarily be rebuilt between patch or even minor releases, but
    using the private API is highly discouraged since this is unstable even
    between patch releases and is really only meant for internal use.

    Adding devel/libqt6xdg and its consumers to the list this time around
    based on [1].

    PR:             283950 [1]

 archivers/lxqt-archiver/Makefile       | 1 +
 deskutils/lxqt-notificationd/Makefile  | 1 +
 devel/liblxqt/Makefile                 | 1 +
 devel/libqt6xdg/Makefile               | 1 +
 net-im/telegram-desktop/Makefile       | 2 +-
 security/lxqt-openssh-askpass/Makefile | 1 +
 security/lxqt-sudo/Makefile            | 1 +
 sysutils/lxqt-admin/Makefile           | 1 +
 sysutils/lxqt-config/Makefile          | 1 +
 sysutils/lxqt-policykit/Makefile       | 1 +
 sysutils/lxqt-powermanagement/Makefile | 1 +
 sysutils/lxqt-qt6plugin/Makefile       | 1 +
 x11-wm/lxqt-panel/Makefile             | 1 +
 x11-wm/lxqt-session/Makefile           | 1 +
 x11-wm/lxqt-wayland-session/Makefile   | 1 +
 x11/lxqt-about/Makefile                | 1 +
 x11/lxqt-globalkeys/Makefile           | 1 +
 x11/lxqt-runner/Makefile               | 1 +
 x11/screengrab/Makefile                | 1 +
 19 files changed, 19 insertions(+), 1 deletion(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to