Currently, local module discovery is broken with luigi installed from
this derivation.
In the documentation, you can see the following command line syntax
used:
```
luigi --module module_name ...
```
However, currently this will result in an error:
```
ModuleNotFoundError: No module named 'module_name'
```
However, if the call is prepended with this:
```
PYTHONPATH=.:$PYTHONPATH
```
then it will work as expected.
This patch makes this the default behaviour.
Couple of things were updated to make this work.
1. webkitgtk24x-gtk3 that is marked unsafe has been replaced with
webkitgtk (2.20.*) as astroid has recently indicated that [>= 2.20
is
acceptable](https://github.com/astroidmail/astroid/commit/48ce7e3010d2ee99ccba18798b4f5333867bd1a2)
2. protobuf built input was added to satisfy requirements
3. astroid was not functional at all without proper icons so gnome3.defaultIconTheme
were added to buildInputs
4. By default, astroid will use `gvim` as a setting for the embedded
editor, however that didn't work well with nixpkgs. vim is now
bundled with astroid by default. This setting can be overridden
by the user in astroid's config file.
For some reason, building powershell derivation started failing with
these errors:
```
liblttng-ust.so.0 -> not found!
...
libpam.so.0 -> not found!
```
This patch adds these dependencies
As we found out in #40032, sit tests won't pass on
aarch64. The problem seems to be related to
`create_dir` not returning an error if the directory
already exists, happening specifically on aarch64+debug
(not aarch64+release)
This update injects a patch for tests that will also
be included in subsequent versions of SIT.
By default, OnlyKey device (https://crp.to/p/) won't work on Linux (and,
therefore, NixOS). This is unintuitive and requires one to search for a
solution in the documentation.
This change allows one to enable OnlyKey device support directly from
their NixOS configuration.
Previously, cargoUpdateHook was meaningful as it was used
in
[`cargo-fetch-deps`](https://github.com/NixOS/nixpkgs/blob/19d3cf81d3436a6600f261579b55b9132a6ca8fb/pkgs/build-support/rust/fetch-cargo-deps#L71).
However, this entire file was removed in
5f8cf0048e. As far as I can
tell, nothing in the code is using it, but it is still
being passed around:
https://github.com/NixOS/nixpkgs/search?q=cargoUpdateHook&type=Code&utf8=%E2%9C%93
There are, however, legitimate use cases for it. For example,
in some software, some dependencies are not locked in Cargo.toml
and this causes Cargo to try fetching another version of them.
This doesn't work well with vendoring crates.
This hook allows to inject patching or whatever necessary workarounds
in the crate vendoring process. I suppose that's what it was for
in there in the first place.
This patch restores this hook and makes it usable again.
For Python 2, tests were failing because they depended on a particular
way of executing the tests module as it defined a global variable
and created a temporary file. Running it through setup.py didn't work.
Invoking it directly solved the issue.
For Python 3, aenum tests were disabled, however, they did't have to
fail. Configuring UTF8 locale resolved the failure that was happening
after the above fix for Python 2 was applied.
Feature rich browser-based frontend with data structure visualizations
(like DDD), and gdb terminal access. Compatible with C, C++, golang,
Rust, fortran. Written in Python and JavaScript
gdbgui is at the top of the GDB Front Ends
list on https://sourceware.org/gdb/wiki/GDB%20Front%20Ends
As per #30645, fish with fish-foreign-env prints this
(harmless) warning:
```
set: Tried to change the read-only variable “_”
```
This patch was developed by @rnhmjoj in the aforementioned
issue discussion
By default, awesome will use "devel" as a version name
(or `git describe`). This has led to awesome always
showing "devel" for its version.
Some extensions depend on version information to figure
out what features they can use.
This change overrides the version for the build from the
derivations' `version` attribute.
Yurii Rashkovskii