winston
2483668ba5
fuse2: fix aarch64 patch hash
2026-05-31 19:24:58 +02:00
Jack Rosenberg
c7c2309c84
fuse3: modernize
2026-05-17 15:02:58 +02:00
Wolfgang Walther
5a0711127c
treewide: run nixfmt 1.0.0
2025-07-24 13:55:40 +02:00
nixpkgs-ci[bot]
0aa7b55674
Merge master into staging-next
2025-07-06 00:19:50 +00:00
John Titor
766ad54fde
treewide: remove primeos from maintainers
...
Signed-off-by: John Titor <50095635+JohnRTitor@users.noreply.github.com >
2025-07-06 00:00:32 +05:30
Alyssa Ross
243fac58b4
fuse: fix build
...
configure.ac uses the AM_ICONV macro, which is part of gettext. The
patch makes autoreconf recognise the project as using gettext, which
has the added benefit of meaning we no longer need to run makeconf.sh,
and can rely on just the autoreconf from autoreconfHook.
Previously, we were actually doing autoreconf twice; once from the
hook and once from the script, which I doubt was intentional…
2025-06-29 18:12:44 +02:00
Grimmauld
589c3fa0db
fuse3: don't build examples
...
follow-up to #417899
2025-06-20 15:26:25 +02:00
Grimmauld
eeee1ff987
fuse3: Disable failing example builds on musl
2025-06-18 18:13:37 +02:00
Grimmauld
8af813b109
fuse3: don't check udev rules on musl to avoid infinite recursion
2025-06-18 17:49:49 +02:00
Grimmauld
2c14bf92a1
treewide: add udevCheckHook to packages with udev rules output
...
- [x] `{ doInstallCheck = false; name = "acpilight-1.2"; }`
- Configuration file /nix/store/sckm27vsrh58glp3acw07z8jdmpj72q7-acpilight-1.2/etc/udev/rules.d/90-backlight.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
- [x] `{ doInstallCheck = false; name = "airspy-1.0.10"; }`
- propagated via libusb1
- [ ] `{ doInstallCheck = false; name = "alsa-utils-1.2.13"; }`
- /nix/store/pj5lqap32lsaipnmr1pjp8zi6zmc1ng2-alsa-utils-1.2.13/lib/udev/rules.d/90-alsa-restore.rules:16 GOTO="alsa_restore_std" has no matching label, ignoring.
- /nix/store/pj5lqap32lsaipnmr1pjp8zi6zmc1ng2-alsa-utils-1.2.13/lib/udev/rules.d/90-alsa-restore.rules:16 The line has no effect any more, dropping.
- /nix/store/pj5lqap32lsaipnmr1pjp8zi6zmc1ng2-alsa-utils-1.2.13/lib/udev/rules.d/90-alsa-restore.rules:20 GOTO="alsa_restore_std" has no matching label, ignoring.
- /nix/store/pj5lqap32lsaipnmr1pjp8zi6zmc1ng2-alsa-utils-1.2.13/lib/udev/rules.d/90-alsa-restore.rules:20 The line has no effect any more, dropping.
- /nix/store/pj5lqap32lsaipnmr1pjp8zi6zmc1ng2-alsa-utils-1.2.13/lib/udev/rules.d/90-alsa-restore.rules: udev rules check failed.
- [x] `{ doInstallCheck = false; name = "amazon-ec2-net-utils-2.5.5"; }`
- [x] `{ doInstallCheck = true; name = "amazon-ec2-utils-2.2.0"; }`
- has butchered pre/post phases, needs some proper cleaning up
- [x] `{ doInstallCheck = false; name = "android-udev-rules-20250314"; }`
- Configuration file /nix/store/30028n5xqh5lr1lxvm1vsmgxrpyk65fj-android-udev-rules-20250314/lib/udev/rules.d/51-android.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
- [x] `{ doInstallCheck = false; name = "antimicrox-3.5.1"; }`
- [x] `{ doInstallCheck = false; name = "apio-udev-rules-0.9.5"; }`
- Configuration file /nix/store/hh4k648cymsa3dq966f6ivf2l0i528vx-apio-udev-rules-0.9.5/lib/udev/rules.d/70-fpga-ftdi.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
- Configuration file /nix/store/hh4k648cymsa3dq966f6ivf2l0i528vx-apio-udev-rules-0.9.5/lib/udev/rules.d/70-fpga-serial.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
- [x] `{ doInstallCheck = false; name = "argyllcms-3.3.0"; }`
- [ ] `{ doInstallCheck = false; name = "artisan-3.1.4"; }`
- ???? No udev rules
- [x] `{ doInstallCheck = false; name = "asdbctl-1.0.0"; }`
- [x] `{ doInstallCheck = false; name = "asusctl-6.1.12"; }`
- [x] `{ doInstallCheck = true; name = "autorandr-1.15"; }`
- [ ] `{ doInstallCheck = false; name = "bazecor-1.7.0"; }`
- wrapAppImage does not support postInstallCheck: a094b5d8cc/pkgs/build-support/appimage/default.nix (L60-L79)
2025-05-28 10:51:29 +02:00
Yuxuan Shui
6c359f48f3
fuse: move env vars to env.*
...
See #217206
Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com >
2024-11-08 00:59:23 +00:00
oxalica
32ddebd1e3
fuse: split outputs and clean up
...
`fuse` consists of the library and SUID binaries. They serve different
scenarios. Packages depending on libfuse don't want to pull in binaries
which shadow SUID ones like `fusermount` and cause troubles.
With outputs splitted, we can use `fuse.dev` in development environment
without risking shadowing SUID binaries.
The `common` output and top-level `fuse-common` are removed because they
are not useful since a long time ago.
2024-09-30 15:26:38 -04:00
Artturin
e0464e4788
treewide: replace stdenv.is with stdenv.hostPlatform.is
...
In preparation for the deprecation of `stdenv.isX`.
These shorthands are not conducive to cross-compilation because they
hide the platforms.
Darwin might get cross-compilation for which the continued usage of `stdenv.isDarwin` will get in the way
One example of why this is bad and especially affects compiler packages
https://www.github.com/NixOS/nixpkgs/pull/343059
There are too many files to go through manually but a treewide should
get users thinking when they see a `hostPlatform.isX` in a place where it
doesn't make sense.
```
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv.is" "stdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv'.is" "stdenv'.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "clangStdenv.is" "clangStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "gccStdenv.is" "gccStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenvNoCC.is" "stdenvNoCC.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "inherit (stdenv) is" "inherit (stdenv.hostPlatform) is"
fd --type f "\.nix" | xargs sd --fixed-strings "buildStdenv.is" "buildStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "effectiveStdenv.is" "effectiveStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "originalStdenv.is" "originalStdenv.hostPlatform.is"
```
2024-09-25 00:04:37 +03:00
6t8k
dd4f12ef27
fuse3: 3.11.0 -> 3.16.1
...
https://github.com/libfuse/libfuse/blob/fuse-3.16.1/ChangeLog.rst#libfuse-3161-2023-08-08
One change can be expected to break some setups:
- Unsupported mount options are no longer silently accepted [1]
For example, sshfs built against the present libfuse 3.11.0,
`$ sshfs 127.0.0.1:/home/test/testdir /home/test/sshfs_mnt -o atime`
terminates successfully (with the mount point established), while when
built against 3.16.1, it outputs the error message `fuse: unknown
option(s): `-o atime'` and terminates with exit status 1.
2023-10-22 19:44:51 +02:00
Weijia Wang
0db685d18a
fuse: patch against loongarch64-linux
2023-04-27 20:06:21 +03:00
Guillaume Girol
33afbf39f6
treewide: switch to nativeCheckInputs
...
checkInputs used to be added to nativeBuildInputs. Now we have
nativeCheckInputs to do that instead. Doing this treewide change allows
to keep hashes identical to before the introduction of
nativeCheckInputs.
2023-01-21 12:00:00 +00:00
Martin Weinelt
d0bfb3ccbb
Merge remote-tracking branch 'origin/master' into staging-next
2022-03-31 03:49:37 +02:00
Sandro Jäckel
1c0f4cb809
fuse: fix nix-update/nix-prefetch crashing
...
error: attribute 'homepage' missing
at ~/src/nixpkgs/pkgs/os-specific/linux/fuse/common.nix:91:21:
90|
91| meta = with lib; {
| ^
92| description = "Library that allows filesystems to be implemented in user space";
2022-03-30 00:17:03 +02:00
Maximilian Bosch
8631ba18ee
fuse: fix build w/glibc-2.34
...
`closefrom` is now a part of `glibc-2.34`[1]:
> * The function closefrom has been added. It closes all file descriptors
> greater than or equal to a given integer. This function is a GNU extension,
> although it is also present in other systems.
Failing Hydra build: https://hydra.nixos.org/build/152456339
[1] https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html
2022-02-27 10:25:36 +01:00
Alyssa Ross
917218e8e2
fusePackages: don't manually enableParallelBuilding
...
This is automatic for Meson builds.
2021-05-12 11:57:35 +00:00
Guillaume Girol
0c9ed22e64
Merge pull request #119562 from symphorien/fusermountsetuid
...
fuse: fix mount.fuse -o setuid=...
2021-04-30 14:26:39 +00:00
Symphorien Gibol
fbb8dbdac6
fuse: fix mount.fuse -o setuid=...
...
when mounting a fuse fs by fstab on can write:
/nix/store/sdlflj/bin/somefuseexe#argument /mountpoint fuse setuid=someuser
mount is run by root, and setuid is a way to tell mount.fuse to run
somefuseexe as someuser instead. Under the hood, mount.fuse uses su.
The problem is that mount is run by systemd in a seemingly very empty
environment not containing /run/current-system/sw/bin nor
/run/wrappers/bin in $PATH, so mount fails with "su command not found".
We now patch the command to run su with an absolute path.
man mount.fuse3 indicates that this option is reserved to root (or with
enough capabilities) so not using
/run/wrappers/bin/su is thus correct. It has the very small advantage of
possibly working on non nixos.
2021-04-17 21:51:40 +02:00
Michael Weiss
4e90ff6e61
fuse3: 3.10.2 -> 3.10.3
2021-04-12 13:45:51 +02:00
Ben Siraphob
16d91ee628
pkgs/os-specific: stdenv.lib -> lib
2021-01-17 23:26:08 +07:00
Profpatsch
4a7f99d55d
treewide: with stdenv.lib; in meta -> with lib;
...
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
2021-01-11 10:38:22 +01:00
Graham Christensen
bc49a0815a
utillinux: rename to util-linux
2020-11-24 12:42:06 -05:00
Michael Weiss
33473c422c
fuse3: 3.9.4 -> 3.10.0 ( #100075 )
2020-10-10 12:51:49 +02:00
Michael Weiss
a3c71c3e5d
fuse3: 3.9.2 -> 3.9.4 ( #95072 )
...
Note: Version 3.9.3 and 3.9.4 are equivalent:
"This was an "accidental" release, it is equivalent to 3.9.3."
2020-08-10 16:04:55 +02:00
Michael Weiss
68e9ddacc2
fuse3: 3.9.0 -> 3.9.1 ( #82999 )
2020-03-21 21:41:37 +01:00
volth
c814d72b51
treewide: name -> pname
2019-08-17 10:54:38 +00:00
Michael Weiss
50464716e3
fuse3: 3.6.1 -> 3.6.2
2019-07-10 13:29:00 +02:00
Michael Weiss
f2cfc158b2
fuse,fuse3: Avoid unnecessary build warnings
...
Do not set FUSERMOUNT_DIR since we already set it though
NIX_CFLAGS_COMPILE.
Setting it twice results in a lot of warnings like this one:
<command-line>:0:0: warning: "FUSERMOUNT_DIR" redefined
which makes the build look potentially broken.
This doesn't affect the result but fuse3 will now build without any
warnings and building fuse yields less warnings.
2019-06-14 22:09:15 +02:00
Vladimír Čunát
765d695b89
Merge branch 'staging-next'
...
Security fixes for a few packages are included.
2018-08-21 15:36:02 +02:00
Markus Kowalewski
da7a32ef17
fuse: add license
2018-08-20 00:47:52 +02:00
Jan Malakhovski
662756bb6d
fuse: make tests run, but disable
2018-08-11 09:35:31 +00:00
volth
52f53c69ce
pkgs/*: remove unreferenced function arguments
2018-07-21 02:48:04 +00:00
Michael Weiss
fa6941f108
fuse3: 3.2.3 -> 3.2.4
2018-07-13 16:43:21 +02:00
Michael Weiss
d3e3e131f5
fuse3: 3.2.2 -> 3.2.3
2018-05-11 22:12:53 +02:00
Michael Raskin
085eab7ef6
fuse3: install fuse.conf without execute bit
2018-04-01 23:02:25 +02:00
Michael Weiss
c00b5bf6a2
fuse3: 3.2.1 -> 3.2.2
...
Stop using bin/mount.fuse from fuse3 for fuse2 (mount.fuse from fuse3
isn't guaranteed to remain backwards compatible).
2018-04-01 01:55:14 +02:00
Shea Levy
ed5bd8ad49
fuse: Fix cross-compilation
2018-02-28 15:01:32 -05:00
Michael Weiss
f46003798e
fuse3: 3.2.0 -> 3.2.1
2017-11-15 13:42:44 +01:00
Michael Weiss
1a9467edd5
fuse3: 3.1.1 -> 3.2.0
2017-09-23 21:31:15 +02:00
Michael Weiss
351f5fc585
fuse3: init at 3.1.1
...
This includes fuse-common (fusePackages.fuse_3.common) as recommended by
upstream. But while fuse(2) and fuse3 would normally depend on
fuse-common we can't do that in nixpkgs while fuse-common is just
another output from the fuse3 multiple-output derivation (i.e. this
would result in a circular dependency). To avoid building fuse3 twice I
decided it would be best to copy the shared files (i.e. the ones
provided by fuse(2) and fuse3) from fuse-common to fuse (version 2) and
avoid collision warnings by defining priorities. Now it should be
possible to install an arbitrary combination of "fuse", "fuse3", and
"fuse-common" without getting any collision warnings. The end result
should be the same and all changes should be backwards compatible
(assuming that mount.fuse from fuse3 is backwards compatible as stated
by upstream [0] - if not this might break some /etc/fstab definitions
but that should be very unlikely).
My tests with sshfs (version 2 and 3) didn't show any problems.
See #28409 for some additional information.
[0]: https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
2017-09-21 23:59:46 +02:00
