On Fri, 3 Sep 2010, Christoph Maser wrote:
Am Freitag, den 03.09.2010, 14:38 +0200 schrieb Yury V. Zaytsev:
On Fri, 2010-09-03 at 14:05 +0200, Christoph Maser wrote:
At least, rkhunter does not need it at all.
But perl-Net-SSLeay does and this is an dependency of rkhunter...
However, perl-Net-SSLeay is in base! Does rkhunter requires newer
perl-Net-SSLeay than 1.30?
Uhm wait a second i mixed that up. The newer rpmforge perl-AnyEvent
needs a new version of perl-Net-SSLeay. So actually you were right
blacklisting perl-AnyEvent should do the trick. Sorry for the confusion.
Time to start fixing this mess ? Who is interested to make a list of base
packages that RPMforge replaces, and tag these SPEC files accordingly ?
We discussed this previously, creating a new repository (eg. extras) and
use a different tag (eg. rfx) for packages that replace base.
Beware the we need to do this for RHEL3, RHEL4 and RHEL5 and in case the
tag is different for RHEL3, RHEL4 and RHEL5 (eg. dstat) this would mean:
%{?el6:# Tag: rfx}
%{?el5:# Tag: rfx}
%{?el4:# Tag: rf}
%{?el3:# Tag: rf}
Which is better IMO than forking into 4 SPEC files and maintaining each
seperately.
Once we have a list and agree on the above changes for those packages we
replace, I will remove the original packages from the repositories and add
the extras repository to the rpmforge-release package. The repository
metadata backend already understands the scenario, as does the buildtool.
--
-- dag wieers, [email protected], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
