Re: Serious regression in systemd 215-17+deb8u10

2019-03-11 Thread Michael Biebl
Am 11.03.19 um 19:17 schrieb Markus Koschany: > > Am 11.03.19 um 15:51 schrieb Dan Poltawski: >> Thanks for your responses. One of my colleagues has been looking into this >> trying to get the bottom of it and we do seem to have identified a memory >> leak which isn't present on stretch. I note

Time allocation per CVE

2019-03-11 Thread Sylvain Beucler
Hi, I spent the day reproducing (unbreaking) the sqlalchemy exploit, figuring out how to run the test suite, attempting a backport of the upstream fix, plus some communication. I did about the same for the gnutls/nettle issue last week (only to conclude with a no-dsa T_T). While I believe those

Accepted zabbix 1:2.2.23+dfsg-0+deb8u1 (source amd64 all) into oldstable

2019-03-11 Thread Markus Koschany
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Mar 2019 13:16:44 +0100 Source: zabbix Binary: zabbix-agent zabbix-frontend-php zabbix-java-gateway zabbix-proxy-mysql zabbix-proxy-pgsql zabbix-proxy-sqlite3 zabbix-server-mysql zabbix-server-pgsql Architecture: source

sqlalchemy testsuite

2019-03-11 Thread Sylvain Beucler
Hi, Here are some notes about running the sqlalchemy test suite on jessie. The document leaves a lot of the setup up to the user. I still have some failures with MySQL and Unicode, even when configuring everything in utf8... I'm aggregating test suite notes at

Re: Serious regression in systemd 215-17+deb8u10

2019-03-11 Thread Markus Koschany
Am 11.03.19 um 15:51 schrieb Dan Poltawski: > Thanks for your responses. One of my colleagues has been looking into this > trying to get the bottom of it and we do seem to have identified a memory > leak which isn't present on stretch. I note the report posted to the list >

Re: Serious regression in systemd 215-17+deb8u10

2019-03-11 Thread Dan Poltawski
Thanks for your responses. One of my colleagues has been looking into this trying to get the bottom of it and we do seem to have identified a memory leak which isn't present on stretch. I note the report posted to the list https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924060. Here are what

Re: Contacting maintainers about no-dsa

2019-03-11 Thread Holger Levsen
On Mon, Mar 11, 2019 at 10:48:24AM +0100, Sylvain Beucler wrote: > A few days passed, I assume we reached consensus :) :) indeed. > I rephrased to explain this is not required. Also added the "no-dsa" > keyword in the previous section and clarified that one can fix a no-dsa > if they want to.

Re: Contacting maintainers about no-dsa

2019-03-11 Thread Sylvain Beucler
Hi, On 08/03/2019 15:54, Holger Levsen wrote: > On Fri, Mar 08, 2019 at 12:22:40PM +0100, Sylvain Beucler wrote: >> I was about do contact the nettle and gnutls maintainers, but after >> discussing with Emilio on IRC it appears that we do not contact >> maintainers for this anymore. >> >> Should