jiebi/CodeConvo huggingface dataset:
Change:
As I am trying to port the budgie desktop form the abandoned PR A of my port results in the error: mentioned this may be due to missing introspection files in the libpulseaudio package. The relevant part of the derivation is:
It ought to be sufficient to add to PulseAudioʼs and to .
Apparently, libpulse is not based on GObject so it does not provide introspection. It should install VAPIs though, not sure why it is not happening.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue 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. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I've recently been trying to build budgie as well, and have run into the same issue. Was any solution found? Here's my derivation:
Looking at it again, the issue is that the vapi files (in ) are removed here: So you would either need to fix that in nixpkgs, or use the gigantic package instead.
Would a fix in nixpkgs just be removing all of $out/share except for any .vapi (and possibly .deps) files?
Correct. Or rather, the whole directory should be preserved.

Discussion:
''; postInstall = lib.optionalString libOnly '' <del> rm -rf $out/{bin,share,etc,lib/{pulse-*,systemd}} </del> <ins> find $out/share -maxdepth 1 -mindepth 1 ! -name "vala" -prune -exec rm -r {} ; find $out/share/vala -maxdepth 1 -mindepth 1 ! -name "vapi" -prune -exec rm -r {} ; rm -r $out/{bin,etc,lib/pulse-*} </ins> '' + '' moveToOutput lib/cmake "$dev"
Change:
it's supposed to be reachable via , from within emacs, but it is not. However, the program can find it, when run as
I misunderstood some emacs-related things. I'm not sure if the situation is perfect or not, but at least the manual I want is available at

Discussion:
buildGoPackage rec { pname = "nomad"; <del> version = "0.10.5"; </del> <ins> version = "0.11.0"; </ins> rev = "v${version}"; goPackagePath = "github.com/hashicorp/nomad";

owner = "hashicorp"; repo = pname; inherit rev; <del> sha256 = "0i9104anf3qaydm1izlwrzvpzizd6p1zy651hsynscnnxa56cmyk"; </del> <ins> sha256 = "0jg7h52wlgd2aslx13fs97j3b8g5xfgil3p2jsc4j95l7lmqn7bv"; </ins> }; # ui:

noip = callPackage ../tools/networking/noip { }; <del> nomad = callPackage ../applications/networking/cluster/nomad { buildGoPackage = buildGo112Package; }; </del> <ins> nomad = callPackage ../applications/networking/cluster/nomad { }; </ins> notable = callPackage ../applications/misc/notable { };
Change:
Describe the bug A clear and concise description of what the bug is. mitmproxy tests broken on unstable. To Reproduce Steps to reproduce the behavior: nix-env -iA nixos-unstable.mitmproxy Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
thank you for submitting this, ill get it fixed

