| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Haven't really tested this one yet other than checking that
patches applies, which does not need a new patchset yet given
still based on chromium-130 like 6.9 is.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
On second thought, will set this in the eclass. Affects at least one
more package (qtmultimedia), and unused or replaced CMakeLists.txt is
a common trend in Qt and this may be volatile. If something breaks
with cmake-4, would rather that it just breaks rather than do the =3.5
workaround and will fix it then.
This reverts commit 73194358936565f89dcd99b29d74627cdbb99b0e.
Bug: https://bugs.gentoo.org/957476
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Was tempting to just set it in the eclass, but only two
packages it looks like.
Closes: https://bugs.gentoo.org/957476
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-{4,5} -> 6.9-{6,7} changes:
Updated:
- cstdint.patch (several more added for gcc-16)
May possibly be more missing for USE=-jumbo-build but have
not tried that.
Closes: https://bugs.gentoo.org/957200
Thanks-to: tdr
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Not the only issue, but this one is known exploited in the wild
giving it higher priority (rest will likely wait until Qt 6.9.2
like usual).
Bug: https://bugs.gentoo.org/957076
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-4 -> 6.9-5 changes:
Updated:
- gn-bootstrap.patch (drop NINJAFLAGS chunk)
While fixing an issue to conditionally pass -v to ninja, Qt
interestingly added support for the same env var (NINJAFLAGS)
that we were adding.
Unsure if upstream's support works right though (not tested), it
uses simple string replacement rather than separate_arguments().
Could imagine potentially causing issues if NINJAFLAGS had double
spaces inherited from users setting NINJAOPTS.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Just to be in sync with other ebuilds and propagate to new users.
Skipping revbump is not "correct" but:
1. qtwebengine-6.9.1 is due soon (May 15 if not delayed), and won't
be masked unlike 6.9.0 (which already has :=)
2. assume new libxml2 won't be unmasked before then outside testing
3. for stable, 6.9.1 will likely be stabilized before new libxml2,
and then 6.8.2+6.8.3 will be removed from the tree.
For special cases, e.g. users unmasking for testing or using the
new libxml2 in stable, then can let preserved-rebuild do its thing
rather than make *everyone* do a very large rebuild for likely nothing.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Closes: https://bugs.gentoo.org/955345
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Closes: https://bugs.gentoo.org/925718
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
|
|
Adapted from linked PR given hasn't been updated yet and wanted
to rebuild qtwebengine with the new dependencies on my llvm-musl
chroot now.
[atomic-builtins] is not enough given passes -latomic either way,
and not planning to try to get this fixed in chromium.
Also move to DEPEND-only, doesn't seem to be linked with shared
libatomic for gcc (and stub is static-only).
Skipping revbump given not worth rebuilds just to be able to
depclean gcc and qtwebengine-6.9.1 is not that far off. Besides
it's difficult to depclean given nodejs depends on it for libatomic
at the moment still.
Closes: https://github.com/gentoo/gentoo/pull/41689
Thanks-to: Michal Rostecki <vadorovsky@disroot.org>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
On second thought, think would rather ensure that this is disabled
even if do not know how it happened in the first place, especially
given chromium itself relies on noexecstack rather than notes, but
then qtwebengine does not pass it for the final linking phase.
Believe this is only an issue for qtwebengine with its multitude
of asm files that may or may not be used, so not doing it in the
eclass.
Not revbumping given it seems to only happen in edge cases, but may
as well get this done before stable 6.8.3 so that if glibc-2.41 is
stabled later it'll ensure it's fine for them.
Closes: https://bugs.gentoo.org/953111
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Haven't reproduced the crash myself, but both falkon and
qutebrowser upstreams had reports about that issue with 6.9.0,
and may as well include it before potential unmasking.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-3 -> 6.9-4 changes:
Updated:
- musl-no-execinfo.patch
As usual only tend to test musl (+clang/libcxx) with .0 release
and there was one minor build failure due to a new execinfo-related
function not being guarded by #if/#endif.
Runtime also seems fine on llvm-musl, qutebrowser-9999 test pass
and can browse normally as well.
Still not including the other patches given they (hopefully)
shouldn't be that long lived.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Also including backport for QTBUG-135047 (x11 pixmap leak) which
is fixed in 6.9.9999 but hasn't been included in the 6.9.0 release.
Not bothering putting it in the patchset given would need to make
new one for 6.9.9999 already.
The glibc-2.41 patch is also still not included, but it should
whenever 6.9.9999 gets a qtwebengine-chromium submodule update.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Just so it's propagated when do bumps and reduce amount of revbumps
needed later (given qtwebengine is a huge package), it will be needed
whenever libxml2-2.14 is added & keyworded/unmasked with a new soname.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Same issue that chromium ran into wrt bug #951816
Bug: https://bugs.gentoo.org/951816
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Or probably clang-20 anyway, haven't confirmed that 19 works
for 6.8.3 (but definitely fine for 6.8.2, and the same bit of
code exists in it).
On that note, qtwebengine-6.8.2 is probably affected too, but
6.8.3 "should" be stabilized before clang-20 and it saves having
to test+change stable 6.8.2 for this.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Does not build without anymore due to some lacking guards
in tests, but it's not worth worrying with and may as well
require it (arguably this USE shouldn't even exist and be
hard enabled).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Seems to be lacking some guards against the other options,
but it doesn't really make sense for the ebuild to rely on
these and should just not pass when the main switch is off.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-2 -> 6.9-3 changes:
Updated:
- cstdint.patch (add a minor known missing include)
Likely still not final, but just a minor update before 6.9.0-rc.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Kind of forgot strip-flags no longer filters lto. Not that it was
*needed* given qt6-build.eclass filters lto either way but these
should be considered separate issues (aka, we may drop it from
qt6-build.eclass in the future but keep it in qtwebengine, or at
least when using gcc).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Merging with the other cstdint patch to re-use the description.
Believe 6.9 patchset is missing 1 bit of that patch that I forgot
about when rebasing it, but will update the patchset for 6.9.0-rc
later rather than make a separate patch here.
Closes: https://bugs.gentoo.org/950579
Thanks-to: Anthony G. Basile <blueness@gentoo.org>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
9GB is "enough" but rather borderline (last build 8.9GB), and
may be a problem depending on USE+*FLAGS. Let's put it a 1GB
over to safe.
Also actually links with udev in 6.9+ now.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
I'd assume may not be needed for that long, but just so
don't forget about this. Was testing 6.9.9999 and wondering
why tst_origins was failing (it was this).
At least means that the test suite does pick this up.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
6.9-1 -> 6.9-2 changes:
Removed:
* missing-prefinalizer.patch (upstreamed)
* no-vulkan-build.patch (upstreamed)
Plus rebasing where needed. This is due to Qt bumping baseline chromium
again in 6.9, it is now based on chromium-130.
This is still only preliminary updates just so patches applies and still
needs proper testing, will be checked using 6.9.0-rc when it releases.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
I see a change that is likely to prevent the race condition
issues, but not 100% sure.
cstdint.patch is upstreamed in >=6.9, still needed for 6.8.
6.9 newly needs nodejs[icu] or else it'll fail on some regex syntax
error (likely due to use of unicode bits in it). www-client/chromium
depends on nodejs[inspector] instead which itself depends on icu+ssl
(that we do need), but we do not seem to need inspector.
Also add [icu] to 6.8.9999 just-in-case, odds are won't be testing -icu
anymore and may miss something and no harm in having users set it for
6.8.3 before 6.9.0 drops
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Formerly left disabled given nothing in the tree needed it and it was
just an oddity, but some packages started to use it now (skanpage and
upcoming frescobaldi bump through pyqt6) and it is annoying to find
out that you need to rebuild qtwebengine to enable it.
It does add a bit to the compile time and size making it wasteful for
"most" users but it is ultimately kind of negligible in relation to
webengine itself.
Doing it live-only to spare a rebuild, will be for next bump.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
(actually) import from www-client/chromium this time, had missed
that the final used patch was different than the one on the bug.
No need for another revbump given it'd have just failed to build
if <2.41, and was fine if using 2.41.
Bug: https://bugs.gentoo.org/949654
Thanks-to: Sam James <sam@gentoo.org>
Fixes: 030898ec7dfd200a15c25027787ccb588627e031
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
qtwebengine appears affected as well, reproduced the crash on
imgur's main page by scrolling in qutebrowser. Haven't tested
the patch myself but it appears to works fine for qtwebengine
according to Chiitoo.
Bug: https://bugs.gentoo.org/949654
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
...which is default on hardened profiles, and unfortunately cannot
revbump only for hardened, so will cause unnecessary rebuilds.
Ideally would backport the proper fix, but have not tried to identify
what fixes this and, given workaround is temporary (should be fixed in
6.9), it may not be worth the trouble meanwhile.
On a side-note, was able to reproduce with qutebrowser by visiting some
specific websites.
Closes: https://bugs.gentoo.org/947356
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
|
|
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
