On Wed, 8 Jul 2009, Olaf Mueller wrote:
Dag Wieers wrote:
On Wed, 8 Jul 2009, Olaf Mueller wrote:
Hugo van der Kooij wrote:
Joe Ogulin wrote:
I am running CentOS 5.3. I thought it was just going to be two
packages... perl-MP3-Tag and perl-Unix-Process... then today, it
added 5 more.
Great. So you mix Centos, rpmforge and random other packages and now
all of a sudden it is a rpmforge problem?
Please make sure that you only combine Centos and rpmforge
repositories before you start to report problems.
I have a server with only CentOS and rpmforge as repos and it breaks
dependencies on perl packages. And this is a problem by rpmforge
cause of building new perl packages without solving all dependencies.
Great. I don't mix repos on this server and rpmforge breaks yum.
And now? What should I do? Give me your good suggestion.
Your complete answer is wrong, the original poster has a problem with
rpmforge repo. It is no others repo fault.
Maybe we should ask money so people can demand something to be changed
Is this your goal for rpmforge repo? To take money?
No, but apparently people (you) expect things from us as if we are being
paid for doing this.
That is why I am making it absolutely clear we don't guarantee anything,
what is provided, is provided as-is.
You shouldn't be using RPMforge anyway if your systems are so
critical.
In my opinion that is an important statement. One of my server is a
mailserver with only clamav packages from rpmforge for mail scanning. I
will think about alternatives.
You cut away an important statement. "You shouldn't use RPMforge
*directly* if your systems are critical. You should manage your own
repository and cherry-pick the packages you need."
We don't do any security auditing either, so you might want to make a big
distinction between the RHEL packages, and the packages you get from other
sources...
CentOS, epel and other yum repos are all serious projects with the aim
to be stable as possible. I always thought rpmforge is such a project
too.
Yes, we aim to be as stable as possible. Mind you though, that all of the
above projects make no claim what is possible.
Maybe a 'testing before delivering' rpmforge-repo would be a good
choice. But you are right, nobody forces me to use rpmforge.
We do have that. Let me ask you a question, would you be willing to help
implement something better ? Or are you just one of those users that want
everything, as long as someone else is doing it ?
I don't mind if you are, but I guess that limits this conversation quite
severly.
I have answer to Hugo van der Kooij mail cause he informed the original
poster wrong. It is not the fault by other repos. Stand to your own
mistakes and don't take the user of your repo for an idiot.
I don't think anybody claims otherwise. Hugo made a general statement
about not mixing repositories. It was quite clear that the perl
dependency issues are caused by RPMforge. Anyone following the svn-commits
mailinglist would know.
On the other hand, I think you need to talk to the yum developers too.
Since there is no good reason for blocking all updates if one dependency
is missing.
--
-- 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
