Hi Santiago,

Le 14/07/2025 à 02:36, Santiago Vila a écrit :
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.

Thanks for your comments!
Don't worry, we are indeed willing to fix this issue, there is no reason for letting it go. I was just pointing out that in my opinion, the issue does not seem to be "serious" right now...


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.

... but certainly, this looks like a good way to go. You may file the bug to ask for trixie-ignore, thanks a lot for this!


Thanks.

Have a very good day,

--
Pierre

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to