On Sun, Jul 13, 2025 at 08:03:24AM +0200, Pierre Gruet wrote: > However, my feeling is that the bug is not RC, since it shows up only in > VMs: in practice it does not affect the autobuilders nor the developers on > their individual machines. What do you think?
Those seem weak reasons to me. We don't really know if it shows up only in VMs. Just because it fails on the VMs I've provided does not mean that it fails *because* I'm using VMs. But in either case lowering support for VMs looks arbitrary to me. What will we tell the end user who wants to build this from source? Will we say "Sorry, this is not supported because you are using a VM?" What's wrong with using VMs? That would not fit very well with our idea that Debian is the universal operating system, valid for servers and desktops, and also valid for VMs and real hardware. We also don't even know if this will happen in the autobuilders, because this started to happen when I switched to using trixie (including the kernel of trixie) and there has not been any build of scilab in the official autobuilders using the kernel of trixie yet. In cases like this one, I suggest that we ask for a trixie-ignore tag while we await for some reply from upstream. As a team member, I can file the release.debian.org bug if nobody else volunteers. Thanks.
