On Fri, 26 Sep 2008, Nils Breunese (Lemonbit) wrote:
Dag Wieers wrote:
> Until yum has magically transformed into apt it would be nice towards
> RPMForge users to provide a repository that doesn't cause these errors on
> their end when they haven't done anything wrong (like mixing incompatible
> repositories).
Sure, by all means help us. I am not planning to spend any more time than I
am already putting into this. But I welcome anyone interested in helping
with this. (either in RPMforge or rpmrepo)
For one, I have no interest in maintaining a testing and production
repository if that means I have to spend time selecting packages and
transfering packages.
As long as everybody is complaining and nobody is willing to help, the
situation will be the same. You cannot claim any more of my free time :)
I believe you knew you were breaking yum update for people who are using your
audacity package with the update to wxGTK 2.8. You posted a message about
this on your blog, but not on this list, so I'm not surprised that people
didn't know and posted messages to this list to complain. Of course you don't
owe anyone anything, but replying that they should use apt instead is just
not very nice to your users. You have every right to say what you want, as I
believe you put a lot of time into this, but blowing people off like that is
just putting me off and I wanted to let you know.
Why is it blowing people off if I say that apt does not have this problem ?
I think yum should be more resilient, but I have been saying that for
years and nobody did anything about it. I don't care because I don't use
it as long as I can use apt and yum is still in its infancy.
We can argue whether the above is true, but I have no time to fix yum, I
am not interested in spending more time to maintain more infrastructure.
rpmrepo was going to be the solution, but apparently is either not having
enough manpower or nobody driving it.
I am not interested in driving rpmrepo because I have no more freetime.
And I don't mind that people complain it is not working, I do mind that
they are not helping to solve the issue.
Besides, audacity is hardly that important. It may be for some users, but
they have the option to not upgrade. Maybe we fix it next week if we can
update flac ? I do not promise anything.
And maybe it is very egoistic of me to update wxGTK when I needed
truecrypt and at the same time broke audacity. But then again we have
people complain that EPEL is not compatible with RPMforge because they
have wxGTK 2.8.
So I cannot do good anyway, so I prefer to do myself good :-)
I'm afraid I can't be of any help building packages, but I always try to help
people here with any issues that I know how to solve.
And I appreciate it.
--
-- 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
