[#14666] https://pear.horde.org/ doesn't include latest security updates
Summary https://pear.horde.org/ doesn't include latest security updates
Queue Horde.org Servers
Queue Version PEAR server
Type Bug
State Resolved
Priority 3. High
Owners Horde Developers, mrubinsk@horde.org
Requester jonathan@tietznet.de
Created 2017-07-19 (793 days ago)
Due 07/19/2017 (793 days ago)
Updated 2017-07-23 (789 days ago)
Assigned 2017-07-21 (791 days ago)
Resolved 2017-07-23 (789 days ago)
Milestone
Patch No

Comments
jonathan@tietznet.de 2017-07-19 21:58:14
hi,

on the page
Horde_Image (2.3.6) and and Whups 3.0.8

doesn't include the latest versions (security)

Michael Rubinsky <mrubinsk@horde.org> 2017-07-21 17:16:09
Indeed. Might be the pear server just needs to be rebuilt. I'll look 
at this soon.

nvanheuverzwijn@kronostechnologies.com 2017-07-21 18:19:21
> Indeed. Might be the pear server just needs to be rebuilt. I'll look 
> at this soon.
Is it normal that some version of many horde package in pear are 
missing ? Like "https://pear.horde.org/get/Horde_Support-2.2.0.tgz
returns 404 Not Found. I know this package used to exist because I had 
it in my composer cache.

arjen+horde@de-korte.org 2017-07-21 19:55:18
See https://pear.horde.org/ for the latest versions of packages. It 
looks like the latest version of Horde_Support is 2.1.5...

nvanheuverzwijn@kronostechnologies.com 2017-07-21 19:59:55
> See https://pear.horde.org/ for the latest versions of packages. It 
> looks like the latest version of Horde_Support is 2.1.5...

I know this is the latest version. I'm just saying that the 2.2.0 
version used to exist and it does not and it seems strange to me.

Michael Rubinsky <mrubinsk@horde.org> 2017-07-22 00:01:23
> See https://pear.horde.org/ for the latest versions of packages. It 
> looks like the latest version of Horde_Support is 2.1.5...

No, actually, there should be a 2.2.0. It was released back in 
February.  There is definitely something screwy going on here. Might 
be related to the recent server issues/ migration. I'm looking into it.

Michael Rubinsky <mrubinsk@horde.org> 2017-07-22 00:19:18

The issue is that the box running the production web server is down. 
We have DNS failover to a backup server that was evidently not 
rsyncing any more. I have emails out to the appropriate people.


Michael Rubinsky <mrubinsk@horde.org> 2017-07-23 14:45:34
This is resolved.

The DNS for the new box was changed, but the health check was not, so 
the health check was failing, causing the failover box to take over. 
Additionally, there was some permission issue on the failover box that 
was causing the rsync process to fail - so the pear files were not 
properly sync'd.

Hopefully all is well now. A new sync is currently running to populate 
the failover, and the "real" server is currently answering requests.