Andrew Gaul
Andrew Gaul
This seems fixed since #2619 passed.
Is there any kind of test we can add that exercises these code paths?
We have a few outstanding locking fixes and the shared_ptr PR but does anything else block 1.95?
We haven't merged anything that will break CentOS 7 so 1.95 should be compatible. But I would like to explore FUSE3 and C++17 for 1.96 which will break CentOS 7.
Does anything block the release? I suggest these release notes: * Add `ipresolve` option to select IPv4- or IPv6-only * Changed s3fs logo * Enable static lock checking and fix...
Thanks as always @juliogonzalez! I will try the Fedora 41 package when it reaches testing.
I don't exactly understand how Debian manages releases but this seems to have the entire git history which is why Takeshi and my names show up. I file issues with...
I opened this issue to upgrade Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086865
> Build for architectures other than `x86_64`, `ppc64le` and `aarch64` was failing. So only those architectures are available. What kind of build failures? Occasionally 32-bit compatibility issues creep in but...
OK it's not a s3fs source issue then. I don't have the entire Raspberry Pi situation in my head but even my RPi4 running bookworm defaults to a 64-bit kernel...