Analyzing rubygem-redis-client failures [1], that is also the same issue. So 3 packages from my set are broken just by this silly limitation :( Funnily enough, the error message is a bit different this time:
~~~
ArgumentError: too long unix socket path (130bytes given but 108bytes max)
~~~
That is likely a Redis / Valkey reinterpretation of the message.
Vít
On Wed, Aug 7, 2024 at 1:09 PM Vít Ondruch <vondruch@xxxxxxxxxx> wrote:
With new RPM, I hit the limit in two packages:
https://koschei.fedoraproject.org/package/rubygem-abrt
https://koschei.fedoraproject.org/package/rubygem-pg
I have read:
https://unix.stackexchange.com/questions/367008/why-is-socket-path-length-limited-to-a-hundred-chars
https://stackoverflow.com/questions/34829600/why-is-the-maximal-path-length-allowed-for-unix-sockets-on-linux-108
But I still wonder why we should live with such limitation in 21st century.
Vít
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
