hey, which process core dumped exactly and what do you want to document?

i was adding a short paragraph to the manual on how to use what you've developed with #67627.
i tried building the manual to review my changes, but it failed:

pille@saba ~ % cd /tmp/nixpkgs/nixos/doc/manual 
pille@saba manual % make                                                                                                                                                                                                                                               (git)[grub-loopback.cfg-iso-doc(4450)| U116]
nix-build ../../release.nix \
	--attr manualGeneratedSources.x86_64-linux \
	--out-link ./generated
error: value is an integer while a list was expected, at /tmp/nixpkgs/nixos/doc/manual/default.nix:14:48
(use '--show-trace' to show detailed location information)
make: *** [Makefile:28: generated] Error 1
pille@saba manual [2] % nix-build ../../release.nix \                                                                                                                                                                                                                  (git)[grub-loopback.cfg-iso-doc(4450)| U116]
                --attr manualGeneratedSources.x86_64-linux \
                --out-link ./generated --show-trace
[1]    64735 abort (core dumped)  nix-build ../../release.nix --attr manualGeneratedSources.x86_64-linux   
pille@saba manual [134] %                                                                                                                                                                                                                                              (git)[grub-loopback.cfg-iso-doc(4450)| U116]

i was running this on a sabayon machine via their nix package https://packages.sabayon.org/show/nix,227342,sabayonlinux.org,amd64,5,standard, so this may be out of scope.

I currently have this config to boot the isos, maybe you also want to document the "nixos" way. I also have to find a nicer way to get the autoiso.cfg from the source..

  boot.loader.grub = {
    extraEntries = ''
      submenu isos {
        source /grub/autoiso.cfg
      }
    '';
    extraFiles."/grub/autoiso.cfg" = (pkgs.stdenv.mkDerivation {
      name = "autoiso.cfg";
      src = pkgs.grub2.src;
      phases = [ "unpackPhase" "installPhase" ];
      installPhase = ''
        cp docs/autoiso.cfg $out
      '';
    });
  };

@pille is this dead?

@mrVanDalo: i've left this here as-is, to take care of documenting a feature that i requested. i'm not working on this, since i'm not using NixOS and can't compile the docs.

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

please leave this open, wrt my last comment.

I marked this as stale due to inactivity. → More info