From: "stabbles (Harmen Stoppels) via ruby-core" Date: 2026-10-28T10:27:46+00:00 Subject: [ruby-core:127259] [Ruby Bug#22480] Ruby's release tarballs are not POSIX compliant since 2018 Issue #22480 has been reported by stabbles (Harmen Stoppels). ---------------------------------------- Bug #22480: Ruby's release tarballs are not POSIX compliant since 2018 https://bugs.ruby-lang.org/issues/22480 * Author: stabbles (Harmen Stoppels) * Status: Open * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- Hi, This is a bit of a curiosity, but I noticed that Ruby's release tarballs are not POSIX compliant, because they're missing an end-of-archive marker. See https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pax.html#:~:text=At%20the%20end%20of%20the%20archive%20file%20there%20shall%20be%20two%20512-byte%20blocks Apparently Ruby has custom code to create its release tarballs, and it does not close the tar writer, which would add this. I noticed this cause I'm working on https://stoppels.ch/tar/, a test suite with dozens of tricky tar files, plus a table that maps the differences between tar implementations. For security purposes, some package managers (like uv), are looking to harden tar parsers, and Ruby's release tarballs would not be accepted. The release tarballs from Ruby 2.6.0 onwards are not POSIX compliant, basically since 2018. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/