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-
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
>
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
>
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
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
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
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
> >
. 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:
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,
>
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
> >
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 ~
On 2016-11-30 21:22:38 [+], Thorsten Glaser wrote:
> Kurt Roeckx dixit:
>
> >But the errors I've always been seeing is a segfault during the
> >tests, and I have no idea what that is about.
>
> That didn't happen for me, but I found a wrong codegen bug in a
> testsuite recently (probably not
e time writing this email than
the patch. And I would like to avoid switching B-D now and looking at it
again after the release.
> cu
> Adrian
Sebastian
>From dc21aa1a25fa59e3e667cff8487f971dd74a3d0a Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: W
On 2016-11-05 21:59:27 [+0100], Sebastian Andrzej Siewior wrote:
> I've been playing with ben. I tried a few things and this is the best I
> was able to achieve [0]:
>
> title = "openssl 1.0";
> is_affected = .build-depends ~ /libssl1.0-dev/;
> is_good = .depen
On 2016-11-26 11:31:49 [+0200], Adrian Bunk wrote:
> Package: libtspi-dev
> Version: 0.3.14+fixed1-1
> Severity: serious
> Control: block 827061 by -1
>
> libtspi-dev must not force OpenSSL 1.1 on packages that
> are not ready for 1.1
>
> At least opencryptoki (#828465) and tpm-tools (#828577)
>
On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote:
> Package: polygraph
> Version: 4.3.2-4
> Severity: serious
> Tags: patch
> Control: block 827061 by -1
>
> ...
> checking for CRYPTO_lock in -lcrypto... no
> checking for CRYPTO_add_lock in -lcrypto... no
> ...
>
> Not a perfect solution but an
Should I NMU it?
Sebastian
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Tue, 29 Nov 2016 21:10:31 +0100
Subject: [PATCH] cherry-pick patches for OpenSSL 1.1.0 support and TCP_NODELAY
Signed-off-by: Sebastian Andrzej Siewior <sebast...@breakpoint.cc&g
On 2016-11-28 23:31:38 [+0200], Adrian Bunk wrote:
> Control: retitle -1 gnubiff: FTBFS due to missing #include
> Control: tags -1 patch fixed-upstream
> Control: unblock 827061 by -1
>
> I've confirmed that gnubiff builds fine with OpenSSL 1.1
>
> The attached patch cherry-picks the missing
control: reopen -1
control: severity -1 important
On 2016-11-22 17:06:05 [+], Debian Bug Tracking System wrote:
>* Build-depend on libssl1.0-dev, upgrade to 1.1 requires v3.0 upstream
> release. Closes: #835811
please keep this bug open and close once it builds against openssl
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
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
On 2016-11-18 15:22:07 [+0100], Benjamin Drung wrote:
> Instead of forcing salt to use OpenSSL 1.0, let's try to make it work
> with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1
> was quite easy. I forwarded the patch upstream to
> https://github.com/saltstack/salt/pull/37772
control: tags -1 patch fixed-upstream
On 2016-07-24 12:01:29 [+0200], Oswald Buddenhagen wrote:
> fixed in git on isync_1_2_branch.
Upstream fixed it
https://sourceforge.net/p/isync/isync/ci/41308e481466b91813f6765a0c92ad83fd9d1ab2/
In their 1.2 release branch which is available in
SSL_no_config
the problem is that salt/rsax931.py loads the library manually and
expects certain symbols which are no longer available in OpenSSL 1.1.0.
And it loads the first libcrypto it finds plus has no dependency on
openssl.
Sebastian
>From 67676f782796071a793ec1908de50c7b86e9fbee Mon Sep 17
Control: tags -1 - patch
On 2016-11-10 12:31:00 [+0200], Adrian Bunk wrote:
>
> Not a perfect solution but sufficient for stretch is the following
> change to use OpenSSL 1.0.2:
>
> --- debian/control.old2016-11-10 10:20:58.0 +
> +++ debian/control2016-11-10
On 2016-11-14 22:43:16 [+0100], gregor herrmann wrote:
> Yay, this looks good!
So upstream came up with the patch attached after I forwaded mine. Can
you please confirm whether this works or not?
> Cheers,
> gregor
Sebastian
diff --git a/src/prototypes.h b/src/prototypes.h
index
On 2016-11-15 12:39:25 [+0100], Apollon Oikonomopoulos wrote:
> Hi Ian,
Hi,
> On 11:16 Tue 15 Nov , Ian Jackson wrote:
> > 812166 is nothing to do with openssl AFAICT.
> > I don't think Xen is involved with the openssl transition.
> >
> > Did you get the wrong bug ?
>
> I'm terribly sorry
On 2016-11-14 22:43:16 [+0100], gregor herrmann wrote:
> Control: tag -1 + patch
>
> On Mon, 14 Nov 2016 22:07:12 +0100, Sebastian Andrzej Siewior wrote:
>
> > On 2016-11-14 00:17:31 [+0100], gregor herrmann wrote:
> > > Thanks, but nope, still the same:
> &
On 2016-11-14 00:17:31 [+0100], gregor herrmann wrote:
> Thanks, but nope, still the same:
What about this one?
Sebastian
>From b436cd6527a2a32bd94b67ff10363e45a2f52430 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Mon, 14 Nov 2016 21
On 2016-11-11 16:05:05 [+0100], gregor herrmann wrote:
> As soon as fetchnews connects, stunnel4 segfaults.
I tried your config against a http server and mail server with no luck.
> The messages in the syslog:
> Nov 11 15:53:55 jadzia stunnel: LOG2[2]: Double free attempt:
> ptr=0x7f6340010430
Source: libesmtp
Version: 1.0.6-4
Severity: serious
Control: block 827061 by -1
OpenSSL 1.1.0 has been released. During a rebuild of all packages using
OpenSSL this package succeeded to build but it should have failed. That is why
this bug is coming so late. The build simply deactivated TLS
On 2016-11-12 21:57:29 [+0100], Kurt Roeckx wrote:
> > Yes, you are right. Maybe we shouldn't run the testsuite in parallel.
> The test suite should not be running parallel? As far as I know
> that's not supported, and we're not doing it.
I think so. Looking at logs of armel, amd64, arm64 the
On 2016-11-12 21:21:23 [+0100], Kurt Roeckx wrote:
> On Sat, Nov 12, 2016 at 08:51:09PM +0100, Sebastian Andrzej Siewior wrote:
> > Why did it say "Keys mismatch" then? I don#t see this in a normal built.
>
> I see it in all the logs? But it seems to be at a slighty
On 2016-11-12 17:22:42 [+0100], Kurt Roeckx wrote:
> On Fri, Nov 11, 2016 at 09:21:41AM +0100, jean-christophe manciot wrote:
> > Package: openssl
> > Version: 1.1.0c-1
>
> > skipped: Test only supported in a shared build
> > ../test/recipes/90-test_srp.t ..
>
> This test did not
On 2016-11-11 19:21:26 [+0100], sternasky wrote:
> Hello,
Hi,
> after some analysis i found infos about php security changes after
> 5.6,7.0.12.2
>
> Self Signed Certs like
>
> SSLCertificateFile/etc/ssl/certs/ssl-cert-snakeoil.pem
> SSLCertificateKeyFile
On 2016-11-10 12:10:41 [+0100], Ondřej Surý wrote:
> Sebastian,
Hi Ondřej,
> thanks for the patch. The 0.13~svn685-7 version in unstable includes
> your patch,
> and I would really appreciate if someone could test whether
> dnssec-trigger now
> works.
I managed to get around to test it. So the
On 2016-11-10 12:10:04 [+0200], Adrian Bunk wrote:
> On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior wrote:
> > control: forwarded -1 https://github.com/rbsec/sslscan/issues/108
>
> Sebastian, Marvin, what is the status regarding getting this patch that
> wa
rks? I am confident
but don't time todo it myself just now.
Sebastian
>From 05cd529e19d317b8bcc69f7d883873a27195b904 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Mon, 7 Nov 2016 20:59:11 +
Subject: [PATCH] dnssec-trigger: openssl 1.1.0 fixup
On 2016-11-03 22:15:50 [+0100], Marek Lukaszuk wrote:
> Thanks, it works, I feel like an idiot for not finding this.
it wasn't documented. how should you find it? I just figured it out
myself.
> > Let me see what upstream says…
>
> It is a bit of a surprise, normally I would argue for a bit more
On 2016-10-26 10:55:19 [+0200], Emilio Pozuelo Monfort wrote:
> So let's do this. Let's try to get it finished and only ship openssl 1.1. We
> still have three months until the full freeze, and depending on how many
> packages (and which ones, for risk management etc) are left to be fixed after
>
On 2016-11-03 23:39:32 [+0100], László Böszörményi (GCS) wrote:
> OK, it remained the same then. May you try the work in progress
> update[1]? I'm off for sleeping. :-/
yup, worked.
> Thanks,
> Laszlo/GCS
Sebastian
On 2016-11-03 22:02:23 [+0100], László Böszörményi (GCS) wrote:
> On Thu, Nov 3, 2016 at 8:48 PM, Sebastian Andrzej Siewior
> <sebast...@breakpoint.cc> wrote:
> > On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> > fetchmail builds against openssl 1.
On 2016-11-03 15:59:25 [+0100], Marek Lukaszuk wrote:
> passphrase I'm getting below error:
>
> > cat file_encrypted.dat | openssl enc -d -aes-256-cbc
> enter aes-256-cbc decryption password:
> bad decrypt
> 139814539760704:error:06065064:digital envelope
>
control: retitle: -1 fetchmail: FTBFS if building in parallel
On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote:
> Hello Kurt Roeckx.
Hi,
> The failure in this build log didn't look like it was really openssl related.
> I've tried rebuilding the package which succeded for me.
>
> Could
On 2016-11-01 17:41:27 [-0400], Sam Hartman wrote:
> Hi.
Hi,
> I'm sorry I didn't get a chance to respond to your other mail.
> upstream has dealt with moonshot-gss-eap and moonshot-ui and I plan to
> address the bugs there with a new upstream version.
You could point that out in the relevant
and is using it. So far it seems only alpine does [0].
[0]
http://sources.debian.net/src/alpine/2.20%2Bdfsg1-2/web/src/alpined.d/alpined.c/?hl=10831#L10831
> Kurt
Sebastian
>From b45c2495fffd431a4eee359c24a0b292c87bc33c Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@brea
control: tags -1 fixed-upstream
control: forwarded -1 https://github.com/libevent/libevent/pull/397
my understaning is that an updated version of this patch has been merged
upstream. That is
https://github.com/libevent/libevent/commit/3e9e0a0d46e4508e8782ec3787c6d86bab63046d
Sebastian
Attempted/moonshot-gss-eap_0.9.5-1_amd64-20160529-1451
this builds now. Do you have anything to verify?
> Kurt
Sebastian
>From 50b12a010649c57ca7080cc728c8088abf53f73e Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Tue, 1 Nov 2016 20:41:46
On 2016-10-31 11:16:38 [-0400], Sam Hartman wrote:
> At least one of the clusters of packages I'm involved in--shibboleth and
> moonshot will require some real upstream porting effort.
> That's under way in a time scale that will work for buster, but is very
> unlikely to meet the stretch freeze
control: tags -1 patch
On 2016-06-26 12:24:29 [+0200], Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
> OpenSSL this package fail to build. A log of that build can be found at:
>
control: forwarded -1 https://github.com/OpenSC/pkcs11-helper/pull/7
control: tags -1 patch
On 2016-06-26 12:23:44 [+0200], Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
> OpenSSL this package fail to build. A log of that build can be found at:
On 2016-06-26 12:21:14 [+0200], Kurt Roeckx wrote:
> Source: cargo
> Version: 0.9.0-1
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
> OpenSSL this package fail to build. A log of that build can be
On 2016-10-28 22:54:58 [+0200], Thomas Goirand wrote:
> Hi,
Hi,
> Until OpenSSL 1.1.0 is in Sid, there's no reason to have the bug
> severity raised to serious. Currently, it's only in Experimental.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827061#931 which
says to set it serious.
>
control: reopen -1
On 2016-10-29 14:15:26 [+0200], Sebastian Andrzej Siewior wrote:
> I moved away from bsdiff and don't need this anymore. This improvement help a
> little the main reason for moving away is that the average file was getting
> bigger to a point where bsdiff was still t
On 2016-10-29 14:15:30 [-0700], Noah Meyerhans wrote:
> Control: tags -1 - patch + upstream
> Control: forwarded -1 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7361
>
> Unfortunately, this patch breaks compatibility with OpenSSL < 1.1.0, as
> the CRYPTO_zalloc function does not exist
control: tags -1 patch fixed-upstream
control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=118344
Crypt-SMIME-0.18 has the fix
Sebastian
Control: tags - patch
builds. Further testing is welcome.
Sebastian
>From f6afa6be81eae0b149ad18a0642c67e75b148c69 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Thu, 27 Oct 2016 19:43:15 +
Subject: [PATCH] opendkim: port to open
On 2016-10-26 21:31:26 [+0200], Kurt Roeckx wrote:
> > Is this situation
> > supported or should we expect things to break? This can easily happen if an
> > app
> > links against a library libA which uses openssl 1.0, and against libB which
> > uses
> > openssl 1.1.
>
> When linking you
control: tags -1 pending
On 2016-10-25 19:46:00 [+0200], Andreas Beckmann wrote:
> 1m3.1s ERROR: FAIL: Package purging left files on system:
> /etc/systemd/system/clamav-daemon.service.d/ not owned
Interresting. So it is just a folder that remains after a purge of
clamav-daemon.
On 2016-10-24 14:35:46 [-0400], Michael Jeanson wrote:
> After discussing it with Jérémie the rc1 was officially released, I've
> just pushed it to Debian, should be available in unstable tomorrow.
So I tried to build the perf ctf I noticed that I need
diff --git
Package: babeltrace
Version: 1.4.0-3
Severity: wishlist
Could you please bump babeltrace to the 1.5 series which is prepared in
https://github.com/jgalar/babeltrace/tree/stable-1.5-staging
This is upstream kind answer to what is needed to get the `perf' command
(from the linux-perf
On 2016-10-17 11:08:12 [+0200], LACROIX Jean Marc wrote:
> I am trying to replace systemd with sysvinit on a fresh Debian jessie 8.6
> It seems there is one problem when updating, because .
>
> root@cubietruck:~# apt-get upgrade
…
> Preconfiguring packages ...
> Can't exec
On 2016-09-01 23:54:23 [+0200], Sebastian Andrzej Siewior wrote:
> The latest build failed against 2.5-2+v2.4-2. I see that 2.5-3 is
> prepared for experimental. Upstream's git seems to build against openssl
> 1.1.0 (didn't test but the commits make it look like).
2.6 has been released a
at to see if everything works.
please find attached.
>
>
> Kurt
Sebastian
>From 669bf5ce0ccdac2b5d121cf693f65c4b1db81862 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Sat, 8 Oct 2016 22:21:32 +
Subject: [PATCH] libcrypt-openssl
on kfreebsd-* (Closes: #840063)
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sat, 08 Oct 2016 15:11:19 +0200
+
xz-utils (5.2.2-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru xz-utils-5.2.2/debian/control xz-utils-5.2.2/debian/control
--- xz-utils-5.2.2/debian/c
Package: xz-utils
Version: 5.2.2-1.1
Severity: normal
FTBFS on kfreebsd. This is to keep track. I will try to look into this.
Sebastian
On 2016-10-05 20:06:13 [+0200], Emilio Pozuelo Monfort wrote:
> configure: Using external LLVM
> checking for supported LLVM version... no (3.8.1)
> configure: error: LLVM < 3.7 required, but "3.8.1"(381) found
> configure: error: Failed to configure LLVM, and LLVM was explicitly requested
it is
; Kurt
Sebastian
>From 6efaaad1f6b5ed33b5079d2f116db8795a708d8c Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Mon, 3 Oct 2016 12:32:38 +
Subject: [PATCH 1/2] libcrypt-openssl-dsa-perl: add openssl 1.1.0 support
Signed-off-by: Sebastian Andrzej Siewior <s
ian
>From fdbda9585f5c99670912e5c0517dbc7a9d92c74b Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Sat, 1 Oct 2016 19:52:44 +
Subject: [PATCH] libcrypt-openssl-rsa-perl: get it compiled with openssl 1.1.0
Signed-off-by: Sebastian Andrzej Siewior <se
te_key().
> Kurt
Sebastian
>From 285baad51e3ce9609958a892d6b5246ed9dda9ce Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Sat, 1 Oct 2016 19:52:44 +
Subject: [PATCH] libcrypt-openssl-rsa-perl: get it compiled with openssl 1.1.0
Signed
control: tags -1 patch
On 2016-09-21 22:59:56 [+0200], Sebastian Andrzej Siewior wrote:
> The patch attached has been sent upstream. It is untested and I kindly
> asked them to test it. I don't tag it patched until someone confirms
> that this works.
the patch attached was tested wi
control: tags -1 fixed-upstream
On 2016-08-28 23:20:07 [+0200], Sebastian Andrzej Siewior wrote:
> done.
seems to be part of 1.5.10.
> Kurt
>
Sebastian
control: forwarded -1 https://github.com/lsh123/xmlsec/pull/40
control: tags -1 fixed-upstream
On 2016-08-31 23:37:54 [+0200], Sebastian Andrzej Siewior wrote:
>
> 1.2.22 plus the patch attached and it builds again :)
This
https://github.com/lsh123/xmlsec/
On 2016-09-12 22:10:34 [+0200], Sebastian Andrzej Siewior wrote:
> VirtualBox hackers! Could you please take a look at this? It should
> compile against openssl 1.1.0 and 1.0.2h and work.
It seems the patch is/was not perfect. According to [0] they applied
parts of it to trunk and will ba
On 2016-09-18 21:33:43 [+0200], Kurt Roeckx wrote:
>
> So OpenSSL 1.1.0 was released about 3 weeks ago. Since then we've
now a month and a few days now.
> been working on the key packages, to get them to build with
> OpenSSL 1.1.0. You can see that status of that at:
>
Package: gsoap
Version: 2.8.35-2
Severity: serious
The package FTBFS with -j16:
| make[5]: Entering directory '/<>/gsoap/src'
| /bin/bash ../../ylwrap soapcpp2_yacc.y y.tab.c soapcpp2_yacc.c y.tab.h `echo
soapcpp2_yacc.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx / -e
s/c++$/h++/ -e
On 2016-09-26 22:16:02 [+0200], Sebastian Andrzej Siewior wrote:
> I've prepared an NMU for xz-utils (versioned as 5.2.2-1.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
And this version is the debian/ folder only ignoring the main versi
control: tags -1 patch
On 2016-06-26 12:23:21 [+0200], Kurt Roeckx wrote:
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
builds.
> Kurt
Sebastian
From: Sebastian Andrze
control: tags -1 patch fixed-upstream
On 2016-06-26 12:22:21 [+0200], Kurt Roeckx wrote:
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
please find attached the upstream patches.
>
control: tags -1 patch fixed-upstream
On 2016-06-26 12:23:58 [+0200], Kurt Roeckx wrote:
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
from
feel free to contact us.
>
>
> Kurt
Sebastian
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Thu, 22 Sep 2016 11:19:42 +
Subject: [PATCH] spamassassin: get it compiled against openssl 1.1.0
CRYPTO_lock was part of the old locking API which got removed. I p
rms
that this works.
> Kurt
Sebastian
>From 0bd3b308f964f52db02b20b5db3a6f9a45c35072 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Wed, 21 Sep 2016 19:54:04 +
Subject: [PATCH] spice-gtk: get it compiled against openssl 1.1.0
and also 1.0
On 2016-09-21 15:35:31 [+], Louis Bouchard wrote:
> A very basic test is available :
> make -f makefile.shared stest
>
> ./stest
t;entries,i);
>
> I think you're looking for:
> for (i = 0; NULL != subj && i < X509_NAME_entry_count(subj); i++)
> {
> X509_NAME_ENTRY *ne = X509_NAME_get_entry(subj, i);
>
exactly. Thank you.
The patch attached should contain the cha
On 2016-09-16 11:53:07 [+0200], Ph. Marek wrote:
> $ openssl rand -base64 3
> WTIu
> unable to write 'random state'
Thanks. I posted a patch
https://mta.openssl.org/pipermail/openssl-dev/2016-September/008508.html
let's see what upstream says.
Sebastian
control: tags -1 fixed-upstream
On 2016-09-17 22:01:25 [+0900], Tatsuhiro Tsujikawa wrote:
> > Thank you for the patch. It has been applied and merged into master
> > branch.
> > I've made another couple of commits to fix OpenSSL 1.1.0 deprecation
> > warnings.
That would be
rom 9e74d00a28bf3294722d07a52646a8b1a5740237 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Thu, 15 Sep 2016 20:01:49 +
Subject: [PATCH] spdylay: compile against openssl-1.1.0
It fails to compile against openssl 1.1.0 due to th
Hi,
can you close this or merge it with #828401 (which is archived).
Sebastian
blic key to the
> function.
I think I've found it a few lines above.
VirtualBox hackers! Could you please take a look at this? It should
compile against openssl 1.1.0 and 1.0.2h and work.
> Kurt
Sebastian
>From 0e3d6cc69959fdf4f4fd56f65353b76897c0daad Mon Sep 17 00:00:00 2001
hed. I could throw on a freebsd-* porter box
first if you want me to.
Sebastian
>From 02edb8d94682fcf13a7e98618294e06f728e66e6 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Sat, 10 Sep 2016 19:27:17 +
Subject: [PATCH] sendmail: compile agains
On 2016-09-10 16:36:35 [+0200], Kurt Roeckx wrote:
> Looking at the certificate subject looks just wrong. It should
> at least check the Subject Altnerative Name, if present, and it
> should be present. And it really shouldn't convert it to a string
> and hope there are no other field that
ing sendmail in stretch!
could you please try if the patch attached works? It compiles :)
> Andreas
Sebastian
>From ac5e68745e050f8e86e435994eec866718128242 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Sat, 10 Sep 2016 19:27:17 +
Subject: [
control: forwarded -1 https://bugs.php.net/bug.php?id=72360
control: tags -1 fixed-upstream
On 2016-06-26 12:23:40 [+0200], Kurt Roeckx wrote:
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything
and I have no idea what
it was and its purpose was. They don't even assign anything to it in
1.0.2h.
> Kurt
Sebastian
>From 0e3d6cc69959fdf4f4fd56f65353b76897c0daad Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Wed, 7 Sep 2016 20:22:54
control: tags -1 patch
On 2016-06-25 12:57:24 [+0200], Kurt Roeckx wrote:
> Your package is failing to build with openssl 1.1:
> otp.c: In function 'otp_hash':
> otp.c:121:16: error: storage size of 'mdctx' isn't known
> EVP_MD_CTX mdctx;
>
> The struct has been made opaque and you now
On 2016-09-05 23:27:57 [+0100], Sandro Tosi wrote:
> thanks for the patch, against which version is this based on? 2.92
> reached unstable after this bug was filed
unstable.
Sebastian
> Kurt
Sebastian
>From 9978fb6970420bcaab9f60c544b6a369c5638ce2 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Mon, 5 Sep 2016 21:49:07 +
Subject: [PATCH] transmission: build against openssl 1.1.0
Signed-off-by: Sebastian Andrzej Siewior <se
On 2016-06-28 16:40:09 [-0300], Antonio Terceiro wrote:
> upstream already has support for OpenSSL 1.1.0 in trunk for Ruby 2.4;
> see upstream bug linked above. given the current state of afairs, we
> will need to either backport that for Ruby 2.3 ourselves, or disable the
> openssl extension
pen in there. If HALP is turned into 0 then it compiles.
> Kurt
Sebastian
>From 58fa4e5de620b90fca7c2366a130ec73d0aee0f0 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Mon, 5 Sep 2016 10:49:54 +
Subject: [PATCH] virtuoso-opensource: build agains
On 2016-09-04 21:37:45 [+0300], Stefanos Sofroniou wrote:
> Weird...I have the same problem with 52.0.2743.116-2 and it happened a few
> minutes ago when I tried to open multiple tabs at once.
>
> I'm using Debian testing 64-bit, fully updated.
Fully updated unstable and it works again after
1201 - 1300 of 1880 matches
Mail list logo
