|
Oops! I guess I'm really running Sid. I
didn't realize that unstable had been changed to Sid. Duh! What rock
have I been hiding under?
Anyways, my problem still stands. Could some
kind soul please shed a little light on it for me? Please?
Tom
----- Original Message -----
From: Thomas
Delany
Sent: Friday, December 22, 2000 2:01 PM
Subject: Woody dselect Woes Hi,
I have a Debian system running Woody that I am
having big problems with re: dselect and updating it.
I was in the middle of updating the system with
dselect when I attempted to background the dselect process in order to do
something that was suggested by the output from one of the packages that was
being configured. Any way, to make a long story short, I somehow managed
to hang the system and had to (gulp) push the reset button.
After reboot, things were a mess. I now have
a bunch of half-configured packages, and a bunch more that won't install due to
dependency problems. The biggest problem seems to involve getting debconf
configured. When its configuration runs, I get the following:
Use of reserved word "our" is deprecated at
/usr/lib/perl5/Debconf/Gettext.pm line 19.
Bareword "our" not allowed while "strict subs" in use at /usr/lib/perl5/Debconf/Gettext.pm line 19. Unquoted string "our" may clash with future reserved word at /usr/lib/perl5/Debconf/Gettext.pm line 19. Array found where operator expected at /usr/lib/perl5/Debconf/Gettext.pm line 19, at end of line (Do you need to predeclare our?) Global symbol "@EXPORT" requires explicit package name at /usr/lib/perl5/Debconf/Gettext.pm line 19. syntax error at /usr/lib/perl5/Debconf/Gettext.pm line 19, near "our @EXPORT" BEGIN failed--compilation aborted at /usr/lib/perl5/Debconf/Template.pm line 7. 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 I ran dpkg --install for the debconf package by itself to capture the above error text. I admit that I'm hardly a Linux power user, and I'm totally at a loss as to how to fix this. Any help would be greatly appreciated. Tom |