https://bugzilla.redhat.com/show_bug.cgi?id=1631988



--- Comment #8 from Julio Gonzalez Gil <[email protected]> ---
> Did you check to see if fuse 2.8.3 would work? I looked at the commit that 
> changed it to 2.8.4[1], and I don't see anything in it that indicates it was 
> changed in such a way that 2.8.3 couldn't work.

Well, because of the changes at configure.ac, s3fs-fuse does not even build
without a patch, and that's (I guess) the reason Jorge added the requirement,
and I never tried 2.8.3

However if I patch configure.ac to allow 2.8.3, then yes, it compiles and at
least some basic tests are working (mounting the bucket, listing the objects,
getting an object...).

However when running the testsuite, 4 tests failed:

> FAIL: test_truncate_file
> FAIL: test_remove_nonempty_directory
> FAIL: test_special_characters
> FAIL: test_extended_attributes

The key seems to be here: https://github.com/s3fs-fuse/s3fs-fuse/issues/42

So besides that instability that is mentioned (reading the linked issue at
google code I would say it was not related to fuse, but I am not an expert),
some basic functionality already don't now (and in the future more
functionality could stop working).

FMPOV we should keep the requirement >= 2.8.4 to allow people to use s3fs-fuse
on CentOS6/RHEL6 if they want to install a newer fuse version, even if it's not
official (just googling there are a lot of links about how to do it, and I even
provide the SPEC to create 2.8.4).

I will add a comment with a brief explanation and a link to the GitHub issue.
Is this OK?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to