Discussion:
[users] Open letter - Recent repoforge package updates
David Hrbáč
2014-05-13 08:55:07 UTC
Permalink
Dear Dag,

I can see new updates within the Repoforge. Well, thanks for them.

On the other hand, damn, those updates are not covered by commits in our
git repository on Github. They are not committed into the repository.
They goes even much further. We have plenty of upgrades in the commits
on the queue and your recent updates completely ignore the community
commits.

Well, can you comment on that? Do you consider RF project to be a
community one? Do you take it as a personal repo? Do you want the
community to cooperate, share and commit?

Regard,
David Hrb??
Dag Wieers
2014-05-13 13:46:01 UTC
Permalink
On Tue, 13 May 2014, David Hrb?? wrote:

> Dear Dag,
>
> I can see new updates within the Repoforge. Well, thanks for them.
>
> On the other hand, damn, those updates are not covered by commits in our
> git repository on Github. They are not committed into the repository.
> They goes even much further. We have plenty of upgrades in the commits
> on the queue and your recent updates completely ignore the community
> commits.
>
> Well, can you comment on that? Do you consider RF project to be a
> community one? Do you take it as a personal repo? Do you want the
> community to cooperate, share and commit?

David,

As I told you a few times, merging my local working copy with Github has
become a nightmare. I spend more time getting my local copy working to a
state again that allowed me to push to Github that I stopped bothering. I
simply don't have the time.

I gave you everything in order for you to push to Repoforge so that I am
no longer needed to build and push updates, but for some reason I never
heard back from you regarding this. (This was about adding your keys to
the rpmforge-release package, because you already have access to the
repositories).

So in the meantime I update the few packages that I need myself, or those
that have a security problem (notably clamav and flash-plugin). If
Repoforge is not a community project, we can conclude it is dead IMO.

--
-- dag wieers, dag at wieers.com, http://dag.wieers.com/
-- dagit linux solutions, contact at dagit.net, http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]
David Hrbáč
2014-05-15 22:01:24 UTC
Permalink
Dne 13.5.2014 15:46, Dag Wieers napsal(a):
> David,
>
> As I told you a few times, merging my local working copy with Github
> has become a nightmare. I spend more time getting my local copy
> working to a state again that allowed me to push to Github that I
> stopped bothering. I simply don't have the time.
>

Dag,

I really would be glad to help you with our git repo. Or maybe you can
leave you local copy and pull the upstream one. :)

> I gave you everything in order for you to push to Repoforge so that I
> am no longer needed to build and push updates, but for some reason I
> never heard back from you regarding this. (This was about adding your
> keys to the rpmforge-release package, because you already have access
> to the repositories).
>

OK, I get it. Maybe it's my fault. I definitely have my share on the
current state of RepoForge. That's I'm sure of. I dare to take it
personally :) and I'm going to step in again. I had a lot of other
job-work and had no time for RF. :(

> So in the meantime I update the few packages that I need myself, or
> those that have a security problem

Well, that's something very annoying. Since now we _again_ ship the
packages which do not have the proper spec prescription in the git
repository. And we want them to be here. We don't need the entropy here.
:) We want the repo to be reproducible for every one out there, don't we? :)

> (notably clamav and flash-plugin). If Repoforge is not a community
> project, we can conclude it is dead IMO.
>

I hope that we are still the community one, maybe rather or too much
outdated, depend on the point of view :) Maybe having the clinical death
or just resting... :)

(It's not dead parrot, he is just resting...
http://youtu.be/4vuW6tQ0218?t=23s)

Well, we are where we are and my letter was not the best solution.
Anyway, I just felt disappointed, exhausted, and all that stuff. I just
do not want the RepoForge die. I guess, it's too early...

Regards,
David Hrb??
Bjarne Saltbæk
2014-06-16 00:20:58 UTC
Permalink
Hi David.

Is there anything I can help with?
I have the time but dont know what to do to help getting Repoforge active again?

BR,
Bjarne


> Date: Fri, 16 May 2014 00:01:24 +0200
> From: david-lists at hrbac.cz
> To: dag at wieers.com
> CC: users at lists.repoforge.org
> Subject: Re: [users] Open letter - Recent repoforge package updates
>
> Dne 13.5.2014 15:46, Dag Wieers napsal(a):
> > David,
> >
> > As I told you a few times, merging my local working copy with Github
> > has become a nightmare. I spend more time getting my local copy
> > working to a state again that allowed me to push to Github that I
> > stopped bothering. I simply don't have the time.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20140616/603b2bc6/attachment.html>
David Hrbáč
2014-06-16 13:08:51 UTC
Permalink
Dne 16.6.2014 02:20, Bjarne Saltb?k napsal(a):
> Hi David.
>
> Is there anything I can help with?
> I have the time but dont know what to do to help getting
> Repoforge active again?
>
> BR,
> Bjarne

Hi Bjarne,

Well, sorry to reply so late, I'm terribly busy. We have to build all
the packages which are newer in Git repo then those in the RPM
repository. It would be nice to have the script which will tell ok, the
package within repository is older then this spec file version.

Can you elaborate on it? It can incorporate repoquery on SRPM repo.

Are you familiar with Koji o Punghi?

Thanks,
DH

>
>
> > Date: Fri, 16 May 2014 00:01:24 +0200
> > From: david-lists at hrbac.cz
> > To: dag at wieers.com
> > CC: users at lists.repoforge.org
> > Subject: Re: [users] Open letter - Recent repoforge package updates
> >
> > Dne 13.5.2014 15:46, Dag Wieers napsal(a):
> > > David,
> > >
> > > As I told you a few times, merging my local working copy with Github
> > > has become a nightmare. I spend more time getting my local copy
> > > working to a state again that allowed me to push to Github that I
> > > stopped bothering. I simply don't have the time.
>
>
>
> _______________________________________________
> users mailing list
> users at lists.repoforge.org
> http://lists.repoforge.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20140616/a4db2e66/attachment.html>
Loading...