Bug#854468: lprng: diff for NMU version 3.8.B-2.1

with OpenSSL 1.1, patch by +Reiner Herrmann <rei...@reiner-h.de> (Closes: #854468). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Wed, 08 Feb 2017 21:20:30 +0100 + lprng (3.8.B-2) unstable; urgency=low * Compilies on hurd-i386 Closes: #671848 diff -Nru lprng-3.8.B/de

Bug#846908: netsurf: diff for NMU version 3.6-3.1

). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Wed, 08 Feb 2017 21:10:34 +0100 + netsurf (3.6-3) unstable; urgency=medium * Apply upstream patch fixing nsgenbind on BE architectures diff -Nru netsurf-3.6/debian/control netsurf-3.6/debian/control --- netsurf-3.6/debian/c

Bug#854412: unblock: tpm-tools/1.3.9-0.1

On 2017-02-06 21:35:00 [+], Niels Thykier wrote: > Ok, please go ahead with the upload. thank you. Uploaded & built. > For the next time: Please consider providing a filtered debdiff leaving > out auto-generated noise (just remember to include information about > what exactly you have

Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

On 2017-01-17 19:34:59 [+0200], Adrian Bunk wrote: > Unfortunately tpm-tools is not fine, and even fixing the other trivial > build error #811576 depends on this. but now it is. Can this be closed? > cu > Adrian Sebastian

Bug#811576: tpm-tools: diff for NMU version 1.3.9-0.1

On 2017-02-07 13:38:49 [+0100], John Paul Adrian Glaubitz wrote: > Hi! Hi, > > now I understand what you mean. Earlier, while reading it, I though you > > were asking to get them removed because I introduced them. Now I > > understand what you emant. > > Ok, any idea where these changes come

Bug#811576: tpm-tools: diff for NMU version 1.3.9-0.1

On 2017-02-05 23:46:07 [+0100], John Paul Adrian Glaubitz wrote: > Hi Sebastian! Hi Adrian, > However, I'm afraid your patch currently has no chance to get merged into > the Debian package as it involves too many changes and will therefore > rejected by the release team for Debian Stretch. as

Bug#852924: collectd: diff for NMU version 5.7.1-1.1

(openssl's functionality is not used by +collectd). Add drop_lssl_lcrypto_from_linking.patch (Closes: #852924). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 05 Feb 2017 20:40:33 +0100 + collectd (5.7.1-1) unstable; urgency=medium * New upstream release. diff -Nru co

Bug#827068: m2crypto: diff for NMU version 0.24.0-1.1

-maintainer upload. + * Build depend on openssl 1.0 for Stretch (Closes: #827068) + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 05 Feb 2017 14:37:04 +0100 + m2crypto (0.24.0-1) unstable; urgency=medium * New upstream release (Closes: #818986): diff -Nru m2crypto-0.24.0/

Bug#854253: m2ext: diff for NMU version 0.1-1.1

: #854253). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 05 Feb 2017 15:04:00 +0100 + m2ext (0.1-1) unstable; urgency=low * Initial release. (Closes: #705949) diff -Nru m2ext-0.1/debian/control m2ext-0.1/debian/control --- m2ext-0.1/debian/control 2013-06-13 14:23:19.000

Bug#854253: m2ext: need to depend on libssl1.0 due to m2crypto

Source: m2ext Version: 0.1-1 Severity: serious Control: block 827061 by -1 m2crypto will probably go with libssl1.0 for Stretch and m2ext should use the same library. Sebastian

Bug#854154: unblock: libesmtp/1.0.6-4.2

.0 +0100 +++ libesmtp-1.0.6/debian/changelog 2017-01-31 23:51:33.0 +0100 @@ -1,3 +1,10 @@ +libesmtp (1.0.6-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * Drop "-lssl -lcrypto" from exported libs flags (Closes: #852884). + + -- Sebastian Andrzej Siewior <

Bug#854151: unblock: libapache2-mod-auth-cas/1.1-2.1

) unstable; urgency=medium + + * Non-maintainer upload. + * Build depend open OpenSSL 1.0 for Stretch (Closes: #850883). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 31 Jan 2017 21:23:57 +0100 + libapache2-mod-auth-cas (1.1-2) unstable; urgency=medium * Update con

Bug#854148: unblock: lastpass-cli/1.0.0-1.2

to openssl 1.0 (Closes: #850882). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 31 Jan 2017 21:05:57 +0100 + lastpass-cli (1.0.0-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru lastpass-cli-1.0.0/debian/control lastpass-cli-1.0.0/debian/control --- la

Bug#827061: transition: openssl

On 2017-02-01 22:18:07 [+0100], Sebastian Andrzej Siewior wrote: > Currently I am rebuilding testing with the same set of package against > libssl-dev provided by libssl1.0-dev. After that I retry the failed > packages above where I am not sure why they failed (mostly I suspect the &

Bug#827061: transition: openssl

On 2017-02-02 22:26:35 [+0200], Adrian Bunk wrote: > The kannel package does not claim to support parallel building. > > If you attempt parallel building on that, > then any build failures are your fault. what is wrong with passing -j16 to sbuild? Other packages, that do not support parallel

Bug#827061: transition: openssl

On 2017-02-02 16:54:08 [+], Holger Levsen wrote: > > I'm surprised to see that many packages failing to build in parallel, as we're > building everything in parallel and I dont remember such failures recentl.y So retried them with -j1 [0] and: - passed: boxbackup 0.11.1~r2837-4 erlang

Bug#827061: transition: openssl

On 2017-01-28 19:37:09 [+0100], Julien Cristau wrote: > At this point, it seems clear to me that we're getting nowhere fast. > With the freeze looming in a few days, this is growing to be a very big > risk for the stretch release. I rebuild testing, with the subset of: grep-dctrl -FDepends

Bug#828482: bug 828482 fix

On 2017-02-01 09:59:02 [+0800], Di-Shi Sun wrote: > Hi Sebastian, Hi Di-Shi, > I am pretty sure that 4.11.3+dfsg-1 is not influenced by 828482 (FTBFS with > openssl 1.1.0). Please send us the build log showing the issue you report. sbuild (Debian sbuild) 0.73.0 (23 Dec 2016) on debbuildd

Bug#852924: collectd: FTBFS: ld: cannot find -lssl

nevertheless (making this mistake in > collectd's Makefile work by accident). This is not the case on the > AWS-based builder. Okay. Unmerged, back. Earlier net-snmp's -dev package pulled in libssl-dev. This packages explicitly adds "-lssl -lcrypto" but does not need to link against an

Bug#852884: libesmtp: diff for NMU version 1.0.6-4.2

libs flags (Closes: #852884). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 31 Jan 2017 23:51:33 +0100 + libesmtp (1.0.6-4.1) unstable; urgency=medium * Non-maintainer upload diff -Nru libesmtp-1.0.6/debian/patches/remove_ssl_libs_from_libs.patch libesmtp-1.0.

Bug#827068: m2crypto: doesn't work together with OpenSSL 1.1 (API changes)

On 2016-11-15 12:36:09 [+0100], Daniel Stender wrote: > On Mon, 14 Nov 2016 19:52:31 +0100 Daniel Stender > wrote: > > The diff doesn't work like that on the upstream code in the archive > > ... the same is true for 0.25.1. > > I'm on it. Should I take 0.25.1 and

Bug#828482: bug 828482 fix

On 2016-10-27 08:56:23 [+0800], Di-Shi Sun wrote: > osptoolkit/3.4.2-1.2 is out of date and osptoolkit/4.11.3+dfsg-1 has been > released to replace it. so what? 4.11.3+dfsg-1 is still affected by this problem. > Regards, > > > > Di-Shi Sun > VoIP Routing, Accounting, Security Sebastian

Bug#850883: libapache2-mod-auth-cas: diff for NMU version 1.1-2.1

for Stretch (Closes: #850883). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 31 Jan 2017 21:23:57 +0100 + libapache2-mod-auth-cas (1.1-2) unstable; urgency=medium * Update configure for OpenSSL 1.1 (closes: #828378). diff -Nru libapache2-mod-auth-cas-1.1/debian/control liba

Bug#828449: net-snmp will stay with 1.0 for stretch

control: retitle -1 net-snmp: Please migrate to openssl1.1 in buster control: unblock 827061 with -1 Dmitry, in [0] you said, that this bug affects zabbix. If it is still the case, please explain how otherwise please remove the `affects' tag. [0]

Bug#850882: lastpass-cli: diff for NMU version 1.0.0-1.2

-12-06 21:10:47.0 +0100 +++ lastpass-cli-1.0.0/debian/changelog 2017-01-31 21:05:57.0 +0100 @@ -1,3 +1,10 @@ +lastpass-cli (1.0.0-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Switch to openssl 1.0 (Closes: #850882). + + -- Sebastian Andrzej Siewior <seb

Bug#853730: handshake failure alert number 40

On 2017-01-31 07:05:46 [-0500], Leand wrote: > After a recent upgrade of debian testing Kmail failes to nogotiate > SSL with two accounts. In fact openssl gives handshake failure > alert if I test with imap: > > openssl s_client -connect imap.fastwebnet.it:993 or > openssl s_client -connect

Bug#853260: unblock: lcmaps-plugins-voms/1.6.2-2.1

-maintainer upload. + * Get it built with openssl 1.1. (Closes: #828376). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 29 Jan 2017 21:51:50 +0100 + lcmaps-plugins-voms (1.6.2-2) unstable; urgency=low [ Mischa Salle ] diff -Nru lcmaps-plugins-voms-1.6.2/debian/p

Bug#852894: [Pkg-clamav-devel] Bug#852894: Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

control: forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=11739 On 2017-01-28 12:50:41 [-0500], Scott Kitterman wrote: > > Thanks for patch. I wrongly assumed you were one of the curl maintainers. > The release team is considering if the change should be reverted, so I'm > going >

Bug#851838: httest: diff for NMU version 2.4.18-1.1

On 2017-01-27 16:58:25 [+0100], Eva Ramon wrote: > Thanks Sebastian! You are welcome. Unfortunately I noticed too late that you changed B-D on libssl1.0-dev so despite the effort to get it to work with 1.1 it will remain with 1.0 for the release. If you get bored, you might want to think about

Bug#828375: OpenSSL: The LCMAPS/VOMS/Globus cluster

8.0 +0100 +++ lcmaps-plugins-voms-1.6.2/debian/changelog 2017-01-29 21:51:50.0 +0100 @@ -1,3 +1,10 @@ +lcmaps-plugins-voms (1.6.2-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Get it built with openssl 1.1. (Closes: #828376). + + -- Sebastian Andrzej Siewior <seb

Bug#852920: fixed in svn

control: tags -1 pending fixed in SVN. Sebastian

Bug#846597: linux: please enable `perf data' support

On 2017-01-26 16:36:45 [+0100], Hector Oron wrote: > Hello, Hi, > On Fri, Dec 02, 2016 at 02:37:21PM +0100, Sebastian Andrzej Siewior wrote: > > diff --git a/debian/templates/control.source.in > > b/debian/templates/control.source.in > > index 08969a3da9d9..2a1fdf048823

Bug#851838: httest: diff for NMU version 2.4.18-1.1

:44.0 +0100 +++ httest-2.4.18/debian/changelog 2016-04-20 21:00:04.0 +0200 @@ -1,3 +1,10 @@ +httest (2.4.18-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Copy config.{guess|sub} to the correct location (Closes: #851838). + + -- Sebastian Andrzej Siewior <seb

Bug#851946: Depending on libssl1.0-dev breaks PHP builds

On 2017-01-24 06:34:00 [+], Niels Thykier wrote: > The guard, you proposed, is using 1.0.2, so this patch will be > unnecessary (guess I misunderstood your original intention). But the > end result should be the same. :) If you compile net-snmp against openssl 1.1.0 then you should still use

Bug#851946: Depending on libssl1.0-dev breaks PHP builds

0 +0100 @@ -1,3 +1,11 @@ +net-snmp (5.7.3+dfsg-1.7) unstable; urgency=medium + + * Non-maintainer upload. + * drop dep on libssl1.0-dev in the dev package + * add a guard to catch users of the wrong library + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 22 Jan 2017 21:30:

Bug#851946: Depending on libssl1.0-dev breaks PHP builds

On 2017-01-20 21:36:00 [+], Niels Thykier wrote: > Hi Ondřej, > > Sorry for being the "messenger" triggering this issue in php7.0. > > Kurt/Sebastian, what are you recommendations here? Should we migrate > net-snmp itself to ssl1.1 (possibly with all of its rdeps) or can we > detangle

Bug#852017: [Pkg-openssl-devel] Bug#852017: perl:any isn't the best idea as dependency - it breaks debootstrap

On 2017-01-20 20:18:35 [+0100], Sven Joachim wrote: > For the record, this is #836525 in debootstrap. thank you, I am going to workaorund this… > Cheers, >Sven Sebastian

Bug#851965: RM: android-tools [armel mips mips64el mipsel ppc ppc64el s390x] -- ANAIS; architectures limited

Package: ftp.debian.org Severity: normal The android-tools package in its latest upload [0] limited its architecures from linux-any to "amd64 arm64 armhf i386" so please remove the old binaries. It probably won't migrate to testing but atleast it will pop green in the openssl tracker :) [0]

Bug#851615: xz-utils: please upgrade to 5.2.3

On 2017-01-16 21:43:24 [+], Thorsten Glaser wrote: > Sebastian Andrzej Siewior dixit: > > >Please upgrade to 5.2.3 for Stretch. One visible change is the usage of > > That’s rather late, I’d not risk it, especially not for a package > that is so low in the stack as xz

Bug#851615: xz-utils: please upgrade to 5.2.3

Package: xz-utils Version: 5.2.2-1.2 Severity: wishlist Please upgrade to 5.2.3 for Stretch. One visible change is the usage of sched_getaffinity() which is preferred over all online CPUs especially on bigger NUMA boxes where affinity mask is often limited to a node. Sebastian

Bug#806602: ace: diff for NMU version 6.3.3+dfsg-1.2

with -A as it +did before (Closes: #806602). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sat, 14 Jan 2017 13:47:41 + + ace (6.3.3+dfsg-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru ace-6.3.3+dfsg/debian/control ace-6.3.3+dfsg/debian/control --- ace-6.3.3+dfsg/

Bug#851254: androidsdk-tools: please don't depend on android-tools-adb

Package: androidsdk-tools Version: 22.2+git20130830~92d25d6-3 Severity: serious The adb binary seems to have migrated from the android-tools-adb package to the adb package provided by the android-platform-system-core source package. The package libandroidsdk-ddmlib-java (which is part of

Bug#851070: ccnet: Please migrate to openssl1.1 in buster

Package: ccnet Version: 6.0.2-1 Severity: important Tags: sid buster This package build-depends on libssl1.0-dev. Please migrate to libssl-dev in the buster cycle. Sebastian

Bug#851069: cjose: Please migrate to openssl1.1 in buster

Package: cjose Version: 0.4.1-2 Severity: important Tags: sid buster This package build-depends on libssl1.0-dev. Please migrate to libssl-dev in the buster cycle. Sebastian

Bug#397507: Debian OpenSSL Bug 397507

On 2017-01-10 21:53:11 [+0100], Olaf van der Spek wrote: > >> So why does this file contain "countryName_default = AU"? > >> AU doesn't make sense, IMO a better one would be the empty string. > > > > Why doesn't AU make sense? It is a fictional entry / example which > > matches the

Bug#375834: openssl bug

On 2006-06-28 13:55:18 [+0200], j...@roesner.it wrote: > The verification of CRL's does not work correctly. What happens is: > > $>openssl crl -inform PEM -in ca-1.crl.pem -CAfile ca-1.pem -noout > $>verify OK > > Then I try : > > $>openssl crl -inform PEM -in ca-1.crl.pem -CAfile ca-2.pem

Bug#397507: Debian OpenSSL Bug 397507

On 2011-05-08 10:55:58 [+0200], Olaf van der Spek wrote: > Hi Scott, Hi Olaf, > 397507@ doesn't reach the submitter, you might want to use 397507-submitter@. > > > 3) /etc/ssl/openssl.cnf (if installed from Debian package -- specified > at compile-time) > > So why does this file contain

Bug#843064: openssl: incompatibility for enc command between openssl 1.1.0b-2 and previous 1.0.x versions

On 2017-01-09 09:55:02 [+0100], Ondřej Surý wrote: > Maybe this is also a release notes material? So you wondered why `openssl enc -d' stopped working for you and you stumbled over this bug? If yes and you think that release notes would help then I might open a bug with a note about this. Also I

Bug#534699: libssl0.9.8: likely race condition in int_new_ex_data()

On 2009-06-26 23:26:34 [+1000], Russell Coker wrote: > ==28314== Possible data race during read of size 8 at 0x6535338 by thread #3 > ==28314==at 0x52D183B: int_new_ex_data (ex_data.c:410) > ==28314==by 0x5318BD7: RSA_new_method (rsa_lib.c:185) > ==28314==by 0x531B76C: rsa_cb

Bug#534687: libssl0.9.8: lh_retrieve modifies global data, bug in valgrind or OpenSSL?

On 2009-06-26 21:09:13 [+1000], Russell Coker wrote: > ==27681== Possible data race during write of size 4 at 0x652e2f0 by thread #5 > ==27681==at 0x5330C84: lh_retrieve (lhash.c:254) > ==27681==by 0x52D12E1: def_get_class (ex_data.c:301) > ==27681==by 0x52D180A: int_new_ex_data

Bug#534534: libssl0.9.8: valgrind/helgrind reports Possible data race during write

On 2009-06-25 15:59:32 [+1000], Russell Coker wrote: > ==32465== Possible data race during write of size 4 at 0x55D7CE8 > ==32465==at 0x52CD88D: CRYPTO_malloc (mem.c:298) > ==32465==by 0x534AC75: asn1_item_ex_combine_new (tasn_new.c:191) > ==32465==by 0x534E184: ASN1_item_ex_d2i

Bug#422882: openssl: mistake in note on x509v3_config manual page

control: tags -1 - patch On 2007-05-09 00:27:24 [+0200], Javier Barroso wrote: > > And I have no idea what you think is wrong ... > > I can't generate the certificate (with a crlDistributionPoints ldap > uri within it) with manual page instruction. > > When subjectAltName is

Bug#843064: openssl: incompatibility for enc command between openssl 1.1.0b-2 and previous 1.0.x versions

control: tags -1 pending On 2016-11-07 14:33:38 [+0100], Marek Lukaszuk wrote: > I'm following the conversation on openssl-dev mailing list. > I've checked the package changelog using "aptitude changelog openssl" > before opening the ticket, so maybe putting it somewhere there would be > a good

Bug#828556: sslscan: FTBFS with openssl 1.1.0

On 2017-01-05 23:33:59 [+0100], Christoph Berg wrote: > > why on libssl-dev (<< 1.1.0~)? > > The | libssl-dev (<< 1.1.0~) part is there to enable backporting to > jessie without having to revert libssl1.0-dev back to libssl-dev. and I though that this is one of the changes you do when you intend

Bug#828556: sslscan: FTBFS with openssl 1.1.0

On 2017-01-05 15:08:00 [+0100], Christoph Berg wrote: > NMU diff: > > > Control files: lines which differ (wdiff format) > > Build-Depends: debhelper (>= 9), {+libssl1.0-dev |+} libssl-dev {+(<< > 1.1.0~)+} why on libssl-dev (<< 1.1.0~)?

Bug#845193: [Pkg-openssl-devel] Bug#845193: Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-29 00:25:05 [+0100], To Kurt Roeckx wrote: > > Figure out why it uses link_a instead of link_o, and maybe fix it? so that link_a instead of link_o is always used - not just on x32. Replacing _a with _o here gets the build to continue but fails later in a (normal) link_o rule:

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-28 17:01:10 [+0100], Kurt Roeckx wrote: > On Wed, Dec 28, 2016 at 02:59:18PM +0100, Sebastian Andrzej Siewior wrote: > > On 2016-12-08 01:20:06 [+0100], Guillem Jover wrote: > > > Hi! > > Hi, > > > > > The actual problem here, is that for wh

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-08 01:20:06 [+0100], Guillem Jover wrote: > Hi! Hi, > The actual problem here, is that for whatever reason on x32 and only > x32, the build system is (as I noted in #845193#10) calling link_a.gnu > instead of the link_o.gnu target, which tries to link a static library > composed of PIE

Bug#828342: Re: [Htt-developers] Building with OpenSSL 1.0.2 is sufficient for stretch

On 2016-12-23 09:42:22 [+0100], Christian Liesch wrote: > Hey all Hi, > Thanks for the patch, I build a new version => 2.4.18. Enjoy. Thank you Christian. Eva, I don't know if you have seen Christian's email regarding 2.4.18. It did not make it to the bug report…

Bug#828342: [Htt-developers] Building with OpenSSL 1.0.2 is sufficient for stretch

On 2016-12-22 18:54:05 [+0100], Eva Ramon wrote: > Hi there, Hi, > I'll do the repackage as soon as Christian takes a look at it and > uploads a new upstream version. In the meantime if you want to apply > your patch, feel free to do a nmu. If you are happy to wait so am I. There is one spot

Bug#848957: [Pkg-openssl-devel] Bug#848957: openssl: support architecture tilegx

On 2016-12-21 08:44:34 [+0100], Helmut Grohne wrote: > openssl has special casing for each and every Debian architecture and > thus needs to be updated whenever a new architecture is being brought > up. Thus it needs to be updated for tilegx. Please consider applying the > attached patch. This

Bug#848926: jessie-pu: package libclamunrar/0.99-0+deb8u2

On 2016-12-20 21:56:22 [+], Adam D. Barratt wrote: > Please go ahead. done, thx. > Regards, > > Adam Sebastian

Bug#848926: jessie-pu: package libclamunrar/0.99-0+deb8u2

. + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Fri, 16 Dec 2016 21:38:26 +0100 + libclamunrar (0.99-0+deb8u1) stable; urgency=medium [ Scott Kitterman ] @@ -10,7 +17,7 @@ * switch from libclamunrar6 to libclamunrar7 * copy clamav's watch file * add pkg-

Bug#828340: fixed in hhvm 3.12.11+dfsg-1

On 2016-12-18 00:50:07 [+], Faidon Liambotis wrote: > Changes: > hhvm (3.12.11+dfsg-1) unstable; urgency=medium > . >[ Faidon Liambotis ] >* Build-Depend on libssl1.0-dev, as HHVM is not ready for OpenSSL 1.1.0 > yet. > (Closes: #828340) Is this this working? I am asking

Bug#828601: wpa: FTBFS with openssl 1.1.0

On 2016-11-13 14:45:30 [+0100], Julian Wollrath wrote: > I cannot do it myself but since the openssl transistion is ongoing now, > maybe the wpa version from experimental, which fixes this bug, should > be uploaded to unstable? Andrew, any chance that this upload hits unstable? It won't work like

Bug#848652: build fails on ppc64el, double free or corruption, stack suggests libssl

control: reassign -1 src:resiprocate On 2016-12-19 21:57:42 [+0100], Daniel Pocock wrote: > Thanks for taking the time to look at this. > > Is there an example of how this cleanup should be done, or is there a > specific line of code there that you believe is out of place?

Bug#736687: +pending

Control: tags -1 pending change sits in svn… Sebastian

Bug#848652: build fails on ppc64el, double free or corruption, stack suggests libssl

On 2016-12-19 09:40:38 [+0100], Daniel Pocock wrote: > Could this be a known issue on ppc64el or with libssl? Nothing comes to mind. But it explodes the same way (but without the fancy backtrace) on hurd, too. > FAIL: stunTestVectors > = > > INFO | 20161218-094209.416 | |

Bug#828471: opensc: FTBFS with openssl 1.1.0

control: severity -1 important control: unblock 827061 by -1 Eric, it seems you moved to openssl 1.0. In general you should have close this bug with your upload and cloned this bug with severity important so it can be addressed in Buster cycle. For now I unblocked the transition bug and lowered

Bug#828471: opensc: FTBFS with openssl 1.1.0

On 2016-12-17 21:52:30 [+0100], Sebastian Andrzej Siewior wrote: > Eric, it seems you moved to openssl 1.0. In general you should have Ah. And from looking at the upstream tracker / pull request, the 1.1.0 support has been merged upstream so you could just cherry-pick the 1.1.0 supp

Bug#846569: libsnmp-dev: Should depend on "libssl-dev | libssl1.0-dev" if possible

On 2016-12-02 10:43:17 [+0100], Raphaël Hertzog wrote: > Currently openvas is not buildable because it build-depends on libssh-dev > which depends on libssl1.0-dev and libsnmp-dev which depends on > libssl-dev (and both libssl*-dev are not co-installable). > > I believe we might be able to fix

Bug#848113: libcrypt-openssl-rsa-perl: binary incompatibility with libcrypt-openssl-pkcs10-perl (openssl versions)

On 2016-12-17 20:38:43 [+0200], Niko Tyni wrote: > > > For reference, here's a list of lib.*-perl packages depending on > > > libssl1.*. > > As of unstable, there should be nothing perl related depending on libssl1.0. > > If there is then please let me know because it probably might be good to >

Bug#828247: Building with openssl 1.1

On 2016-11-14 10:53:56 [+0100], Jordi Mallach wrote: > Hi Marc and Salvatore, > > Apologies, > > My intention after the NMU (which was the minimal change approach: build with > the version known to previously work) was to get #828247 cloned and lowered > to severity important so the 1.1 patches

Bug#848113: libcrypt-openssl-rsa-perl: binary incompatibility with libcrypt-openssl-pkcs10-perl (openssl versions)

On 2016-12-17 14:22:16 [+0200], Niko Tyni wrote: > That's assuming all the rebuilt packages migrate into stretch so that > none with libssl1.0.2 dependencies are left. Is anybody monitoring this? from the transition tracker everything *perl* is green so I don't see a reason why it should not

Bug#848113: libcrypt-openssl-rsa-perl: binary incompatibility with libcrypt-openssl-pkcs10-perl (openssl versions)

On 2016-12-14 19:21:07 [+0100], gregor herrmann wrote: > Hm, a breaks with a binNUM version sounds at least inelegant. > > How about: > libcrypt-openssl-pkcs10-perl: Depends: libcrypt-openssl-rsa-perl (>= 0.28-4) > libcrypt-openssl-rsa-perl: Breaks: libcrypt-openssl-pkcs10-perl (<< 0.16-2) All

Bug#828279: davix: diff for NMU version 0.6.4-1.1

gtest's header files or static libs. + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Thu, 15 Dec 2016 21:40:12 +0100 + davix (0.6.4-1) unstable; urgency=medium * Update to version 0.6.4 diff -Nru davix-0.6.4/debian/control davix-0.6.4/debian/control --- davix-0.6.4/debian/c

Bug#828469: openipmi: diff for NMU version 2.0.22-1.1

(Closes: #828469). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Wed, 14 Dec 2016 22:19:50 +0100 + openipmi (2.0.22-1) unstable; urgency=medium * new upstream release from 2016-06-01 diff -Nru openipmi-2.0.22/debian/patches/0001-Add-openssl-1.1.0-support.patch openipmi-2.0.22/

Bug#828408: fixed in libpoe-filter-ssl-perl 0.30-2

ndrzej Siewior <sebast...@breakpoint.cc> Date: Wed, 14 Dec 2016 22:03:38 +0100 Subject: [PATCH] libpoe-filter-ssl-perl: add openssl 1.1.0 support Signed-off-by: Sebastian Andrzej Siewior <sebast...@breakpoint.cc> --- SSL.xs | 24 ++-- 1 file changed, 18 insertio

Bug#847612: [Pkg-nagios-devel] Bug#847612: monitoring-plugins-basic lost OpenSSL support

On 2016-12-11 16:25:27 [+0100], Jan Wagner wrote: > Am 09.12.16 um 22:10 schrieb Adrian Bunk: > > configure: WARNING: OpenSSL or GnuTLS libs could not be found or were > > disabled > > thanks for notifying. Seems that there was a change in depencies in > unstable (and testing) for some of the

Bug#828477: Building against openssl1.0 for the time being

Control: severity -1 important On 2016-12-12 19:53:38 [+0100], Alberto Gonzalez Iniesta wrote: > Uploaded 2.4~rc1-1 build against openssl1.0 until upstream moves to 1.1 Okay. And with the lower severity it has a chance to get into testing. Sebastian

Bug#848079: nmu: libcrypt-openssl-bignum-perl_0.07-1

Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal nmu libcrypt-openssl-bignum-perl_0.07-1 . ANY . unstable . -m "rebuild against openssl 1.1.0" This NMU should pickup libssl1.1 instead 1.0.2 which is it currently linked against. Once this

Bug#848031: manpages: Can not be installed with initscripts

Package: manpages Version: 4.09-1 Severity: serious An upgrade fails: |Preparing to unpack .../manpages_4.09-1_all.deb ... |Unpacking manpages (4.09-1) over (4.08-1) ... |dpkg: error processing archive /var/cache/apt/archives/manpages_4.09-1_all.deb (--unpack): | trying to overwrite

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

On 2016-11-26 16:18:44 [+0100], gregor herrmann wrote: > I also mentioned your patch in the upstream bug: > https://rt.cpan.org/Ticket/Display.html?id=117481 > which contains a different patch from Petr Písař. > > No reaction there from either Petr or the upstream authors. > I just pinged the

Bug#828267: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

On 2016-12-11 21:07:14 [+0100], Michael Meskes wrote: > Sorry, wasn't precise enough it seems. I was wondering why you left out > the third possible option, namely the compatibility API in libssl 1.1. Ach. It does not work that way, this "compatibility" API is defined by the openssl build and

Bug#828267: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

control: merge -1 846543 On 2016-12-11 09:54:42 [+0100], Michael Meskes wrote: > What are you trying to do here? Reopen 828267 and merge with itself? > There is no other bug mentioned. What do I miss? Yeah. Not very smart. I intended to merge it with 846543. > > from the change [0] you use say

Bug#828267: reopen, it is still valid

control: reopen -1 control: merge -1 828267 from the change [0] you use say that a compatible API is used but the CFLAG change makes no sense. This is probably a miss understanding. You have two choices: - port (or let port) the software to use libssl-dev which provides the openssl 1.1.0 API

Bug#835800: transmission: FTBFS with openssl 1.1.0

On 2016-09-05 23:27:57 [+0100], Sandro Tosi wrote: > On Mon, Sep 5, 2016 at 10:59 PM, Sebastian Andrzej Siewior > <sebast...@breakpoint.cc> wrote: > > control: tags -1 patch > > thanks for the patch, against which version is this based on? 2.92 > reached unstab

Bug#828342: Building with OpenSSL 1.0.2 is sufficient for stretch

Can upstream please look at it? > cu > Adrian > Sebastian >From d22a8aad49283131472f79c9a1f369d78a397c9d Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Date: Thu, 8 Dec 2016 20:47:15 + Subject: [PATCH] httest: add OpenSSL 1.1.0 support Mo

Bug#846648: Raising severity

On 2016-12-03 10:19:56 [+0100], Yves-Alexis Perez wrote: > I'm not sure if it's the same issue than in 845785 so I'm not reopening that > bug, but rather raising the severity of this one. I can confirm chromium still > crashes here and there, sometime randomly, sometimes consistently. It looks

Bug#828371: lastpass-cli: diff for NMU version 1.0.0-1.1

against openssl 1.1.0 (Closes: #828371). + + -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 06 Dec 2016 21:10:47 +0100 + lastpass-cli (1.0.0-1) unstable; urgency=medium * New upstream 1.0.0 diff -Nru lastpass-cli-1.0.0/debian/patches/0001-cipher-support-

Bug#828564: sx: FTBFS with openssl 1.1.0

On 2016-12-05 22:36:39 [+0100], László Böszörményi (GCS) wrote: > Hi Sebastian, Hi László, > On Mon, Dec 5, 2016 at 10:20 PM, Sebastian Andrzej Siewior > > Okay. What do we do here? Any idea Laszlo? > > I could try to cherry-pick the three patches into the currect 2.0 but I >

Bug#828564: sx: FTBFS with openssl 1.1.0

On 2016-10-09 11:38:37 [+0300], Török Edwin wrote: > Dear Maintainer, > > Patches to build with both OpenSSL 1.0.x, and 1.1.0 are available in the > upstream git repository: > https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44 >

Bug#830482: [Pkg-clamav-devel] Bug#830482: clamav-freshclam: duplicate logging with systemd

On 2016-07-08 14:39:26 [+0200], Marki wrote: > freshclam is configured to log to its logfile by itself (UpdateLogFile). > However systemd unit file (as shipped with jessie) runs freshclam in > foreground and redirects its stdout to syslog. > > LogSyslog false > Foreground false According to the

Bug#840331: [Pkg-clamav-devel] Bug#840331: clamav autoconfiguring a Proxy based on Apt settings

On 2016-10-10 17:54:12 [+0100], T A F Thorne wrote: > If I check in /etc/clamav/freshclam.conf I can see: > # Check for new database 24 times a day > Checks 24 > DatabaseMirror db.local.clamav.net > DatabaseMirror database.clamav.net > # Proxy: http://warden.pt.local:3142/ > HTTPProxyServer

Bug#844066: [Pkg-clamav-devel] Bug#844066: clamav FTCBFS: build-depends on host architecture perl and python

control: tags -1 pending On 2016-11-12 09:42:18 [+0100], Helmut Grohne wrote: > clamav fails to cross build from source, because it Build-Depends on the > host architecture perl and python, both of which are neither installable > nor executable. Indeed clamav only uses both interpreters as build

Bug#828258: canl-c/gridsite: FTBFS with openssl 1.1.0

On 2016-12-03 12:14:38 [+0100], Stefan Fritsch wrote: > On Friday, 2 December 2016 00:16:24 CET Sebastian Andrzej Siewior wrote: > > is there a reason for gridsite not to go for 3.0 (or backport the > > change) and libssl-dev? Apache stays 1.0 but does not expose anything > >

Bug#846597: linux: please enable `perf data' support

. Upstream disabled it by default until more distros ship a libbabeltrace with the requested functions (and Debian is the first one). All this can be found in the patch attached. Sebastian From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Date: Fri, 2 Dec 2016 13:09:45 + Subject:

Bug#828371: lastpass-cli openssl 1.1.0 now has PR upstream

On 2016-11-02 22:13:04 [+0100], Andreas Henriksson wrote: > Hello! Hi, > > I've sent a PR to upstream that fixes building against OpenSSL 1.1.0. > Same patch should apply cleanly to the packaged version. could you please address the review comments and update your pull request? > Regards, >

Bug#828330: canl-c/gridsite: FTBFS with openssl 1.1.0

On 2016-11-15 20:22:10 [+0100], Stefan Fritsch wrote: > Hi again, Hi, > On Saturday, 12 November 2016 07:51:40 CET Stefan Fritsch wrote: > > If these two packages cannot transition to openssl 1.1.0 before apache2 > > does, I suggest that you build with openssl 1.0.2 explicitly and then > >

Bug#827061: transition: openssl

On 2016-12-01 00:52:59 [+0200], Adrian Bunk wrote: > Wouldn't "depends on libssl1.0.2 and does not build-depend on libssl1.0-dev" > give a reasonably small superset of all packages that need a binNMU? Do you mean something like is_affected = .depends ~ /libssl1\.0\.2/ & ! .build-depends ~

<    7   8   9   10   11   12   13   14   15   16   >