mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #878] support LTS versions like rhel6/centos6 #513
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#513
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @f1-outsourcing on GitHub (Dec 26, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/878
Would be nice if you take into account to support LTS versions like rhel6 and centos6.
@gaul commented on GitHub (Dec 26, 2018):
Do these instructions work:
https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes#installing-on-centos-6-s3fs-version-174
I believe that RHEL 6 has an older FUSE which makes packaging it difficult. @juliogonzalez might know more.
@juliogonzalez commented on GitHub (Dec 30, 2018):
@f1-outsourcing, sadly s3fs-fuse can't officially support RHEL6/CentOS 6 anymore, as the fuse version there is breaking some basic functionality. That's the reason I am not even submitting
s3fs-fusepackage for CentOS6.That said, you can build install an updated version of fuse (2.8.4 at least), but keep in mind the consequences, specially if you are using RHEL6.
I just updated all the instructions at https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes#fedora--centos--rhel. I even added a link to one of my personal repositories so you can create RPMs (in fact I am using that repository to submit the
s3fs-fusepackage for Fedora and EPEL -RHEL/CentOS-).I hope this answers your question (if so, please close the issue)
@juliogonzalez commented on GitHub (Mar 23, 2019):
@f1-outsourcing can this issue be closed?
@gaul commented on GitHub (Jun 25, 2019):
Please reopen if the suggested workaround does not address your symptoms.