On Fri, 26 Sep 2008, Bogdan Costescu wrote:
On Fri, 26 Sep 2008, Dag Wieers wrote:
Why is it blowing people off if I say that apt does not have this problem
?
It's not about saying it. It's about the way you have chosen to show it in
practice. Your repo is a highly regarded one, but an attitude of "I take my
toys and go home" doesn't inspire trust anymore.
OK, I hope it inspires a new repository. If I would be giving the wrong
impression by indicating all is well, how would that be better ?
I am not interested in spending more time to maintain more infrastructure
Can maintaining the infrastructure be separated from maintaining the repo ?
If so, can someone else maintain it ?
I would certainly hope so.
rpmrepo was going to be the solution, but apparently is either not having
enough manpower or nobody driving it.
There was very little public info about rpmrepo or at least very little came
my way. Can you give a more detailed explanation ? What kind of help is
needed for that ?
I don't know where it is blocked. I am trying to net get involved too much
in rpmrepo because I want to reduce the time, not increase it.
I am not interested in driving rpmrepo because I have no more freetime.
I thought that RPMForge was supposed to morph into rpmrepo such that you'd be
involved into only one repo and not in 2. Did I understand it wrong ? Or is
maintaining even one repo taking too much of your time ?
The problem is that RPMforge does not scale very well. We are a bunch of
guys, there is not central infrastructure. I have no problem helping with
another project (or changing RPMforge) so that more people can help create
packages in a way that there is an upgrade path from RPMforge. But doing
what we have been doing is not viable.
Because it depends on me mostly.
So we need to remove the dependency on me, and that is one of the reasons
why I don't want to change what we have now (the other reason is the time
I am spending right now).
So while it is technically possible to prevent the wxGTK problems and
making sure that there is a testing repository and we have tools to make
the production repository consistent, I will not be the person spending
time on that.
And I don't mind that people complain it is not working, I do mind that
they are not helping to solve the issue.
Telling people "you have to switch to apt to use my repo" will not drive them
to help you. Posting a list of things that others could do might bring much
better results. Or better ideas of doing the whole thing.
I am not saying people have to switch to apt. But it would be one
solution. The other is helping with the rpmrepo project, or making yum
more resilient.
Besides, audacity is hardly that important.
I have been bitten myself by such situations in the past, so it's not a
single case. Needing to use several media players means that a lot of
libraries are required and when something breaks it's usually a whole lot of
applications and not only one.
Because of your remarks, I don't view this case as an isolated one but more
of a statement that you make about the whole repo. I came to rely on your
repo for many things, simply because I hate duplication of effort and because
you've earned my trust over the years to produce nice packages. But trust can
also be lost...
Of course. But frankly, I am spending a few hours every day with my
packages. This will not happen for the next 10 years. I may have children,
I may have other things outside RPMforge to do.
If nothing happens, that trust will be lost at some other point in time.
Your trust does not feed me. I have been cutting back on the time I have
put in the repository when I became self-employed last year. Maybe people
haven't noticed, but that is the case.
I wanted a solution that did not depend on me for a few years now, but
nothing was forthcoming and there still does not seem to be a solution
right now. So where do we go from here ? I don't know.
And maybe it is very egoistic of me to update wxGTK when I needed
truecrypt and at the same time broke audacity.
I think that it would have be much better received if you'd have sent an
e-mail to the list saying: "OK, I know that some things are broken but
they'll be fixed shortly"; people have been patient in the past and will
likely be again if they just know what to expect.
I cannot promise that they will be fixed shortly. Do you prefer that I lie ?
I may be able to update flac, but who knows what problems that may spawn.
Again, if I could build audacity or knew there was a solution shortly, do
you think I would have released those packages ? Of course not. I released
them because they were blocking other updates after a few days of trying
to find a solution.
And only audacity was a problem. And only if you are using yum.
Many people may not have noticed, and maybe more people are now using
truecrypt than that have been affected by audacity.
Who knows ? I don't even know how many people are using RPMforge.
--
-- 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
