3 ms·
> Okay, suppose someone backporting a Rust update runs a big batch of tests and finds, say, two dozen packages with regressions. > Now what? > Spend two weeks
by zozbot234 7y ago
> Okay, suppose someone backporting a Rust update runs a big batch of tests and finds, say, two dozen packages with regressions.
> Now what?
> Spend two weeks investigating all the test failures? Backporting updates to these packages as well, all while users are patiently waiting for their Firefox to have its zero‐day fixed? Are the tests even correct? Were they failing before and nobody noticed?
Yes, people do exactly that. It's part of running a "rolling" distro, see e.g. the Debian Testing transition tracker at https://release.debian.org/transitions/ https://release.debian.org/transitions/ - These transitions are running essentially all the time; they're only "put on hold" as a first step in the process of making a new stable release. And even then, newer versions of packages such as rust can still enter stable as part of an "unrelated" security update.
- anjbe 7y ago> Yes, people do exactly that. It's part of running a "rolling" distro And we do that too—for OpenBSD -current. But we have neither the manpower nor the interest to do such work for old releases.
- fluffything 7y agoThere are many options to solve that: * switch to a shorter stable release cycle (4 weeks, 6 weeks, etc.) with dynamic releases (e.g. if a zero day happens, fix current, and do a new stable release) * switch to only supporting -current * switch to something like Nix to allow stable users to "switch" some packages from stable to current, without having to bump their whole system (this would have allowed stable users to update their Firefox-stable to Firefox-current) A good packaging process should not assume that downstream packages can be trusted to have meaningful processes. Relying on Firefox having -esr releases is a temporary workaround.
- lllr_finger 7y agoThe OpenBSD port for Rust 1.39 - the long awaited async/await release - wasn't available for several (6?) weeks. The reason for this was the maintainer is a single person with a complex setup, trying to wrestle with LLVM issues and more esoteric things like Sparc64 support. It's a small miracle things like Rust are supported on OpenBSD at all, let alone things outside of -current.