It now has been more than four months since the last reply by anyone.
PLEASE, is there anything I can to to push this through? It can not be
that hard!
Problem: The package is completely broken and unusable.
History:
* 2017/11/15: First mention of this issue in my post to
https://bugs.de
It now has been more than two months since the last reply by anyone.
PLEASE, is there anything I can to to push this through? It can not be
that hard!
Problem: The package is completely broken and unusable.
History:
* 2017/11/15: First mention of this issue in my post to
https://bugs.deb
Dear Julien, dear Maintainers,
the OpenSSL 1.1.x compatibility patch that was applied for #828555
breaks the package and leads to segfaults.
This breaks for example "skrooge" and other applications depending on
libsqlcipher0. I have no idea why this was not caught before the
release, but on a fres
017 14:58:28 +0100 Philipp Berger
> wrote:
>> Package: libsqlcipher0
>> Version: 3.2.0-2
>> Followup-For: Bug #863530
>>
>> Dear Maintainer,
>>
>> the OpenSSL 1.1.x compatability patch that was applied for #828555 breaks
>> the package and leads to
Package: libsqlcipher0
Version: 3.2.0-2
Followup-For: Bug #863530
Dear Maintainer,
the OpenSSL 1.1.x compatability patch that was applied for #828555 breaks the
package and leads to segfaults.
This breaks skrooge and other applications depending on libsqlcipher0.
I diffed src/crypto_openssl.c a
Dear Dirk, dear Hans-Christoph,
this dependency on OpenSSL 1.0 may lead to unexpected Segmentation
Faults, one of which I stumbled on when using SqlCipher with Qt5 (which
links OpenSSL 1.1). Is there any planned update for stretch to sqlcipher
3.4.1? Is it possible to pull sqlcipher 3.4.1 to stret
Dear Maintainers,
we have the same issues on our ProLiant DL360 G5 systems.
How can we help triage this issue? This is a showstopper for us and
preventing the upgrade to Stretch.
Cheers,
Philipp
--
Philipp Berger
https://moves.rwth-aachen.de
7 matches
Mail list logo
