Hello Andreas, thank you for the bugreport. I already noticed the misbehavior of expeyes, when I tried to install it in a chroot, but I ignored that the solution was as simple as the one you hinted me.
I fix the bug shortly. Best regards, Georges. Andreas Beckmann a écrit : > Package: expeyes > Version: 2.0.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package starts processes > where it shouldn't. This is very probably due to not using invoke-rc.d > as mandated by policy 9.3.3.2. This is seriously disturbing! ;-) > > See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 > and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well > as /usr/share/doc/sysv-rc/README.policy-rc.d.gz > > >From the attached log (scroll to the bottom...): > > Selecting previously unselected package expeyes. > (Reading database ... 14017 files and directories currently installed.) > Unpacking expeyes (from .../expeyes_2.0.0-1_all.deb) ... > Setting up expeyes (2.0.0-1) ... > udev requires a mounted sysfs, not started ... failed! > failed! > dpkg: error processing expeyes (--configure): > subprocess installed post-installation script returned error exit status 1 > configured to not write apport reports > Errors were encountered while processing: > expeyes > > > expeyes.postinst uses the 'service' command instead of 'invoke-rc.d' and > disrespects policy-rc.d that way, trying to start udev in a chroot ... > > > > cheers, > > Andreas
signature.asc
Description: Digital signature
