Search Criteria
Package Details: mergerfs 2.42.0-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mergerfs.git (read-only, click to copy) |
|---|---|
| Package Base: | mergerfs |
| Description: | Featureful union filesystem. Combines directories from various filesystems into a storage pool |
| Upstream URL: | https://github.com/trapexit/mergerfs |
| Keywords: | filesystem fuse |
| Licenses: | ISC |
| Submitter: | pheerai |
| Maintainer: | willemw |
| Last Packager: | willemw |
| Votes: | 46 |
| Popularity: | 0.143248 |
| First Submitted: | 2015-10-23 12:47 (UTC) |
| Last Updated: | 2026-05-09 12:34 (UTC) |
Dependencies (4)
- lshw (lshw-gitAUR)
- lsb-release (optional) – for mergerfs.collect-info
- lshw (lshw-gitAUR) (optional) – for mergerfs.collect-info
- mergerfs-tools-gitAUR (optional) – manage data in a pool
Required by (2)
- rbdoom-3-bfg (optional)
- try-git
Latest Comments
« First ‹ Previous 1 2 3 4 5 Next › Last »
willemw commented on 2020-12-21 08:43 (UTC)
@trumee: it might be worth checking and/or reporting that upstream (https://github.com/trapexit/mergerfs#mergerfs-or-libfuse-crashing).
trumee commented on 2020-12-21 06:20 (UTC)
I was getting "Transport endpoint not connected" with kernel linux-lts-5.4.83-1 and mergerfs-2.32.1-1-x86_64.pkg.tar.xz.
Reverting back to 5.4.77-1-lts and mergerfs-2.31.0-1-x86_64.pkg.tar.xz resolved the issue for me.
willemw commented on 2020-03-25 00:08 (UTC)
@Sparticuz:
My point was that it is not necessary to extend "arch" in order to build on ARM.
Even ArchLinuxARM themselves don't do it for their own repository packages. Not even for modified PKGBUILD files specific for ARM (https://github.com/archlinuxarm/PKGBUILDs).
Sparticuz commented on 2020-03-24 23:57 (UTC)
@willemw I think what @cryzed is saying is that it builds just fine on arm, so adding arm would allow the package to be built on arm. In fact, looking at debians package, they have a bunch of different Arch's. https://packages.debian.org/stretch/utils/mergerfs ... Unless I'm missing something?
willemw commented on 2020-03-24 23:40 (UTC)
@cryzed:
"any" will create a ...-any.pkg.tar.zst package file, which you can install on any platform. Used for installing script files, which are portable.
"x86_64" will create a ...-x86_64.pkg.tar.zst package file, which you can only install on a x86_64 platform. Used for compiled packages, which are only binary compatible with a specific platform.
willemw commented on 2020-03-24 23:19 (UTC)
@cryzed:
I prefer not to extent the "arch" array. Most packages, that are compiled, don't do that (otherwise it would mean updating a lot of PKGBUILD files).
You can use "makepkg --ignorearch" (indirectly through an AUR helper) to build packages on other platforms. ArchLinuxARM even used to mention this in their Wiki.
Extending the "arch" array is, for example, useful for *-bin packages.
cryzed commented on 2020-03-24 23:02 (UTC)
@willemw thanks, but what about extending the
archarray?willemw commented on 2020-03-24 20:22 (UTC)
@cryzed: Thanks. Added fuse2.
cryzed commented on 2020-03-24 20:12 (UTC) (edited on 2020-03-24 20:13 (UTC) by cryzed)
You should define
fuse2as an optional dependency, it's needed to get mergerfs to work with/etc/fstab. Also I tested this successfully on a Raspberry Pi 4, the architecturearmv7hcan be added to thearcharray.« First ‹ Previous 1 2 3 4 5 Next › Last »