mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #2213] 1.93 release #1125
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#1125
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 @gaul on GitHub (Jul 13, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2213
I would like to run a 1.93 release to include #2212 which I suspect is a widespread regression. master includes a few thread-safety fixes and also has support for macOS FUSE-T. Do we have anything else low-risk that we can merge? I am traveling this weekend but should be able to run a release next week or weekend.
@ggtakec commented on GitHub (Jul 13, 2023):
@gaul I find the possibility of Thread data race only one more in the processing of HeadRequest.
I will send a PR by the end of the day.
(I sorry for PR was delayed because I was investigating this along with other investigations.)
If you are allowing with the fix, merge and we can go to release.
Please wat a while.
@ggtakec commented on GitHub (Jul 13, 2023):
@gaul I posted #2214 PR.
This PR code is a fix for a data race that I noticed while investigating and responding to macos.
However, I have yet to see a report from
ThreadSanitizerabout this problem.But I think (maybe) this fix will be necessary.
Once this PR is finished(merged or not), I think we can release new version.
Thanks in advance for your assistance.
@ggtakec commented on GitHub (Jul 17, 2023):
@gaul The data race(#2220) remains, but I don't think this small problem will stop the release.
I believe that we can release with the code of the current master.
@juliogonzalez commented on GitHub (Jul 19, 2023):
As usual, here goes my report about submissions to Fedora/EPEL/openSUSE
Git repository
openSUSE/SLE
From there, it should get shortly into openSUSE Tumbleweed/MicroOS, etc.
Fedora/EPEL
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2209081
Fedora Rawhide (39): https://bodhi.fedoraproject.org/updates/FEDORA-2023-94583f994f
Fedora 38: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b33f00d784
Fedora 37: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0c114a6bd5
EPEL9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-aa3ec29bd6
EPEL8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5b2cef31a4
EPEL7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-cd6d182415
@hereTac commented on GitHub (Jul 20, 2023):
When will v1.93 in these repositories become available, and where can I track this status information? Do I need to solely observe this repository? https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/s/ @juliogonzalez
@juliogonzalez commented on GitHub (Jul 23, 2023):
2-3 weeks. The links to track the status will be added to my previous comment.
@juliogonzalez commented on GitHub (Jul 25, 2023):
All submissions complete.
See https://github.com/s3fs-fuse/s3fs-fuse/issues/2213#issuecomment-1642886726 for the details.
For Fedora/EPEL, remember you can speed up the procedure if you test the updates and provided karma. If enough positive karma is collected (3), then the corresponding update is pushed to stable.
@ggtakec commented on GitHub (Jul 25, 2023):
@juliogonzalez Thank you for your cooperation!