Julio González Gil

> @juliogonzalez Sorry for my poor explanation. > > The reason it's failing is because Github Actions' actions/checkout@v3 can't checkout the source code, and this is a problem specific to...

Is the plan about this being the last CentOS7 release still valid? If that's the case, I am not sure EPEL7 is going to accept it. But in any case...

# Tracking for RPM submissions ## Git main repository - **PR:** https://github.com/juliogonzalez/s3fs-fuse-rpm/pull/32 (merged) - **Release:** https://github.com/juliogonzalez/s3fs-fuse-rpm/releases/tag/1.95-1 ## openSUSE - **SR**: https://build.opensuse.org/requests/1218679 As usual, one accepted this will be submitted to...

> Thanks as always @juliogonzalez! I will try the Fedora 41 package when it reaches testing. Done, see above. Regarding CentOS7 and clones: The submission for EPEL7 could not be...

1.95 now available at: - https://build.opensuse.org/package/show/filesystems/s3fs as experimental for all supported SUSE/openSUSE OS - openSUSE Tumbleweed - EPEL8 - EPEL9 - Fedora 39 - Fedora 40 - Fedora 41 -...

@gaul I see you contributed to the Debian package https://salsa.debian.org/debian/s3fs-fuse/-/commits/debian/?ref_type=HEADS, so apparently one doesn't need to be maintainer to send MRs to that repo. I will see what I can...

> 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...

I bring some news to this issue about CentOS7 and family. As explained at https://github.com/s3fs-fuse/s3fs-fuse/issues/2496#issuecomment-2440117118, I could not provide packages for EPEL7 back then, as it was already End of...

> What kind of build failures? Occasionally 32-bit compatibility issues creep in but those are easy to fix. Raspberry Pi/armv7 is the only real reason to fix these. Strictly speaking...

> 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...