| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This commit was created by a combination of scripts and tools:
- an ast-grep script to prefix things in meta with `lib.`,
- a modified nixf-diagnose / nixf combination to remove unused `with
lib;`, and
- regular nixfmt.
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
|
|
|
|
|
|
|
|
|
|
This atime-based test fails on some FreeBSD configurations
|
|
https://lists.gnu.org/archive/html/bug-diffutils/2025-04/msg00004.html
|
|
More Rosetta 2 issues. AArch32 can continue coming along for the ride,
I guess.
|
|
|
|
changelog: https://savannah.gnu.org/news/?id=10749
|
|
Changes: https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00003.html
|
|
update-armv56_bootstrap_tools
|
|
test-sigsegv-catch-stackoverflow1 and 2 on Aarch32
Those tests fail on qemu making it impossible to build on other architectures
|
|
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \
--argstr baseRev b32a0943687d2a5094a6d92f25a4b6e16a76b5b7
result/bin/apply-formatting $NIXPKGS_PATH
|
|
Prior to August 2023, any config.guess generated by autoconf will
include a hardcoded /usr/bin/uname invocation for FreeBSD on any
architecture other than arm. This clearly doesn't work under nix.
We must then update or otherwise patch each old config.guess.
|
|
|
|
This reverts commit 45584b3e5a7d25bf7f9dcb4e0a1888c98330c53a.
These work fine now that we have an up-to-date bootstrap tarball for
this platform.
|
|
The tests have never worked on aarch64 musl, so this restores the
previous behaviour on that platform of building successfully even
though the tests don't pass.
Since the tests work on x86_64 musl, and not aarch64 musl, my best
guess having not looked too closely is that the difference is because
aarch64 is stuck on ancient bootstrap tools for musl that cause all
sorts of problems. Hopefully we can revert this once the bootstrap
tools are updated. Having diffutils building is a prerequisite to
doing that.
Fixes: 9588972fe983 ("diffutils: 3.9 -> 3.10")
|
|
The test-c-stack tests hang on x86_64-darwin when they are run under
Rosetta 2. Disabling these tests allows the rest of the tests to run
successfully on that platform.
This is a similar to the issue that affected gnugrep (NixOS#236229).
|
|
Fixes the issue introduced in 3.9 and makes cmp and diff work past Y2K39
|
|
Changes: https://savannah.gnu.org/forum/forum.php?forum_id=10282
|
|
ChangeLog: https://fossies.org/linux/misc/diffutils-3.8.tar.xz/diffutils-3.8/ChangeLog
Will be needed to fix its build with glibc-2.34[1].
[1] https://github.com/NixOS/nixpkgs/pull/133431
|
|
|
|
|
|
Part of: https://github.com/NixOS/nixpkgs/issues/108938
meta = with stdenv.lib;
is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.
This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.
The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
|
|
This adds a warning to the top of each “boot” package that reads:
Note: this package is used for bootstrapping fetchurl, and thus cannot
use fetchpatch! All mutable patches (generated by GitHub or cgit) that
are needed here should be included directly in Nixpkgs as files.
This makes it clear to maintainer that they may need to treat this
package a little differently than others. Importantly, we can’t use
fetchpatch here due to using <nix/fetchurl.nix>. To avoid having stale
hashes, we need to include patches that are subject to changing
overtime (for instance, gitweb’s patches contain a version number at
the bottom).
|
|
|
|
https://savannah.gnu.org/forum/forum.php?forum_id=9341
|
|
HTTP -> HTTPS for :
- http://gnu.org/
- http://www.gnu.org/
- http://elpa.gnu.org/
- http://lists.gnu.org/
- http://gcc.gnu.org/
- http://ftp.gnu.org/ (except in fetchurl mirrors)
- http://bugs.gnu.org/
|
|
|
|
|
|
|
|
|
|
Releases announcements:
3.4: http://lists.gnu.org/archive/html/info-gnu/2016-08/msg00004.html
3.5: http://lists.gnu.org/archive/html/info-gnu/2016-08/msg00010.html
|
|
Was meant to go into staging, sorry
This reverts commit 57b2d1e9b0dcdd1d25bd2d450174764b9417ffc1, reversing
changes made to 760b2b9048ea775c319cb348d74447a20dea513e.
|
|
See http://lists.gnu.org/archive/html/info-gnu/2016-08/msg00004.html
for release announcement.
|
|
Build-tested on x86_64 Linux & Mac.
|
|
Presumably needed due to the last staging merge.
There was some stdenv stage refactoring within, IIRC.
|
|
|
|
|
|
|
|
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs"
sounds like an imperative rather than a noun phrase.
|
|
|
|
|
|
This is a follow-up to 77fdc7bb3583606c86b2dd602b76a20a1bf6bc7c ("GNU
Coreutils: Allow builds with newer versions of glibc.").
|
|
svn path=/nixpkgs/branches/stdenv-updates/; revision=29590
|
|
svn path=/nixpkgs/branches/stdenv-updates/; revision=22942
|
|
After this, the 'bootstrap-tools' can be cross-built.
svn path=/nixpkgs/branches/stdenv-updates/; revision=20945
|
