<p>@<span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> I did once have an unresolvable problem where a package manager did not do what everybody thought, and kept an ancient version of a package long after it was assumed to have been updated. Meanwhile the package drifted out of compatibility with our code, and the maintainers dropped the last version we were compatible with.</p><p>So when we trashed that build machine (VM) and made a new one, the package manager found no package, fetched the latest, and suddenly the project didn't build, the version we were compatible with no longer existed, and nobody left at the company knew how that part was supposed to work - fun days!</p><p>Not 100% sure if this relates to your post, but I was reminded of it... It did take over a decade of only ever building that subsystem on the same VM for this to happen, which is unusual, I'll admit.</p>
