| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This setup hook discovers glycin loaders in the inputs list it is placed into, and adds them to `gappsWrapperArgs`. This should simplify glycin-dependent programs’ expressions.
Just add `libglycin.setupHook` (for Rust programs) or `libglycin` (for other languages) to `buildInputs`. The latter will also pull in the setup hook.
Note, the setup hook needs to go to the `buildInputs` since we cannot have a different offset when used as standalone hook instead of propagated from `libglycin`. We chose `hostOffset` to make it work with the proper placement of `libglycin` in `buildInputs`.
Co-authored-by: Seth Flynn <getchoo@tuta.io>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Glycin rust library searches `bwrap` on path. This would require every reverse dependency to add `bubblewrap` to its `PATH`, which would be quite annoying to ensure. Especially when libraries start using glycin.
We provide `passthru.glycinPathsPatch` to perform source-level hardcoding but that doesn't work with apps that use `rustPlatform.cargoSetupHook` since it assumes a setup where snapshots of GNOME sources already contain vendored Rust dependencies under `vendor/`.
The setup hook instead provides a much more flexible approach that uses the `$cargoDepsCopy` variable provided by `cargoSetupHook`, which points to the local, modifiable copy of Cargo dependencies, to patch `src/sandbox.rs` just like `glycinPathsPatch`. If `$cargoDepsCopy` is not found, then the old behavior is used where Cargo dependencies are assumed to be under `vendor/`.
Additionally, the patch requires modifying `Cargo.lock` when using `rustPlatform.fetchCargoVendor`. The setup hook fixes that as well.
Rust programs just need to add `libglycin.patchVendorHook` and it should take care of this.
Co-authored-by: Seth Flynn <getchoo@tuta.io>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
minio had 3 moderate, 4 high and 4 critical security vulnerabilities since
2022-10-24, so even though we don't know this specific minio version is
affected, it's not worth the risk.
Furthermore 3 years should be enough time to migrate your data.
|
| |\ \ \
| | | |
| | | |
| | | | |
(#481815)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* docs/nixpkgs: mention rename of pkg
* docs/nixos: mention rename of module and new module options
* address review comment:
https://github.com/NixOS/nixpkgs/pull/481815#discussion_r2706713675
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added guidance on installing Rocq language servers when using
`coq.withPackages`.
#484870
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
fetchFromCodeberg
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
|
| |\ \ \ |
|
| | |/ / |
|
| |\| | |
|
| | |\ \ |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | |/
| | |/| |
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Diff: https://github.com/lima-vm/lima/compare/v1.2.2...v2.0.1
Release: https://github.com/lima-vm/lima/releases/tag/v2.0.1
2.0.0 replaced a call to the external pkill command with an internal function.
This change conflicts with the current nixpkgs patch,
so we must remove the patch to prevent a build error.
Updates: a9b8ff8c8cae79f4f849840895a85b9f7af55545
2.0.0: Replace a pkill call:
https://github.com/lima-vm/lima/commit/75079f679b196d06904de2a63c5add3948706e2f
2.0.1: Adds graceful shutdown support:
https://github.com/lima-vm/lima/commit/e769391e72d5bc0438b16fcf5cf622a85cb4bc42
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | |_|/
| |/| | |
|
| |/ / /
| | |
| | |
| | | |
Causes non-reproducible CI failures: https://github.com/NixOS/nixpkgs/actions/runs/21102527291/job/60688698991?pr=480436
|
| |\ \ \ |
|
| | |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
https://forgejo.org/2026-01-release-v14-0/
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/14.0.0.md
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
coreth has been moved by upstream into `AvalancheGo`, which is also
packaged in nixpkgs.
Additionally, it has been unmaintained and the Darwin build broken since
2024.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Savannah administrators do not want package maintainers to use
cgit snapshots due to putting strain on the servers and have disabled
cgit snapshots for most if not all of their repositories.
See: https://lists.gnu.org/archive/html/savannah-hackers/2025-12/msg00014.html
Co-authored-by: Philip Taron <philip.taron@gmail.com>
Co-authored-by: LIN, Jian <me@linj.tech>
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
The version 2 release contains breaking changes.
See https://pocket-id.org/docs/setup/major-releases/migrate-v2.
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- https://codeberg.org/OpenRGB/OpenRGB/releases/tag/release_candidate_1.0rc1
> Plugin API has been updated to API version 4 so until the official 1.0
> release, use the latest pipeline builds of the plugins.
- https://codeberg.org/OpenRGB/OpenRGB/releases/tag/release_candidate_1.0rc2
> There have been some upgrades to the user interface since 1.0rc1 and
> some additional device support and fixes.
> The plugin interface and SDK version remain the same as 1.0rc1, so
> plugins that worked with 1.0rc1 should work with 1.0rc2 as well.
As part of updating `withPlugins`, it has been re-implemented as a
wrapper derivation. This means the base package is not re-compiled when
it is used.
Co-authored-by: liberodark <liberodark@gmail.com>
Co-authored-by: Multipixelone <finn@cnwr.net>
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes issues with the help browser by copying vocabulary roots instead
of symlinking them. Although, I am convinced that this is an issue that
should be fixed upstream, eventually.
Fixes #469242
Fixes #474869
|
| | | | | | |
|
| | |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
By moving the zig setup hook to the zig derivation itself, we allow for
zig to splice correctly with `callPackage`, meaning that the correct zig
can be pulled in during builds when zig is in `nativeBuildInputs` (for
example).
This change retains the `zig.hook` attribute for backward compatibility
by just pointing to the zig derivation. This also removes
`zig_default_flags`, since now the setup hook is not a derivation that
can be overridden. Overriding the build flags can now be done by setting
`dontSetZigDefaultFlags = true`.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
activation script (#473367)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
activation script
This deprecation is part of a bigger effort to deprecate activation scripts altogether, which will take place over several releases.
There are no in-tree usages of the now-deprecated reload/restart functionality.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | | |
|