On Tue, Jan 02, 2018 at 08:02:37AM +0100, Irrwahn wrote:
> Hendrik Boom wrote on 02.01.2018 03:49:
> > lprng is only partially installed after upgrade.  Aptitude and apt keep 
> > telling me this.  However, it seems to work fine, and I have no problems 
> > talking to my postscript laser printer. 
> > 
> > lprng's line in interactive aptitude is:
> > 
> > Ch    lprng                          3.8.B-2.1    3.8.B-2.1
> > 
> > on trying to clear its status by an explicit install, it appears not to 
> > be able to 'start' it: 
> > 
> > root@notlookedfor:/home/hendrik/printme# aptitude install lprng
> > The following partially installed packages will be configured:
> >   lprng 
> > No packages will be installed, upgraded, or removed.
> > 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> > Need to get 0 B of archives. After unpacking 0 B will be used.
> > Setting up lprng (3.8.B-2.1) ...         
> > invoke-rc.d: initscript lprng, action "start" failed.
> > dpkg: error processing package lprng (--configure):
> >  subprocess installed post-installation script returned error exit status 
> > 1
> > Errors were encountered while processing:
> >  lprng
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > Setting up lprng (3.8.B-2.1) ...
> > invoke-rc.d: initscript lprng, action "start" failed.
> > dpkg: error processing package lprng (--configure):
> >  subprocess installed post-installation script returned error exit status 
> > 1
> > Errors were encountered while processing:
> >  lprng
> >                                          
> > root@notlookedfor:/home/hendrik/printme# 
> > 
> > 
> > Any ideas?
> 
> Lprng installs and configures fine on my ascii VM (after removing
> cups-bsd and cups-client, BTW.)

Mine was upgraded from jessie a few days ago.

> 
> * Did any relevant messages end up in the system log?

I'll look in the upgrade log.

> 
> * Did you try to completely purge and then reinstall the package?

Not yet.

> 
> * There's only a few places where the /etc/init.d/lprng script can 
>   exit with a code different from 0 upon start.
>   Maybe you could try manually executing those parts of the script
>   to check which one actually fails? E.g.:
>   #test -f /usr/sbin/lpd || test -d /usr/lib/x86_64-linux-gnu/lprng || exit 5
> 
> Going by your recent slew of problem reports I cannot help the 
> impression your system may be hosed in a rather peculiar way.

It had been hosed a year or so ago -- when aptitude had thousands of 
broken or uninstalled and uninstallable packages .  A package repository 
for up-to-date ocaml had been in my sources.list and it apparently had 
packages that related neither to ocaml or Devuan jessie.  I could still 
use aptitude from the command-line, but intereactive aptitude was 
unusable.

I had to purge aptitude entirely and reinstall it using apt to cure the 
problem.

-- hendrik
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to