@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

> @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. :)

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.

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 \
```

@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?

Possible relevant info: I've tried to upload this package a few times, but my package.xml was broken. My guess is that broken upload packages are still stored in the `files` table, with the same `basename`, but with a fullpath that points to a non-existing file.

If that is true, the query on line web-pecl/src/Release.php:447 gives the wrong file.

SELECT `fullpath`, `release`, `id` FROM files WHERE UPPER(basename) = ?

As @zimt Peter wrote, I don't know what's in this table for the ssh2 extension, and I'm just guessing, but as basename is not defined to be unique in table `files`, at least there is an issue there.

still not fixed, team work?

perhaps if pecl website maintainers are unable to fix simple 500 error over two months, ssh2 package maintainer just uploads new version like 1.2.1?

This should be fixed now. There were indeed odd records in the database which I had to manually purge.

This issue has just been fixed by Derick! \o/