0.5.15lorg3.1 loses epochs on rh7.3/rh8.0/rh9 (promoteepoch?)

[Dag Wieers]

On Mon, 5 Jun 2006, Axel Thimm wrote:

> On Fri, May 26, 2006 at 08:32:07PM +0200, Axel Thimm wrote:
> > The following packages have unmet dependencies:
> >   rpm-build.32bit: Depends: perl (>= 5.006001)
> > 
> > rpm-build requires 5.006001 and perl offers 1:5.6.1-36.1.73, so it
> > looks like the epoch was dropped.
> > 
> > I think this might be a promoteepoch handling bug. All these three
> > have promoteepoch turned on [and need it turned on :/].
> 
> just an update: Panu fixed this in r200 (thanks again!), so if anyone
> uses apt on any of these distros, you should grab this changeset
> (although it is probably only triggered by the presence of a newer
> rpm, but if you use apt to manage chroots of elder distros on a newer
> system, you're a candidate, too).

I don't have this problem and I don't have to use promoteepoch when using 
older distros on a newer system (eg. my buildsystem is EL4, the chroots 
are original-rpm el2,rh7,rh9,el3,fc1,fc2,fc3,el4).

I'm a bit confused to who needs to use this promoteepoch configuration 
option. Is it possible that it is only required if the packages were made 
with rpm < 4.2.1 and the rpm in use is >= 4.2.1 ? (basicly atrpms)

Kind regards,
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]