GDM now specifies ordering between `plymouth-quit` and `display-manager`:
9be5321097c16
This causes an ordering cycle between GDM and plymouth-quit which can result in
systemd breaking GDM:
```
plymouth-quit.service: Job display-manager.service/start deleted to break
ordering cycle starting with plymouth-quit.service/start
```
Not sure how often this triggers, as I've run my system with plymouth and
9be5321097c16 without any issues. But I did catch a VM doing this.
NOTE: I also tried to remove the ordering in GDM to see if plymouth managed to
live longer, but it didn't seem to help. So I opted to stick as close to
upstream (upstream GDM specifies ordering, but plymouth does not).
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`.
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
+ added webarchive source for reliable builds in the future
+ removed `${version}` from url, as it actually adds more hassle to
have it in there and no benefits whatsoever, since the url keeps
changing other parts too
