| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
stress-ng: 0.10.19 -> 0.11.01
|
| | |
|
|\ \
| | |
| | | |
ipmitool: migrate to openssl 1.1
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* remove no-op substitution of s6_addr16 -> s6_addr
This string doesn't exist anymore in that file.
* clean up configureFlags
|
| | |
| | |
| | |
| | |
| | |
| | | |
This adds a patch from debian to switch ipmitool to openssl 1.1.
Upstream seems to already carry a version of this but that is yet to be
part of a release.
|
|\ \ \
| | |/
| |/| |
Staging next
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| |_|/
|/| | |
bfs: 1.5.2 -> 1.6
|
| |/ |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
s-tui: migrate to python3
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Includes LC_ALL = "en_US.UTF-8"; that resolves a locale.Error exception
during the check phase.
[...]
File "/build/s-tui-1.0.0/s_tui/sensors_menu.py", line 27, in <module>
import urwid
File "/nix/store/xxhpq1kcjy0kimfwnwqlzh2pchkp9khi-python3.7-urwid-2.1.0/lib/python3.7/site-packages/urwid/__init__.py", line 26, in <module>
from urwid.widget import (FLOW, BOX, FIXED, LEFT, RIGHT, CENTER, TOP, MIDDLE,
File "/nix/store/xxhpq1kcjy0kimfwnwqlzh2pchkp9khi-python3.7-urwid-2.1.0/lib/python3.7/site-packages/urwid/widget.py", line 27, in <module>
from urwid.util import (MetaSuper, decompose_tagmarkup, calc_width,
File "/nix/store/xxhpq1kcjy0kimfwnwqlzh2pchkp9khi-python3.7-urwid-2.1.0/lib/python3.7/site-packages/urwid/util.py", line 61, in <module>
detected_encoding = detect_encoding()
File "/nix/store/xxhpq1kcjy0kimfwnwqlzh2pchkp9khi-python3.7-urwid-2.1.0/lib/python3.7/site-packages/urwid/util.py", line 58, in detect_encoding
locale.setlocale(locale.LC_ALL, initial)
File "/nix/store/ja04f3cmapzb3f2mvjrb883bfqclsirq-python3-3.7.6/lib/python3.7/locale.py", line 608, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
|
|\ \
| | |
| | | |
plan9port: fix linker flags for macosx
|
| | | |
|
| |/ |
|
|/ |
|
|\
| |
| | |
ytop: 0.4.0 -> 0.5.1
|
| | |
|
|/
|
|
|
| |
Same as efivar; I believe it doesn't really needs LTO. I checked:
nix build -f nixos/release-combined.nix nixos.iso_minimal.i686-linux
|
|\
| |
| | |
mq-cli: upgrade cargo fetcher and cargoSha256
|
| |
| |
| |
| | |
Infra upgrade as part of #79975; ran `nixpkgs-review wip` successfully.
|
| |
| |
| |
| | |
I don't think it really needs LTO.
|
|/
|
|
| |
Infra upgrade as part of #79975; ran `nixpkgs-review wip` successfully.
|
|
|
|
|
| |
As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified
is now `false`.
|
|\
| |
| | |
stress-ng: 0.10.16 -> 0.10.19
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Changes the default fetcher in the Rust Platform to be the newer
`fetchCargoTarball`, and changes every application using the current default to
instead opt out.
This commit does not change any hashes or cause any rebuilds. Once integrated,
we will start deleting the opt-outs and recomputing hashes.
See #79975 for details.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has several advantages:
1. It takes up less space on disk in-between builds in the nix store.
2. It uses less space in the binary cache for vendor derivation packages.
3. It uses less network traffic downloading from the binary cache.
4. It plays nicely with hashed mirrors like tarballs.nixos.org, which only
substitute --flat hashes on single files (not recursive directory hashes).
5. It's consistent with how simple `fetchurl` src derivations work.
6. It provides a stronger abstraction between input src-package and output
package, e.g., it's harder to accidentally depend on the src derivation at
runtime by referencing something like `${src}/etc/index.html`. Likewise, in
the store it's harder to get confused with something that is just there as a
build-time dependency vs. a runtime dependency, since the build-time
src dependencies are tarred up.
Disadvantages are:
1. It takes slightly longer to untar at the start of a build.
As currently implemented, this attaches the compacted vendor.tar.gz feature as a
rider on `verifyCargoDeps`, since both of them are relatively newly implemented
behavior that change the `cargoSha256`.
If this PR is accepted, I will push forward the remaining rust packages with a
series of treewide PRs to update the `cargoSha256`s.
|
|\
| |
| | |
ioping: 1.1 -> 1.2
|
| | |
|
| | |
|
|\ \
| | |
| | | |
lr: 1.5 -> 1.5.1
|
| | | |
|
|\ \ \
| | | |
| | | | |
java-service-wrapper: 3.5.41 -> 3.5.42
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
jump: 0.30.0 -> 0.30.1
|
| |/ |
|
|/
|
|
|
|
|
| |
ofborg does not build them yet, but at least nixpkgs-update does.
https://github.com/ryantm/nixpkgs-update/pull/118
Note this test passes and would not have detected
https://github.com/NixOS/nixpkgs/issues/79304
|
|\
| |
| | |
ytop: init at 0.4.0
|
| | |
|
|\ \
| |/
|/| |
Staging next
|
| |\ |
|
| | | |
|