On Wed, 16 Aug 2006, Matthias Klose wrote:
Alexey Toptygin writes:gcc-4.0-base and gcc-4.1-base in unstable still have this bug:the comment in the bug report still holds:yes, these are identical, because they are hard links, needed to solve an upgrade issue when upgrading from 4.0.2-9.
Right, but this view: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gcc-4.1-baselists the bug as resolved and to-be-archived. I think it would be good to clone this bug to gcc-4.0-base, since it affects that package as well.
Alexey