On 5/25/26 5:26 PM, Rich Pieri wrote:
No. This isn't how Debian works. Quantity and quality of bug reports doesn't affect build system scheduling.
When the Copy Fail bug (a short Python program to a `#` root prompt) hit the scene on April 29 I got a new kernel for x86_64 on May 1, but I didn't get a new aarch_64 kernel until May 13.
But the numbers of bugs don't matter? aarch_64 has always been significantly lagging and I just haven't noticed?
I can imagine the build system is automated, but doesn't triaging and testing patches that make it into the build involve humans? The Linux kernel is very impressive for being written almost entirely in C, yet run on different CPUs. But within limits, they periodically drop targets for a reason, it is work to support different CPUs. An aarch_64 kernel is much more different from an x86_64 kernel than is a user land program compiled for the two architectures. Isn't it? Aren't humans involved? Aren't these same humans dealing with other patches? Aren't they a lot busier than they were a couple months ago??
-kb _______________________________________________ Discuss mailing list [email protected] https://lists.blu.org/mailman/listinfo/discuss
