In my earlier commit
manual: Don't suggest exposing VM port to local network.
I made a side change titled
Use `127.0.0.1` also on the VM side, otherwise connections to
services that, in the VM, bind to `127.0.0.1` only
(doing the safe approach) do not work.
Unfortunately, that was wrong:
QEMU inside the VM always communicates via the virtualised
Ethernet interface, not via the VM's loopback interface.
So trying to connect to `127.0.0.1` on the VM's side cannot work.
fixes the following error message:
```
$ node-gyp rebuild
info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it.
[1/4] Resolving packages...
error Failed to auto-install node-gyp. Please run "yarn global add node-gyp" manually. Error: "Couldn't find any versions for \"node-gyp\" that matches \"latest\" in our cache (possible versions are \"\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue."
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
https://hydra.nixos.org/build/239684452
These are needed, as the used sourcehut version is not compatible with
the newer major-releases for both packages.
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
The version of crosvm we have packaged only passes its tests with 4K
pages.
The whole patch doesn't apply, but that's okay, because we don't run
most of the affected tests.
* mixRelease: format code by nixpkgs-format
* mixRelease: investigate why erlang is referenced in resulting derivation
* mixRelease: organize nativeBuildInputs and buildInputs
It:
+ organizes `nativeBuildInputs` in a structured way.
+ moves `builtins.attrValues mixNixDeps` to `nativeBuildInputs`, because it's only used in compile-time
* mixRelease: remove current attempt for removing erlang references in resulting derivation
As said in the comment about "remove erlang references in resulting
derivation", for now, we don't have a robust method to do that.
Although these removed code did some work, they did not achieve the
final goal - remove erlang references in resulting derivation.
Therefore, it is better to remove them and provide future implementation
with a clean foundation.
> If you want to find these old codes, you can also retrieve them from
> the git history.
* mixRelease: remove all files for Microsoft Windows
* mixRelease: add new option - `removeCookie`
* mixRelease: polish comments
+ Capitalize the sentences.
+ Add punctuation marks.
+ Format a little code.
* mixRelease: wrap programs in $out/bin with their runtime deps
* mixRelease: commit what happysalada suggests
---------
Co-authored-by: c4710n <c4710n@users.noreply.github.com>
