Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76054 - [quazip-qt5] contains the Qt6 libraries
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Thursday, 29 September 2022, 06:55 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 29 September 2022, 07:25 GMT
Opened by Andreas Baumann (andreas_baumann) - Thursday, 29 September 2022, 06:55 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 29 September 2022, 07:25 GMT
|
DetailsDescription:
This is the original reported bug: https://bugs.archlinux32.org/index.php?do=details&task_id=273 The build log shows "using Qt version 6" for build5 and build6. I fear, as soon as both qt6-base and qt5-base are installed, Qt6 always wins. I didn't see a way to overwrite and force a specific Qt version. Maybe a way out (besides having two packages for each Qt version) is to have patches CMakeLists.txt, one for Qt5 and one for Qt6? Copying them in place before cmake-ing and the remove the build folder (or at least CMakeList.txt and CMakeCache). Additional info: * package version(s): 1.3-1 Steps to reproduce: asp update asp export extra/quazip cd quazip staging-x86_64-build tar tvf quazip-qt5-1.3-1-x86_64.pkg.tar.zst | grep -v Qt6 | grep -v qt6 # => shows no Qt5 files, but Qt6 files (/usr/include/QuaZip-Qt6-1.3, /usr/lib/libquazip1-qt6.so*) tar tvf quazip-qt6-1.3-1-x86_64.pkg.tar.zst | grep -v Qt5 | grep -v qt5 # -> shows Qt6 files |
This task depends upon
Closed by Antonio Rojas (arojas)
Thursday, 29 September 2022, 07:25 GMT
Reason for closing: Not a bug
Thursday, 29 September 2022, 07:25 GMT
Reason for closing: Not a bug
But the next one will most likely not be. :-)