In commit 17dd7bcd89 the systemd unit
generator now uses lndir instead of "ln -s", so we need to have lndir
available in the Nix store for the installer tests to be able to build
the units and thus the whole system.
This should fix the installer tests, although I have only tested it with
the "simple" subtest.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @jtojnar, @xeji, @edolstra
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/caja/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/caja -h’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/caja --help’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/caja-connect-server -h’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/caja-connect-server --help’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/.caja-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/.caja-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/.caja-connect-server-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1/bin/.caja-connect-server-wrapped --help’ got 0 exit code
- found 1.21.1 with grep in /nix/store/vpa6y0jj5wa85md64941j0mmd5h8w269-caja-1.21.1
- directory tree listing: https://gist.github.com/46fb531ddeedf504b1610ffcaf01f09f
- du listing: https://gist.github.com/5396435fca3703ee457ac3c66b5c0121
When doing source routing/multihoming, it's practical to give names to routing
tables. The absence of the rt_table file in /etc make this impossible.
This patch recreates these files on rebuild so that they can be modified
by the user see NixOS#38638.
iproute2 is modified to look into config.networking.iproute2.confDir instead of
/etc/iproute2.
The manual still had a reference to an option that was already renamed
ages ago and a7ed44ccad made it 'visible'.
With the visible attribute set to false for extraKernelModules, the
option no longer appears in the manual and thus breaks the link from the
manual to the options.
This is easily fixed by referring to boot.initrd.kernelModules instead
of the obsolete option boot.initrd.extraKernelModules.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @rycee, @matthewbauer
The original `nexus` derivation required `/run/sonatype-work/nexus3`
which explicitly depended on the NixOS path structure.
This would break `nexus` for everyone using `nixpkgs` on a non-NixOS
system, additionally the module never created `/run/sonatype-work`, so
the systemd unit created in `services.nexus` fails as well. The issue
wasn't actively known as the `nixos/nexus` test wasn't registered in
Hydra (see #40257).
This patch contains the following changes:
* Adds `tests.nexus` to `release.nix` to run the test on Hydra.
* Makes JVM parameters configurable: by default all JVM options were located
in `result/bin/nexus.vmoptions` which made it quite hard to patch
these parameters. Now it's possible to override all parameters by
running `VM_OPTS_FILE=custom-nexus.vmoptions ./result/bin/nexus run`
(after patching the `nexus` shell script), additionally it's possible
to override these parameters with `services.nexus.vmoptions`.
* Bumped Nexus from 3.5.1 to 3.11.0
* Run the `nexus` test on Hydra with `callTest` in `nixos/release.nix`,
furthermore the test checks if the UI is available on the specified
port.
* Added myself as maintainer for the NixOS test and the package to have
some more people in case of further breakage.
* Added sufficient disk space to the `nexus` test, otherwise the service
fails with the following errors:
```
com.orientechnologies.orient.core.exception.ODatabaseException: Cannot create database 'accesslog'
com.orientechnologies.orient.core.exception.OLowDiskSpaceException: Error occurred while executing
a write operation to database 'accesslog' due to limited free space on the disk (242 MB). The database
is now working in read-only mode. Please close the database (or stop OrientDB), make room on your hard
drive and then reopen the database. The minimal required space is 256 MB. Required space is now set to
256MB (you can change it by setting parameter storage.diskCache.diskFreeSpaceLimit) .
```
/cc @ironpinguin @xeji
When a package contains a directory in one of the systemd directories
(like flatpak does), it is symlinked into the *-units derivation.
Then later, the derivation will try to create the directory, which
will fail:
mkdir: cannot create directory '/nix/store/…-user-units/dbus.service.d': File exists
builder for '/nix/store/…-user-units.drv' failed with exit code 1
Closes: #33233
It turns out none of this stuff is needed. The docs aren't evenly built
properly anyways so the build trivially succeeds either way, due to what
looks like upstream misunderstanding automake. If I try to build the
docs manually in a cross shell (before and after this change), there's a
make rule error such that some HTML files aren't even attempted to be
built and then a copy fails.
Even if this was all fixed, these been a good number of cross fixes
upstream getting them to use CC_FOR_BUILD and other good stuff, so I
doubt such hacks would be needed.
Progress towards #40531 and #33302.
Some of the new tests need the `nix` executable on `PATH`.
One also needs `hpack`, but we really don’t want to embiggen (heh) the closure
because of that.
