Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/dev-qt/qtbase
Commit message (Collapse)AuthorAgeFilesLines
* dev-qt/*: sync keywords in live (qt6)Ionen Wolkens2024-01-303-3/+3
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: note the sandbox bug in childstack patchIonen Wolkens2024-01-271-0/+4
| | | | | | | | | | Not that need to be in a hurry to tentatively drop this (harmless), esp. given (unlike gtest) this affects building and not just tests and need to wait for most users to be updated after release+stable. Just so do not forget entirely. Bug: https://bugs.gentoo.org/923013 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: revbump to ensure rdrand is enabledIonen Wolkens2024-01-231-0/+0
| | | | | | | | | | Following previous commit. Apologies for the rebuilds, can't rely on --changed-use to do the right thing here. Bug: https://bugs.gentoo.org/922498 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Revert "dev-qt/qtbase: add IUSE=cpu_flags_x86_rdrand"Ionen Wolkens2024-01-234-40/+4
| | | | | | | | | | | | | Regardless of if that worked or not, on second thought this was a bad idea. The flag is rather misleading for generic binhosts because they should actually *enable* it to allow optional usage (runtime detection). And then, this is actually broken on top, so let's just return to the previous state. This reverts commit c198f69e66547b5ba7d2ba1b9bae576ce93ee703. Bug: https://bugs.gentoo.org/922498 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add IUSE=cpu_flags_x86_rdrandIonen Wolkens2024-01-194-4/+40
| | | | | | | | | | | | | | | | | | | Hopefully this is enough to (actually) fix bug #922498, doing -mno-rdrnd had a similar effect of passing QT_FEATURE_rdrnd=OFF (but don't have a cpu to test behavior with just -march=native). Maybe will extend this at some point, but let's treat this one as as a special case given not the first I've seen of this with rdrand. For anyone with rdrand issues, obviously do not enable this. Probably not worth a revbump considering issue is at build time, seems safe and could save a few rebuilds. fwiw also won't fail in case of an aberrant rdrand being set combined with -mno-rdrnd. Closes: https://bugs.gentoo.org/922498 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: shorten intrin test a bitIonen Wolkens2024-01-084-12/+0
| | | | | | | | | Felt more correct but do not actually need the header for these. Could alternatively use tc-cpp-is-true too, but fwiw current method allows batching in a single compiler call. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: drop vulnerable 6.6.1-r1Ionen Wolkens2024-01-081-361/+0
| | | | | | | All done for Qt6's qtbase end wrt bug #921292. Bug: https://bugs.gentoo.org/921292 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: stabilize 6.6.1-r3 for amd64Ionen Wolkens2024-01-081-1/+1
| | | | | Bug: https://bugs.gentoo.org/921292 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: skip tst_qtimer (randomly hangs)Ionen Wolkens2024-01-074-3/+11
| | | | | | | | Ran into this while testing the previous patch (which did not touch anything timer-related), and worked again after another rebuild. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: backport fix for QTBUG-116905Ionen Wolkens2024-01-072-0/+3
| | | | | | | | | | | | As recommended for use with Plasma 6 which is currently being tested: https://community.kde.org/Plasma/Plasma_6.0_Release_notes#Required_Qt_Version Tests changes were excluded due to not applying cleanly, but this does not prevent current tests from building and passing. Will be properly included in qtbase-6.6.2 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: backport CVE-2023-51714 HTTP2 fixIonen Wolkens2024-01-032-0/+417
| | | | | | | Still pending stable, which won't need to wait long. Bug: https://bugs.gentoo.org/921292 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: drop 6.5.3-r1Ionen Wolkens2023-12-194-399/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: extend testlib comment a bitIonen Wolkens2023-12-175-5/+10
| | | | | | | | | | | Just to clarify that this was an issue when not building tests too. Primary reason this been made default was because some other dev-qt packages (qtdeclarative I recall?) failed even with USE=-test and did not felt worth working around nor have a IUSE=+testlib (saves the need to declare it for tests on a whole lot of packages too). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: Stabilize 6.6.1-r1 amd64, #920154Arthur Zamarin2023-12-171-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* dev-qt/qtbase: add 6.7.9999Ionen Wolkens2023-12-121-0/+363
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: update liveIonen Wolkens2023-12-121-2/+3
| | | | | | | | | | | | | wayland is no longer optfeature-only and there is an actual flag now which is required to be set by live qtwayland. By default it auto-enables it if wayland libraries are found *but* does not seem to actually do anything with them. Could be overlooking something but do not believe there is any reason to depend on dev-libs/wayland right now if we control the option ourselves. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: drop 6.6.0-r1Ionen Wolkens2023-12-122-355/+0
| | | | | | Not a stable candidate (6.6.1 is), so dropping this one now. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: Keyword 6.6.1-r1 riscv, #914026Jakov Smolić2023-12-011-1/+1
| | | | Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>
* dev-qt/qtbase: skip a few known failing tests only for sparcIonen Wolkens2023-12-013-0/+18
| | | | | Closes: https://bugs.gentoo.org/914033 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: Keyword 6.6.1-r1 ppc64, #914026Sam James2023-12-011-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* dev-qt/qtbase: Keyword 6.6.1-r1 sparc, #914026Sam James2023-12-011-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* dev-qt/qtbase: skip tst_quuid for nowIonen Wolkens2023-11-303-3/+6
| | | | | | | | | | | | uint128 parts for this test are new, and is likely not worth holding back keywording over. Unlikely to result in real runtime problems. Needs confirmation, but believed that this would (now) fail on other 64bit BE arches as well and is not ppc64be-specific. Closes: https://bugs.gentoo.org/918878 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: Keyword 6.6.1-r1 ppc, #914026Sam James2023-11-291-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* dev-qt/qtbase: re-add forkfd stacksize patch but with 32kIonen Wolkens2023-11-294-0/+26
| | | | | | Bug: https://bugs.gentoo.org/918664 Bug: https://bugs.gentoo.org/915695 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add 6.6.1Ionen Wolkens2023-11-272-0/+353
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: drop 6.5.2-r2Ionen Wolkens2023-11-154-781/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: Stabilize 6.5.3-r1 amd64, #915549Arthur Zamarin2023-11-151-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* dev-qt/qtbase: Remove redundant local flag descsMichał Górny2023-10-271-1/+0
| | | | Signed-off-by: Michał Górny <mgorny@gentoo.org>
* dev-qt/qtbase: skip tst_qfiledialog{,2} regardless of muslIonen Wolkens2023-10-274-4/+8
| | | | | | | | | | | | | Seems the issue I had with musl were unrelated and just random, so let's just skip it globally (along with the first one). *Could* use -j1, but qtbase has the longest test suite out of Qt package and would rather keep the extra jobs unless the issues are more widespread (as usual the tests here are more to get a baseline for regressions than for full coverage either way). Closes: https://bugs.gentoo.org/916181 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: skip tst_qprinterIonen Wolkens2023-10-274-0/+4
| | | | | Closes: https://bugs.gentoo.org/916216 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add xkbcommon upper bound in stableIonen Wolkens2023-10-221-0/+1
| | | | | | | | | | Stabilization is dragging wrt bug #915549, so may as well add a bound in stable while waiting for fixed version. Depend-only w/o revbump given non-issue if it is already built. Closes: https://bugs.gentoo.org/915907 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: fix qsb and qmake with sandboxIonen Wolkens2023-10-213-0/+29
| | | | | | | | | | | | | | | | | | Also add to 6.5.3, while the issue has been less prominent in 6.5.x, there has been users that ran into issues with older versions, and is needed for stable users. See bug #915695 for details, the others are essentially duplicates which are hopefully fixed too (please report if still issues given I could never reproduce myself and cannot confirm). Closes: https://bugs.gentoo.org/908809 Closes: https://bugs.gentoo.org/908816 Closes: https://bugs.gentoo.org/913493 Closes: https://bugs.gentoo.org/915695 Thanks-to: vowstar Thanks-to: Mike Gilbert <floppym@gentoo.org> Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: clarify comment about qtprintsupport/cupsIonen Wolkens2023-10-175-5/+10
| | | | | | | | | Albeit information remains kind of buried in there, but in case someone happens to look at it when trying to figure out what to depend on for qtprintsupport -- aka not [cups] but rather need [gui,widgets]. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: remove xkbcommon patch in liveIonen Wolkens2023-10-102-2/+0
| | | | | | | Technically only in 6.9999 at the moment, but will be picked to 6.6.9999 soon. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: update 6.6+ live required useIonen Wolkens2023-10-102-2/+2
| | | | | | | xcb is no longer required to enable accessibility (upstream change did not make it in 6.6.0, will be in 6.6.1). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add 6.6.0Ionen Wolkens2023-10-102-0/+351
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: drop 6.6.0_rcIonen Wolkens2023-10-102-351/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: use a safer fix for xkbcommon-1.6.0Ionen Wolkens2023-10-091-1/+5
| | | | | | | Do not believe it matters either way given these should be unused, but shouldn't hurt to inline instead until upstream's own fix. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: fix build with >=libxkbcommon-1.6.0Ionen Wolkens2023-10-095-0/+18
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add 6.5.3Ionen Wolkens2023-09-282-0/+348
| | | | | Closes: https://bugs.gentoo.org/914460 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/*: drop 6.5.9999Ionen Wolkens2023-09-281-347/+0
| | | | | | | | Technically an LTS branch but 6.5.3 is due to be the last "public" release for this branch plus Plasma 6 is based on 6.6, so should have no use for this anymore. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: add 6.6.0_rcIonen Wolkens2023-09-262-0/+350
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: skip test newly failing with sandbox in 6.6+Ionen Wolkens2023-09-262-0/+4
| | | | | | | | | Passes fine if just run it on its own or disable all sandboxes. Exact cause unknown given gives no sandbox violations and does not seem to be ipc/pid-sandbox. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/*: sync live keywords (qt6)Ionen Wolkens2023-09-263-3/+3
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: skip flaky tst_qfontIonen Wolkens2023-09-264-4/+4
| | | | | | | | | Similar issues as tst_qrawfont, and that the system is not setup exactly like Qt's tests expect does not necessarily mean fonts will not be usable. Bug: https://bugs.gentoo.org/914737 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: use bit more correct libglvnd[X?] depIonen Wolkens2023-09-244-4/+16
| | | | | | | | | Enabling X+opengl+gles2-only but wanting X off on libglvnd is a bit of a stretch, but technically GLX is not used with gles2-only. Not worth a revbump. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: backport fix for libglvnd[-X]Ionen Wolkens2023-09-244-0/+32
| | | | | | | | | | | | | | Currently only exists in 6.9999 and will be in Qt6.7 unless upstream backports it to 6.6.x earlier. Originally thought that this already worked with the cmake migration, thus libglvnd[-X] not being only for gles2-only like in qtgui:5. Rather than change that dependency, just backport the cmake check to allow building. Trivial elseif() so this does nothing unless GLX is missing. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* dev-qt/qtbase: forward ~loongWANG Xuerui2023-09-253-3/+3
| | | | Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
* dev-qt/qtbase: keyword 6.5.2-r2 for ~loongWANG Xuerui2023-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Two test cases are failing on a Loongson 3A6000 box: 71 - tst_qprocess (Failed) 304 - tst_qnetworkinterface (Failed) With the following log messages: FAIL! : tst_QProcess::startStopStartStopBuffers(separate-separate) 'process.bytesToWrite() > 0' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)] FAIL! : tst_QProcess::startStopStartStopBuffers(separate-merged) 'process.bytesToWrite() > 0' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)] FAIL! : tst_QProcess::startStopStartStopBuffers(merged-separate) 'process.bytesToWrite() > 0' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)] FAIL! : tst_QProcess::startStopStartStopBuffers(merged-merged) 'process.bytesToWrite() > 0' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)] FAIL! : tst_QProcess::startStopStartStopBuffers(merged-forwarded) 'process.bytesToWrite() > 0' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)] FAIL! : tst_QNetworkInterface::localAddress(wg0-xxx.xxx.xxx.xxx) 'pmtu <= outgoingIface->maximumTransmissionUnit()' returned FALSE. () Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/network/kernel/qnetworkinterface/tst_qnetworkinterface.cpp(246)] But both are spurious to some extent. For the startStopStartStopBuffers case, a 128KiB write is made to hopefully retain some unwritten data even if the pipe is found writable, and the comment in the test code indicates that Linux is the "worst case" defaulting to 64KiB pipe buffers. This is actually PIPE_DEF_BUFFERS pages, according to include/linux/pipe_fs_i.h; popular arches use 4KiB pages, so 64KiB for them. Linux/LoongArch defaults to 16KiB pages, however, and the test case passes when the write size is quadrupled. And for the localAddress case, it may just be that the WireGuard interface behaves differently than physical ones, and indeed the other interfaces passed the test. So, the library should actually be fully functional on loong, hence the keyword. Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
* dev-qt/qtbase: Keyword 6.5.2-r2 hppa, #914026Sam James2023-09-221-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>