On Sat, Mar 26, 2005 at 03:06:58PM +0100, Roberto wrote: > Package: wspanish > Version: 1.0.14 > > When I upgrade wspanish with apt-get in Sarge, after uncompressed > wspanish, apt-get gives error because: > > Can't call method "choices" on an undefined value at > /usr/share/perl5/Debconf/Question.pm line 85, <GEN1> line 5. > > and apt-get don't install wspanish. > > żis this a bug of wspanish? > > > I am using Debian GNU/Linux Sarge, kernel > 2.4.27-2-k7
Let me guess, is your /var partition nearly full? That seems debconf type 1 db corruption >From the (not yet uploaded) dictionaries-common README.problems file: ======================================================================= Problems removing a wordlist/ispell dictionary ---------------------------------------------- Something like --- # dpkg --purge wbritish (Reading database ... 111027 files and directories currently installed.) Removing wbritish ... Can't call method "choices" on an undefined value at /usr/share/perl5/Debconf/Question.pm line 85, <GEN0> line 4. dpkg: error processing wbritish (--purge): subprocess post-removal script returned error exit status 29 Errors were encountered while processing: wbritish --- is usually related to debconf type 1 db corruption, see e.g., http://bugs.debian.org/198297 or pages for bug reports 224400, 247849, 255193, 282587, 284287, 297534. Please take a look at those bug reports to check whether the problem is actually the same, and see if you can provide more information about the problem before proceeding further. As a side note, it has been pointed out that there is a high probability of this problem being related to a nearly full /var partition. After that, the suggested fix is, quoting Joey Hess message in above bug page > By purging and reinstalling the package, you only fixed the entries for > that package. I suggest you run /usr/share/debconf/fix_db.pl as root, > which will delete all the orphaned questions. You may end up having to > repeat your answers to some debconf questions during future upgrades, > but that's a small price to pay for a consistent debconf database. ========================================================================== While it deals with removal, seems the same problem. Unless not the case, I will reassign this bug report top debconf. Cheers, -- Agustin
