[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Please don't remove gcc-3.2 before release of sarge

Andreas Barth writes:
> > systemimager doesn't build-depend on gcc-3.2 anymore (in unstable). I
> > we really need to keep gcc-3.2, I'd like to remove the binaries not
> > really needed (g++-3.2, g77-3.2, gnat-3.2, gobjc-3.2,
> > libstdc++5-{dbg,dev,pic} (not libstdc++5-3.3-{dbg,dev,pic}), gcc-3.2-nof.
> Ok. Systemimager is RC-buggy in sid, but as it's not part of base, it
> needs to be either fixed there, or removed. (?)
> Xen still build-deps on gcc-3.2 on all archs, even in sid. However,
> looking at Bug #243048 tells me that this dependency is not necessary
> any more. Adam, is this information correct? [Ccing him]

please recheck with the packages from http://people.debian.org/~doko/gcc-3.3/

> > On the other hand libxml2 builds with gcc-3.4 on hppa.
> If libxml2 build with gcc-3.4 in sid, perhaps a new upload should
> happen. (Or does this have a too great risk of new problems?)

that one is done. libxml2 currently builds with 3.3 on hppa (2.6.11-4).
checked with today's unstable.

> Another remark: Even if gcc-3.2 is removed from unstable now, it'll
> stay in sarge as there is a base freeze. So, the question is to the
> RM team: Should gcc-3.2 be removed from sarge? If so, I'll take care
> of fixing xen and libxml2 in sid (even if this means a NMU).

there is currently not a single binary package built from the gcc-3.2
source in base, so that should be a safe choice.


Reply to: