g++-3.4 (3.4.1-7) has a dependency of the form

	gcc-3.4 (>= 3.4.1-7), gcc-3.4 (<< 3.4.2)

to ensure that the g++ driver (/usr/bin/g++-3.4) can find files in the
gcclibdir (/usr/lib/gcc/<arch>/3.4.1 or /usr/lib/gcc/<arch>/3.4.2).

Having installed all of gcc-3.4 3.4.1-7 binaries, and installing new
gcc-3.4-base, cpp-3.4, gcc-3.4, libcpp1 (all 3.4.2-1) using dpkg -i
succeeds, leaving a broken g++-3.4:

configure:2230: g++-3.4 -o conftest    conftest.C  1>&5
ld: cannot open crtbegin.o: No such file or directory
configure: failed program was:
#line 2225 "configure"
#include "confdefs.h"
int main(){return(0);}

calling now dselect hints you at the broken dependencies. Is dpkg
supposed to reject this upgrade?

	Matthias

merge 217862 270545 170825
thanks
If you install g++-3.4 3.4.1-7 binaries at the same time you try to
install gcc-3.4 3.4.2-1 binaries, this fails.  It's only the upgrade
that's not failing.

This is just a symptom of the "dpkg doesn't recheck versioned
dependencies" bug, merging with that.  It's a good test case for it.

Scott