IUS Community Project

request php*-pecl-ssh2-0.12

Asked by Tommy McNeely

One of our customers is using php53u-pecl-ssh2 to do some ssh2 (sftp) operations and has reported that they need version 0.12 which was release on 2012-10-15 <http://pecl.php.net/package/ssh2> in order to have the "chmod" capability that they need. Can we make the "official" request to upgrade that package somehow?

Thanks in advance,
Tommy

Question information

Language:
English Edit question
Status:
Solved
For:
IUS Community Project Edit question
Assignee:
No assignee Edit question
Solved by:
bharper
Solved:
Last query:
Last reply:
Revision history for this message
Best bharper (bharper) said : 		#1

Hello Tommy,

Thanks for taking the time to contact IUS. We are very cautious when it comes to packaging beta quality software and that is why the current php ssh2 modules are in the development repos. We did not package the 0.12 version due to dependencies in el 5. See the following bug for the details:

https://bugs.launchpad.net/ius/+bug/1170131

In general, requests for changes or new packages are done within the a bug.

-Ben

Revision history for this message
Tommy McNeely (c-tommy) said : 		#2

Thank you for taking time to answer my question. I appreciate the cautiousness since we run IUS on our production servers. All releases of pecl-ssh2 have been tagged as beta per <http://pecl.php.net/package/ssh2> ... so I didn't figure that another updated beta release of the same software would be that tall of an order.

The EL5 dependency issue is somewhat mute because php53u-pecl-ssh2 isn't available on the EL5 repo anyhow <http://dl.iuscommunity.org/pub/ius/stable/CentOS/5/x86_64/repoview/development.languages.group.html>. We did take the EL6 SRPM and rebuild it for EL5 in our old data center, and it did work fine for us, but we knew we were on shaky ground. Since it is currently a beta release on EL6 only, it should probably be updated (only on EL6). I can make a comment on that bug as well. I wasn't sure what the correct procedure to request was, so I "Asked a question" :)

~tommy

PS: Since my "question" is answered (file a bug), I will mark this as solved.

Revision history for this message
Tommy McNeely (c-tommy) said : 		#3

Thanks bharper, that solved my question.