Package: sbuild Version: 0.86.2 Dear maintainers:
When I try to build (using the unshare backend) a package which may not be built because their build-dependencies may not be installed, quite often, but not always, I get a message like this: Install dose3 build dependencies (apt-based resolver) ----------------------------------------------------- Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: dose-distcheck The following NEW packages will be installed: dose-distcheck sbuild-build-depends-dose3-dummy 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1207 kB of archives. After this operation, 4930 kB of additional disk space will be used. Get:1 copy:/<<RESOLVERDIR>>/apt_archive ./ sbuild-build-depends-dose3-dummy 0.invalid.0 [848 B] Get:2 http://deb.debian.org/debian trixie/main amd64 dose-distcheck amd64 7.0.0-5+b5 [1207 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 1207 kB in 0s (83.2 MB/s) Selecting previously unselected package dose-distcheck. (Reading database ... 11796 files and directories currently installed.) Preparing to unpack .../dose-distcheck_7.0.0-5+b5_amd64.deb ... Unpacking dose-distcheck (7.0.0-5+b5) ... Selecting previously unselected package sbuild-build-depends-dose3-dummy. Preparing to unpack .../sbuild-build-depends-dose3-dummy_0.invalid.0_amd64.deb ... Unpacking sbuild-build-depends-dose3-dummy (0.invalid.0) ... Setting up dose-distcheck (7.0.0-5+b5) ... Setting up sbuild-build-depends-dose3-dummy (0.invalid.0) ... failed to create symlink /dev/fd at /usr/libexec/sbuild-usernsexec line 384. E: ABORT: Received PIPE signal (requesting cleanup and shutdown) E: apt-helper failed E: Failed to explain bd-uninstallable Sorry not to be more specific, as the failure happens randomly. I asked Jochen and he suggested that I should report this here. Line 384 in context: 369 for my $link ( 370 ["/dev/fd", "/proc/self/fd"], 371 ["/dev/stdin", "/proc/self/fd/0"], 372 ["/dev/stdout", "/proc/self/fd/1"], 373 ["/dev/stderr", "/proc/self/fd/2"], 374 ["/dev/ptmx", "/dev/pts/ptmx"], 375 ["/dev/ptmx", "/dev/pts/ptmx"] 376 ) { 377 my ($link, $target) = @{$link}; 378 if (-l "$rootdir/$link") { 379 unlink "$rootdir/$link" or die "cannot unlink $link"; 380 } 381 if (-e "$rootdir/$link") { 382 unlink "$rootdir/$link" or die "cannot unlink $link"; 383 } 384 symlink $target, "$rootdir/$link" 385 or die "failed to create symlink $link"; 386 } What could be a good reason for the symlink in line 384 to fail? Funny detail: Some of my autobuilders have 1 CPU and others have 2 CPUs. As of today, I only have messages like the above from machines with 2 CPUs. Maybe it's a coincidence, or maybe not. I'm attaching a full build log as a sample. Thanks.
osmo-bts_1.7.2+dfsg1-2_amd64-20241015T103926.265Z.gz
Description: application/gzip
