| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Util-linux does not fail when crypt() isn't available. It just doesn't
build sulogin, which in turn breaks the initrd-builder for the
systemd-stage-1 tests.
|
|
|
|
https://kernel.org/pub/linux/utils/util-linux/v2.38/v2.38-ReleaseNotes
|
|
Introduce new boolean arguments "pamSupport" and "capabilitiesSupport" that
control whether "pam" and "libcap" are compiled in. These flags are true by
default, so this commit does not cause any rebuilds.
|
|
|
|
Prior to this commit, util-linux supported compilation without systemd
if systemd==null. This commit preserves that behavior, and
additionally triggers it when the global systemdSupport attr is set to
false. The systemdSupport argument is understood by many other
nixpkgs expressions and can be set globally in
~/.config/nixpkgs/config.nix.
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
repology
|
|
Fixes: CVE-2022-0563
|
|
|
|
[staging-next] Revert "util-linux: fix static build"
|
|
This reverts commit 1f0ef842ca88a57613faf1ef4cd9a5d4e77efd81. The
underlying issue was fixed in 2ebeb02a99a ("stdenv/setup: tell libtool
about library paths"), so we don't need a workaround in util-linux any
more.
|
|
|
|
|
|
|
|
These programs are both still built even when we don't pass the
flags. (It appears that this was not the case when they were added to
the expression.)
|
|
The "minimal" argument just removed some files to reduce package
size. Now that we have multiple output derivations in Nixpkgs (we
didn't when "minimal" was added), we can just throw more outputs at
this problem and get the same effect, with the advantage that those
files are actually there, available for download without a rebuild, if
they're ever needed.
I've tested that with this change, there's no difference in the
closure size of util-linuxMinimal.bin.
We have to set SYSCONFSTATICDIR to stop $bin/bin/agetty looking in
$out for issue or issue.d. SYSCONFSTATICDIR is supposed to be for
configuration that comes with a package, but it's currently only used
for finding an issue, and util-linux doesn't come with any issue
files, so I'm not really sure what the point is...
|
|
Removing the locales after they've been built and installed is a big
hack when util-linux gives us an option to disable them directly.
This way, the code in util-linux that deals with locales can be
disabled as well, leading to a (very small) size reduction.
|
|
Quoting uuidd(8), as generated prior to this commit:
> By default, the pid file is written to
> /nix/store/6ig1awrlxd‐nadna38kxgfvds9kfr6ny2-util-linux-2.36.2/var/run/uuidd/uuidd.pid.
That's not right...
|
|
This was probably needed for scriptrelay(1) before it was rewritten
from Perl to C in util-linux 2.14. I've checked with Diffoscope that
after removing the build input, the result is bit-for-bit identical
except for the different prefix.
|
|
|
|
|
|
|
|
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
|
|
|
|
https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.36/v2.36.1-ReleaseNotes
|
|
|
|
|
|
|
|
|
|
This wasn’t updated when adding the bin output.
|
|
|
|
|
|
https://lkml.org/lkml/2019/4/9/474
|
|
|
|
|
|
https://www.kernel.org/pub/linux/utils/util-linux/v2.33/v2.33.1-ReleaseNotes
https://www.kernel.org/pub/linux/utils/util-linux/v2.33/v2.33.1-ChangeLog
|
|
https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.33/v2.33-ReleaseNotes
|
|
Commits from master, conflict resolutions, etc.
|
|
Introduced in that f83b5e4 refactoring as well.
Thanks Dezgeg for noticing!
|
|
treewide: enable working, fix fixable, disable broken tests
|
|
|
|
|
|
|
|
More cleanup will come later
|
|
* substitute(): --subst-var was silently coercing to "" if the variable does not exist.
* libffi: simplify using `checkInputs`
* pythonPackges.hypothesis, pythonPackages.pytest: simpify dependency cycle fix
* utillinux: 2.32 -> 2.32.1
https://lkml.org/lkml/2018/7/16/532
* busybox: 1.29.0 -> 1.29.1
* bind: 9.12.1-P2 -> 9.12.2
https://ftp.isc.org/isc/bind9/9.12.2/RELEASE-NOTES-bind-9.12.2.html
* curl: 7.60.0 -> 7.61.0
* gvfs: make tests run, but disable
* ilmbase: disable tests on i686. Spooky!
* mdds: fix tests
* git: disable checks as tests are run in installcheck
* ruby: disable tests
* libcommuni: disable checks as tests are run in installcheck
* librdf: make tests run, but disable
* neon, neon_0_29: make tests run, but disable
* pciutils: 3.6.0 -> 3.6.1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pciutils/versions.
* mesa: more include fixes
mostly from void-linux (thanks!)
* npth: 1.5 -> 1.6
minor bump
* boost167: Add lockfree next_prior patch
* stdenv: cleanup darwin bootstrapping
Also gets rid of the full python and some of it's dependencies in the
stdenv build closure.
* Revert "pciutils: use standardized equivalent for canonicalize_file_name"
This reverts commit f8db20fb3ae382eba1ba2b160fe24739f43c0bd7.
Patching should no longer be needed with 3.6.1.
* binutils-wrapper: Try to avoid adding unnecessary -L flags
(cherry picked from commit f3758258b8895508475caf83e92bfb236a27ceb9)
Signed-off-by: Domen Kožar <domen@dev.si>
* libffi: don't check on darwin
libffi usages in stdenv broken darwin. We need to disable doCheck for that case.
* "rm $out/share/icons/hicolor/icon-theme.cache" -> hicolor-icon-theme setup-hook
* python.pkgs.pytest: setupHook to prevent creation of .pytest-cache folder, fixes #40273
When `py.test` was run with a folder as argument, it would not only
search for tests in that folder, but also create a .pytest-cache folder.
Not only is this state we don't want, but it was also causing
collisions.
* parity-ui: fix after merge
* python.pkgs.pytest-flake8: disable test, fix build
* Revert "meson: 0.46.1 -> 0.47.0"
With meson 0.47.0 (or 0.47.1, or git)
things are very wrong re:rpath handling
resulting in at best missing libs but
even corrupt binaries :(.
When we run patchelf it masks the problem
by removing obviously busted paths.
Which is probably why this wasn't noticed immediately.
Unfortunately the binary already
has a long series of paths scribbled
in a space intended for a much smaller string;
in my testing it was something like
lengths were 67 with 300+ written to it.
I think we've reported the relevant issues upstream,
but unfortunately it appears our patches
are what introduces the overwrite/corruption
(by no longer being correct in what they assume)
This doesn't look so bad to fix but it's
not something I can spend more time on
at the moment.
--
Interestingly the overwritten string data
(because it is scribbled past the bounds)
remains in the binary and is why we're suddenly
seeing unexpected references in various builds
-- notably this is is the reason we're
seeing the "extra-utils" breakage
that entirely crippled NixOS on master
(and probably on staging before?).
Fixes #43650.
This reverts commit 305ac4dade5758c58e8ab1666ad0197fd305828d.
(cherry picked from commit 273d68eff8f7b6cd4ebed3718e5078a0f43cb55d)
Signed-off-by: Domen Kožar <domen@dev.si>
|
|
|
|
|
|
|
|
|
|
|
