Re: Please don't remove gcc-3.2 before release of sarge
* Matthias Klose (doko@cs.tu-berlin.de) [040731 11:25]:
> Andreas Barth writes:
> > currently, three package still build-dep on gcc-3.2: libxml2,
> > systemimager and xen. However, 520 packages depend on one of the
> > libxml2-binary packages, including kde and gnome. So, I would consider
> > it a bad idea to remove gcc-3.2 before release of sarge.
> 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]
> 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?)
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).
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Reply to: