(Closes: #940547).
+
+ -- Sebastian Andrzej Siewior Mon, 30 Sep 2019 20:58:11 +0200
+
python-cryptography (1.7.1-3+deb9u1) stretch; urgency=medium
* Remove BIO_callback_ctrl: The prototype differs with the OpenSSL's
diff -Nru python-cryptography-1.7.1/debian/patches/series p
On 2019-04-17 07:46:44 [+], Mayer, Dirk wrote:
> Is there any chance with bug will be fixed ?
> Do you need more information ?
I just stumbled uppon this report. Is this still the case as with
1.7.1-3+deb9u1? I think it appeared shortly after you wrote this email.
> Thanks an best regards
> D
edium
+
+ * Non-maintainer upload.
+ * Backport two patches to fix the testsute with newer openssl.
+ * Ignore test_load_ecdsa_no_named_curve in the testsuite because it known to
+break with newer openssl (Closes: #940547).
+
+ -- Sebastian Andrzej Siewior Tue, 24 Sep 2019 21:10:32 +0200
+
p
On 2019-09-11 09:23:24 [+0200], Matus UHLAR - fantomas wrote:
> > On September 9, 2019 10:03:13 AM UTC, Matus UHLAR - fantomas
> > wrote:
> > > Please, add meta package pointing to current libclamunrar.
>
> On 10.09.19 16:02, Sebastian Andrzej Siewior wrote:
> >
Package: python-cryptography
Version: 2.6.1-3
Severity: serious
The upload of latest openssl 1.1.1d triggert three testsuite failures in
python-cryptography [0]
- _ test_buffer_protocol_alternate_modes[mode5]
__
|mode =
|backend =
|
|@pytest.mark.parametriz
On September 9, 2019 10:03:13 AM UTC, Matus UHLAR - fantomas
wrote:
>Please, add meta package pointing to current libclamunrar.
Do you have an example how that should look like? I can't add package to main
which has a recommends or depends on a package in contrib or non-free, see:
https://ww
On 2019-09-03 21:24:04 [-0400], Dylan H. wrote:
> As title says. Using AppImages with older OpenSSL binaries instantly aborts
> the
> application and I get no error codes. I have tested this with Ripcord and it
> will not open.
can you give some more details? Like what you have installed and what
On 2019-08-25 15:00:21 [+0100], Adam D. Barratt wrote:
> Please go ahead.
thanks, both packages are uploaded.
> Regards,
>
> Adam
>
Sebastian
],[$PCRE_HOME],[$have_pcre])
fi
CL_MSG_STATUS([libmspack ],[yes],[$mspack_msg])
-if test "x$XML_LIBS" = "x"; then
+if test "x$XML_LIBS" = "x"; then
CL_MSG_STATUS([libxml2 ],[no],[])
else
CL_MSG_STATUS([libxml2 ],[yes, from $XML_HOME
On 2019-08-22 15:36:31 [-0400], Hugo Lefeuvre wrote:
> Great! Is anybody working on 0.101.4 updates for stretch/buster? I plan to
> backport the update to jessie after that.
I'm tired now but I plan to take care of this over the weekend.
> regards,
> Hugo
Sebastian
dansguardian-2.10.1.1/debian/changelog
--- dansguardian-2.10.1.1/debian/changelog
+++ dansguardian-2.10.1.1/debian/changelog
@@ -1,3 +1,10 @@
+dansguardian (2.10.1.1-5.1+deb9u2) stretch; urgency=medium
+
+ * Non-maintainer upload.
+ * Add support for clamav 0.101 (Closes: #923981).
+
+ -- Sebastian Andrzej
)
+m4_include([m4/reorganization/code_checks/fuzz.m4])
m4_include([m4/reorganization/code_checks/functions.m4])
m4_include([m4/reorganization/code_checks/mpool.m4])
m4_include([m4/reorganization/code_checks/unit_tests.m4])
diff -Nru libclamunrar-0.101.1/debian/changelog
libclamunrar-0.101.2/de
upload.
+ * Add support for clamav 0.101.1 (Closes: #919814).
+
+ -- Sebastian Andrzej Siewior Sun, 10 Mar 2019
22:00:14 +0100
+
c-icap-modules (1:0.4.4-1) unstable; urgency=medium
* New upstream release
diff -Nru c-icap-modules-0.4.4/debian/control
c-icap-modules-0.4.4/debian/control
match
+
+ -- Sebastian Andrzej Siewior Sun, 10 Mar 2019
17:30:34 +0100
+
havp (0.92a-4) unstable; urgency=medium
[ Andreas Cadhalpun ]
diff -Nru havp-0.92a/debian/control havp-0.92a/debian/control
--- havp-0.92a/debian/control 2015-07-31 22:54:50.0 +0200
+++ havp-0.92a/debian/control
]
+ * Add d/p/python-clamav-add-support-for-clamav-0.101.0.patch to that
+python-clamav builds/works with clamav 101.1 and newer (Closes: #920959)
+ * Bump libclamav-dev build-depends to match
+
+ -- Sebastian Andrzej Siewior Sun, 10 Mar 2019
20:49:14 +0100
+
python-clamav (0.4.1-8) unstable
On 2019-08-20 23:45:18 [+0100], Adam D. Barratt wrote:
> > and then open p-u bugs
> > for the transition?
>
> Is anything required beyond binNMUs of r-deps?
I tried to highight this in the first email of this bug:
|It affects the following packages as part of the transistion which
|require a sou
On 2019-08-20 22:18:28 [+0100], Adam D. Barratt wrote:
> Indeed, and then we dropped the ball again. :-(
>
> Let's get this going.
So I upload the here promissed Stretch package and then open p-u bugs
for the transition?
> Regards,
>
> Adam
Sebastian
control: tags -1 patch
control: fixed -1 2.12+dfsg-1
control: forwarded -1
http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=ccec71ec318fdf739f55858d5bffaf4fd6520036
On 2013-05-22 14:32:48 [+0200], appzer0 wrote:
> Upstream patch (applied on git but never released, as cpio 2.11 is pretty
> old
On 2019-08-12 23:59:10 [+0200], Kurt Roeckx wrote:
> > Kurt, could we get something into OpenSSL (aka openssl s_client
> > -connect) which describes the error more accurate / verbose?
> > I will try to collect some information and point the ssllabs people to
> > it hoping that it will pop up in the
On 2019-08-12 18:22:38 [+0200], Kurt Roeckx wrote:
> On Mon, Aug 12, 2019 at 10:42:06AM +0200, Johannes Schauer wrote:
> > > > curl: (35) error:1414D172:SSL
> > > > routines:tls12_check_peer_sigalg:wrong signature type
> >
> > thanks to juliank on #debian-devel I found out that this issue see
control: found -1 0.98.6+dfsg-1
On 2019-08-12 08:21:22 [+0200], Hugo Lefeuvre wrote:
> Hi Sebastian,
Hi,
> I'm sorry if this sounded insistent, it was not intended like that.
No problem, everything is okay. I was planning to open a similar bug
just to point out that the issue is not completly fi
On 2019-08-10 09:39:22 [+0200], Hugo Lefeuvre wrote:
> Source: clamav
> Version: 0.101.2+dfsg-3
> Severity: important
> Tags: security upstream
> Forwarded: https://bugzilla.clamav.net/show_bug.cgi?id=12356
>
> Hi,
>
> clamav is affected by a DoS vulnerability caused by crafted, extremely
> compr
1.2+dfsg-1+deb10u1) buster; urgency=medium
+
+ * Cherry-pick a fix from 0.101.3 to address a vulnerability to
+non-recursive zip bombs.
+
+ -- Sebastian Andrzej Siewior Tue, 06 Aug 2019
22:07:01 +0200
+
clamav (0.101.2+dfsg-1) unstable; urgency=high
* Import 0.101.2
diff -Nru clamav-0.
which was fixed in OpenSSL 1.1.1c (Closes: #929903).
+
+ -- Sebastian Andrzej Siewior Sat, 08 Jun 2019 12:35:11 +0200
+
m2crypto (0.31.0-3) unstable; urgency=medium
* add 0002-tests-test_ssl-use-ciphercuites-for-TLS1.3-cipher-in.patch
diff -Nru m2crypto-0.31.0/debian/patches/0003-Remove-dupl
).
+
+ -- Sebastian Andrzej Siewior Sat, 08 Jun 2019 12:35:11 +0200
+
m2crypto (0.31.0-3) unstable; urgency=medium
* add 0002-tests-test_ssl-use-ciphercuites-for-TLS1.3-cipher-in.patch
diff -Nru m2crypto-0.31.0/debian/patches/0003-Remove-duplicate-call-of-the-error-code.patch m2crypto-0.31.0
On 2019-06-08 10:28:38 [+0200], Matěj Cepl wrote:
> Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 23:10 +0200:
> > It did not if I understand the python correctly:
> > >with self.assertRaises(RSA.RSAError):
> > >priv.private_decrypt(ctxt, RSA.s
On 2019-06-08 10:22:54 [+0200], Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi Sebastian,
Hi Paul,
> Can you please elaborate why this version meets the freeze policy, or
> why it should get an exception? In the text above there is no mention at
> all of serious bugs that get fixed. openss
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package openssl.
The updated package is the `c' version, which is the latest upstream
release for the 1.1.1 series.
This update causes a regresion in the m2crypto test suite w
On 2019-06-04 14:24:12 [+0200], Matěj Cepl wrote:
> Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 14:15 +0200:
> > Let me ping upstream: Matěj, could you please take a look at
> > https://bugs.debian.org/929903
> >
> > and check if it is okay the test no
On 2019-06-04 12:12:35 [+0200], Kurt Roeckx wrote:
> On Tue, Jun 04, 2019 at 12:46:07AM +0200, Sebastian Andrzej Siewior wrote:
> >
> > So if I decoded it right, it does
> >
> > | fbuf = sha1("The magic words are squeamish ossifrage."); /* 0xbf
On 2019-06-02 23:39:22 [+0200], Kurt Roeckx wrote:
> > So, I added a small test for RSA_SSLV23_PADDING, as an extra commit,
> > since it will likely not cherry-pick in stable branches.
>
> It's about this change:
> -good &= constant_time_lt(threes_in_row, 8);
> +good &= constant_time_ge(th
Package: openssl
Version: 1.1.1c-1
Severity: serious
The m2crypto test suite fails with c, passes with b. The error log
https://ci.debian.net/data/autopkgtest/testing/amd64/m/m2crypto/2436983/log.gz
The testsuite complains about a missing error / the exception is not
raised. The bisect says, th
On 2019-04-21 16:52:30 [+0200], Paul Gevers wrote:
> Hi Kurt, Christoph, Sebastian, others,
Hi Paul,
> Could somebody of the openssl team propose a text that can be added to
> the release-notes about the new defaults? I am not asking for package
> specific text (although that is welcome of course)
On 2019-04-15 08:50:52 [+0100], Adam D. Barratt wrote:
> OK, thanks for the confirmation.
>
> Please go ahead.
uploaded.
> Regards,
>
> Adam
Sebastian
On 2019-04-14 21:08:46 [+0100], Adam D. Barratt wrote:
> On Sun, 2018-11-25 at 13:49 +0100, Sebastian Andrzej Siewior wrote:
> > With the intention of pushing OpenSSL 1.1.0j into Stretch here is the
> > proposed change for python-cryptography.
> > The package python-cryptograp
On 2019-04-14 11:28:59 [+0100], Adam D. Barratt wrote:
> In the interest of keeping things moving, please feel free to go ahead.
thanks, uploaded.
> Adam
Sebastian
On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote:
> On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote:
> > I'm proposing this attached debdiff.
> > For testing I compiled it against libssl1.0-dev 1.0.2j-5 and then
> > upgraded to the versio
On 2019-04-03 11:14:54 [+0100], Dimitri John Ledkov wrote:
> $ wget https://google.com
>
> fails in Buster alpha installer, when used from a booted netinst iso
> in a tty. It also means that fetch-url fails, and thus one cannot use
> https preseeding.
>
> A fix/workaround, is $ touch /usr/lib/ssl
control: reassing -1 src:openssl
control: forcemerge 923516 -1
On 2019-04-03 15:27:42 [+0200], Štěpán Liška wrote:
> https://github.com/openssl/openssl/issues/8375
So you want also the openssl issue 8375 fixed in Buster/Sid openssl.
This can be done however upstream did not merge a patch for that
URE_FLAGS], [$build_configure_args])
+m4_include([m4/reorganization/code_checks/fuzz.m4])
m4_include([m4/reorganization/code_checks/functions.m4])
m4_include([m4/reorganization/code_checks/mpool.m4])
m4_include([m4/reorganization/code_checks/unit_tests.m4])
diff -Nru libclamunrar-0.101.1/debian
On 2019-03-10 23:55:55 [+0100], To sub...@bugs.debian.org wrote:
> We would like to update clamav in stable to 0.101.1 which is the latest
> release provided by upstream.
> This won't be as easy as it was previously because it will trigger a
> transistion (libclamav7 -> libclamav9) in stable simila
On 2019-03-20 15:49:07 [+0100], Christoph Berg wrote:
> PostgreSQL is BSD-licensed, so there is no problem in PostgreSQL
> itself. (We use libedit instead of libreadline in psql to avoid the
> libssl problem.) Also unlike the mariadb case, we have been shipping
> libpq linked against libssl for at
On 2019-03-19 08:39:37 [+0900], Atsuhito Kohda wrote:
> Hi Sebastian,
Hi, Atsuhito
> On Mon, 18 Mar 2019 20:34:04 +0100, Sebastian Andrzej Siewior wrote:
>
> > I suggest to close this bug becuase I don't think it is an openssl bug
> > nor dovecot. The part about minimal
I suggest to close this bug becuase I don't think it is an openssl bug
nor dovecot. The part about minimal key/cipher requirement is already
documented since 1.1.1-2 in NEWS.Debian.gz. The difference between a and
b release is simply that it now the return code is now set properly in
the error case
On 2019-03-15 11:42:37 [+0900], Atsuhito Kohda wrote:
> A bit precise info:
> I upgraded openssl on both server and local macheines.
> Then the problem happened so, first, I downgraded openssl
> on local machine but the problem remained. So I downgraded
> openssl on server machine then fetchmail wo
Package: acme-tiny
Version: 20171115-2
Severity: serious
Hi,
the package is using the ACME-v1 API. Since v4.0.0 (available since Thu
Mar 15 22:03:38 2018 -0700) it is using the ACME-v2 API. One difference
is that the received certificate contains the parent certificate.
The important part and t
On 2019-02-27 20:56:00 [+], Niels Thykier wrote:
> Please go ahead. :)
The transition looks complete.
> Thanks,
> ~Niels
Sebastian
Package: dansguardian
Version: 2.10.1.1-5.1
Severity: important
Tags: patch
Please add support for clamav 0.101.1. The attached patch adds this and
has been lightly tested.
Sebastian
#! /bin/sh /usr/share/dpatch/dpatch-run
## 90_clamav111_support.dpatch by Sebastian A. Siewior
##
## All lines beg
On 2019-03-02 11:54:54 [+0100], Sébastien Villemot wrote:
> Le samedi 02 mars 2019 à 11:26 +0100, Sebastian Andrzej Siewior a écrit :
> >
> > So if the bug is really in libssl1.1 then I don't see why you should do
> > something. I will try to backport that commit then
Sebastian
>From 862167880780c1b1219b6be3864ba587f0bdddba Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior
Date: Sat, 2 Mar 2019 17:08:39 +0100
Subject: [PATCH] tests/test_ssl: use -ciphercuites for TLS1.3 cipher in
openssl1.1
The -cipher can not be used in OpenSSL 1.1.b+ for TLS1.3 cipher sinc
On 2019-03-01 23:55:11 [+0100], Jeroen Ooms wrote:
> On Fri, Mar 1, 2019 at 8:05 PM Sebastian Andrzej Siewior
> wrote:
> >
> > On 2019-03-01 11:16:35 [+0100], Jeroen Ooms wrote:
> > > FWIW, the underlying problem in a regression in libssl though. So if
> > > th
On 2019-02-28 12:17:49 [+0100], Paul Gevers wrote:
> === FAILURES
> _ MiscSSLClientTestCase.test_cipher_ok
>
> self =
…
> tests/test_ssl.py:472:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> /usr/lib/python2.7/dist-
On 2019-03-01 21:30:04 [+0100], gregor herrmann wrote:
> On Fri, 01 Mar 2019 21:18:37 +0100, Sebastian Andrzej Siewior wrote:
>
> > The patch attached fixes the issue in libanyevent-perl by setting the
> > default DH value to 2048.
>
> There's also a new A
+perl, last uploader of libanyevent-perl
On 2019-02-28 22:15:48 [+0100], To Paul Gevers wrote:
> On 2019-02-28 12:40:25 [+0100], Paul Gevers wrote:
> > Source: stunnel4
> > Version: 3:5.50-2
>
> > __DIE__ handler invoked: dh params schmorp1539: failed to set DH
> > parameters at debian/tests/runt
On 2019-03-01 11:16:35 [+0100], Jeroen Ooms wrote:
> FWIW, the underlying problem in a regression in libssl though. So if
> the problem appears for other packages you could also backport this
> libssl patch: https://github.com/openssl/openssl/issues/8375
Does this problem solve your problem or doe
On 2019-02-28 23:24:54 [+0100], Moritz Muehlenhoff wrote:
> Could we force the removal of src:openssl1.0 at this point?
+ROM
> Besides various outdated kfreebsd binaries there are only
> three source packages left:
…
I opened #923194, #923195 to deal with the outdated packages.
> Cheers,
>
Source: cyrus-imapd
Version: 3.0.8-3
Severity: Serious
Control: block 922004 by -1
By the time we planned the transition for libclamav there was no
cyrus-imapd package which depended on libclamav-dev but this changed. I
just realised that.
The package failed to build because the ABI on clamav's s
On 2019-02-28 12:40:25 [+0100], Paul Gevers wrote:
> Source: stunnel4
> Version: 3:5.50-2
> __DIE__ handler invoked: dh params schmorp1539: failed to set DH
> parameters at debian/tests/runtime line 295.
> dh params schmorp1539: failed to set DH parameters at
> debian/tests/runtime line 295.
This
Package: ftp.debian.org
Severity: normal
As part of the of the openssl1.0 removal, I'm asking for the removal of
the following packages:
dak rm -p -R -n -B bitcoin -a kfreebsd-amd64,kfreebsd-i386
|Will remove the following packages from unstable:
|
|bitcoin-tx | 0.12.1-0.1 | kfreebsd-amd64, kfre
Package: ftp.debian.org
Severity: normal
As part of the of the openssl1.0 removal, I'm asking for the removal of
the following packages.
A newer version of those packages was built on other architectures but
not on kfreebsd-* and or hurd-i386. Some of those broken dependencies
are arch ALL (like n
On 2019-02-24 16:25:32 [+0100], Christoph Biedl wrote:
> diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/control
> netkit-ftp-ssl-0.17.34+0.2/debian/control
> --- netkit-ftp-ssl-0.17.34+0.2/debian/control 2017-02-08 18:30:50.0
> +0100
> +++ netkit-ftp-ssl-0.17.34+0.2/debian/control 2019-02-24
On 2019-02-23 12:47:40 [+0100], Christoph Biedl wrote:
> Sebastian Andrzej Siewior wrote...
>
> > Do you still plan to address this or should a RM be filled? The window
> > for Buster has been closed imho.
>
> Yes, and yes :(
>
> Patches are more or less done but I
ation (Closes: #897882).
+ * Get it compiled against OpenSSL 1.1+ (Closes: #859784).
+ * Use priority optional instead of extra.
+
+ -- Sebastian Andrzej Siewior Fri, 22 Feb 2019 23:52:58 +0100
+
validns (0.8+git20160720-3) unstable; urgency=medium
* debian/copyright Add License: stat
On 2019-02-21 23:18:33 [+0100], Moritz Muehlenhoff wrote:
> On Thu, Feb 21, 2019 at 08:56:14PM +0100, Sebastian Andrzej Siewior wrote:
> > Its popcon is dropping. It will not be part of Buster. So either RM it
> > or
>
> I have no use it for, I was just looking at it be
On 2019-02-20 23:09:11 [+0100], Moritz Mühlenhoff wrote:
> On Wed, Feb 20, 2019 at 08:51:16AM +0100, Moritz Muehlenhoff wrote:
> > On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote:
> > > On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
On 2019-02-19 22:32:59 [+0100], Moritz Mühlenhoff wrote:
> Someone should NMU it soon, then. We're down to four remaining packages
> using OpenSSL 1.0 and this will not drag for more than a few weeks, the
> openssl1.0 is already going on for ages.
Someone just did.
> Cheers,
> Moritz
Seb
On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
There has bee
gelog
@@ -1,3 +1,11 @@
+conserver (8.2.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * cherry-pick a handfull patches from upstream for OpenSSL 1.1 compatibility
+(Closes: #851085).
+
+ -- Sebastian Andrzej Siewior Tue, 19 Feb 2019 23:50:54 +0100
+
conserver (8.2.1-1) uns
On 2019-01-27 06:06:08 [+0100], Moritz Muehlenhoff wrote:
> Should zorp be removed? It's incompatible with OpenSSL 1.1 and the bug has
> been unacknowledged since 15 months (859840). It's one of the few remaining
> packages blocking the removal at this point, so this doesn't get ported
> to OpenSSL
On 2019-01-10 23:59:09 [+0100], Christoph Biedl wrote:
> Sebastian Andrzej Siewior wrote...
>
> > On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote:
> >
> > > Or should we rather remove netkit-ftp-ssl? There are TLS-capable ftp
> > > client
> >
+
+ * Non-maintainer upload.
+ * Drop check openssl compile time version vs runtime version
+(Closes: #917485).
+
+ -- Sebastian Andrzej Siewior Thu, 14 Feb 2019 23:35:55 +0100
+
ckermit (302-5.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ckermit-302/debian/pa
On 2019-02-08 12:55:28 [+], Adam D. Barratt wrote:
> Hi,
Hi,
> Apologies for the delay in getting back to you on this.
no worries.
> On 2018-11-25 12:49, Sebastian Andrzej Siewior wrote:
> > Any feedback from the python team is welcome.
>
> Was there any feedback?
On 2019-01-12 13:25:12 [+0100], Andreas Beckmann wrote:
> For #917485:
> A proper fix to the package should drop this misleading line from the error
> message and tighten the dependencies on libssl1.x.y unless the requirement can
> be softened.
a proper dependecy on libssl1.0-dev does the magic.
On 2019-01-31 08:55:36 [+0100], Christian Hilgers wrote:
> Hi Sebastian,
Hi,
> thanks for the patch. I will update havp this weekend.
> I would like to include your name and email. Is that ok?
Sure. Could you please also browse over the patches we have in Debian
which are located at
https://s
Source: dansguardian
Version: 2.10.1.1-5.1
Severity: important
Tags: patch
The patch attached lets python-clamav compile against clamav from
experimental (it does not compile unstable anymore).
Sebastian
From: Sebastian Andrzej Siewior
Date: Wed, 30 Jan 2019 23:53:48 +0100
Subject: [PATCH
Source: python-clamav
Version: 0.4.1-8
Severity: important
Tags: patch
The patch attached lets python-clamav compile against clamav from
experimental (it does not compile unstable anymore).
Sebastian
From: Sebastian Andrzej Siewior
Date: Wed, 30 Jan 2019 23:22:55 +0100
Subject: [PATCH] python
Source: havp
Version: 0.92a-4
Severity: important
tags: patch
havp does not compile against new clamav. The patch attached does solve
the issue.
Sebastian
From: Sebastian Andrzej Siewior
Date: Tue, 29 Jan 2019 23:21:02 +0100
Subject: [PATCH] havp: Update to clamav 0.101
MIME-Version: 1.0
On 2016-02-08 13:42:47 [+0100], Enrico Zini wrote:
> Hello,
Hi,
> I was archiving and xz-compressing mail from last year when my laptop
> tripped thermal protection and switched off. The resulting filesystem
> situation is this:
…
> The source files are gone, and the target files are empty.
>
> I
rt of those changes.
Sebastian
From: Sebastian Andrzej Siewior
Date: Sat, 19 Jan 2019 21:12:25 +0100
Subject: [PATCH] backport clamav changes from 0.5.3
---
configure.ac | 12
services/virus_scan/clamav_mod.c | 62 +++-
2 files ch
Package: ftp.debian.org
Severity: normal
Please remove pion from unstable. Its popcon is low, it has been
recently orphaned (#919210) it is not fit for a release due to a RC bug
and has no reverse dependencies. The old maintainer gave me his
blessing [0] to file this removal.
[0]
https://alioth
On 2019-01-12 15:51:03 [+], Debian Bug Tracking System wrote:
> Paul just told me this should be ok now, so closing.
Okay. We have one additional breaks in git. If anyone needs more, I
don't mind adding them later if it helps…
> Ivo
Sebastian
On 2019-01-10 19:21:33 [+0200], Vincas Dargis wrote:
> On Wed, 9 Jan 2019 23:44:56 +0100 Sebastian Andrzej Siewior
> wrote:
> > > It appears this is somehow related to overlay or tmpfs
>
> Try changing:
>
> ```
> /usr/bin/freshclam {
> ```
>
> In
On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote:
> On Thu, Dec 27, 2018 at 12:57:31PM +0100, Moritz Mühlenhoff wrote:
> > On Sat, Nov 11, 2017 at 12:51:56PM +0100, Sebastian Andrzej Siewior wrote:
> > > On 2017-11-11 12:37:15 [+0100], To Mats Erik Andersson wrote:
>
control: forwarded -1 http://savannah.gnu.org/bugs/?53228
control: tags -1 patch
There is patch at
https://lists.gnu.org/archive/html/bug-patch/2018-02/msg00010.html
This behaviour (crash) is new in 2.7.6, does not happen in 2.7.5. Is it
possible to get this addressed for Buster? It just
On 2019-01-09 08:01:47 [+], Witold Baryluk wrote:
intrigeri, halp :) The good news is that I addressed the other two
apparmor related bugs. Now, I got a new one that reached my capacity:
> Here is dmesg output for the latest run:
>
> [129772.521856] audit: type=1400 audit(1547018290.209:137)
On 2019-01-02 22:50:32 [+0100], To Witold Baryluk wrote:
> "dmesg" should give you the output you look for. Like "apparmor: denied
> $this because of $reason".
Could you please send me the dmesg output for your failure? I have an
up-to-date sid system here with enabled apparmor and I can't reprodu
On 2019-01-08 17:40:04 [+0100], Jérémy Lal wrote:
> Package: openssl
> Version: 1.1.1a-1
> Severity: normal
>
> Hi,
>
> curl https://portal.gexpertise.fr/GexPortal
> returns an error,
>
> however (you need nodejs 10.15~dfsg-8 for this file to be available - the
> file in itself
> is there to be
On 2018-12-29 20:28:23 [+], Witold Baryluk wrote:
> It looks it is by default on Debian, because libgtk or something depends
> on apparmor and then it is automatically enabled. Or some package
> suggests it and my apt by default probably install suggests or something.
that and the fact that app
On 2018-12-11 18:26:24 [-0500], Sam Hartman wrote:
> Fixing moonshot-gss-eap and getting a new moonshot-ui is next up for me
> for Debian weekend tasks.
This means an upload from exp to unstable?
Sebastian
On 2018-12-20 13:12:53 [+0200], Adrian Bunk wrote:
> That's a duplicate of #145257.
I've been tol to file that bug.
> It used to be a lot worse, but has recently been fixed for binary-any
> so only build dependencies for binary-all packages are left affected
> by this bug.
Okay.
> I have an eye
On 2018-12-20 20:07:37 [+0100], To 836...@bugs.debian.org wrote:
> On 2018-12-20 10:48:03 [-0800], Daniel Schepler wrote:
> > On Thu, Dec 20, 2018 at 10:33 AM Sebastian Andrzej Siewior
> > wrote:
> > > If you want then I can sponsor the upload. If you want me to package t
On 2018-12-20 10:48:03 [-0800], Daniel Schepler wrote:
> On Thu, Dec 20, 2018 at 10:33 AM Sebastian Andrzej Siewior
> wrote:
> > If you want then I can sponsor the upload. If you want me to package the
> > latest release and NMU then this might work, too. Someone should do th
On December 20, 2018 4:31:18 PM UTC, Daniel Schepler
wrote:
>On Wed, Dec 19, 2018 at 3:42 PM Sebastian Andrzej Siewior
> wrote:
>> frobtads wasn't part of Stretch and has two RC bugs open with no
>action
>> in over a year.
>> Can it be removed or is somehow imp
Hi,
frobtads wasn't part of Stretch and has two RC bugs open with no action
in over a year.
Can it be removed or is somehow important?
Sebastian
On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote:
> Source: cfengine2
> Severity: serious
>
> This is replaced by src:cfengine2 and stretch has both cfengine2 and
> cfengine3,
> so users can migrate within a stable release to 3.
>
> The current version is also RC-buggy for a long time an
Package: pass-tomb
Version: 1.1-2
Severity: serious
pass-tomb build-depends on kcov which is not in testing. britney migrated
the package to testing regardless. However the package is not fit for a
release because it can not be built in testing as of now [0].
This bug can be closed either once kc
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: britney
Severity: normal
Britney does not look at build dependencies before migrating a package.
Therefore it can migrate a package to testing which build-depends did
not yet migrate. As a result this package can be
On 2018-11-17 11:55:54 [+0100], Emilio Pozuelo Monfort wrote:
> There's also kde4libs #858937.
This got fixed and migrated to testing.
Could we please get rid of libssl1.0.2 in testing? I have a RC bug against it
so it should not reenter.
> Emilio
Sebastian
On 2018-12-15 22:21:52 [+0100], Cyril Brulebois wrote:
> regular bugfixes; we seem to have missed this regression on gen4/gen5,
> so I've started checking whether the upstream fix was being queued for
> linux-4.18.y, and moved to trying to get a work around once I've noticed
that bug is a bummer.
On 2018-12-06 12:42:50 [+0100], gregor herrmann wrote:
> On Wed, 05 Dec 2018 13:57:05 +, Debian Bug Tracking System wrote:
>
> > ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium
> > .
> >* Non-maintainer upload.
> >* Revert below upload and build with OpenSSL 1.1+.
> >* Add
501 - 600 of 1895 matches
Mail list logo
