[Tickets #14100] Check for Updated Packages fails

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14100
------------------------------------------------------------------------------
  Ticket           | 14100
  Erstellt Von     | jens_reg_02 at nachthell.net
  Zusammenfassung  | Check for Updated Packages fails
  Warteschlange    | Horde Base
  Version          | 5.2.7
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


jens_reg_02 at nachthell.net (2015-09-06 12:50) hat geschrieben:

Hi there!

This Bug is related to my pear installation 5.2.10 which is not listed here.

After upgrading to the latest packages, but unfortunately also after  
upgrading from Debian 7 to 8 and all pecl packages I get the following  
error when I go to Administration -> Check for new package versions:

Undefined constant 'http\Client\Curl\AUTH_ANY'

1. Horde_ErrorHandler::catchFatalError()

Details
Die vollständige Fehlermeldung wurde in Hordes Logdatei geschrieben  
und für Administratoren weiter unten ausgegeben. Benutzer, die keine  
Administratoren sind, bekommen diese Details nicht zu sehen.

ErrorException Object
(
     [message:protected] => Undefined constant 'http\Client\Curl\AUTH_ANY'
     [string:Exception:private] =>
     [code:protected] => 0
     [file:protected] => /usr/share/php/Horde/Http/Request/Factory.php
     [line:protected] => 29
     [trace:Exception:private] => Array
         (
             [0] => Array
                 (
                     [function] => catchFatalError
                     [class] => Horde_ErrorHandler
                     [type] => ::
                     [args] => Array
                         (
                         )

                 )

         )

     [previous:Exception:private] =>
     [severity:protected] => 1
     [logged] => 1
)

This is actually not very serious, but I'm not sure if this is a bug  
from Horde or from my server configuration.

Best
Jens