12:43 a.m.
RHEL 5.3 brought with it some new additions
pexepct ( congrats rsc, your package got in unmodified)
java-1.6.0-openjdk (only on i386 and x86_64) we will need to ExclusiveArch
ppc it.
In accordance with out guideline of not replacing RHEL packages we need to
remove them. there are possibly others. Im going to get together a list of
packages that moved from EPEL to RHEL. I will mark them dead in cvs and
remove them from the repos.
Dennis
1:43 a.m.
On Fri, 23 Jan 2009, Dennis Gilmore wrote:
pexepct ( congrats rsc, your package got in unmodified)
That already happend for RHEL 5.2, that's nothing new for RHEL 5.3.
In accordance with out guideline of not replacing RHEL packages we
need to
remove them. there are possibly others. Im going to get together a list of
packages that moved from EPEL to RHEL. I will mark them dead in cvs and
remove them from the repos.
Again, can we please move an older version of pexpect (e.g. -0 rather -1 or
so) for EPEL? You did not answer my question until now.
Greetings,
Robert
8:30 a.m.
On Fri, 23 Jan 2009, Robert Scheck wrote:
On Fri, 23 Jan 2009, Dennis Gilmore wrote:
> pexepct ( congrats rsc, your package got in unmodified)
That already happend for RHEL 5.2, that's nothing new for RHEL 5.3.
> In accordance with out guideline of not replacing RHEL packages we need to
> remove them. there are possibly others. Im going to get together a list of
> packages that moved from EPEL to RHEL. I will mark them dead in cvs and
> remove them from the repos.
Again, can we please move an older version of pexpect (e.g. -0 rather -1 or
so) for EPEL? You did not answer my question until now.
I'm not sure why you think you and pexpect are so special. We've done
this many times in the past and it works just fine.
-Mike
9:49 a.m.
On Fri, 23 Jan 2009, Mike McGrath wrote:
I'm not sure why you think you and pexpect are so special.
We've done
this many times in the past and it works just fine.
I'm not sure why you are still thinking, that we need to break things by
removing the package: It won't break more as Red Hat already has broken by
not incrementing release of ENVRA when importing it from EPEL into RHEL.
As we figgured out in this thread before, the only real way is to increment
release on Red Hat side and freeze the package in EPEL or keep ENVRA of it
in EPEL below ENVRA of it in RHEL.
Greetings,
Robert
5565
days inactive
5565
days old
epel-devel@lists.fedoraproject.org
3 comments
3 participants
participants (3)
-
Dennis Gilmore -
Mike McGrath -
Robert Scheck