package: startpar severity: serious version: 0.59-2 Hi,
several people have asked me why their package fail on piuparts.debian.org with the following: 0m46.4s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/init/startpar-bridge.conf This example was taken from https://piuparts.debian.org/testing2sid/fail/libgcc1_1:4.9-20140411-2.log The probem is, that startpar is a (pseudo) essential package, so all packages are affected... So I investigated what is happening exactly and create a jessie chroot with debootstrap, saved /etc/init/startpar-bridge.conf, upgraded to sid and compared the two files: # diff /etc/init/startpar-bridge.conf /etc/init/startpar-bridge.conf.bak 15c15 < exec /lib/startpar/startpar-upstart-inject "$JOB" "$INSTANCE" "$UPSTART_EVENTS" --- > exec startpar-upstart-inject "$JOB" "$INSTANCE" "$UPSTART_EVENTS" So that's why. cheers, Holger
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel