Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iosevka: 32.1.0 -> 32.2.1 #365044

Merged
merged 2 commits into from
Dec 14, 2024
Merged

iosevka: 32.1.0 -> 32.2.1 #365044

merged 2 commits into from
Dec 14, 2024

Conversation

lunik1
Copy link
Contributor

@lunik1 lunik1 commented Dec 13, 2024

Things done

Upgrade iosevka 32.1.0 -> 32.2.1

Suppress progress bar

  • 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:
  • 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/)
  • 25.05 Release Notes (or backporting 24.11 and 25.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.

@drupol drupol merged commit 7f03d9d into NixOS:master Dec 14, 2024
23 of 24 checks passed
@lunik1 lunik1 deleted the iosevka-32.1.0 branch December 14, 2024 15:42
@kurnevsky
Copy link
Member

kurnevsky commented Dec 30, 2024

@lunik1 did you notice any changes in the build time or memory usage after this update? I used to build 3 iosevka packages in parallel with NIX_BUILD_CORES=32, and now I barely have enough RAM to build 1 package at a time. But I'm not sure why - I don't see any obvious change that might have caused this :)

@lunik1
Copy link
Contributor Author

lunik1 commented Dec 30, 2024

I didn't notice one, but wasn't explicitly looking. The build has always been very resource hungry for me, ~1GB memory per job and pinning all the cores you throw at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants