Querying resulted in the following error:
$ goobook query test
Traceback (most recent call last):
File "/nix/store/y68w4wwx65yfck84vjsdvfwnii5594lc-python3.7-goobook-3.4/bin/.goobook-wrapped", line 7, in <module>
from goobook.application import main
File "/nix/store/y68w4wwx65yfck84vjsdvfwnii5594lc-python3.7-goobook-3.4/lib/python3.7/site-packages/goobook/application.py", line 18, in <module>
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'
This reverts commit ad6aada7e2c3ece14e5ab0e34acdcf35f11e4014.
The patch does not apply to our version.
This commit was part of https://github.com/NixOS/nixpkgs/pull/68875
cc @worldofpeace
@garbas and @seppeljordan, are these updates correct?
I removed `offlinehacker/pypi2nix` as an unmaintained ancestor of the current repo `nix-community/pypi2nix`. It appears @garbas forked `offlinehacker/pypi2nix` to `garbas/pypi2nix` and then handed off maintainership to @seppeljordan, transferring the repo to `nix-community/pypi2nix`.
- setuptools includes *.exe files by default, but can be excluded with an ENV variable.
- setuptools was built as an egg, which had reproducibility problems. Instead use a wheel
These are various *.exe and *.xml files used only on windows. setuptools
includes them by default since it normally creates a single release for
all operating systems.
This reduces the size from 1020.0K to 801.6K according to `nix-path -sh`.
The egg is a zip file. setuptools leaves timestamps in the egg,
which makes the build unreproducible. Unfortunately the files aren't
compressed so the size of setuptools increases to 2.3M from 0.8M
according to `nix path-info -sh`.
With this change, setuptools is reproducible according to
nix-build -A python37Packages.setuptools --check
We had these set so gtk2 can discover themes properly, however we failed
realize that gtk2 already has a patch that makes it search in XDG_DATA_DIRS.
I don't believe any issue is solved by setting these.
https://github.com/MindFlavor/prometheus_wireguard_exporter/releases/tag/3.2.0
Previously, the exporter used `wg show all dump` by default to retrieve
information about wireguard peers. If a wireguard config is set, the interface is
now extracted automatically and the exporter runs `wg show <interface> dump`[1].
The cargo hash didn't change as no dependency updates were done in this
release.
[1] 4e332cb73f
