On Mon, Oct 19, 2026 at 07:32:50PM +0900, Luke Yasuda wrote: > Hi again! > > On 2026-03-28 18:13, Samuel Thibault wrote: > > Hello, > > > > Luke Yasuda, le sam. 28 mars 2026 12:06:25 +0900, a ecrit: > > > vim seems to be stuck on buildd, the build has already taken 6 days > > > on both > > > hurd-amd64 and hurd-i386. > > > https://buildd.debian.org/status/package.php?p=vim > > > > vim still has testsuite issues, so there is no point letting buildds try > > to build it. > > > [...] > > vim still FTBFS on hurd-any after 6 months. This causes hurd-any to be > un-debootstrap-able. Can a nocheck build be arranged for vim on hurd-any?
Please don't fix the problem that way. AFAIK, the problem is that vim FTBFS on systems with 1 CPU. I already reported this here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085065 but the bug has been neglected for 2 years. This can be checked on amd64 by simply booting with GRUB_CMDLINE_LINUX="nr_cpus=1". If you fix the underlying bug (which may be as simple as disabling an obviously wrongly designed test), it might build on the hurd again. Thanks.
