Re: Debconf failed configure
"Francesco P. Lovergine" <frankie@debian.org> writes:
> 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):
> >
[...]
> Latest version is 1.0.16 in unstable.
> My first 2 cents suggestion is to upgrade to this one.
I tried debconf 1.0.16 and even 1.0.17 but it didn't work. I
downloaded packages from
<ftp://ftp.fi.debian.org/debian/pool/main/d/debconf/>. Here's an
example (without sudo):
# dpkg -i debconf_1.0.17_all.deb
(Reading database ... 61463 files and directories currently installed.)
Preparing to replace debconf 1.0.16 (using debconf_1.0.17_all.deb) ...
Unpacking replacement debconf ...
Setting up debconf (1.0.17) ...
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 (--install):
subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
debconf
#
> Moreover, I found sudo causes sometimes weird things. Run dpkg as root
> instead, whenever possible.
Can you elaborate more? I have used sudo few years now without any
problems and I have never had or heard of any problems with it. I think
it's a great tool. But if there are problems with it, I *really* would
like to know.
--
Kalle Valo
Reply to: