| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| |\
| |
| | |
mergerfs: 2.22.1 -> 2.23.0
|
| | | |
|
| |/
|
|
|
|
|
| |
It was being parsed incorrectly, as noted on
https://github.com/NixOS/nix/issues/1440
nix-repl> builtins.parseDrvName ntfs3g.name
{ name = "ntfs"; version = "3g-2017.3.23"; }
|
| |\
| |
| | |
Fixup various setuid/setgid permission problems, part 2
|
| | | |
|
| |\ \
| | |
| | | |
mergerfs: 2.16.1 -> 2.22.1
|
| | |/ |
|
| |/ |
|
| |
|
|
| |
related to #26600
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Or else `services.udev.packages = [ bcache-tools ]` cannot be used.
To not break bcache in the initrd I'm modifying this in stage-1.nix:
- --replace /bin/sh ${extraUtils}/bin/sh
+ --replace ${bash}/bin/sh ${extraUtils}/bin/sh
Reasoning behind that change:
* If not modifying the /bin/sh pattern in any way, it will also match
${bash}/bin/sh, creating a broken path like
/nix/store/HASH-bash/nix/store/HASH-bash/bin/sh in the udev rule file.
* The addition of /bin/sh was done in 775f381a9e34
("stage-1: add bcache support"). It seems somewhat plausible that
no new users have appeared since then and we can take this opportunity
to back out of this change without much fear of regressions.
If there _are_ regressions, they should be in the form of build time
errors, not runtime (boot), due to how the udev rule output is checked
for invalid path references. So low risk, IMHO.
* An alternative approach could be to copy the /bin/sh substitute rule
over to the non-initrd udev rules implementation in NixOS, but I think
this way is better:
- The rules file comes with a working path out of the box.
- We can use more precise pattern matching when modifying the udev
rules for the initrd.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
So that
$ nix-build -A bcache-tools.src
gives
/nix/store/HASH-bcache-tools-1.0.7.tar.gz
instead of
/nix/store/HASH-v1.0.7.tar.gz
|
| |\
| |
| | |
Fix: GlusterFS python tools all have import errors
|
| | | |
|
| | |
| |
| |
| | |
I checked for determinism with `nix-build --option build-repeat 10`.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Done by setting PATH and PYTHONPATH appropriately.
Adds the following patches:
* One that removes hardcodes to /sbin, /usr/bin, etc.
from gluster, so that programs like `lvm` and `xfs_info` can be
called at runtime; see https://bugzilla.redhat.com/show_bug.cgi?id=1450546.
* One that fixes unsubstituted autoconf macros in paths (a problem
in the 3.10 release); see https://bugzilla.redhat.com/show_bug.cgi?id=1450588.
* One that removes uses of the `find_library()` Python function that does
not behave as expected in Python < 3.6 (and would not behave correctly
even on 3.6 in nixpkgs due to #25763);
see https://bugzilla.redhat.com/show_bug.cgi?id=1450593.
I think that all of these patches should be upstreamed.
Also adds tests to check that none of the Python based utilities
throw import errors, calling `--help` or equivalent on them.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is because the source tarball available on
https://download.gluster.org/pub/gluster/glusterfs/3.10/3.10.1/glusterfs-3.10.1.tar.gz
has different contents than the v3.10.1 tag;
for example, it lacks the file `xlators/features/ganesha/src/Makefile.am`,
which the tag has.
This is because GluserFS's release process removes some unused files.
This made impossible to apply patches written by or for upstream, as those
are written against what's in upstream's git.
As a nice side effect, we no longer have to hardcode the "3.10" in the
`3.10/${version}` part of the URL.
|
| | |
| |
| |
| |
| | |
They were made unnecessary in commit d07154b3bc8, which added
`makeFlags = "DESTDIR=$(out)";`.
|
| | | |
|
| |\ \
| | |
| | | |
bcachefs-tools: init at a588eb0
|
| | |/ |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
irods: init at 4.2.0
|
| | | |
|
| |\ \
| | |
| | | |
Introduce `mapNullable` into lib and use it in a few places
|
| | | |
| | |
| | |
| | | |
Also simply some configure flag logic my grep also alerted me too.
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit c0cef0425eff1db8ddc07e78ea5aa16eb4a9666b.
The output of the command-line tool has changed somewhat and at least
nixos-generate-config.pl needs modifications to match. I'm leaving that
to someone who knows a bit more about btrfs.
Issue #24810.
|
| | | | |
| | | |
| | | |
| | | | |
http://hydra.nixos.org/build/51461475
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| |/ / |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Mark linux-only pkgs
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
mtools: fix build on darwin
|
| | |/ / |
|
| |/ /
| |
| |
| | |
build from source, not the release configure scripts already generated
|
| | |
| |
| |
| |
| | |
It's sad, but he's been inactive for the last five years.
Keeping such people in meta.maintainers is counter-productive.
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
gitfs: 0.2.5 -> 0.4.5.1
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| | |
* mhddfs: fix-format-security
* mhddfs: use fputs instead of fprintf
|