libg++-2.7.2.deb is old?

[Amos Shapira <amos@dsi.co.il>]

Hello,

In order to test a local copy of buzz-fixed before burning it on a
CD-ROM, we tried to run "dpkg --root=... --unpack", just to see if the
files aren't corrupted.

We got some results we don't understand completly:

1. Most packages finished fine, they produced output like:

(Reading database ... 3368 files and directories currently installed.)
Preparing to replace CGI-modules (using .../devel/CGI-modules_2.75-3.deb) ...
Unpacking replacement CGI-modules ...
Selecting previously deselected package aout-binutils.
Unpacking aout-binutils (from .../aout-binutils_2.5.2-11.deb) ...
Selecting previously deselected package aout-gcc.
Unpacking aout-gcc (from .../devel/aout-gcc_2.6.3-13.deb) ...


and so on.  So I assume it means I'm more-or-less on the right
track.

2. some packages produced the following output:

Selecting previously deselected package perl.
Unpacking perl (from .../devel/perl_5.003-2.deb) ...
dpkg (subprocess): unable to execute new pre-installation script: No such
file or directory
dpkg: error processing yigal/debian/buzz-fixed/binary-i386/devel/perl_5.0
03-2.deb (--unpack):
 subprocess pre-installation script returned error exit status 2

(I've cut a couple of lines to fit to the mail message).

Notice that the system-level error is "No such file or directory".
When run without the --root option, it installs fine.

In addition, libg++ in particular seems to be still in old .deb format
(0.93).

I've updated the dpkg I use to be 1.2.14elf, from buzz-fixed.

Can anyone explain me what I'm doing wrong?

Thanks,

--Amos