Re: Debconf failed configure
On Fri, Oct 26, 2001 at 04:23:12PM +0300, Kalle Valo wrote:
> I have managed to break debconf somehow, but I don't how. I don't
> remember doing anything stupid. Here's some info (sorry for long
> lines):
>
> litku:~$ dpkg -l debconf
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-==============-==============-============================================
> iF debconf 1.0.15 Debian configuration management system
> litku:~$ sudo dpkg --configure debconf
> Setting up debconf (1.0.15) ...
> Bareword found where operator expected at /usr/share/perl5/Debconf/DbDriver.pm line 25, near "qr/$params{$field}/i"
> syntax error at /usr/share/perl5/Debconf/DbDriver.pm line 25, near "qr/$params{$field}/i"
> 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 22.
> BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 22.
> dpkg: error processing debconf (--configure):
> subprocess post-installation script returned error exit status 255
> Errors were encountered while processing:
> debconf
> litku:~$
>
> I'm running unstable and I have updated my system quite often, until
> this problem appeared.
>
> Can you give any hints to fix this or what the problem might be? I can
> provide more info if needed.
>
Latest version is 1.0.16 in unstable.
My first 2 cents suggestion is to upgrade to this one.
Moreover, I found sudo causes sometimes weird things. Run dpkg as root
instead, whenever possible.
--
Francesco P. Lovergine
Reply to: