| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | |\
| | |
| | | |
erlang_26: 26.2.2 -> 26.2.3
|
| | | | |
|
| |\| | |
|
| | |\ \
| | |/
| |/| |
rakudo: 2023.08 -> 2024.01
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
modules
This reverts commit ca6452f8edba8aaf9252b692ac821f1313ec9e7a.
Regressions appeared and they need time to get resolved; see:
https://github.com/NixOS/nixpkgs/pull/289135#issuecomment-1978270396
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
rascal: 0.28.2 -> 0.33.8
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
zef: 0.21.2 -> 0.21.4
|
| | | | |/
| | |/| |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Diff: https://github.com/luau-lang/luau/compare/614...0.615
Changelog: https://github.com/luau-lang/luau/releases/tag/0.615
|
| |\| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The end of life for Python 3.8 is scheduled for 2024/10. As such it
cannot be a part of NixOS 24.05, because its support cycle goes past
that.
|
| |\| | | |
|
| | |\ \ \
| | | | |
| | | | | |
treewide: use finalAttrs in packages maintained by @fgaz
|
| | | | | | |
|
| | | |/ / |
|
| |\| | | |
|
| | | | | |
|
| |\| | | |
|
| | |\ \ \
| | | | |
| | | | | |
sbcl, ecl, clisp: set meta.mainProgram
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \ |
|
| | |\| | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\| | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
pythonCatchConflictsHook: avoid infinite recursion
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add test case where a package enlists
itself as propagated build input.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Albeit counter-intutive, the `propagatedBuildInputs`
mechanism and the corresponding package files in
`nix-support/propagated-build-inputs`
can form a dependency cycle.
This can happen if a package adds itself to this file,
or if multiple outputs of one derivation reference each other.
An example for this is the `patchPpdFilesHook`:
In its mission to collect dependency packages with binaries
that might be required by the dependent package to be created,
it sometimes picks up the dependent package itself.
This indicates that if a file of the dependent package
is used, the package itself should also be installed.
In the case of a multiple output package,
it is also possible that two outputs depend on each other,
creating a dependency cycle.
Since commit 2651ddc7b0788932df9da7416ccd1618d76c11fe,
the `find_packages` function in `catch_conflicts.py`
recursively collects all `propagated-build-inputs` files.
If it encounters a dependency cycle, it must not follow the
cycle to avoid infinite recursion (and a stack overflow).
The commit at hand adds a check so that the function skips over
a package that it already encountered and processed earlier.
This does not loosen the script's checks as the script
still recursively collects all propagated build inputs.
|
| |\| | | | |
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
luau: 0.613 -> 614
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Diff: https://github.com/luau-lang/luau/compare/0.613...614
Changelog: https://github.com/luau-lang/luau/releases/tag/614
|
| |\| | | | |
|
| | |\| | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\| | | |
|
| | | |\ \ \
| | | | | |
| | | | | | |
babashka-unwrapped: 1.3.188 -> 1.3.189
|
| | | | | | | |
|
| | | |\ \ \ \
| | | |/ / /
| | |/| | | |
cpython: allow full variant on all platformns where bluez is available
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes: #289113
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
previously, when the lua setup hook found a system lua module,
it would simply add that library to LUA_PATH, meaning the default
path would no longer be used.
for luajit, this bug would always occur, due to it having
several inbuilt libraries such as luabitop.
lua5 still passed unit tests, simply because the test
environment doesn't include any system lua libaries,
but the bug would still occur if lua5 was used in a derivation with
a buildInput from luaPackages, since that package would be found by
the envHook and overwrite the default path.
now, the setup hook will use any system module paths in addition to
the default path, instead of overriding it.
|
| |\| | | | |
|