Package: r-cran-nlme
Version: 3.1.68-2
Followup-For: Bug #349550

I think I ran into the same problem as reported in this bug, but am reporting
it just in case:
Preparing to replace r-cran-nlme 3.1.62-1 (using 
.../r-cran-nlme_3.1.68-2_i386.deb) ...
Unpacking replacement r-cran-nlme ...
Can't open perl script "/usr/lib/R/share/perl/build-help.pl": No such file or 
directory
dpkg: warning - old post-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
dpkg: ... it looks like that went OK.
Preparing to replace r-recommended 2.2.1-4 (using 
.../r-recommended_2.2.1-6_i386.deb) ...
Unpacking replacement r-recommended ...
Preparing to replace r-base-dev 2.2.1-4 (using .../r-base-dev_2.2.1-6_all.deb) 
...
Unpacking replacement r-base-dev ...
Preparing to replace r-base-core 2.2.1-4 (using 
.../r-base-core_2.2.1-6_i386.deb) ...
Unpacking replacement r-base-core ...

Comments on this bug seemed to indicate that things should be OK with
r-base-core 2.2.1-4, but as you can see I was at that level initially
and still had the problem

Also, this is in the context of an upgrade, not an uninstall.  I'm not
sure that matters, since I think upgrade = uninstall and reinstall.

Finally, note that dpkg says it thinks it recovered from the problem.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27adnvcd
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages r-cran-nlme depends on:
ii  libc6                        2.3.5-13    GNU C Library: Shared libraries an
ii  r-base-core                  2.2.1-6     GNU R core of statistical computin
ii  r-cran-lattice               0.12-11.1-1 GNU R package for 'Trellis' graphi

r-cran-nlme recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to