vim: 9.1.0707 -> 9.1.0765

[LeSuisse]

Fixes CVE-2024-47814 / GHSA-rj48-v4mq-j4vg.

Changes:
vim/vim@v9.1.0707...v9.1.0765

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 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.

---

Add a 👍 reaction to pull requests you find important.

[philiptaron]

@emilazy, I thought we fixed the everything-depend-on-vim problem with #335277. I guess there's more wood to chop.

[LeSuisse]

Yup I thought that too 😅

Rebasing on staging.

[emilazy]

What was the ofborg rebuilds list before the force push?

Edit: I guess we’ll see the same list now anyway, so no worries.

[philiptaron]

... it's full of vimPlugins.

https://gist.github.com/GrahamcOfBorg/905b1d3e525c759363eaeb4b026df9e6

[philiptaron]

Basically, I think we could merge this against master and it'd be fine.

[emilazy]

As @vcunat often says, Hydra’s bottlenecks are not what you expect: it’s not building large derivations that is necessarily the problem, but rather the job count, because of stuff around scheduling and compressing and uploading outputs that I don’t fully understand myself. I don’t know whether or not this would pass the threshold for being too much.

[vcunat]

The CVE doesn't seem urgent, but it's just the plugins. What about staging-next as a compromise?

[github-actions]

Successfully created backport PR for staging-24.05:

• [Backport staging-24.05] vim: 9.1.0707 -> 9.1.0765 #347245

[vcunat]

Yes, I believe so. It should get into master in just a few days, and we still save infra time by not doubling the rebuilds (master + staging-next) + maybe some plugins for darwin haven't even built for staging-next yet.