control: tags -1 unreproducible > Building logrotate twice with pbuilder (part of reproducible builds) e.g. > 'sudo > pbuilder build --twice logrotate_<version>-<debian_revision>.dsc' results in a > stray process at the end of the second build that requires manual intervention > (hitting 'q' key) to exit and complete the build, see output below.
I tried the reproducer but it works for me. > dpkg-genchanges: info: not including original source code in upload > I: copying local configuration > I: Copying back the cached apt archive contents > I: unmounting dev/ptmx filesystem > I: unmounting dev/pts filesystem > I: unmounting dev/shm filesystem > I: unmounting proc filesystem > I: unmounting sys filesystem > W: Stray processes left from build: > * system-pbuilder-build-logrotate_3.21.0\x2d2-24623.slice - Slice > /system/pbuilder/build/logrotate_3.21.> > Loaded: loaded > Active: active since Thu 2024-06-13 20:23:04 BST; 46s ago > Invocation: 73d59e481a6848a489f3c27c57c333cb > Tasks: 2 > Memory: 253.4M (peak: 369.5M) > CPU: 1min 1.590s > CGroup: /system.slice/system-pbuilder.slice/system-pbuilder- > build.slice/system-pbuilder-build-logro> > `-run-r8841d7ef13ad49709af4343b1c9e543b.scope > |-43056 flock state -c "sleep 10" > `-43062 sleep 10 Seems like test-0092 did not finish, but I wonder how a `sleep 10` could stall. > Jun 13 20:23:04 ks-windu systemd[1]: Created slice system-pbuilder-build- > logrotate_3.21.0\x2d2-24623.sli> > I: cleaning the build env > I: removing directory /var/cache/pbuilder/build/24623 and its subdirectories > I: Current time: Thu Jun 13 20:24:11 BST 2024 > I: pbuilder-time-stamp: 1718306651
