I'm built the first icewm-el5 package two weeks ago and it's still in
Is it being auto-pushed into epel-release, or do I need to manually push
Googling for answer didn't return any meaningful answers.
I am working on a project that requires EPEL RPMs as part of the installation
process. We also need to support environments where the target machines are
disconnected from the Internet. My question is, how would you (the EPEL
maintainers) prefer to have these packages distributed? Here are the options as
I see them:
1. Include the needed EPEL RPMS on our distribution media.
2. Include the epel-release RPM only and provide instructions for setting up a
local EPEL mirror and modifying the epel.repo file to point to that local mirror.
We will certainly give credit to the EPEL project in our documentation and
clearly indicate which RPMS are pulled from EPEL regardless of how we distribute
Let me know if anyone here has an opinion on this topic.
|=- Red Hat, Engineering, Emerging Technologies, Boston -=|
|=- Email: pmyers(a)redhat.com Phone: +1 703 362 9622 -=|
|=- GnuPG: E65E4F3D 88F9 F1C9 C2F3 1303 01FE 817C C5D2 8B91 E65E 4F3D -=|
Got a new bug report today about being unable to install Ejabberd on
EL-5. Ejabberd requires Erlang. Ejabberd is in the stable repository,
but Erlang is in the testing repository. So if you don't enable the
testing repository you can't install Ejabberd due to missing
Can either Erlang or Ejabberd be moved so that they are both available
in the same repository? I'd be fine with Ejabberd being moved back to
the testing repository.
On 29.10.2007 13:38, Michael Schwendt wrote:
> On Sun, 28 Oct 2007 21:11:26 +0100, Thorsten Leemhuis wrote:
>> * lots of packages in epel5 were moved from testing to the proper repo;
>> this thread] for some details
> Do "cvs up Config_EPEL.py" on the buildsys master to be able to define
> in the repoprune_keepdict how many pkgs to keep in the testing repos.
> For a very long time we've relied on the old defaults only: keep=1 for
> development, keep=2 for stable repos, plus the kmod whitelists. So
> for EPEL it has been keep=2 for *all* repos so far.
Seems to work fine afaics. Many thx for your help Michael!