python-imaging in EPEL4

Michael Schwendt bugs.michael at gmx.net
Mon Jan 21 19:12:52 UTC 2008


On Mon, 21 Jan 2008 20:01:53 +0100, Thorsten Leemhuis wrote:

> >> On the other hand: we cannot increase the epoch only in EPEL4 because
> >> then the upgrade path to RHEL5 is broken (still/again).
> >> Which of the two things is worse?
> > The third thing. ;) Replacing a pkg from RHEL ;-P
> 
> That would only happen on update afaics.

Only because RHEL4 does not include python-imaging at all. Still, even
for fresh install upgrades from EL4 -> EL5 this package would be downgraded.
Anything fixed in 1.1.6 might reappear due to this downgrade. The
python-imaging ChangeLog is not short.

The least to expect would be to include RHEL5's package _as is_ in EPEL4
and not downgrade it to 1.1.4 and not upgrade it to 1.1.6 either.




More information about the epel-devel-list mailing list