Bug#886146: stretch-pu: package sqlcipher/3.2.0-2+deb9u1
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.debian.org/cgi-bin/bugreport.cgi?bug=863530 * 2017/12/01: I submitted a patch for the problem to #863530 * 2018/01/02: This issue was opened to fix the problem against release.debian.org It now has been EIGHT months since the patch was initially submitted.
Bug#886146: stretch-pu: package sqlcipher/3.2.0-2+deb9u1
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.debian.org/cgi-bin/bugreport.cgi?bug=863530 * 2017/12/01: I submitted a patch for the problem to #863530 * 2018/01/02: This issue was opened to fix the problem against release.debian.org It now has been 6 and 1/2 months since the patch was initially submitted.
Bug#886146: Testing and Issues
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 fresh install of Debian 9.4, all default settings, I installed "skrooge". After opening the program, click "New", then "Save As", enter a valid name, e.g. "test" and save - the program immediately crashes with the described problem in LibSQLCipher. So this is definitely an existing issue, even in the most current version of Debian 9! For the path: I diffed src/crypto_openssl.c against the most current version (3.4.1) and noticed the switch to the non-deprecated API function around EVP_CipherInit_ex instead of EVP_CipherInit. I ported these differences to 3.2.0-2, recompiled the package from Debian sources including my patch. The resulting binaries no longer produce segfaults and work as expected. This is in line with release 3.4.1-1 on sid.
Bug#863530: [sqlcipher] Current version not compatible with OpenSSL 1.1
Dear Gianfranco, I can confirm that the binaries you attached fix the problem and work as expected! How do I open the bug against release.debian.org or will you be doing that? Kind regards, Philipp Am 02.12.2017 um 13:54 schrieb Gianfranco Costamagna: > Hello Philipp, > On Fri, 01 Dec 2017 14:58:28 +0100 Philipp Berger <deb...@philippberger.de> > 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 segfaults. >> This breaks skrooge and other applications depending on libsqlcipher0. > can you please test the binaries I'm attaching to this email? (unfortunately > the build server seems to be misconfigured) > > I'm also attaching the patch (debdiff) against the current release in stable. > > If your testing is good, we will have to open a bug against release.debian.org > with this patch :) > > G.
Bug#863530: [sqlcipher] Current version not compatible with OpenSSL 1.1
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 against the most current version (3.4.1) and noticed the switch to the non-deprecated API function around EVP_CipherInit_ex instead of EVP_CipherInit. I ported these differences to 3.2.0-2, recompiled the package from Debian sources including my patch. The resulting binaries no longer produce segfaults and work as expected. This is in line with release 3.4.1-1 on sid. You can find the patch at http://paste.debian.net/998532/ Please review the patch and include it in stable. Kind regards, Philipp -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (890, 'stable'), (500, 'stable-updates'), (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsqlcipher0 depends on: ii libc6 2.24-11+deb9u1 ii libssl1.1 1.1.0f-3+deb9u1 libsqlcipher0 recommends no packages. libsqlcipher0 suggests no packages. -- no debconf information
Bug#863530: Segmentation Fault
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 stretch-backports (and what can I do to help)? This blocks my users from installing/using software requiring sqlcipher. It would be very nice when we could resolve this without having to ship and compile the entire sqlcipher stack at the client. Cheers, Philipp smime.p7s Description: S/MIME Cryptographic Signature
Bug#861746: linux-image-4.9.0-2-amd64: Infinity `soft lockup` at kernel 4.9.0-1+ on HP ProLiant DL360G5
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/people/berger/ Software Modeling and Verification Group RWTH Aachen University Phone +49/241/80-21206 Ahornstraße 55, 52056 Aachen, Germany smime.p7s Description: S/MIME Cryptographic Signature
