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
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 version pro
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
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
ganization/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/debian/changelog
--- libclamunrar-0.101.1/debian/changelog 2019-02-28 23:57:23.0
+0100
+++ libclamunrar-0.101.2/debian/cha
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
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 k
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
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
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
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
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 and
tian
>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 since
ope
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:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
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 An
+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
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
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
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.
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,
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
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
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 do
(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: statement
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 a
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...@bug
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
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
@@ -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) unstable
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
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
> >
n-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/patches/
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
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.
>
>
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 changed
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]
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
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
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
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
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
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 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 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 importan
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
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
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
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+.
> >*
control: tags -1 pending
control: found -1 1.1.1-1
control: notfound -1 0.6.4-1
On 2018-12-04 21:50:20 [+0100], Olaf van der Spek wrote:
> lighttpd (1.4.49-2) unstable; urgency=medium
>* Add a patch to work against openssl 1.1.1. (Closes: #913251)
Added
Breaks: lighttpd (<<
On 2018-12-05 11:09:25 [+0100], Manuel Montecelo wrote:
> the subcommand genrsa changed interface from its previous version, and does
> not
> accept -config or -batch options anymore:
…
> I worked around the issue in other ways, and I know that "genpkey" is supposed
> to supercede "genrsa", but
On 2018-12-03 12:30:53 [+0100], Didier 'OdyX' Raboud wrote:
> > If you switch to openssl-dev with this upload, please make it depend on
> > libssl1.1 (which does not happen because it does not depend on any symbols)
> > and the you could also close
> >
> > #913959 [S| | ] [src:kde4libs]
On 2018-12-02 13:06:04 [+], Debian Bug Tracking System wrote:
> #900160: ruby-eventmachine: FTBFS against openssl 1.1.1
> ruby-eventmachine (1.0.7-4.1) unstable; urgency=medium
> .
>* Non-maintainer upload.
>* Build-Depend against libssl1.0-dev; aka OpenSSL << 1.1
> (Closes:
On December 1, 2018 2:02:42 PM UTC, Didier 'OdyX' Raboud
wrote:
>So; to get the ball rolling on this RC bug:
>
>* I've prepared a Debian patch with it
If you switch to openssl-dev with this upload, please make it depend on
libssl1.1 (which does not happen because it does not depend on any
On 2018-11-28 13:43:07 [+0100], Olaf van der Spek wrote:
> > > They might just as well install haveged or configure virtio-rng in such
> > > a case.
> >
> > Right. Do you think, that it would necessary to add something to the
> > release notes?
>
> I do. ;)
> What's the workaround for VMware?
>
On 2018-11-28 21:25:45 [+0100], Petter Reinholdtsen wrote:
> The upgrade from openssl version 1.1.0h-4 to 1.1.1-1 break pagekite on
> the FreedomBox. After a debug session with the pagekite author I
> discovered the reason is changes in /etc/ssl/openssl.cfg, which now
> block connection to the
Version: 1.1.1-1
On 2001-03-06 12:06:26 [+0100], Robert Bihlmeyer wrote:
> For libssl, /dev/urandom is probably the right default, as it can be
> used in circumstances with a time-security-tradeoff (e.g. webserver).
>
> OTOH, "openssl" has no time constraints, and needs maximum security -
>
On 2018-11-27 09:57:58 [+0100], Michael Biebl wrote:
> Sigh, and there is nothing that systemd can do to fix this, so I don't
> see a point re-assigning this to systemd (again).
I was about to close it myself then I though maybe reassign in case you
want close it if that PR gets merged it.
>
control: reassign -1 postfix 3.2.2-1
On 2018-01-29 12:47:11 [-0500], Scott Kitterman wrote:
> On Monday, January 29, 2018 05:53:47 PM Kurt Roeckx wrote:
> > I'm not sure why you've reassign it. I think that postfix really
> > should do that, just like it enables anonymous ciphers.
> >
> >
control: reassign -1 systemd 239-13
I hereby reassign the bug to systemd.
The problem is that OpenSSL is now using getrandom() for entropy which
is not (yet) ready and therefore OpenSSH needs longer for startup by
simply waiting for entropy.
Theodore Y. Ts'o suggested adding hw-rng to KVM/virt
On 2018-11-04 22:15:04 [+0100], Kurt Roeckx wrote:
> > You're implying openvpn doesn't pick up the openssl.cnf changes so I
> > have to set tls-version-min 1.0 in the server side configuration? OK,
> > that works too.
>
> Your client doesn't support the settings in the openssl.cfg file. Your
>
On 2018-11-04 15:10:42 [+0100], Julien Lecomte wrote:
> I'll move the issue directly to ubiquiti to figure out what is going wrong.
should we just close on the Debian side or did you gather additional
information?
> Thanks
> Julien
Sebastian
On 2018-11-25 13:49:15 [+0100], To sub...@bugs.debian.org wrote:
diff -Nru python-cryptography-1.7.1/debian/changelog
python-cryptography-1.7.1/debian/changelog
--- python-cryptography-1.7.1/debian/changelog 2017-05-28 04:20:33.0
+0200
+++ python-cryptography-1.7.1/debian/changelog
. It has no
+users.
+
+ -- Sebastian Andrzej Siewior Sun, 02 Sep 2018 15:17:35 +0200
+
python-cryptography (1.7.1-3) unstable; urgency=medium
* Apply patch 6e7ea2e7 from upstream to fix compilation against OpenSSL
diff -Nru python-cryptography-1.7.1/debian/patches/Remove
On 2018-11-19 21:01:07 [+0100], To Adam Lambert wrote:
> On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote:
> > I believe I already supplied all that way back when I opened up this bug
> > report. But for reference, here it is again:
>
> I tried it back then with no luck. Thanks for the info.
On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote:
> I believe I already supplied all that way back when I opened up this bug
> report. But for reference, here it is again:
I tried it back then with no luck. Thanks for the info. I will try to
reproduce this asap and get back to you.
Sebastian
Package: openssl1.0
Version: 1.0.2o-1
Severity: serious
The package libssl1.0-dev should be removed from Buster and not be part
of the release. It has no dependecies in Buster anymore, everything
migrated over to libssl-dev.
Sebastian
Control: blocks -1 by 913251
On November 12, 2018 10:17:09 AM UTC, Olaf van der Spek wrote:
>I think libssl1.1 breaks Lighttpd, Ondřej Surý requested I report this.
>Does libssl1.1 need a versioned breaks on lighttpd?
Yes, looks that way. According to the bug you listed there is not a fixed
On 2018-11-08 15:15:57 [-0800], Adam Lambert wrote:
> What do you need me to do to provide debug info on this?
I would like to reproduce this. I would need the clamd.conf, kernel
command line if something non-standard and what it is you do.
If I can reproduce this on my Stretch VM then I try to
On 2018-11-03 17:11:07 [+], Scott Kitterman wrote:
> Does anyone still have this problem with 0.100.2? It's been out awhile and
> this bug has gone quiet.
I would suggest to close it. I never had any luck to reproduce it. It
may or may not be a problem but without any additional help to get
intrigeri, I added you on Cc since you were a help the last time
apparmor came around.
On 2018-11-06 10:45:15 [+0800], Paul Wise wrote:
> Package: clamav-daemon
> Version: 0.100.2+dfsg-1
> Severity: normal
> File: /etc/apparmor.d/usr.sbin.clamd
> Usertags: apparmor
>
> When I restart
On 2018-11-06 08:41:47 [+0700], Dmitriy wrote:
>
> Yes. I compiled deb package from source and add to Clamav daemon. After this
> it works.
> I think in man page for clam antivirus must be menchioned that some non GNU
> code are absent (like RAR code)
> This is be very heplfull for users to
On 2018-02-25 10:59:57 [+0100], Emilio Pozuelo Monfort wrote:
> We're getting close. According to the transition tracker, the remaining rdeps
> in
> testing are:
…
> kopete - no fix upstream, optional for jingle (call) support in XMPP
…
This is the last one in testing. kopete's #858938 has been
On 2018-11-03 18:12:07 [+0100], Christoph Biedl wrote:
> Subject: Build against openssl 1.1.
> Author: Chris West
> Bug: https://github.com/tobez/validns/pull/64
> Bug-Debian: https://bugs.debian.org/859784
> Last-Update: 2018-11-03
>
> --- a/dnskey.c
> +++ b/dnskey.c
> @@ -154,6 +154,7 @@
>
On 2018-05-26 23:35:46 [+0200], To sub...@bugs.debian.org wrote:
> The Error in the testsuite could be due to:
> 1.1.1~~pre6-1 changelog):
> | * Increase default security level from 1 to 2. This moves from the 80 bit
> | security level to the 112 bit securit level and will require 2048 bit
On 2018-11-04 11:39:59 [-0800], James Bottomley wrote:
> > > OK, so I'm weary of trying to construct a theory of what the bug
> > > actually is, why don't you try to come up with one. The symptoms
> > > are
> > > that openvpn in openwrt works with server 1.1.0 and fails with
> > > server
> > >
On 2018-11-04 15:10:42 [+0100], Julien Lecomte wrote:
> Hello
Hi,
> Thanks to your remark I tried connecting my computer directly to the set-top
> box.
>
> Connected directly, the file downloads fine (verified via md5sum).
> Connected indirectly, the download shows the issues I encountered.
>
>
).
+
+ -- Sebastian Andrzej Siewior Sun, 04 Nov 2018 12:37:23 +0100
+
python-boto (2.44.0-1) unstable; urgency=medium
* New upstream release.
only in patch2:
unchanged:
--- python-boto-2.44.0.orig/boto/connection.py
+++ python-boto-2.44.0/boto/connection.py
@@ -821,23 +821,24 @@
h
On 2018-11-01 19:50:35 [-0400], Theodore Y. Ts'o wrote:
> On Thu, Nov 01, 2018 at 11:18:14PM +0100, Sebastian Andrzej Siewior wrote:
> > Okay. So you wrote what can be done for a system with HW-RNG/kvm. On
> > bare metal with nothing fancy I have:
> > [3.544985] systemd[1]
On 2018-11-02 08:11:49 [+0700], Dmitriy wrote:
> I've some problems with scanning RAR archives in emails. Clamav daemon in
> debug mode don't show any info about
do you have libclamunrar7 installed?
Sebastian
On 2018-10-31 18:41:06 [-0400], Theodore Y. Ts'o wrote:
> On Wed, Oct 31, 2018 at 11:21:59AM +0000, Sebastian Andrzej Siewior wrote:
> > On October 30, 2018 8:51:36 PM UTC, "Theodore Y. Ts'o"
> > wrote:
> > >
> > >So it's complicated. It's not a
501 - 600 of 1863 matches
Mail list logo
