| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
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`.
|
|
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
|
|
activation script (#473367)
|
|
- 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>
|
|
The version 2 release contains breaking changes.
See https://pocket-id.org/docs/setup/major-releases/migrate-v2.
|
|
|
|
|
|
|
|
|
|
|
|
Nixpkgs config, for defining things like which licenses are
permitted, can either be an attrset or a function that is passed a
`pkgs` argument. Evaluating that `pkgs` argument requires computing the
Nixpkgs fixpoint, which requires checking whether the derivations used
in the Nixpkgs bootstrap have valid licenses. This works provided
nothing tries to use Nixpkgs functions to validate or merge anything
included in the configuration.
f5deefd4631e (config: add and document {allow,block}listedLicenses,
2025-08-31), in #437723, added type checking and merging to the lists of
permitted/forbidden licenses. That resulted in a recursion loop if a
list of licenses included, say, `pkgs.lib.licenses.bsd0`.
To allow licenses to be specified from Nixpkgs' library, pass `lib` as
well as `pkgs` to any config function. Computing `lib` doesn't require
working out the full Nixpkgs fixpoint. The change in #437723 will still
break things for some people, but it at least provides a sensible route
to getting the config working again.
Fixes #456994.
|
|
As @uninsane points out, these are designed to rot rapidly.
|
|
|
|
(#476820)
|
|
|
|
|
|
This will become part of the 26.05 release notes, not the already
released 25.11.
|
|
|
|
|
|
|
|
|
|
0.10.0-unstable-2025-12-29
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Matt Sturgeon <matt@sturgeon.me.uk>
|
|
Adds a nixos module for configuring `pkgs.nextcloud-spreed-signaling`
and running it as a systemd service. This allows setting up a "High
Performance Backend" for use with Nextcloud Talk.
|
|
|
|
|
|
|
|
|
