On 17.07.2007 13:13, Joel Andres Granados wrote:
Thorsten Leemhuis wrote:
> On 17.07.2007 12:13, Joel Andres Granados wrote:
> For the situations at hand:
> Problem1 -- python-imaging was EPEL: We made a error, but we are still
> in the testing/buildup phase, so we can still remove it from the repo
Is this true for EPEL/el4 and EPEL/el5? I ask because I have them both
in the CVS and assumed that EPEL/el4 was an already *stable* release.
/me can't follow, sorry.
EPEL in general and the Repos EPEL4 and EPEL5 are still not officially
started; that's planed for next weeks Thursday.
> and say loudly "apologize" and "we are
sorry"(¹). Not ideal, but problem
> solved.
> Problem2 -- python-imaging had a higher EVR then the EL5Client package:
> Ignore those users that got the newer python-imaging from EPEL (see
> Problem 1: "EPEL is still in testing" and "apologize").
IMO this is also very precarious "to ignore the user".
And the users isn't helped if we fix one error by making another
(bigger) one.
> (¹) -- we likely should put something (test-scripts?) in place to
make
> sure something similar does not happen again
IMO, This is VERY necessary.
Any volunteers?
[...]
CU
thl