Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-31 Thread Mark Hindley
Control: tags -1 upstream
Control: retitle -1 Upstream testsuite fails to produce deterministic results

Santiago,

On Sun, Oct 29, 2023 at 02:39:44PM +0100, Santiago Vila wrote:
> However, I can create a machine for you to reproduce the problem.

Thanks. I have reproduced on your provided machine, but still not locally and I
can't identify the underlying difference between the builds.

In the failure case the problem is in the upstream testsuite, specifically the
test for #491391 in tests/run-testsuite which produces

init.d:
bootchart
four
one
rmnologin
three
two

insserv:
override

rc0.d:

rc1.d:

rc2.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc3.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc4.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc5.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc6.d:

rcS.d:
error: incorrect 5 sequence bootchart not before rmnologin

The same failure mode appears to be responsible for armel and armhf autopkgtest
failures logged on ci.debian.net[1]

As Ian pointed out[2], there are significant and surprising changes in looping
order and behaviour between the successful and failing testsuites. The diff is 
attached.

Having said that, I still can't reproduce locally or determine a good fix.
Hopefully Jesse will have a useful contribution

Mark

[1]  
https://ci.debian.net/data/autopkgtest/unstable/armel/i/insserv/38435862/log.gz

[2]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052942#15

diff -u --label /sshx\:atlas\:/tmp/build.log --label /home/mark/src/debian/insserv/build.log /tmp/tramp.mDUEXG.log /home/mark/src/debian/insserv/build.log
--- /sshx:atlas:/tmp/build.log
+++ /home/mark/src/debian/insserv/build.log
@@ -4,8 +4,15 @@
 dpkg-buildpackage: info: source changed by Mark Hindley 
  dpkg-source --before-build .
 dpkg-buildpackage: info: host architecture amd64
- fakeroot debian/rules clean
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+dpkg-source: info: using patch list from debian/patches/series
+dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
+dpkg-source: info: applying 11_debian_conf.patch
+dpkg-source: info: applying 110_portmap.patch
+dpkg-source: info: applying warn_in_ignore_mode.patch
+dpkg-source: info: applying 0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
+dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
+ debian/rules clean
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh clean --with=bash-completion
dh_auto_clean
@@ -18,7 +25,7 @@
 make[1]: Leaving directory '/home/mark/insserv-1.24.0'
dh_clean
  debian/rules build
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh build --with=bash-completion
dh_update_autotools_config
@@ -31,14 +31,14 @@
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c map.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c listing.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   insserv.c -c 
-insserv.c: In function ‘main’:
-insserv.c:2923:20: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
+insserv.c: In function 'main':
+insserv.c:2923:20: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result]
  2923 |asprintf(_path, "%s/.", optarg);
   |

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-29 Thread Santiago Vila

El 29/10/23 a las 14:20, Mark Hindley escribió:

Lucas,

I am afraid I still cannot reproduce this.

I attach my successful .buildinfo. What are the differences to yours?


Hello. The problem is that failed builds do not produce .buildinfo files,
so we can't compare buildinfo files in this case.

However, I can create a machine for you to reproduce the problem.

Please contact me privately for details.

Thanks.



Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-29 Thread Mark Hindley
Lucas,

I am afraid I still cannot reproduce this.

I attach my successful .buildinfo. What are the differences to yours?

Thanks

Mark
Format: 1.0
Source: insserv
Binary: insserv insserv-dbgsym
Architecture: amd64
Version: 1.24.0-1
Checksums-Md5:
 3c928ff0990c2942950fa368b3978086 79480 insserv-dbgsym_1.24.0-1_amd64.deb
 9bffd1e3395d57a5979030bc472dc80c 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha1:
 aa26018adc027c1af58704991d3339c1a43dccf2 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 1d1a7b8f6e5b5ea864a7661f34e767b9a93e4b77 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha256:
 39912ad2e18538a91ae397467a6cd96519dd948fee2ed90b39c40b4477352bc1 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 e4e58a1a6a3cb6a68e205341606b1702ef10dd5bd6d43af03e123b536b4cc8f8 50572 
insserv_1.24.0-1_amd64.deb
Build-Origin: Debian
Build-Architecture: amd64
Build-Date: Sun, 29 Oct 2023 13:16:40 +
Build-Path: /build/insserv-1.24.0
Build-Tainted-By:
 merged-usr-via-aliased-dirs
