emacs: use held back patchelf_0_15 to avoid upstream bug

[trofi]

patchelf-0.17.2 corrupts $out/bin/emacs binary. It has something to do with program headers change. Let's pin emacs back to 0.15.0 until patchelf is fixed.

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[fabianhjr]

Built and tested with:

    emacs = {
      enable = true;
      package = pkgs.emacs28NativeComp;
      extraPackages = epkgs:
        with epkgs; [
          # agda2-mode # Needs to be from same build as agda
          vterm
        ];
    };

on staging-next

[vcunat]

It bothers me that the corruption didn't get detected within build of the corrupted package. Therefore we might have more of these cases that don't get detected at Hydra. Well, maybe it's OK-ish uncertainty for nixpkgs master. Either way I hope the bug can be analyzed and fixed quickly upstream.