Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/www-client/qutebrowser
Commit message (Collapse)AuthorAgeFilesLines
* www-client/qutebrowser: add 3.4.0Ionen Wolkens33 hours2-0/+172
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop obsolete pytest-bdd upper bound in liveIonen Wolkens10 days1-2/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Rename dev-python/{PyQt6 → pyqt6}Michał Górny2024-11-232-4/+4
| | | | Signed-off-by: Michał Górny <mgorny@gentoo.org>
* Rename dev-python/{PyQt6-WebEngine → pyqt6-webengine}Michał Górny2024-11-232-2/+2
| | | | Signed-off-by: Michał Górny <mgorny@gentoo.org>
* www-client/qutebrowser: add issue link for pytest-bdd upper boundIonen Wolkens2024-11-142-0/+2
| | | | | | | | fwiw there is a PR that may fix this, albeit no urgency given no other packages use pytest-bdd, so a upper bound is pretty harmless until upstream merge&release. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: depend on <pytest-bdd-8Ionen Wolkens2024-11-142-2/+2
| | | | | | | | pytest-bdd changed its parser, and syntax used here is completly broken with it, upstream keeps up with pytest-bdd changes so it should be fixed sooner or later. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: add missing pillow test depIonen Wolkens2024-11-132-0/+2
| | | | | | | Meant to add this alongside 3.13 compat when noticed it was missing, but overlooked change wasn't queue'd when pushed. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: enable py3.13Ionen Wolkens2024-11-132-4/+2
| | | | | | | | Looking upstream, the only issue left is with some specific tests that we're not running and the failure does not indicate a runtime problem (it's the test itself that has random issues). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: adjust tests for Qt6.8 in non-liveIonen Wolkens2024-11-131-0/+7
| | | | | | | | | | Should be non-issues. Technically the resource type one also fails in live, but upstream already knows that it needs to be updated and it will likely be fixed soon, leave it out so don't forget to drop it next bump. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Rename dev-python/{jinja → jinja2}Michał Górny2024-11-112-2/+2
| | | | Signed-off-by: Michał Górny <mgorny@gentoo.org>
* www-client/qutebrowser: drop 3.2.1Ionen Wolkens2024-11-042-172/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: Stabilize 3.3.1 ALLARCHES, #941960Joonas Niilola2024-10-231-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* www-client/qutebrowser: add 3.3.1Ionen Wolkens2024-10-122-0/+172
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: note link for py3.13 supportIonen Wolkens2024-09-032-0/+2
| | | | | | Next release has some fixes, albeit unsure if complete yet. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop 3.2.0Ionen Wolkens2024-09-032-171/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: Stabilize 3.2.1 ALLARCHES, #935554Arthur Zamarin2024-07-051-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/qutebrowser: drop 3.1.0-r1Ionen Wolkens2024-06-285-308/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: add 3.2.1Ionen Wolkens2024-06-252-0/+171
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: Stabilize 3.2.0 ALLARCHES, #934770Joonas Niilola2024-06-241-1/+1
| | | | Signed-off-by: Joonas Niilola <juippis@gentoo.org>
* www-client/qutebrowser: adjust tests skipping for Qt 6.7.2Ionen Wolkens2024-06-183-9/+15
| | | | | | | | | | | | | | version.py newly checks for chromium security version which fails given it does not know about 6.7.2's, and so just skip the whole suite given not very meaningful downstream. Also, Qt 6.7.2 introduced new warnings about failing to initialize vulkan and qutebrowser's tests fail if it sees unrecognized warnings. It might work if had mesa's lavapipe enabled in Xvfb but new warnings been a recurring issue and little sense in worrying further about these downstream. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: add 3.2.0Ionen Wolkens2024-06-032-0/+169
| | | | | | | | | | | | | Note that the Qt5 support had been dropped in the live ebuild a while ago, and this is the first keyworded ebuild with that change. Upstream still support Qt5 (albeit discouraged), but seeing little reason to keep supporting it here when we have working Qt6. Many sites are broken with old qtwebengine:5 and, even with backports, it is a security hazard. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: update liveIonen Wolkens2024-06-031-5/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: backport tests fix for PyQt6-6.7.0Ionen Wolkens2024-04-262-0/+74
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: limit pdfjs to <4.1 for nowIonen Wolkens2024-04-142-2/+5
| | | | | | | | | | Incompatible with the non-legacy sdist of 4.1.329 and will fail to load any pdf with type errors. Not that 4.1.329 is in-tree yet, just doing it before it breaks (revbumps are cheap for this package) and will revisit later. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: force-enable Qt6 in liveIonen Wolkens2024-03-271-55/+8
| | | | | | | | | | | | | | | | Still supported upstream, but qtwebengine:5 is slowly on its way out in Gentoo and offers a poor browsing experience with modern websites. Some may prefer Qt5 for better DE integration at the moment, but considering that these issues throne over that. Also drop the transition warning, we can rely on the warning that qutebrowser itself will do (formerly was missing, thus the ebuild warning was more useful). Plus given there is no USE to disable Qt6 anymore going back the other way is unlikely. Qutebrowser's default is Qt6 so we can also drop the overrides. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: show USE=-qt6 warning regardless of archIonen Wolkens2024-03-271-2/+1
| | | | | | qtwebengine:6 is keyworded on arm64 now, and x86 keywords were dropped. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: fix tests qith upcoming Qt6.6.3+6.7.0Ionen Wolkens2024-03-212-0/+16
| | | | | | | | | | Thought this was 6.7.0-only at first, but seems it was backported to 6.6.3 which should release very soon. Not touching live given upstream is likely to look more closely at 6.7.0 issues soon. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: warn about qtwebengine[bindist]Ionen Wolkens2024-02-092-0/+16
| | | | | | | | With the binhost gaining popularity, it may be good to warn about it. Not an issue for most packages, but losing e.g. h264 in a full web browser is not great and may leave users confused. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: fix casing typo in commentIonen Wolkens2024-01-092-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: fix tests due to python-utils changesIonen Wolkens2024-01-082-6/+22
| | | | | | | | | | | Several tests fail due to `-o tmp_path_retention_policy=failed` from python-utils.eclass since commit b77499537549, so set back to the default (=all). The other setting (tmp_path_retention_count=0) does not seem to be a problem. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop 3.0.2-r1Ionen Wolkens2024-01-082-200/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: stabilize 3.1.0 for amd64Ionen Wolkens2023-12-161-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: add 3.1.0Ionen Wolkens2023-12-082-0/+200
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop x86 keywordIonen Wolkens2023-11-302-2/+2
| | | | | | | | Same issue as calibre, qutebrowser and qtwebengine are masked on x86 -- so let's just drop the keyword rather than pretend that it's still supported. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: preemptively add pdfjs upper boundIonen Wolkens2023-11-271-1/+1
| | | | | | | Not added to ::gentoo yet but is known incompatible at the moment. Should be fixed next qutebrowser release. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop 3.0.0Ionen Wolkens2023-11-273-216/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: stabilize 3.0.2 for amd64Ionen Wolkens2023-11-061-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: revert to back to old verify-sig handlingIonen Wolkens2023-11-013-27/+3
| | | | | | | This was done for BROOT, but if BROOT no longer need to be passed then redefining src_unpack is unnecessary. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Remove BROOT from VERIFY_SIG_OPENPGP_KEY_PATHMike Gilbert2023-10-313-3/+3
| | | | Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* www-client/qutebrowser: add 3.0.2Ionen Wolkens2023-10-192-0/+208
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: fix VariableScopeIonen Wolkens2023-10-102-2/+18
| | | | | | Would probably be simpler if the eclass could handle BROOT by itself. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: add bug link for qt653 tests patchIonen Wolkens2023-09-281-4/+6
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Revert "www-client/qutebrowser: drop 6.5.3 tests workaround"Ionen Wolkens2023-09-262-0/+14
| | | | | | | | | This reverts commit 33ef6a9d4df3ea6a0c688b0bb3bde2f7fa5e481d. Actually still cause problems with 6.6.0-rc, going to keep this around for a bit longer and see how it goes. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop 6.5.3 tests workaroundIonen Wolkens2023-09-262-14/+0
| | | | | | Got fixed on Qt's end before release. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: drop 2.5.4-r1Ionen Wolkens2023-09-183-265/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: skip chromium version testIonen Wolkens2023-09-162-0/+4
| | | | | | | | | | | | | Checks if the chromium version matches known versions recorded in the test. Upstream updates as needed but that means failure for any older qutebrowser version whenever there's a new major qtwebengine (aka, currently fails with 6.6.9999 which reports 112 rather than 108, but otherwise qutebrowser works just fine with it and upstream has updated this in qutebrowser-9999). Not really useful for us, let's just skip it rather than update. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: ignore new Qt warnings for testsIonen Wolkens2023-09-162-0/+14
| | | | | | | | | | Maybe bit early to do this, but currently getting these warnings with due-for-release-soon 6.5.3 and 6.6.0 branches. Temporary either way, that's something upstream will handle if still needed by the time of next release. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: stabilize 3.0.0 for amd64Ionen Wolkens2023-09-151-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: remove widevine workaround for prefixIonen Wolkens2023-09-052-24/+0
| | | | | | | | | | | | | | | Now prexified in qtwebengine:6 itself, albeit the rare users actually using this on prefix will need to manually rebuild qtwebengine to get the change if <=qtwebengine-6.5.2. Given this messed with tests did not want to keep this in qutebrowser, and it can benefit others. Technically don't need USE=widevine anymore, but prefer this over a optfeature at the moment and qutebrowser is fast to "rebuild" being python-only. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* www-client/qutebrowser: enable py3.12Ionen Wolkens2023-08-212-8/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>