)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"7d54446ec1b0bc0826a305f97e87300ee7caa53f","unresolved":true,"context_lines":[{"line_number":14,"context_line":"  - RHEL 7+"},{"line_number":15,"context_line":"  - Alpine 3.13+"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"RHEL 6 and Alpine 3.12, you had a good run, but you probably aren\u0027t"},{"line_number":18,"context_line":"going to be using py310+ (which is now required) anyway."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Change-Id: I7539b2420bdfce3c026dba873774175cb65a4c83"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"0e363ef7_fd8a66d1","line":17,"updated":"2026-02-04 20:53:42.000000000","message":"Actually, this *also* kills off RHEL 5 -- the old `manylinux2010` image had `auditwheel` saying things like\n```\nWheel is eligible for a higher priority tag. You requested\nmanylinux2010_x86_64 but I have found this wheel is eligible\nfor manylinux_2_5_x86_64.\n```\nso we\u0027d get a free upgrade (er, downgrade?) on the tags and publish `manylinux1` wheels. Still, 2014 is more than 10 years ago now... and at least there\u0027s *something* available (now! today!) for those old platforms for people stuck on them.\n\n(Apparently it comes down to `memcpy@@GLIBC_2.14` instead of `memcpy@@GLIBC_2.2.5`)","commit_id":"00624f44cfcb3aed6d6b25d2d954a5c70680425e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"ee3b243cc6abb994e2057fe0010b7814f4769b78","unresolved":true,"context_lines":[{"line_number":14,"context_line":"  - RHEL 7+"},{"line_number":15,"context_line":"  - Alpine 3.13+"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"RHEL 6 and Alpine 3.12, you had a good run, but you probably aren\u0027t"},{"line_number":18,"context_line":"going to be using py310+ (which is now required) anyway."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Change-Id: I7539b2420bdfce3c026dba873774175cb65a4c83"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"90ba344a_339e9bee","line":17,"in_reply_to":"0e363ef7_fd8a66d1","updated":"2026-03-05 22:56:54.000000000","message":"\u003e (Apparently it comes down to `memcpy@@GLIBC_2.14` instead of `memcpy@@GLIBC_2.2.5`)\n\nOK, *maybe* there\u0027s some way to still force the old version when working with newer build chains? See some of the proposed answers at https://stackoverflow.com/questions/8823267/linking-against-older-symbol-version-in-a-so-file\n\nNot convinced it\u0027s worth the effort, though.","commit_id":"00624f44cfcb3aed6d6b25d2d954a5c70680425e"}]}
