On Fri, Jul 27, 2001 at 01:24:16PM -0300, Henry Lebowzki wrote: > I'm sorry if I sound hysterical, but I have reasons for concern. In > fact, I'm truly desperate: it has been over a three months that I try to > tackle this problem whenever I have some time. > I was never able to use TeX on my potato, because the package somehow > got "broken". And I mean *badly* broken. In dselect, it appear as *RI, > which means that I should reinstall it.
> (Reading database ... 115823 files and directories currently installed.) > Preparing to replace tetex-bin 1.0.6-7 (using > .../tetex-bin_1.0.6-7_i386.deb) ... > Unpacking replacement tetex-bin ... > open /var/lib/xaw-wrappers/update-wrappers-history: Arquivo ou diret?rio > n?o encontrado [file or directory not found] > dpkg: warning - old post-removal script returned error exit status 2 > dpkg - trying script from the new package instead ... > open /var/lib/xaw-wrappers/update-wrappers-history: Arquivo ou diret?rio > n?o encontrado [file or directory not found] > dpkg: error processing > /var/cache/apt/archives/tetex-bin_1.0.6-7_i386.deb (--unpack): > subprocess new post-removal script returned error exit status 2 > open /var/lib/xaw-wrappers/update-wrappers-history: Arquivo ou diret?rio > n?o encontrado [file or directory not found] Just a remark: I'm not entirely sure if it wise to use any other than the default locale settings in the root account. > I have no idea...I'm desperate, I've tried everything I know. Even dpkg > with the force option... Try $EDITOR /var/lib/dpkg/info/tetex-bin.prerm and comment out the offending line or fix the statement so that it doesn't break. Please also consider filing a properly documented bug into the debian bug tracking system. > With all the time and effort I put in solving this problem, I'm sttil at > ground zero with this package. > > I am seriously considering the possibility that: > 1) There is a bug in the tetex-bin package > 2) There is a bug in apt-get (!!!!!!!!!!!!!) > > Why am I considering apt-get? Because if I try to install *anything*, > apt-get simply goes crazy with stupid messages. For instance, when I > apt-get install grep-dctrl: The bug is probably in tetex-bin, for having a broken prerm script. The problem on the packaging system level is not with apt-get, but in dpkg, in that it is not possible to deal with broken maintainer scripts in any other fashion than to edit the scripts. Cheers, Joost
