Search Criteria
Package Details: python-mfusepy 3.1.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/python-mfusepy.git (read-only, click to copy) |
|---|---|
| Package Base: | python-mfusepy |
| Description: | Ctypes bindings for the high-level API in libfuse 2 and 3 |
| Upstream URL: | https://github.com/mxmlnkn/mfusepy |
| Licenses: | ISC |
| Submitter: | Universebenzene |
| Maintainer: | Universebenzene |
| Last Packager: | Universebenzene |
| Votes: | 1 |
| Popularity: | 0.001395 |
| First Submitted: | 2025-06-23 08:59 (UTC) |
| Last Updated: | 2026-03-13 01:53 (UTC) |
Dependencies (9)
- python
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- fuse2 (check)
- python-ioctl-opt (check)
- python-pytest-order (check)
- fuse2 (optional)
- fuse3 (fuse3-gitAUR) (optional)
Required by (3)
- gitfourchette-bin (optional)
- gitfourchette-git (optional)
- ratarmount
Latest Comments
mxmln commented on 2026-03-12 23:03 (UTC) (edited on 2026-03-13 00:01 (UTC) by mxmln)
Hello, I am getting this error when trying to install it:
I don't understand what's going wrong. I even have python-setuptools installed and the correct version (82) at that:
Could it be that 82.0.1-1 does not match <=82?!
Adding
into the 'prepare' section, actually fixes the problem ... I am flabbergasted about this version matching, argh. I will try to fix it upstream.
The error could also be resolved by removing the --no-isolation flag. That would also make it future-safe in case python-setuptools gets updated past 82. Removing the flag helps in my local test, but https://wiki.archlinux.org/title/Python_package_guidelines has this flag, so I am not sure whether it is good style to remove it. But I think there is no other way in the future because of this most obnoxious API break in setuptools: https://github.com/pypa/setuptools/issues/4903 . Installing an older installation in an isolated build seemed like the best solution to me, but I forgot that AUR builds without isolation.
If you want, it would also be nice if you could add me as a contributor so that I can configure automatic AUR updates in my CI. Check out the details in the ratarmount AUR PKGBUILD header.
I am looking into this because of this recent comment asking for optional fuse3 support: https://aur.archlinux.org/packages/ratarmount#comment-1062767 . My idea was to change the fuse2 dependency to fuse2|fuse3. I wanted to test out how this would behave, e.g., if it would ask if neither is installed, but I encountered the above issue.
Trying to install this with makepkg also seems to install fuse2. I see that fuse2 is only listed in "checkdepends". Maybe it could be configured to install fuse3 instead? I think it's time to slowly move away from fuse2 as the default, if possible.