Discussion:
doCheck = (!stdenv.isDarwin); <ins> # examples.complex.xss_scanner doesn't import correctly with pytest5 </ins> checkPhase = '' export HOME=$(mktemp -d) export LC_CTYPE=en_US.UTF-8 <del> pytest -k 'not test_find_unclaimed_URLs and not test_tcp' </del> <ins> pytest --ignore test/examples  -k 'not test_find_unclaimed_URLs and not test_tcp' </ins> ''; propagatedBuildInputs = [
Change:
, (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
See also: ,

Discussion:
# Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}
Change:
, (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
The CVEs mentioned here are fixed in 1.3.10, but newer releases also mention more security fixes, e.g. shows various security bugs being fixed. I'll upgrade to the latest one.
PR at Should be backported to 19.09 afterwards

Discussion:
{ stdenv, fetchurl, pkgconfig, freetype, cmake, python }: stdenv.mkDerivation rec { <del> version = "1.3.6"; </del> <ins> version = "1.3.13"; </ins> pname = "graphite2"; src = fetchurl { url = "https://github.com/silnrsi/graphite/releases/download/" <del> + "${version}/graphite-${version}.tgz"; sha256 = "0xdg6bc02bl8yz39l5i2skczfg17q4lif0qqan0dhvk0mibpcpj7"; </del> <ins> + "${version}/graphite2-${version}.tgz"; sha256 = "01jzhwnj1c3d68dmw15jdxly0hwkmd8ja4kw755rbkykn1ly2qyx"; </ins> }; nativeBuildInputs = [ pkgconfig cmake ];
Change:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
See also:
Is this still an issue if says it fixes this one? You might have more few more fixed issues like this one.
Fixed in

Discussion:
<del> { stdenv, fetchurl, ncurses, readline, autoreconfHook }: </del> <ins> { stdenv, fetchurl, fetchpatch, ncurses, readline, autoreconfHook }: </ins> stdenv.mkDerivation rec { version = "1.7.0";

buildInputs = [ ncurses readline ]; nativeBuildInputs = [ autoreconfHook ]; <del> patches = [ ./0001-Make-hunspell-look-in-XDG_DATA_DIRS-for-dictionaries.patch ]; </del> <ins> patches = [ ./0001-Make-hunspell-look-in-XDG_DATA_DIRS-for-dictionaries.patch (fetchpatch { name = "CVE-2019-16707.patch"; url = "https://github.com/hunspell/hunspell/commit/ac938e2ecb48ab4dd21298126c7921689d60571b.patch"; sha256 = "0bwfksz87iy7ikx3fb54zd5ww169qfm9kl076hsch3cs8p30s8az"; }) ]; </ins> postPatch = '' patchShebangs tests
Change:
, (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
No upstream release so far. Applying will probably be OK, but I don't feel confident enough to do that "backport".
I do :-)

Discussion:
buildInputs = [ openssl zlib ] ++ stdenv.lib.optional stdenv.hostPlatform.isMinGW windows.mingw_w64; <ins> patches = [ # not able to use fetchpatch here: infinite recursion (fetchurl { name = "CVE-2019-17498.patch"; url = "https://github.com/libssh2/libssh2/pull/402.patch"; sha256 = "1n9s2mcz5dkw0xpm3c5x4hzj8bar4i6z0pr1rmqjplhfg888vdvc"; }) ]; </ins> meta = with stdenv.lib; { description = "A client-side C library implementing the SSH2 protocol"; homepage = https://www.libssh2.org;
Change:
, (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
~Should be~ fixed on unstable/master by PR .
09: (staging ATM, but should get into channel within days).

Discussion:
# Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}
Change:
, (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
On it
Done

Discussion:
# Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}
Change:
, (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
On it
Done

Discussion:
<del> {stdenv, fetchurl, fetchpatch, libtool, libjpeg, openssl, zlib, libgcrypt, autoreconfHook, pkgconfig, libpng, systemd </del> <ins> { stdenv, fetchzip, fetchpatch, cmake , libjpeg, openssl, zlib, libgcrypt, libpng , systemd </ins> }: let s = # Generated upstream information rec { <del> baseName="libvncserver"; version="0.9.11"; name="${baseName}-${version}"; url="https://github.com/LibVNC/libvncserver/archive/LibVNCServer-${version}.tar.gz"; sha256="15189n09r1pg2nqrpgxqrcvad89cdcrca9gx6qhm6akjf81n6g8r"; </del> <ins> pname = "libvncserver"; version = "0.9.12"; url = "https://github.com/LibVNC/libvncserver/archive/LibVNCServer-${version}.tar.gz"; sha256 = "1226hb179l914919f5nm2mlf8rhaarqbf48aa649p4rwmghyx9vm"; # unpacked archive checksum </ins> }; in stdenv.mkDerivation { <del> inherit (s) name version; src = fetchurl { </del> <ins> inherit (s) pname version; src = fetchzip { </ins> inherit (s) url sha256; }; patches = [ <del> # CVE-2018-7225. Remove with the next release </del> (fetchpatch { <del> url = https://salsa.debian.org/debian/libvncserver/raw/master/debian/patches/CVE-2018-7225.patch; sha256 = "1hj1lzxsrdmzzl061vg0ncdpvfmvvkrpk8q12mp70qvszcqa7ja3"; </del> <ins> name = "CVE-2018-20750.patch"; url = "https://github.com/LibVNC/libvncserver/commit/09e8fc02f59f16e2583b34fe1a270c238bd9ffec.patch"; sha256 = "004h50786nvjl3y3yazpsi2b767vc9gqrwm1ralj3zgy47kwfhqm"; }) (fetchpatch { name = "CVE-2019-15681.patch"; url = "https://github.com/LibVNC/libvncserver/commit/d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a.patch"; sha256 = "0hf0ss7all2m50z2kan4mck51ws44yim4ymn8p0d991y465y6l9s"; </ins> }) ]; <del> preConfigure = '' sed -e 's@/usr/include/linux@${stdenv.cc.libc}/include/linux@g' -i configure ''; nativeBuildInputs = [ pkgconfig autoreconfHook ]; </del> <ins> nativeBuildInputs = [ cmake ]; </ins> buildInputs = [ <del> libtool libjpeg openssl libgcrypt libpng </del> <ins> libjpeg openssl libgcrypt libpng </ins> ] ++ stdenv.lib.optional stdenv.isLinux systemd; propagatedBuildInputs = [ zlib ]; meta = { inherit (s) version; <del> description =  "VNC server library"; </del> <ins> description = "VNC server library"; homepage = "https://libvnc.github.io/"; </ins> license = stdenv.lib.licenses.gpl2Plus ; maintainers = [stdenv.lib.maintainers.raskin]; platforms = stdenv.lib.platforms.unix;
Change:
, (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
This should be handled now.

Discussion:
stdenv.mkDerivation rec { pname = "samba"; <del> version = "4.10.8"; </del> <ins> version = "4.10.10"; </ins> src = fetchurl { url = "mirror://samba/pub/samba/stable/${pname}-${version}.tar.gz"; <del> sha256 = "1x0hlhb674fndfkmimjicnzs543n3i8465a5ifcmjwvzavxha7y4"; </del> <ins> sha256 = "19b653rr2i9snvapik58phbqj38cxjdlyx6nl3m2y3k1a55p633h"; </ins> }; outputs = [ "out" "dev" "man" ];
Change:
Describe the bug Running the binary from the package produces the following error message: To Reproduce Metadata system: host os: multi-user?: sandbox: version: channels(me): channels(root): nixpkgs: Maintainer information:
cc I've dug through the source a little bit, and it seems that the configure scripts are setting preloading support to false. Unfortunately I do not really understand the autoconf tooling or the preload mechanism, so I'm having a hard time debugging, do you have any tips?
It's caused by the same breakage I mentioned . I've set a reminder to PR a fix for it once I'm home tonight, but here's the fix in overlay format if you like:

Discussion:
buildInputs = [ pam libkrb5 cyrus_sasl miniupnpc ]; <del> configureFlags = ["--with-libc=libc${stdenv.targetPlatform.extensions.sharedLibrary}"]; </del> <ins> configureFlags = if !stdenv.isDarwin then [ "--with-libc=libc.so.6" ] else [ "--with-libc=libc${stdenv.targetPlatform.extensions.sharedLibrary}" ]; </ins> dontAddDisableDepTrack = stdenv.isDarwin;
Change:
Describe the bug would raise an unrelated error when trying to use an insecure package: To Reproduce Steps to reproduce the behavior: any package marked with in system.packages (e.g. evilvte); Expected behavior An error stating the package is insecure, or allows the package to be used if it is in . Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(cheng): nixpkgs:
I stumbled upon this too while upgrading from 19.03 today. For me it was due to the package. Diabling the resolved the issue for now. system: host os: multi-user?: sandbox: version: channels(root): channels(cheng): nixpkgs:
Packages used to have to specify a attribute to , more recently seems to have developed the ability to assemble one from the and attributes, so many packages now don't specify directly. It appears that in hasn't yet grown the ability to handle these packages and instead operates on a copy of this attr taken before its has been generated. Edit: think I've spotted the problem. PR incoming.
Should this be closed? The commit message of seems like it, but doesn't use one of Githubs key words.
I can confirm this issue has been resolved

Discussion:
isUnfree (lib.lists.toList attrs.meta.license) && !allowUnfreePredicate attrs; <del> allowInsecureDefaultPredicate = x: builtins.elem x.name (config.permittedInsecurePackages or []); </del> <ins> allowInsecureDefaultPredicate = x: builtins.elem (getName x) (config.permittedInsecurePackages or []); </ins> allowInsecurePredicate = x: (config.allowInsecurePredicate or allowInsecureDefaultPredicate) x; hasAllowedInsecure = attrs:
Change:
Describe the bug Building neovim doesn't work anymore. To Reproduce Checkout master branch, commit (latest as of now), then build: Expected behavior Building neovim should succeed.
The failing code is (...-stdenv-linux/setup: line 320):
Having the same issue when updating my system.
Ping I think this has something to do with the recent stdenv changes. Do you know how to fix it?
This is from which breaks this manual sourcing of setup hooks I say this is a good thing! We should make those proper dependencies. I will fix shortly.
I have a similar issue in stdenv-linux/setup /nix/store/fiaj00zrmb7dynd2q9xmcrh5rn0mjwj0-stdenv-linux/setup: line 97: $'r': command not found builder for '/nix/store/frqmqjyg649bkqivqhzq041fxbfvsikw-cockpit-' failed with exit code 127
Thanks!

Discussion:
let env = let paths =  requiredLuaModules (extraLibs ++ [ lua ] ); <del> in buildEnv { </del> <ins> in (buildEnv { </ins> name = "${lua.name}-env"; inherit paths;

# we create wrapper for the binaries in the different packages postBuild = '' <del> . "${makeWrapper}/nix-support/setup-hook" # get access to lua functions . ${lua}/nix-support/setup-hook </del> if [ -L "$out/bin" ]; then unlink "$out/bin" fi

''; }; }; <del> }; </del> <ins> }).overrideAttrs (_: { # Add extra deps needed for postBuild hook. nativeBuildInputs = [ makeWrapper lua ]; }); </ins> in env
Change:
We need to standardize and document this. The current contents in nixpkgs manual seems obsolete (section 4.2). I suggest at least these should be standardized: preference for usage of <codelib.licenses.*</codeinstead of the choice from some strings, meta.licenses semantics (any license at your choice, or different parts under different licenses?).
:+1:
I'd go for a documentation changes with pull request and point people to read that.
Is someone working on this? Would be good to get into (which also will presumably have with its new way of handling attributes)
First bullet is addressed in . For more complicated cases when it's not all one single license, I don't know how deep should we go. Choice from multiple licenses is probably the most common and using nix lists for that is suggestive, but it occasionally happens that multiple licenses need to be complied to at once (different files/parts under different licenses) or even more complex combinations. I don't see any possibility of "smooth extension" in such directions.
Solutions I encountered: Debian has per-file license granularity , and offers some RDF-based solution.
what's missing here?
I see the first bullet was fixed in . Attribute is still unspecified, but IMHO describing the licensing precisely in all cases is out of the scope of nixpkgs.
BTW, thanks for the notification. I forget to pass through old open issues.

Discussion:
}: stdenv.mkDerivation rec { <del> name = "nsd-4.1.7"; </del> <ins> name = "nsd-4.1.9"; </ins> src = fetchurl { url = "http://www.nlnetlabs.nl/downloads/nsd/${name}.tar.gz"; <del> sha256 = "12hskfgfbkvcgpa1xxkqd8lnc6xvln1amn97x6avfnj9kfrbxa3v"; </del> <ins> sha256 = "1wn8jm5kpp81m88c77j97850mnmd87yaw8qp3xsdwcakcd6j44dq"; </ins> }; buildInputs = [ libevent openssl ];
Change:
Project description A supercharged alternative to regular expressions (regex), matching patterns against any input text. Metadata homepage URL: https://rosie- source URL: license: mit platforms: unix PS: this may be relevant:
This is a cool program, I'll have a go at packaging :)
Hmm, this will require upstream changes too, as it doesn't seem that amenable to packaging as is. It'll take a bit longer than I hoped, I'll see if I have some quiet time over the holiday period to work on it. But we might be able to avoid the linked as that is about run-time paths, but we know at compile-time where things go.
But while I do that, you can have a play with (it's a hack of a package, but it seems to work, let me know if things are broken). Just clone that repo, and in the repo root directory do .
I think this can be closed since there is a pull request open for this now.
Add to the pr message so github will close the issue automatically when the pr is merged.

Discussion:
<ins> { stdenv , lib , fetchgit , libbsd , readline }: stdenv.mkDerivation rec { pname = "rosie"; version = "unstable-2020-01-11"; src = fetchgit { url = https://gitlab.com/rosie-pattern-language/rosie; rev = "670e9027563609ba2ea31e14e2621a1302742795"; sha256 = "0jc512dbn62a1fniknhbp6q0xa1p7xi3hn5v60is8sy9jgi3afxv"; fetchSubmodules = true; }; postUnpack = '' # The Makefile calls git to update submodules, unless this file exists touch ${src.name}/submodules/~~present~~ ''; preConfigure = '' patchShebangs src/build_info.sh # Part of the same Makefile target which calls git to update submodules ln -s src submodules/lua/include ''; postInstall = '' mkdir -p $out/share/emacs/site-lisp $out/share/vim-plugins $out/share/nvim mv $out/lib/rosie/extra/extra/emacs/* $out/share/emacs/site-lisp/ mv $out/lib/rosie/extra/extra/vim $out/share/vim-plugins/rosie ln -s $out/share/vim-plugins/rosie $out/share/nvim/site ''; makeFlags = [ "DESTDIR=${placeholder "out"}" ]; buildInputs = [ libbsd readline ]; meta = with lib; { homepage = https://rosie-lang.org; description = "Tools for searching using parsing expression grammars"; license = licenses.mit; maintainers = with maintainers; [ kovirobi ]; platforms = with platforms; linux ++ darwin; }; } </ins>

rnv = callPackage ../tools/text/xml/rnv { }; <ins> rosie = callPackage ../tools/text/rosie { }; </ins> rounded-mgenplus = callPackage ../data/fonts/rounded-mgenplus { }; roundup = callPackage ../tools/misc/roundup { };
Change:
nix-env -i chessx && chessx
I'm getting the same error after updating the channel and upgrading, am I missing something ?
See at for how changes move to a channel. If you want to be able to run the fixed program now you can do

Discussion:
# Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}
Change:
Describe the bug seems to be unused in NixOS. Instead it seems to be a duplicate of . When greping for the option, only references of the later are found. Metadata Maintainer information:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
(mkRenamedOptionModule [ "networking" "dnsExtensionMechanism" ] [ "networking" "resolvconf" "dnsExtensionMechanism" ]) (mkRenamedOptionModule [ "networking" "extraResolvconfConf" ] [ "networking" "resolvconf" "extraConfig" ]) (mkRenamedOptionModule [ "networking" "resolvconfOptions" ] [ "networking" "resolvconf" "extraOptions" ]) <ins> (mkRemovedOptionModule [ "networking" "resolvconf" "useHostResolvConf" ] "This option was never used for anything anyways") </ins> ]; options = {

''; }; <del> useHostResolvConf = mkOption { type = types.bool; default = false; description = '' In containers, whether to use the <filename>resolv.conf</filename> supplied by the host. ''; }; </del> dnsSingleRequest = lib.mkOption { type = types.bool; default = false;
Change:
Describe the bug When building twice, the GPT partition has a different GUID. To Reproduce Steps to reproduce the behavior: to see the GUID is not consistent (or at , ) Expected behavior A deterministic GUID Additional context For additional background on why it's helpful for builds to be reproducible, see https://reproducible- I'd be happy to help hunt down and fix this problem further, but this is rather new territory for me, so I'd appreciate any help
Thanks for taking a look at this! I'd suggest to trace it down from , and how things are passed down to - but I'm not exactly sure WHAT creates the GPT partition.
Thanks for the encouragement! Looking closer, it seems the GPT is written by as invoked in . Unfortunately, while manually invoking with fewer flags and indeed has the expected effect, adding that flag to the invocation doesn't. Some more digging to do! :)
Ah it's somehow the post-processing... indeed that seems to generate a new random UUID with . Without it keeps it intact. I wonder if we need the , given already seems to do quite a bit of the work.
Shouldn't this be testable by trying to boot an image without that flag being set on a pure UEFI system?
I tested this by copying the ISO built without that flag to an USB disk, and booting my laptop with the "UEFI: USB disk" selected in the boot priorities. That worked fine. I'll try to prepare a PR that makes the GPT disk GUID static (based on the derivation hash or ) and skips the . (though not sure when I'll get to it, if someone wants to beat me to it, feel free ;) )
Cool, this sounds very promising, also is one more step towards :-) cc yeah, just hashing over the input hash and converting that to the uuid format somehow sounds reasonable.

Discussion:
<del> { stdenv, closureInfo, xorriso, syslinux </del> <ins> { stdenv, closureInfo, xorriso, syslinux, libossp_uuid </ins> , # The file name of the resulting ISO image. isoName ? "cd.iso"

stdenv.mkDerivation { name = isoName; builder = ./make-iso9660-image.sh; <del> buildInputs = [ xorriso syslinux zstd ]; </del> <ins> buildInputs = [ xorriso syslinux zstd libossp_uuid ]; </ins> inherit isoName bootable bootImage compressImage volumeID efiBootImage efiBootable isohybridMbrImage usbBootable;

mkdir -p $out/iso <ins> # daed2280-b91e-42c0-aed6-82c825ca41f3 is an arbitrary namespace, to prevent # independent applications from generating the same UUID for the same value. # (the chance of that being problematic seem pretty slim here, but that's how # version-5 UUID's work) </ins> xorriso="xorriso <ins> -boot_image any gpt_disk_guid=$(uuid -v 5 daed2280-b91e-42c0-aed6-82c825ca41f3 $out | tr -d -) </ins> -as mkisofs -iso-level 3 -volid ${volumeID}

$xorriso -output $out/iso/$isoName <del> if test -n "$usbBootable"; then echo "Making image hybrid..." if test -n "$efiBootable"; then isohybrid --uefi $out/iso/$isoName else isohybrid $out/iso/$isoName fi fi </del> if test -n "$compressImage"; then echo "Compressing image..." zstd -T$NIX_BUILD_CORES --rm $out/iso/$isoName