I've encountered problems with non-responsive maintainer of libssh2 (CC'd). I need to fix some serious issues within Fedora packages, which have been already fixed elsewhere. In particular, bug #539444 breaks Fedora curl and builds of curl in Koji. There are also some packaging issues I'd like to address - see https://bugzilla.redhat.com/show_bug.cgi?id=523796#c6 for details. I've already fixed all of them, but can't get them in since I have no access to Fedora CVS. All Fedora releases are now broken for nothing.[[BR]] [[BR]] As there was no reply for more than a month, I started the non-responsive maintainer process at fedora-devel: http://www.linux-archive.org/fedora-development/304518-formal-request-package-take-over-libssh2.html - it ends up with Chris shown alive, which I really appreciated. Unfortunately I have still no access to CVS, so that I am not able to fix Fedora.[[BR]] [[BR]] Would be possible to reassign the package to me? I already maintain the same package elsewhere. Or at least give me the access for commit to libssh2? Thanks in advance!
bug 539444 is a Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=539444 not a ticket number
At the 2010-01-15 fesco meeting it was decided that I should contact cweyl and see if I can get this fixed up. Also, dgilmore is going to commit the curl fixes needed in rawhide.
We will revisit next week if nothing progresses.
Just to clarify it a bit. All Fedora releases are affected, the bug is critical. The only difference is that F-11 curl builds do not run the test suite and therefore pass well. But curl with broken functionality is actually worse than a build failure :-)
To summarize the current state of art - the most critical bug is now fixed in Fedora 12 and rawhide - Chris finally got the patch in yesterday. Nevertheless the bug still persists in Fedora 11 and there are also some minor issues even in rawhide I'd like to address. Unfortunately I have still no way to communicate with Chris beyond FESCo.
Chris is not non-responsive, so we are going to go ahead and close this out.
Please do file bugs for items you spot. Also, libssh2 has another co-maintainer you can send changes/requests to as well now.
I've already fixed all of the bugs. So filling them as new bugs and then checking how successful is Chris in solving the same bugs again looks like redundant work to me. But you're the boss :-)
I also think (and have said so during the meeting) that forcing kdudka to go through Bugzilla for all his fixes is counterproductive and a big waste of time. Why can't he just get commit access? So I'm hereby personally asking cweyl to put personal differences aside and act in the best interest of the project. I don't see a valid reason for rejecting kdudka's comaintainership request.
Non-responsiveness is back, reopening:[[BR]] [[BR]] https://bugzilla.redhat.com/558964 [[BR]] https://bugzilla.redhat.com/632916 [[BR]]
I mailed the maintainers here for more info. Note that cweyl isn't the only maintainer of that package. I've also asked him to reconsider allowing you to just commit fixes.
I'm all in favour for giving Kamil commit access. Myself I'm only (formally) maintaining the EPEL branches (and I'll be travelling this week) but I'll try to find some time to have a look at the Bz:s towards the weekend.
Chris has been away from Fedora with real-life issues for a few months now; the perl-sig guys (primarily Iain Arnell) have been filling in looking after the perl packages but the other packages are probably in need of more co-maintainers if tickets are not being looked at.
So (as an interested bystander, and co-maintainer of curl, which uses libssh2), I'd also advocate giving Kamil commit access here.
I've mailed Chris and set commits allowed for kdudka on the package.
Login to comment on this ticket.