Bug 523796

Thanks for filing this -- I've been meaning to update but there always seems to be something higher priority to do.

I'll see about getting it out there in the next day or so.

Please consider also applying of the following patch:
http://git.libssh2.org/?p=libssh2.git;a=commitdiff;h=683aa0f6b52fb1014873c961709102b5006372fc

The bug is present in the current Fedora package of libssh2, as well as in the latest stable release 1.2.

Alright -- 1.2 is out in rawhide (with the patch requested) and the various packages depending on it have been rebuilt.  Feel free to ping me with anything else...

Thanks for getting this in time for F-12 beta! Please remove also the trailing spaces from libssh2.spec:

$ sed -i 's/  *$//' libssh2.spec

(IMO it's OK to fix it in the CVS only, no need for build)

Please update to 1.2.2 and build it for Fedora 12.

No chance to contact the maintainer since 2009-11-25.

This package needs some maintenance to be done:
- update to new bugfix release 1.2.2
- apply fix for #539444 (breaks curl)
- re-enable test suite (+ explain why it is actually disabled)
- require OpenSSH to make the test suite more useful
- package also libssh2.pc
- fix gcc warnings

Raising priority to high as curl is still broken.

Chris, just two notes about your activity in curl/devel yesterday:

1. There was absolutely no reason for rebuild of curl in regards to this bug, not even for the release bump.

2. I didn't understand at all why the following line appeared in curl.spec (without any comment around):

        %define _default_patch_fuzz 2 \n\n

Luckily the build has failed anyhow (because of bug 539444), so that I spotted that nonsense and reverted.

You should immediately stop silently doing things on your own, without discussing them with maintainers first.  Most of your changes in curl and libssh2 are counter-productive and dangerous.  Thanks in advance!

libssh2-1.2.2-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libssh2'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0571

(In reply to comment #8)
> Chris, just two notes about your activity in curl/devel yesterday:
> 
> 1. There was absolutely no reason for rebuild of curl in regards to this bug,
> not even for the release bump.
> 
> 2. I didn't understand at all why the following line appeared in curl.spec
> (without any comment around):
> 
>         %define _default_patch_fuzz 2 \n\n
 
Sorry about that -- looks like it crept in from an older bump script.

> Luckily the build has failed anyhow (because of bug 539444), so that I spotted
> that nonsense and reverted.
> 
> You should immediately stop silently doing things on your own, without
> discussing them with maintainers first.  Most of your changes in curl and
> libssh2 are counter-productive and dangerous.  Thanks in advance!    

Counter-productive and dangerous?  Care to elaborate, or are you just taking potshots here?  I don't believe I've ever made a change to the curl package (aside from bump/build), and the only patch I've ever applied to libssh2 came from upstream.  I look forward to your retraction of this statement.  Thanks in advance!

Please try to keep issues to one per bug, rather than the smorgasbord you've listed above.  Thanks. :)

(In reply to comment #10)
> Sorry about that -- looks like it crept in from an older bump script.

I'd like to discuss *all* your changes in the curl package before they happen actually.  There is no excuse to use a script out of your control for this purposes.  If you had been aware of the change, you should have reverted it immediately.  If you were not aware of the change, then it was really dangerous since I even didn't get any mail about it.

> Counter-productive and dangerous?  Care to elaborate, or are you just taking
> potshots here?  I don't believe I've ever made a change to the curl package
> (aside from bump/build), and the only patch I've ever applied to libssh2 came
> from upstream.  I look forward to your retraction of this statement.  Thanks in
> advance!

I personally prefer mail/IRC for discussing it.  Nevertheless if you prefer bz/fesco tickets, there is not much I can do with that...

- disabling the test-suite without telling anybody
- adding "Requires: pkgconfig" to docs subpackage instead of devel
- releasing an update as fix for #539444, before conducting any test yourself
- you broke libgcrypt support for nothing by the yesterdays patch, but to be frank it's not really dangerous when we consider only binary packages

> Please try to keep issues to one per bug, rather than the smorgasbord you've
> listed above.  Thanks. :)

I've only done what I had to - see http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

"When a Fedora member notices that a maintainer isn't answering their bugs, not answering rebuild requests, emails or the like, they need to file a bug against the package in bugzilla asking for the maintainer to respond. This bug should list the outstanding issues they need to address. This is a must."