Re: why can red hat 7 packages be installed on red hat 6.2?

[herrold <herrold owlriver com>]

On Mon, 27 Nov 2000, Rodrigo Barbosa (aka morcego) wrote:

> > (Jeff Johnson:) Almost certainly these are packaging problems,
> > probably due to inaccurate or  missing dependencies, as rpm
> > can (and does) check only dependencies that are present in the
> > package(s) being installed/upgraded.

> Jeff, I'm sorry to desagree with you, but as far as my experience goes,
> it all comes does to RH7 using gcc 2.96, which is not binary compatible
> with gcc 2.95 and egcs. That is the main problem, as far as I know.

... hmmm ...  I've not yet heard a single versioned set of specific
RH production (non-Rawhide) packages mentioned which demonstrate the
issue, so that I might try to recreate it.  We rebuild so much from
SRPM, that we should have seen this if it is truly a compiler issue.

Thre is a rather difficult dependency to satisfy with most of the
initscript started packages with "/etc/init.d" in RH 7.0, and some
might be tempted to --force or --nodeps it.  Perhaps this was done?

Neither have I encountered it in an testing environment running from
RH 2.1 to the present.  We backport rather aggressively, and are
concerned to be able to study the problem cited.

Could either Matt or Rodrigo please provide a combination which
demonstrates the issue, or point to a Bugzilla report?

-- Russ