Installed-Build-Depends:
 autoconf (= 2.71-3),
 automake (= 1:1.16.5-1.3),
 autopoint (= 0.21-12),
 autotools-dev (= 20220109.1),
 base-files (= 13),
 base-passwd (= 3.6.1),
 bash (= 5.2.15-2+b2),
 bash-completion (= 1:2.11-8),
 binutils (= 2.40.50.20230625-1),
 binutils-common (= 2.40.50.20230625-1),
 binutils-x86-64-linux-gnu (= 2.40.50.20230625-1),
 bsdextrautils (= 2.38.1-5+b1),
 bsdutils (= 1:2.38.1-5+b1),
 build-essential (= 12.10),
 bzip2 (= 1.0.8-5+b1),
 coreutils (= 9.1-1),
 cpp (= 4:12.3.0-1),
 cpp-10 (= 10.4.0-9),
 cpp-11 (= 11.4.0-1),
 cpp-12 (= 12.3.0-5),
 cpp-6 (= 6.5.0-2),
 cpp-8 (= 8.4.0-4),
 cpp-9 (= 9.5.0-3),
 dash (= 0.5.12-6),
 debconf (= 1.5.82),
 debhelper (= 13.11.4),
 debianutils (= 5.7-0.4),
 dh-autoreconf (= 20),
 dh-strip-nondeterminism (= 1.13.1-1),
 diffutils (= 1:3.8-4),
 dpkg (= 1.21.22),
 dpkg-dev (= 1.21.22),
 dwz (= 0.15-1),
 file (= 1:5.44-3),
 findutils (= 4.9.0-4),
 g++ (= 4:12.3.0-1),
 g++-12 (= 12.3.0-5),
 gcc (= 4:12.3.0-1),
 gcc-10 (= 10.4.0-9),
 gcc-10-base (= 10.4.0-9),
 gcc-11 (= 11.4.0-1),
 gcc-11-base (= 11.4.0-1),
 gcc-12 (= 12.3.0-5),
 gcc-12-base (= 12.3.0-5),
 gcc-13-base (= 13.1.0-7),
 gcc-6 (= 6.5.0-2),
 gcc-6-base (= 6.5.0-2),
 gcc-7-base (= 7.4.0-14),
 gcc-8 (= 8.4.0-4),
 gcc-8-base (= 8.4.0-4),
 gcc-9 (= 9.5.0-3),
 gcc-9-base (= 9.5.0-3),
 gettext (= 0.21-12),
 gettext-base (= 0.21-12),
 grep (= 3.8-5),
 groff-base (= 1.22.4-10),
 gzip (= 1.12-1),
 hostname (= 3.23+nmu1),
 init-system-helpers (= 1.65.2),
 intltool-debian (= 0.35.0+20060710.6),
 libacl1 (= 2.3.1-3),
 libarchive-zip-perl (= 1.68-1),
 libasan3 (= 6.5.0-2),
 libasan5 (= 9.5.0-3),
 libasan6 (= 11.4.0-1),
 libasan8 (= 13.1.0-7),
 libatomic1 (= 13.1.0-7),
 libattr1 (= 1:2.5.1-4),
 libaudit-common (= 1:3.0.9-1),
 libaudit1 (= 1:3.0.9-1),
 libbinutils (= 2.40.50.20230625-1),
 libblkid1 (= 2.38.1-5+b1),
 libbz2-1.0 (= 1.0.8-5+b1),
 libc-bin (= 2.36-9),
 libc-dev-bin (= 2.36-9),
 libc6 (= 2.36-9),
 libc6-dev (= 2.36-9),
 libcap-ng0 (= 0.8.3-1+b3),
 libcap2 (= 1:2.66-4),
 libcc1-0 (= 13.1.0-7),
 libcilkrts5 (= 7.4.0-14),
 libcom-err2 (= 1.47.0-2),
 libcrypt-dev (= 1:4.4.35-1),
 libcrypt1 (= 1:4.4.35-1),
 libctf-nobfd0 (= 2.40.50.20230625-1),
 libctf0 (= 2.40.50.20230625-1),
 libdb5.3 (= 5.3.28+dfsg2-1),
 libdebconfclient0 (= 0.270),
 libdebhelper-perl (= 13.11.4),
 libdpkg-perl (= 1.21.22),
 libelf1 (= 0.188-2.1),
 libfile-find-rule-perl (= 0.34-3),
 libfile-stripnondeterminism-perl (= 1.13.1-1),
 libgcc-10-dev (= 10.4.0-9),
 libgcc-11-dev (= 11.4.0-1),
 libgcc-12-dev (= 12.3.0-5),
 libgcc-6-dev (= 6.5.0-2),
 libgcc-8-dev (= 8.4.0-4),
 libgcc-9-dev (= 9.5.0-3),
 libgcc-s1 (= 13.1.0-7),
 libgcrypt20 (= 1.10.2-2),
 libgdbm-compat4 (= 1.23-3),
 libgdbm6 (= 1.23-3),
 libgmp10 (= 2:6.2.1+dfsg1-1.1),
 libgomp1 (= 13.1.0-7),
 libgpg-error0 (= 1.46-1),
 libgprofng0 (= 2.40.50.20230625-1),
 libgssapi-krb5-2 (= 1.20.1-2),
 libicu72 (= 72.1-3),
 libisl19 (= 0.20-2),
 libisl22 (= 0.22.1-1),
 libisl23 (= 0.26-3),
 libitm1 (= 13.1.0-7),
 libjansson4 (= 2.14-2),
 libk5crypto3 (= 1.20.1-2),
 libkeyutils1 (= 1.6.3-2),
 libkrb5-3 (= 1.20.1-2),
 libkrb5support0 (= 1.20.1-2),
 liblsan0 (= 13.1.0-7),
 liblz4-1 (= 1.9.4-1),
 liblzma5 (= 5.4.1-0.2),
 libmagic-mgc (= 1:5.44-3),
 libmagic1 (= 1:5.44-3),
 libmd0 (= 1.1.0-1),
 libmount1 (= 2.38.1-5+b1),
 libmpc3 (= 1.3.1-1),
 libmpfr6 (= 4.2.0-1),
 libmpx2 (= 8.4.0-4),
 libnsl-dev (= 1.3.0-2),
 libnsl2 (= 1.3.0-2),
 libnumber-compare-perl (= 0.03-3),
 libpam-modules (= 1.5.2-6),
 libpam-modules-bin (= 1.5.2-6),
 libpam-runtime (= 1.5.2-6),
 libpam0g (= 1.5.2-6),
 libpcre2-8-0 (= 10.42-1),
 libperl5.36 (= 5.36.0-7),
 libpipeline1 (= 1.5.7-1),
 libquadmath0 (= 13.1.0-7),
 libseccomp2 (= 2.5.4-1+b3),
 libselinux1 (= 3.4-1+b6),
 libsmartcols1 (= 2.38.1-5+b1),
 libssl3 (= 3.0.9-1),
 libstdc++-12-dev (= 12.3.0-5),
 libstdc++6 (= 13.1.0-7),
 libsub-override-perl (= 0.09-4),
 libsystemd0 (= 253-4),
 libtext-glob-perl (= 0.11-3),
 libtinfo6 (= 6.4-4),
 libtirpc-common (= 1.3.3+ds-1),
 libtirpc-dev (= 1.3.3+ds-1),
 libtirpc3 (= 1.3.3+ds-1),
 

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-26 Thread Lucas Nussbaum
Hi,

On 04/10/23 at 21:25 +0100, Mark Hindley wrote:
> Control: tags -1 moreinfo
> 
> Ian
> 
> On Wed, Sep 27, 2023 at 10:33:32PM +0100, Ian Jackson wrote:
> > Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read 
> > script nolsbheader: No such file or directory"):
> > > Thanks for this. However, I am currently unable to repoduce this
> > > failure in my customary pbuilder setup. And it doesn't appear at
> > > reproducible builds either[1]
> > 
> > I just tried this myself with my usual sbuild setup and it succeeded
> > there too[1].
> 
> 
> Thanks for your confirmation.
> 
> > Lucas, I think something from your rebuild environment
> > (a chroot of some kind I presume) must be triggering this failure.  Is
> > there some way we can reproduce it more precisely (eg, a buildinfo
> > file?)
> 
> Yes, I agree a buildinfo file might give a hint.
> 
> > I looked at the build log
> >  http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
> > and compared it to the one from my sbuild, using diff.  There are a
> > lot of changes to the "furniture" but also there are noise changes to
> > the output of the insserv test suite, including ordring changes of
> > passing tests.  This seemed surprising to me.
> > 
> > Mark, is the insserv test suite supposed to produce deterministic
> > output ?
> 
> I have never had the need to look at the testsuite since I started looking 
> after
> the package. A quick look now doesn't immediately reveal something that would
> obviously change the order of the tests.
> 
> I tried again locally with make -j8 and still could not reproduce any failure.

It also fails with -j1: it does not look like a concurrency issue. See
attached log.

Lucas
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on ip-10-84-234-181

+==+
| insserv 1.24.0-1 (amd64) Thu, 26 Oct 2023 07:58:20 + |
+==+

Package: insserv
Version: 1.24.0-1
Source Version: 1.24.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-amd64-sbuild-9b6ecbbe-48ed-462f-8959-f9b693a34744' 
with '<>'
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ/resolver-hdop7y' 
with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://127.0.0.1:12990/debian sid InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
NOTICE: 'insserv' packaging is maintained in the 'Git' version control system 
at:
https://salsa.debian.org/debian/insserv.git
Please use:
git clone https://salsa.debian.org/debian/insserv.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 114 kB of source archives.
Get:1 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (dsc) [1996 B]
Get:2 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (tar) [76.5 kB]
Get:3 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (diff) [35.8 kB]
Fetched 114 kB in 0s (1611 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ/insserv-1.24.0' 
with '<>'
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ' with '<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: bash-completion, debhelper-compat (= 12), po-debconf, 
build-essential, fakeroot
Filtered Build-Depends: bash-completion, debhelper-compat (= 12), po-debconf, 
build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [609 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [646 B]
Get:5 copy:/<>/apt_archive ./ Packages [678 B]
Fetched 1933 B in 0s (80.7 kB/s)
Reading package lists...
Reading package lists...

Install main build 

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-10-04 Thread Mark Hindley
Control: tags -1 moreinfo

Ian

On Wed, Sep 27, 2023 at 10:33:32PM +0100, Ian Jackson wrote:
> Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read 
> script nolsbheader: No such file or directory"):
> > Thanks for this. However, I am currently unable to repoduce this
> > failure in my customary pbuilder setup. And it doesn't appear at
> > reproducible builds either[1]
> 
> I just tried this myself with my usual sbuild setup and it succeeded
> there too[1].


Thanks for your confirmation.

> Lucas, I think something from your rebuild environment
> (a chroot of some kind I presume) must be triggering this failure.  Is
> there some way we can reproduce it more precisely (eg, a buildinfo
> file?)

Yes, I agree a buildinfo file might give a hint.

> I looked at the build log
>  http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
> and compared it to the one from my sbuild, using diff.  There are a
> lot of changes to the "furniture" but also there are noise changes to
> the output of the insserv test suite, including ordring changes of
> passing tests.  This seemed surprising to me.
> 
> Mark, is the insserv test suite supposed to produce deterministic
> output ?

I have never had the need to look at the testsuite since I started looking after
the package. A quick look now doesn't immediately reveal something that would
obviously change the order of the tests.

I tried again locally with make -j8 and still could not reproduce any failure.

Mark



Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-09-27 Thread Ian Jackson
Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read 
script nolsbheader: No such file or directory"):
> Thanks for this. However, I am currently unable to repoduce this
> failure in my customary pbuilder setup. And it doesn't appear at
> reproducible builds either[1]

I just tried this myself with my usual sbuild setup and it succeeded
there too[1].  Lucas, I think something from your rebuild environment
(a chroot of some kind I presume) must be triggering this failure.  Is
there some way we can reproduce it more precisely (eg, a buildinfo
file?)

I looked at the build log
 http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
and compared it to the one from my sbuild, using diff.  There are a
lot of changes to the "furniture" but also there are noise changes to
the output of the insserv test suite, including ordring changes of
passing tests.  This seemed surprising to me.

Mark, is the insserv test suite supposed to produce deterministic
output ?

Ian.

[1] just-updated sid chroot, "dgit sbuild -wgf build -c build".



Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-09-26 Thread Mark Hindley
Control: tags -1 unreproducible

Lucas,

Thanks for this. However, I am currently unable to repoduce this failure in my
customary pbuilder setup. And it doesn't appear at reproducible builds either[1]

On Tue, Sep 26, 2023 at 03:45:26PM +0200, Lucas Nussbaum wrote:
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

My successful pbuilder log is attached.

Mark


[1]  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/insserv.html

dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (= 13) 
po-debconf
W: Unmet build-dependency in source
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building insserv using existing ./insserv_1.24.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building insserv in insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: building insserv in insserv_1.24.0-1.dsc
I: Generated dsc will be overwritten by build result; not generating changes 
file
dpkg-source: info: unapplying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: unapplying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: unapplying warn_in_ignore_mode.patch
dpkg-source: info: unapplying 110_portmap.patch
dpkg-source: info: unapplying 11_debian_conf.patch
dpkg-source: info: unapplying install-binaries-ignore-PREFIX.patch
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.20068
I: forking: cp -al /var/cache/pbuilder/base-sid.cow 
/var/cache/pbuilder/build/cow.20068
I: removed stale ilistfile /var/cache/pbuilder/build/cow.20068/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.20068 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts '  '--no-pre-clean'' 
--buildplace /var/cache/pbuilder/build/cow.20068 --buildresult 
/home/mark/src/debian/build --mirror http://deb.debian.org/debian 
--distribution sid --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.20068 cow-shell' 
/home/mark/src/debian/build/insserv_1.24.0-1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Tue Sep 26 17:05:48 BST 2023
I: pbuilder-time-stamp: 1695744348
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage for 
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.dsc]
I: copying [/home/mark/src/debian/build/insserv_1.24.0.orig.tar.gz]
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (insserv_1.24.0-1.dsc)
dpkg-source: info: extracting insserv in insserv-1.24.0
dpkg-source: info: unpacking insserv_1.24.0.orig.tar.gz
dpkg-source: info: unpacking insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
I: using fakeroot in build.
I: Installing the build-deps
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
starting
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
finished
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D05apt-update 
starting

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 http://deb.debian.org/debian unstable InRelease [195 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Ign:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:3 http://deb.debian.org/debian unstable/main Translation-en.diff/Index 
[63.6 kB]
Ign:3 http://deb.debian.org/debian unstable/main 

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

2023-09-26 Thread Lucas Nussbaum
Source: insserv
Version: 1.24.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf tests/root/
> cd tests && ./common
> 
> info: test simple script ordering.
> 
> insserv.conf
> 
> init.d:
> firstscript
> lastscript
> middlescript
> 
> rc0.d:
> 
> rc1.d:
> 
> rc2.d:
> S01firstscript
> S02middlescript
> S03lastscript
> 
> rc3.d:
> S01firstscript
> S02middlescript
> S03lastscript
> 
> rc4.d:
> S01firstscript
> S02middlescript
> S03lastscript
> 
> rc5.d:
> S01firstscript
> S02middlescript
> S03lastscript
> 
> rc6.d:
> 
> rcS.d:
> 
> info: test if loop involving virtual facility is detected.
> 
> insserv: There is a loop between service mountall and hibernate-cleanup if 
> started
> insserv:  loop involving service hibernate-cleanup at depth 3
> insserv:  loop involving service mdadm at depth 2
> insserv: There is a loop between service mountall and hibernate-cleanup if 
> started
> insserv:  loop involving service mountall at depth 1
> insserv: There is a loop between service hibernate-cleanup and mdadm if 
> started
> insserv: exiting now without changing boot order!
> insserv.conf:
> $local_fs   mountall
> insserv.conf
> 
> init.d:
> hibernate
> mdadm
> mountall.sh
> 
> rc0.d:
> 
> rc1.d:
> 
> rc2.d:
> 
> rc3.d:
> S01hibernate
> S02mountall.sh
> 
> rc4.d:
> 
> rc5.d:
> 
> rc6.d:
> 
> rcS.d:
> success: 7 test executed, 0 nonfatal tests failed.
> cd tests && severity=check ./run-testsuite
> 
> info: test normal boot sequence scripts, and their order
> 
> insserv: Could not read script nolsbheader: No such file or directory
> insserv: warning: script 'nolsbheader' missing LSB tags
> insserv: Could not read script nolsbheader: Success
> insserv: warning: script 'nolsbheader' missing LSB tags
> insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
> `nolsbheader'
> insserv: Default-Stop  undefined, assuming empty stop runlevel(s) for script 
> `nolsbheader'
> insserv.conf
> 
> init.d:
> beforenfs
> checkfs.sh
> checkroot.sh
> halt
> hwclock.sh
> ifupdown
> ifupdown-clean
> kexec
> killprocs
> mountall.sh
> mountdevsubfs.sh
> mountkernfs.sh
> mountnfs.sh
> needallfs
> needallfs2
> needlocalfs
> networking
> nolsbheader
> reboot
> single
> sysklogd
> umountfs
> umountnfs
> umountroot
> 
> rc0.d:
> K01hwclock.sh
> K01needallfs
> K01needallfs2
> K01needlocalfs
> K01sysklogd
> K02umountnfs
> K03networking
> K04ifupdown
> K05umountfs
> K06umountroot
> K07halt
> 
> rc1.d:
> K01needallfs
> K01needallfs2
> K01needlocalfs
> K01sysklogd
> S01killprocs
> S02single
> 
> rc2.d:
> S01needallfs2
> S01needlocalfs
> S01sysklogd
> S02needallfs
> 
> rc3.d:
> S01needallfs2
> S01needlocalfs
> S01sysklogd
> S02needallfs
> 
> rc4.d:
> S01needallfs2
> S01needlocalfs
> S01sysklogd
> S02needallfs
> 
> rc5.d:
> S01needallfs2
> S01needlocalfs
> S01sysklogd
> S02needallfs
> 
> rc6.d:
> K01hwclock.sh
> K01needallfs
> K01needallfs2
> K01needlocalfs
> K01sysklogd
> K02umountnfs
> K03networking
> K04ifupdown
> K05umountfs
> K06umountroot
> K07kexec
> K08reboot
> 
> rcS.d:
> S01mountkernfs.sh
> S02mountdevsubfs.sh
> S03checkroot.sh
> S04checkfs.sh
> S05hwclock.sh
> S05ifupdown-clean
> S05mountall.sh
> S06beforenfs
> S06ifupdown
> S07networking
> S08mountnfs.sh
> 
> info: test if override files replace headers in the file
> 
> insserv.conf
> 
> init.d:
> base
> mover
> 
> insserv:
> override
> 
> rc0.d:
> 
> rc1.d:
> 
> rc2.d:
> 
> rc3.d:
> 
> rc4.d:
> 
> rc5.d:
> 
> rc6.d:
> 
> rcS.d:
> S01mover
> S02base
> 
> info: testing to insert scripts with a loop, and the effect of an override 
> file
> 
> insserv: FATAL: service loop2 has to be enabled to use service loop1
> insserv: exiting now!
> insserv: FATAL: service loop1 has to be enabled to use service loop2
> insserv: There is a loop between service loop2 and loop1 if started
> insserv:  loop involving service loop1 at depth 2
> insserv:  loop involving service loop2 at depth 1
> insserv: There is a loop between service loop1 and loop2 if started
> insserv: exiting now without changing boot order!
> 
> info: Try to reproduce BTS #540866
> 
> insserv.conf
> 
> init.d:
> testscript
> 
> insserv:
> override
> 
> rc0.d:
> K01testscript
> 
> rc1.d:
> K01testscript
> 
> rc2.d:
> S01testscript
> 
> rc3.d:
> 
> rc4.d:
> S01testscript
> 
> rc5.d:
> S01testscript
> 
> rc6.d:
> K01testscript
> 
> rcS.d:
> info: Trying to remove the script
> insserv.conf
> 
> init.d:
> testscript
> 
> insserv:
> override
> 
> rc0.d:
> 
> rc1.d:
> 
> rc2.d:
> 
> rc3.d:
> 
> rc4.d:
> 
> rc5.d:
> 
> rc6.d:
> 
> rcS.d:
> 
> info: testing to insert scripts with a longer loop, making sure it fail
> 
> insserv: There is a loop between service loop1 and loop3 if started
> insserv:  loop involving service loop3 at depth 3
> insserv:  loop involving service loop2 at depth 2
>