This allows configuring IP addresses on a tinc interface using
networking.interfaces."tinc.${n}".ipv[46].addresses.
Previously, this would fail with timeouts, because of the dependency
chain
tinc.${netname}.service
--after--> network.target
--after--> network-addresses-tinc.${n}.service (and network-link-…)
--after--> sys-subsystem-net-devices-tinc.${n}.device
But the network interface doesn't exist until tinc creates it! So
systemd waits in vain for the interface to appear, and by then the
network-addresses-* and network-link-* units have failed. This leads
to the network link not being brought up and the network addresses not
being assigned, which in turn stops tinc from actually working.
Using "extraPacks" and "extraLibraries" arguments
it is possible to create fully functional virtual-envs
for SWI-Prolog projects.
(In a way similar to what "ghcWithPackages" does for Haskell)
Creating the timestamp in the patched script's directory has a few
drawbacks:
* if "foo.timestamp" already exists, it will be overwritten
* it requires the directory to be writable
gsettings-desktop-schemas made the following change in 3.32[0]
> Change tablets'/touchscreens' "display" setting to "output" one
> with different semantics.
That coincides with GNOME/mutter#133[1]
This caused a segmentation fault in gala on Fedora[2]
> Settings schema 'org.gnome.desktop.peripherals.touchscreen'
> does not contain a key named 'display'
I haven't experienced said segfault here in NixOS but I don't see
a reason not to use the solution reached there, which was to backport
relevant change[1] to mutter 3.28.
[0]: c7eee129c6
[1]: https://gitlab.gnome.org/GNOME/mutter/merge_requests/133
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1700337
cross-compilation of `btrfs-tools` is broken, and this usually needless dependency of each system closure on `btrfs-tools` prevents cross-compilation of whole system closures
The last upstream update was in 2014. While the software might still work, its usefulness depends on data archives, which are not updated anymore and have not been for several years.
Upstream suggests to use kiwix instead.
The build was broken by updating the underlying python library.
This is the quickfix.
Fixes: ca67a7200cf ("python37Packages.jupyterlab_server: 0.2.0 -> 0.3.0")
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
