package man-db 2.5.7-2 failed to install/upgrade: Bareword found where operator expected at ../../lib/POSIX.pm

Bug #585673 reported by JOSHUA
This bug report is a duplicate of:  Bug #1372673: excessive debconf use when triggered. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: man-db

help

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue May 25 22:18:47 2010
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: man-db
Title: package man-db 2.5.7-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2

Revision history for this message
JOSHUA (jogo305-live) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report

The error is
Processing triggers for man-db ...

Bareword found where operator expected at ../../lib/POSIX.pm (autosplit into ../../lib/auto/POSIX/load_imports.al) line 903, near "setsid setuid sysconf tcgetpgrp tcsetpgrp ttyname)Y"

  (Might be a runaway multi-line () string starting on line 889)

 (Do you need to predeclare setsid?)

syntax errorMissing right curly or square bracket at ../../lib/POSIX.pm (autosplit into ../../lib/auto/POSIX/load_imports.al) line 982, at end of line

Compilation failed in require at /usr/share/perl/5.10/AutoLoader.pm line 27.

 at /usr/lib/perl/5.10/POSIX.pm line 25

BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 7.

Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.

BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.

Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.

BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.

Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.

Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.

BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.

Compilation failed in require at /usr/share/debconf/frontend line 6.

BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.

dpkg: error processing man-db (--remove):

 subprocess installed post-installation script returned error exit status 2

summary: - package man-db 2.5.7-2 failed to install/upgrade: ErrorMessage:
- subprocess installed post-installation script returned error exit status
- 2
+ package man-db 2.5.7-2 failed to install/upgrade: Bareword found where
+ operator expected at ../../lib/POSIX.pm
Changed in man-db (Ubuntu):
importance: Undecided → Low
tags: added: dist-upgrade
Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks for your report. The basic problem here is that man-db's trigger uses debconf to decide whether to update the manual page database, but debconf is not always reliably usable in triggers. I finally figured out a simple way to avoid this problem, which I'm tracking as bug 1372673. If you are still affected by this locally (which I realise is unlikely in the case of some of the older bugs of this type), then running "sudo dpkg --configure -a && sudo apt-get -f install" in a terminal should normally be enough to get the package management system back to a sensible state.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.