On 22/12/2025 12:14, Antonio Terceiro wrote:
It is, but upstream dependency metadata is not perfect either.
It seems the root cause was that the copy of thin 1.8.2 that was installed on my machine required ruby-rack <3 at runtime, but after force-reinstalling the same .deb it now permits ruby-rack <4, which fixed the issue. It seems at some point the runtime dependencies of thin 1.8.2 were bumped and either the version number wasn't incremented or the stale dependencies were cached.
Thanks for the help, A
