Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39/bin/chromedriver passed the binary check.
- Warning: no invocation of /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39/bin/.chromedriver-wrapped had a zero exit code or showed the expected version
- 1 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 2.39 with grep in /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39
- directory tree listing: https://gist.github.com/ed47d14dfe1661b73d2d877b6e790579
- du listing: https://gist.github.com/63dc7bb82190375bce025de50ed2d6fa
The fftw download page provides both an HTTP and FTP endpoint for downloading release tarballs:
http://fftw.org/download.html
Since some users may have difficulty fetching via FTP through corporate
firewalls, we should provide the option to get it over HTTP as well.
Without explicitly specifying that libsasl2 is part of the build, and
without explicitly making it part of pylibmc's linker flags for its
CPython extension, the cpython code enters a build state error where it
instead attempts to blindly `dlopen("libsasl2.so")` out of
$LD_LIBRARY_PATH; this fails as it can't be found in the store,
obviously.
The bigger problem with this is that it otherwise makes pylibmc
unusable, as it will try to immediately load libsasl2 at startup. This
means even using 'import pylibmc' at all will cause a failure.
Instead, add cyrus_sasl into the build closure of the library, and pass
an argument to the setup.py script to properly pass -lsasl2 to the C
extension. This causes a link to properly be formed.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
CVE-2017-9935
CVE-2017-11613
CVE-2017-17095
CVE-2017-18013
CVE-2018-5784
CVE-2018-7456
Re #41748 (master)
Re #41749 (release-18.03 - needs to be cherry-picked)
Adds programs.mosh.withUtempter (default: true).
The option enables -with-utempter for mosh, allowing it to write to
/var/run/utmp and thus making connected sessions appear in the output
of `who -a`.
For that, a guid-wrapper is required. Also, the path to the `utempter` was
hardcoded in the resulting binary until now (so it could never been found),
thus, libutempter was patched accordingly to point to
/run/wrappers/bin/utempter which at least works when the wrapper is
configured.
Upstream changes:
* Record all SSL errors instead of only the first
* Pass arguments to plugin/plugout methods
* Allow the Roster to be initalized without requesting it from the
server
Tested by building and running Gajim 1.0.3.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @abbradar
