Actually, I think I've figured it out. It looks like bugs 770025, which
was an extension of bug 736607, were intended to force gcc-4.7 to be
upgraded to the Jessie version. However, these changes were then trumped
by bug 765379 which just straight-up removed gcc-4.7 from Debian Jessie.
https:/
Package: gcc-4.9-base
Version: 4.9.2-10
Debian bug 770025 added a "Breaks: gcc-4.7-base (< 4.7.3)" header to
gcc-4.9, because it was found in bug 736607 (which relates to gcc-4.8)
that the package manager would sometimes leave the system with an
older-release version of gcc instead of using th
In my particular situation, we have software which *must* be compiled
using gcc-4.7. I'm a little confused by message #20 which seems to imply
that gcc-4.7 could be reinstalled after the upgrade is complete.
Thanks,
Tim Gokcen
3 matches
Mail list logo