| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This may possibly not get released until (after) Qt6.8.1, and
would rather not mask 6.8.1 as well. So add this now (masked)
for testing, will unmask alongside adding 6.8.1 if still no
proper release.
Note have not tested with Qt6.8.0, but rather with 6.8.1 branch
using 6.8.9999. Odds are will not unmask Qt6.8.0 anyway.
This is supposed to need (unreleased) >=pyqt-builder-1.17 and
>=sip-6.9 per project.toml but still "seems" fine with the old
versions at the moment. May "possibly" need newer PyQt6-sip as
well at runtime, but (at least) qutebrowser tests been passing
without it. So avoiding bumping to a bunch of extra snapshots.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Nothing need this at the moment, but the can add given
the package exists.
Not planning to add more keywords at the moment unless
something needs it, so masking on non-amd64 rather than
rekeyword.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Matoro Mahri <matoro_gentoo@matoro.tk>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attempted to patch it like usually do, but this time around some
methods were replaced by alternatives that I'm not sure sip even
supports and have no idea how to patch it properly (esp. since
hardly know sip and C++ as-is). Issues are in coreand USE=testlib,
the rest appears fine.
Not much can do other than wait for PyQt6-6.8.0 to release
(similarly to what pyside6 does) unless someone else can provide
a working patch. If there is a PyQt6 pre-release snapshot will
likely use it once available, but these haven't been happening
*before* Qt releases lately.
Technically no need for a revbump thanks to the binding operator,
but, if we do not do it, portage backtracks a lot more and gives
confusing messages when the whole Qt stack is involved. So want
to propagate the upper bound on user's systems now *long* before
the bump (may be wasted if we get a snapshot in time, but that
seems unlikely). Will spare stable users given we can just stabilize
6.7.1-r1 to cause a rebuild and odds are we will not stable 6.8.0
either way (may wait for 6.8.1 + PyQt6-6.8.x).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
No test suite, so tried some revdeps like usual and *seems* fine
(not that all components were tested at runtime, so who knows).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Does not actually need USE=qml to be set on neither qtspeech
nor PyQt6, just qtdeclarative itself.
project.py: qmake_QT=['texttospeech', '-gui', 'qmlintegration'],
Not worth a revbump due to slow rebuilds (rebuilds are triggered
every Qt bumps either way).
Closes: https://bugs.gentoo.org/930756
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
| |
Despite a major'ish bump, couldn't spot any need
for ebuild changes except depending on newer sip.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Was looking for a better workaround for this, but then realized
that it did not fail for the reason I thought it did.
Perhaps could be improved in PyQt-builder.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/907080
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
|
|
|
|
|
|
|
| |
Flag was added in qtwebengine-6.5.3 and this PyQt6 version checks
for >=6.6.0, so it does not matter anymore.
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: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not sure where these are coming from (does not use _p headers?),
but while testing Qt6.6.1 with PyQt6 built against 6.6.0:
QtCore.abi3.so: undefined symbol: <snip>, version Qt_6_PRIVATE_API
(and from a quick grep, only uses these from qtbase).
So let's just keep it even if rebuilds may not always be necessary,
esp. if it's going to happen on minor versions too.
Sparing revbump for PyQt6-6.5.3 to avoid long mostly unnecessary
rebuilds in stable given PyQt6-6.6.0 will be stabled together with
qtbase-6.6.1 either way.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
42b4c9f60670 did not fix v6.5.3.
Skipping revbump due to long rebuilds, and technically it shouldn't
matter given (as far as I can tell) it'll pass loading this bit at
runtime without USE=opengl being set on PyQt6 (which would ensure
it is set on qtdeclarative through qtbase/qtdeclarative[opengl=]).
Note that this does not affect PyQt5 despite also using the header
given qtdeclarative:5 always installs this that I can see.
Bug: https://bugs.gentoo.org/916889
Signed-off-by: Lucio Sauer <watermanpaint@posteo.net>
Closes: https://github.com/gentoo/gentoo/pull/33678
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skipping revbump due to long rebuilds, and technically it shouldn't
matter given (as far as I can tell) it'll pass loading this bit at
runtime without USE=opengl being set on PyQt6 (which would ensure
it is set on qtdeclarative through qtbase/qtdeclarative[opengl=]).
Note that this does not affect PyQt5 despite also using the header
given qtdeclarative:5 always installs this that I can see.
Closes: https://bugs.gentoo.org/916889
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/915945
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upon closer look the fix is subpar as did not formerly notice the
removed bit had a replacement looking only at the header (without
the commit). Not that this is an issue with what it's used with at
the moment (afaik only qutebrowser really uses PyQt6's sql) so will
stick with it until next release.
Kind of wonder how Arch got it to build without patches given there
is a "Qt 6.6 rebuild" PyQt6 commit, maybe it actually used 6.5 given
6.6 is still in experimental (not that this would be an issue given
it works at runtime with 6.6 then).
Retried with final version (formerly 6.6.0-rc) without patch, and it
still fails.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
| |
Both fail to build. No revbump needed given it should be usable
with 6.6 if it was built against an older version like 6.5.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Believe symbol issues had in the past were more of a fluke than
the norm, not to mention this does not actually use _p.h headers.
Takes a while to rebuild and forcing a rebuild on every Qt bump
may not be worthwhile (back when added this, Qt used 0/a.b rather
than 0/a.b.c so it was not that bad). May revert if get issues again.
(would still cause one more rebuild but -r1 happened in an earlier
commit either way)
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
qtbase[widgets] forces it on qtdeclarative either way, but could
"potentially" lead portage to believe it can schedule enabling
widgets on qtdeclarative after PyQt6.
No revbump needed for this edge case.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QtPdf is enabled in qtwebengine-6.5.3+.
Not using IUSE=pdf given qtwebengine tend to need special treatment,
and this makes it easier to mask the USE globally on arches where it
is not supported. Furthermore IUSE=pdf is default on some profiles and
would pull the heavy qtwebengine for users that may not want it.
Revbumping at same time as 6.5.3 given binding operator will cause
a rebuild either way.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nothing that needs this in PyQt6 currently, but there is no harm
in adding off-by-default support now that these are packaged.
Only ones still missing are:
- QtLocation: still disabled in project.py, so waiting on upstream
- QtPdf: needs enabling & testing in qtwebengine first
- QtRemoteObjects: thought to package this but failing to find anything
that is going to need it currently, will wait until someone requests
(remoteobjects sound interesting but seemingly scarcely used)
- QtAxContainer: this is for Windows (ActiveX), so nothing to do here
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
| |
Which I am part of, so nothing changes beside
being consistent with other PyQt* packages.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|