Qt 5.15 carried a change that renamed a getter for the socket error. In
a later relase that change was reverted (to be less ambiguous) thus now
those that had picked up the change in API had to change their code.
This has now been reverted [0] and thus the consumers also have to
revert their changes…
[0] https://codereview.qt-project.org/c/qt/qtbase/+/289693
As of version 3.0.0 tldextract requires filelock during runtime. [0] In
nixpkgs tldextract was bumped from version 2.2.3 to 3.1.0 in
5b2d82451f without actually updating the
dependencies breaking packages such as qutebrowser.
This fix is part of this series to verify that bumping qt5 to 5.15.2
actually fixes the crash caused by WebRTC [1].
[0] 2eba0e5ebd
[1] https://bugreports.qt.io/browse/QTBUG-86752
This is a maintenance release of the Qt 5.15 release series. It focuses on
bug and security fixes. The feature that made me update this package was
the broken u2f support in QtWebEngine when used together with
Qutebrowser. It previously (on older Qt versions) used to work but
stopped working with the switch to 5.15.
As the changelog is rather extensive the reader is advised to inspect
[0] to checkout the changes to each of the components of their
interest.
This also fixes a security issue with QtWebEngine based browsers that
could be crashed by visiting a website that invokes certain WebRTC
features [1].
[0] https://wiki.qt.io/Qt_5.15.2_Change_Files
[1] https://bugreports.qt.io/browse/QTBUG-86752
* Reduces test time from ~5 mins to ~30 seconds.
* Also converts to pytestCheckHook for better test control.
* Makes fetchFromGitHub variables match convention.
* remove pytest-randomly.
pytest-randomly will randomize test order &
reset random seeds between tests.
We don't want the random test ordering for reproducible builds, so we
remove it.
* Fixes flaky test "test_hashmap_old_version" by pinning pytest to v5,
corresponding to upstream issue:
https://github.com/adobe-type-tools/psautohint/issues/284#issuecomment-742800965
py3.psautohint: use pytest5
If I'm running an Emacs executable from emacsWithPackages as my main
programming environment, and I'm hacking on Emacs, or the Emacs
packaging in Nixpkgs, or whatever, I don't want the Emacs packages
from the wrapper to show up in the load path of that child Emacs. It
results in differing behaviour depending on whether the child Emacs is
run from Emacs or from, for example, an external terminal emulator,
which is very surprising.
To avoid this, pass another environment variable containing the
wrapper site-lisp path, and use that value to remove the corresponding
entry in EMACSLOADPATH, so it won't be propagated to child Emacsen.
An empty entry in EMACSLOADPATH gets filled with the default value.
This is presumably why the wrapper inserted a colon after the entry it
added for the dependencies. But this naive approach wasn't always
correct.
For example, if the user ran emacs with EMACSLOADPATH=foo, the wrapper
would insert the default value (by adding the trailing `:') even
though the user was trying to expressly opt out of it.
To do this correctly, here I've replaced makeWrapper with a bespoke
script that will actually parse the EMACSLOADPATH provided in the
environment (if given), and insert the wrapper's load path just before
the default value. If EMACSLOADPATH is given but contains no default
value, we respect that and don't add the wrapped dependencies at all.
If no EMACSLOADPATH is given, we insert the wrapped dependencies
before the default value, just like before. In this way, the wrapped
Emacs should now behave as if the wrapped dependencies were part of
Emacs's default load-path value.
Previously, meta wasn't being passed through at all, because it's
removed from args without being used anywhere. This made it so that
rcirc-menu wasn't being marked as broken even though it was supposed
to be.
This patch copies the meta handling from melpaBuild, including the
default home page (adapted for ELPA).
* Use pythonPackages instead of python2Packages
* Add vncdo to top-level/python-packages so the library can be used by
other Python programs
* Use toPythonApplication for vnc in top-level/all-packages
* run tests if using Python 3+
* move expression to development/python-modules
