[Bug 297617] textproc/fcitx5-qt: Upgrading from 2026Q2 to 2026Q3 leaves ABI-incompatible shlib

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

            Bug ID: 297617
           Summary: textproc/fcitx5-qt: Upgrading from 2026Q2 to 2026Q3
                    leaves ABI-incompatible shlib
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

I upgraded my system's binary packages from 2026Q2 to 2026Q3. As part of the
upgrade, Qt6 was upgraded to 6.11 from 6.10; fcitx5-qt6, on the other hand, was
not upgraded because both branches have version 5.1.12.

textproc/fcitx5-qt makes use of Qt private APIs and such ought to be rebuilt
whenever Qt's gets bumped:

CMake Warning at /usr/local/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake:339
(message):
  This project is using headers of the GuiPrivate module and will therefore
  be tied to this specific Qt module build version.  Running this project
  against other versions of the Qt modules may crash at any arbitrary point.
  This is not a bug, but a result of using Qt internals.  You have been
  warned!

  You can disable this warning by setting QT_NO_PRIVATE_MODULE_WARNING to ON.
Call Stack (most recent call first):
  /usr/local/lib/cmake/Qt6GuiPrivate/Qt6GuiPrivateConfig.cmake:48
(_qt_internal_show_private_module_warning)
  qt6/CMakeLists.txt:10 (find_package)

However, it is not listed on https://wiki.freebsd.org/KDE/Qt as such, so I
presume it got missed when Qt was upgraded. It should be added there, but I
don't have the an account for the wiki, so I can't do so myself.

The fcitx5-qt6 binary package built from 2026Q3 quarterly branch does not
exhibit these issues, as it was built against the new Qt version from the
get-go. However, since it did not receive a revision bump, pkg upgrade will not
install it.

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