On 2016-11-20 14:58:13 [+0100], Jan Wagner wrote:
> Hi there,
Hi,
> So until openssl 1.1.0 support is added to the package I'll keep this
> bug open.
correct, thank you. Please keep the severity important high rather than normal
for this bug (other bugs which moved explicit to 1.0 have the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi there,
Am 20.11.2016 um 14:00 schrieb Sebastian Andrzej Siewior:
> is there still an issue with this package an openssl 1.1.0 or is
> this resovled?
actualy 2.1.2-3 build depend against libssl1.0-dev. Since
postgresql-9.6 (9.6.1-2) don't
On 2016-11-16 12:09:51 [+0100], Jan Wagner wrote:
> Hi,
Hi,
> This was part of the issue fixed by postgresql-9.6 (9.6.1-2):
is there still an issue with this package an openssl 1.1.0 or is this
resovled? I am asking because it is not abvious from the bug report and it is
severity normal and
Hi,
Am 11.11.16 um 23:25 schrieb Jan Wagner:
> Building against libssl1.0-dev, which was suggested in the
> announcement of the openssl switch, results (actual) into:
>
> [...]
> checking for PQsetdbLogin in -lpq... no
> configure: WARNING: Skipping PostgreSQL plugin (check_pgsql)
> configure:
Re: Jan Wagner 2016-11-11
> Building against libssl1.0-dev, which was suggested in the
> announcement of the openssl switch, results (actual) into:
>
> [...]
> checking for PQsetdbLogin in -lpq... no
> configure: WARNING: Skipping PostgreSQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Source: monitoring-plugins
Severity: normal
Since OpenSSL 1.1 was announced[1] to be default in unstable,
monitoring-plugins builds against libssl1-1-dev.
Indeed this fails:
[...]
checking openssl/ssl.h usability... yes
checking openssl/ssl.h
6 matches
Mail list logo