David Steinbrunner wrote: > David Steinbrunner wrote: > >> David Steinbrunner wrote: >> >> >>> I have noticed a few issues with the modules that should be available via >>> http://packages.sw.be/ but are not. The issue basically boils down to >>> modules >>> not building due to missing dependencies that are built and available. Here >>> are the example I have: >>> >>> perl-Captcha-reCAPTCHA-0.92: >>> - perl(HTML::Tiny) >= 0.904 is needed by >>> perl-Captcha-reCAPTCHA-0.92-1.el5.rf.noarch >>> - perl-HTML-Tiny-1.05-1.el5.rf.noarch.rpm is available >>> >>> perl-Business-OnlinePayment-PayflowPro-1.01: >>> - perl(Business::OnlinePayment) >= 3 is needed by >>> perl-Business-OnlinePayment-PayflowPro-1.01-1.el5.rf.noarch >>> - perl-Business-OnlinePayment-3.00-1.el5.rf.noarch.rpm is available >>> >>> perl-MIME-tools-5.427: >>> - perl(File::Temp) >= 0.17 is needed by >>> perl-MIME-tools-5.427-1.el5.test.noarch >>> - perl-File-Temp-0.22-1.el5.rf.noarch.rpm is available >>> >>> I'm wondering if this is a widespread issue... >> >> Here are some more actually: >> >> perl-Class-MOP-0.98: >> - perl(Try::Tiny) >= 0.02 is needed by perl-Class-MOP-0.98-1.el5.rf.x86_64 >> - perl-Try-Tiny-0.04-1.el5.rf.noarch.rpm is available >> >> perl-Moose-1.00: >> - perl(Try::Tiny) >= 0.02 is needed by perl-Moose-1.00-1.el5.rf.x86_64 >> - same issue with perl-Class-MOP-0.98... >> - perl(Class::MOP) >= 0.98 is needed by perl-Moose-1.00-1.el5.rf.x86_64 >> - would not be an issue if perl-Class-MOP-0.98 would build >> >> perl-MooseX-Types-0.21: >> - perl(Moose) >= 0.91 is needed by perl-MooseX-Types-0.21-1.el5.rf.noarch >> - This is not actually like the other issues but shows that other things >> are >> not getting built due to these issues. If perl-Moose-1.00 would build then >> so >> would perl-MooseX-Types-0.21 > > It has been almost a month since I noted the above. Regardless of why these > builds are not working it appears the a manual rebuild per reported package > would resolve the issue. Is it possible to have manual rebuilds done on the > short time when issues like these are found until a better way to have the big > picture problem resolved?
Ok, at a month and a half on this now. Am I mistaken on thinking this is a slightly big issue? It seems Dag is the only person that can do anything about these issues and a direct email along with a direct donation since reporting these issues has not even resulted in a reply. I don't mean to write to put down Dag or rpmforge. I'm pretty committed to rpmforge and if I was not I would not have made a donation and just moved on to EPEL or the like. Which is basically my point. rpmforge is likely losing a portion of its community and/or not building the community due to a lack of responsiveness on any number of levels. It seems to me things become lost in the mailinglist which would likely not in a issue/ticket/bug tracking system. Another thing is, Dag appears to be a single point of failure for the issues noted above so what would happen if he was permanently indisposed? -- David Steinbrunner _______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
