On 2009-11-02 07:28 +0100, Christian Perrier wrote: > Quoting Michael Prokop (m...@debian.org): >> Package: capiutils >> Version: 1:3.9.20060704-4 >> Severity: grave >> Justification: renders package unusable >> >> >> Fresh installation: >> >> [...] >> Setting up libcapi20-3 (1:3.9.20060704-4) ... >> Setting up capiutils (1:3.9.20060704-4) ... >> Note: running MAKEDEV to create CAPI devices in /dev... >> /var/lib/dpkg/info/capiutils.postinst: line 13: /sbin/MAKEDEV: No such file >> or directory >> dpkg: error processing capiutils (--configure): >> subprocess installed post-installation script returned error exit status 1 >> Errors were encountered while processing: >> capiutils >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > > I just did a QA upload (isdnutils is orphaned and I was fixing l10n > bugs plus each and every trivial stuff I could find) where calls to > MAKEDEV with an hardcoded path were replaced by calls to "MAKEDEV" > alone. > > I'm not sure that will solve the problem. I'm actually sure of the > contrary..:-) > > The problem probably comes from makedev being an extra package now > while it was essential in the past.
I cannot remember makedev ever being essential, though it used to be required. > So, the solution is probably adding it to Depends (or Pre-Depends? I > need to check the policy about this). No, makedev serves absolutely no useful purpose on 99% of all Debian systems. The right solution is to only call MAKEDEV if it is available. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
