Package EVR problems in EPEL 2008-01-20
Joel Andres Granados
jgranado at redhat.com
Mon Jan 21 14:03:06 UTC 2008
Michael Schwendt wrote:
> On Mon, 21 Jan 2008 10:39:42 +0000, José Matos wrote:
>
>> On Sunday 20 January 2008 19:42:55 buildsys wrote:
>>> python-imaging: jamatos AT fc up pt
>>> EPEL4 > EL5 (0:1.1.6-3.el4 > 0:1.1.5-5.el5)
>> Was not this solved before?
>> According to the cvs the last version available is
>>
>> %changelog
>> * Mon Jul 23 2007 Joel Andres Granados <jgranado at redhat dot com> -
>> 0:1.1.4-1
>> - Build python-imaging for EPEL4 with the version from FC3. EPEL4 are
>> packages
>> - that can be installed in RHEL4**.
>>
>> IIRC we had downgraded to cope with the inclusion of it in EL5. This was
>> done before the official launch of EPEL so I have no clue what has gone
>> wrong.
>
> Depends on who "we" is. You cannot downgrade a package without asking the
> epel-signers to delete a newer package in the repo. The repo shows that an
> older package was pushed several months after the higher version:
>
> http://download.fedora.redhat.com/pub/epel/4/SRPMS/
>
> [ ] python-imaging-1.1.4-1.src.rpm 25-Jul-2007 11:03 418K
> [ ] python-imaging-1.1.6-3.el4.sr..> 02-Mar-2007 18:20 436K
This is extremely strange.
1. This didn't come up before :) I've been checking the EPEL fairly regularly
to see if python-imaging had any problems and it had never come up. Since
the 1.1.4 appeared after 25-Jul, it should have screamed immediately
(assuming that the 1.1.6 version was there)
2. I started co maintaining the EPEL package with jamatos around jul-2007, so
the 1.1.6 version must have been there already (IMHO). Can we actually
know who pushed it? Maybe it was automatically brought in :).
3. I checked my email logs and verified that the issue was discussed around Jul-2007
I cannot find earlier mails about the package ( I subscribed around Jul-2007, so
apologies if I'm wrong)
Don't know what to make of it. So I assume from "You cannot downgrade a package
without asking the epel-signers to delete a newer package", that the solution
is to delete the newer package. right?
Regards
--
Joel Andres Granados
Red Hat / Brno, Czech Republic
More information about the epel-devel-list
mailing list