php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #78560 500 on package download https://pecl.php.net/get/ssh2-1.2.tgz
Submitted: 2019-09-18 12:46 UTC Modified: 2019-09-19 11:11 UTC
Votes:16
Avg. Score:4.1 ± 0.9
Reproduced:15 of 15 (100.0%)
Same Version:6 (40.0%)
Same OS:4 (26.7%)
From: BWATERS at SOLUTIONSBYWATERS dot COM Assigned:
Status: Verified Package: Systems problem
PHP Version: Irrelevant OS: irrellevant
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: BWATERS at SOLUTIONSBYWATERS dot COM
New email:
PHP Version: OS:

 

 [2019-09-18 12:46 UTC] BWATERS at SOLUTIONSBYWATERS dot COM
Description:
------------
When I try to download the ssh package

https://pecl.php.net/get/ssh2-1.2.tgz

I receive a 500 internal service error

Looks like this was previously fixed with rsync, but it's back

Test script:
---------------
curl https://pecl.php.net/get/ssh2-1.2.tgz


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2019-09-18 12:58 UTC] cmb@php.net
-Status: Open +Status: Verified -Package: *Web Server problem +Package: ssh2
 [2019-09-19 07:46 UTC] langemeijer@php.net
-Package: ssh2 +Package: Systems problem
 [2019-09-19 07:46 UTC] langemeijer@php.net
@cmb How is this a ssh2 package problem?

URL https://pecl.php.net/get/ssh2 does work, and links to the 1.2 version I uploaded recently.

If someone could explain how I caused a 500 Internal Server Error and there is something I can do I'd be happy to help, but as far as I can see there is nothing I can do now.

Calling it a sysops-problem for now hoping this bugreport finds the right people.

@bwaters as a workaround please download the package on https://pecl.php.net/get/ssh2
 [2019-09-19 11:11 UTC] cmb@php.net
> @cmb How is this a ssh2 package problem?

Well, it probably isn't, but it is definitely not a Web server
problem.  Sorry for the noise. :)
 [2019-09-23 09:11 UTC] arnaud dot goulpeau at guest-suite dot com
As mentioned in the related bug, the url https://pecl.php.net/get/ssh2-1.2.tgz still leads to a 500.

I know the workaround url https://pecl.php.net/get/ssh2 works by hand, but since tools like Scrutinizer, composer and other automatic tools relies on what you put in the page https://pecl.php.net/package/ssh2. 

So the url https://pecl.php.net/get/ssh2-1.2.tgz should work, as the workaround url cannot be used by the majority of users.

Also, please notice that the url https://pecl.php.net/get/ssh2-1.1.tgz works.

For the case when another Scrutinizer user comes. A Scrutinizer staff member helped me to unlock the issue with an extra bit of conf :
build:
    dependencies:
        before:
            - sudo apt-get -y install libssh2-1-dev && echo "y" | pecl install ssh2-1.1.2

Many thanks for your help.
 [2019-09-24 07:20 UTC] patpilus at gmail dot com
I can confirm this issue. If you want to install the newest ssh2 version on the dockerized environment you can do this workaround until fixed:

```
    RUN wget https://pecl.php.net/get/ssh2 -O /tmp/ssh2-1.2.tgz \
    && pear install /tmp/ssh2-1.2.tgz \
    && docker-php-ext-enable apcu ssh2 \
```
 [2019-09-26 14:48 UTC] zimt@php.net
@cmb you seem to be right about the webserver, but it doesn't seem to be a problem with ssh2 itself either.

However a few more information might help to figure this one out:

So a few additional information:
web-pecl/public_html/get allows for 6 variants on how to request a package from pecl.php.net. 

The variant that seems to have the status 500 issue is the "Specific file" one, which causes HTTPdownload in web-pecl/src/Release.php:425 to be called with the 3rd parameter set to the filename.

other releases can be requested without problems through the "Specific file" variant, which seems to indicate that the issue is with the entry in the files table specific for the ssh2-1.2.tgz filename. 

Maybe someone with access to the database can verify or rebut this suspicion?
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Fri Oct 18 18:01:29 2019 UTC