Package Details: fatx 1.17-2

Git Clone URL: https://aur.archlinux.org/fatx.git (read-only, click to copy)
Package Base: fatx
Description: XBox filesystem support for linux
Upstream URL: http://sourceforge.net/projects/fatx/
Keywords: filesystem xbox
Licenses: GPL
Provides: fatx
Submitter: t3kk3n
Maintainer: t3kk3n
Last Packager: t3kk3n
Votes: 10
Popularity: 0.30
First Submitted: 2014-08-09 19:19 (UTC)
Last Updated: 2024-04-17 15:37 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Pinned Comments

Bakasura commented on 2021-07-24 22:05 (UTC)

@everyone this package works again!

Latest Comments

1 2 3 Next › Last »

t3kk3n commented on 2024-04-29 22:38 (UTC)

Past week ended up getting slightly busy on my end, didn't forget about this.

So, I can replicate the issue with the cmake tests using "pkgctl build", yet if I disable the tests, it compiles as expected. It's definitely a weird issue, as installing the compiled binaries and running them, work as one would think.

I do notice however, there is decent change in file size, from compiling via pkgctl, versus compiling on my daily driver laptop. I'm a tiny bit stuck, as I have never troubleshot cmake tests or the like, letalone this is my first time working with pkgctl officially. If anyone has any input, I am all ears!

@katt - That being said, if you comment out the tests and compile, are you able to successfully use fatx?

katt commented on 2024-04-20 09:38 (UTC)

@t3kk3n Sure, here's the output: https://gist.github.com/kattjevfel/39581c185f7d9a24ec634d48e5ace952

To try and cut down on any customization this was built with pkgctl build, which anyone with devtools can do.

Also given your responses thus far, do the tests work on your machine then?

t3kk3n commented on 2024-04-19 17:50 (UTC)

@katt - Could you add the --verbose argument to ctest in the check function and rerun?

Side note - technically I could remove the check function, but would rather not.

katt commented on 2024-04-19 14:20 (UTC)

@t3kk3n I am building for x86_64-v3 with aurutils in a chroot. Skipping the tests would obviously work since that's what's failing.

As for information that would help, build in a chroot I guess :P

t3kk3n commented on 2024-04-19 11:32 (UTC)

katt - I'm unable to replicate what you are experiencing; What architecture are you compiling on? Have you tried compiling without running the tests? Any other information that could help?

katt commented on 2024-04-18 22:15 (UTC)

Tests are failing:

24% tests passed, 16 tests failed out of 21

Total Test time (real) =   1.05 sec

The following tests FAILED:
          1 - Fuse_simple_file_creation (Failed)
          2 - Fuse_moving_file (Failed)
          3 - Fuse_removing_file (Failed)
          4 - Fuse_multiple_file_access (Failed)
          5 - Fuse_directory_copies (Failed)
          6 - Fuse_simultaneous_copies (Failed)
          7 - Fuse_directory_max_entries (Failed)
          8 - Fuse_recover_mode (Failed)
          9 - Fuse_FAT_stress (Failed)
         10 - Fuse_directory_entries_stress (Failed)
         11 - Fuse_simultaneous_creations (Failed)
         12 - Fuse_check_statfs (Failed)
         14 - Label_check_noname (Failed)
         18 - Unrm_remote_recovery (Failed)
         19 - Unrm_remote_dir_recovery (Failed)
         20 - Unrm_local_recovery (Failed)
Errors while running CTest
==> ERROR: A failure occurred in check().
    Aborting...
==> Removing chroot copy [/var/lib/aurbuild/x86_64/katt-229284]...done
==> ERROR: Build failed

t3kk3n commented on 2024-04-17 15:38 (UTC)

@sl1pkn07 - Dang, you are fast haha. Was already working on that, thank you though.

Package is fully up to date and working as of now, cheers!

sl1pkn07 commented on 2024-04-17 13:47 (UTC)

error: failed to commit transaction (conflicting files) fatx: /usr/sbin exists in filesystem (owned by filesystem)

seems needs -DCMAKE_INSTALL_BINDIR=/usr/bin or something similar

t3kk3n commented on 2024-04-16 20:03 (UTC)

I shall take over maintainer duties, noticed someone tried to adopt this, then immediately disowned it. (I have the time nowadays)

Bakasura commented on 2023-01-23 23:04 (UTC)

@dkeruza I do not have an HDD to try at this time, however, I remember that with the "fusefatx" command even with GID and UID, in Nautilus the mount point seemed to belong to root, but at the time of making an "ls" in the terminal, the permits were correct.

In conclusion, I perform all operations by the terminal

I think it's a bug in software.