Source: libengine-gost-openssl1.1
Version: 1.1.0.3-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| [ 3%] Building C object CMakeFiles/gost.dir/gost_ec_keyx.
Source: libdigidoc
Version: 3.10.5-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| [ 76%] Building C object libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o
Source: libcrypt-openssl-pkcs10-perl
Version: 0.16-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
|dh_auto_test
| make -j1 test TEST_VERBOSE=1
| mak
Source: libcrypt-openssl-pkcs12-perl
Version: 1.9-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
|dh_auto_test
| make -j1 test TEST_VERBOSE=1
| make
On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
>
> Feel free to upload; we'll wait for the d-i ack before accepting the
> package into p-u.
Okay. The Bullseye package has been uploaded.
> Regards,
>
> Adam
Sebastian
On 2022-02-24 00:26:51 [-0800], Otto Kekäläinen wrote:
> Hello Sebastian!
Hello Otto,
> I have now MariaDB 10.6 working with OpenSSL 3.0.0. Yihuu!
congratulations.
> However I have problems making the correct debian/control changes. If
> I use just 'libssl-dev' as the dependency then the build w
Source: erlang-p1-tls
Version: 1.1.13-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0. This was once filled
as #996274 and then closed "tried to reproduce this bug the package
built and
Source: dpdk
Version: 20.11.4-2
Severity: important
Tags: bookworm sid ftbfs
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build while trying to figure out if it buils
with OpenSSL 3.0. It also fails with current OpeSSL (in unstable) with
same error
Source: dnsdist
Version: 1.7.0-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| g++ -std=c++17 -DHAVE_CONFIG_H -I. -I. -I. -pthread
-I/usr/include/luajit-
Source: capnproto
Version: 0.8.0-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| kj/compat/tls.c++:334: unimplemented bio_ctrl; cmd = 73
| kj/compat/tls-test
Source: caml-crush
Version: 1.0.12-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| checking OCaml package nettls-gnutls... found
| configure: Using native C
Source: nodejs
Version: 12.22.9~dfsg-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| ../src/node_crypto.cc: In function ‘unsigned int
node::crypto::GetByt
Source: libwebsockets
Version: 4.0.20-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| [ 31%] Building C object
CMakeFiles/websockets.dir/lib/tls/openssl/ope
Source: librabbitmq
Version: 0.10.0-1
Severity: important
Tags: bookworm sid fixed-upstream
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| [ 32%] Linking C executable amqp_sendstring
| cd /<>/obj-x
Source: i2pd
Version: 2.39.0-1
Severity: important
Tags: bookworm sid patch fixed-upstream
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1
https://github.com/PurpleI2P/i2pd/commit/921ec9ec12ead861994c98d96087b93a31051ef5
Your package is failing to build u
Source: yubico-piv-tool
Version: 2.2.0-1
Severity: important
Tags: bookworm sid patch fixed-upstream
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://github.com/Yubico/yubico-piv-tool/pull/334
Your package is failing to build using OpenSSL 3.0 with
On 2022-02-19 17:04:16 [+], Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
…
> Thanks. Assuming the above is still accurate, then this looks good to
> me.
>
> As the package builds a udeb, it will need a d-i ack; tagging and CCing
> accordingly.
I'm confused. May I upload or do I w
Source: python-cryptography
Version: 3.4.8-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://github.com/pyca/cryptography/pull/6000
Your package is failing to build using OpenSSL 3.0 with the
following error:
Source: haproxy
Version: 2.4.12-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| src/ssl_sock.c: In function ‘ctx_set_TLSv13_func’:
| src/ssl_sock.c:2273:
On 2022-02-18 08:31:11 [-0800], Otto Kekäläinen wrote:
> Seems upstream added OpenSSL 3.0 support in
> https://jira.mariadb.org/browse/MDEV-25785. It has 4 git commits
> linked, from which I learned that:
>
> * OpenSSL 3.0 is disabled on all old MariaDB majors
> (https://github.com/MariaDB/server/
Source: mariadb-10.6
Version: 1:10.6.5-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| Installing system database...
| mysql-test-run: *** ERROR: Error execu
On 2022-02-01 21:11:11 [+0100], Sebastian Ramacher wrote:
> > Could you please update this transition request? It's open for four
> > months and no visible response.
>
> Kurt mention some 100 packages failing to build. I only see a handfull
> of bugs filed. So what's the status on those build fai
Source: mysql-8.0
Version: 8.0.23-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1
Your package is failing to build using OpenSSL 3.0 with the
following error:
| -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (fo
Source: mumble
Version: 1.3.4-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| g++ -c -include release/mumble -pipe -g -O2
-ffile-prefix-map=/<>/src/mumble=.
Source: mosh
Version: 1.3.2-2.1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| c++ -DHAVE_CONFIG_H -I. -I../.. -I./../util -Wdate-time -D_FORTIFY_SOURCE=2
Source: nzbget
Version: 21.0+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0 with the
following error:
| daemon/connect/TlsSocket.cpp: In static member function ‘static void
Tls
Source: ntpsec
Version: 1.2.1+dfsg1-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
| Your package is failing to build using OpenSSL 3.0 with the
| following error:
|
| ../../attic/cmac-timing.c: In function ‘One_EVP_MAC’:
| ../../attic
Source: lua-luaossl
Version: 20161214-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://github.com/wahern/luaossl/issues/195
Your package is failing to build using OpenSSL 3.0 with the
following error:
| In f
Source: squid
Version: 5.2-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://bugs.squid-cache.org/show_bug.cgi?id=5133
Your package is failing to build using OpenSSL 3.0 with the
following error:
| ../../src/
Source: ldns
Version: 1.7.1-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://github.com/NLnetLabs/ldns/issues/135
Your package is failing to build using OpenSSL 3.0 with the
following error:
|./dnssec_sign.c
Source: ruby2.7
Version: 2.7.5-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 https://github.com/ruby/openssl/issues/369
Your package is failing to build using OpenSSL 3.0 with the
following error:
| make -f exts.m
Package: firmware-nonfree
Version: 20210818-1
Severity: normal
Hi,
The orig contains already the AMD SEV firmware in the amd folder:
| $ ls -lh amd
| 33K Aug 18 13:08 amd_sev_fam17h_model0xh.sbin
| 43K Aug 18 13:08 amd_sev_fam17h_model3xh.sbin
Could this be please package? I have an AMD box aski
On 2022-01-25 22:10:00 [-0500], Anders Kaseorg wrote:
> Control: fixed 989604 1.1.1i-1
> Control: tags 989604 + buster patch
Thanks.
> The fix is trivial, swapping two lines of assembly. I’ve attached it as a
> debdiff, and tested it in a Debian 10 container on an M1 MacBook. Can it
> be cons
On 2022-01-25 18:46:16 [+], Adam D. Barratt wrote:
> For the record, .5 was released via {buster,bullseye}-updates last
> night; see SUA211-1 /
> https://lists.debian.org/debian-stable-announce/2022/01/msg1.html
Thank you.
> Regards,
>
> Adam
Sebastian
g/configure.ac
--- clamav-0.103.4+dfsg/configure.ac 2021-11-13 21:57:13.0 +0100
+++ clamav-0.103.5+dfsg/configure.ac 2022-01-12 20:53:22.0 +0100
@@ -1,4 +1,4 @@
-dnl Copyright (C) 2013-2021 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
+dnl Copyright (C) 2013-20
On 2022-01-11 21:17:54 [+], Adam D. Barratt wrote:
> Now that the equivalent update made it to stretch, this seems as good a
> time as any - I'm assuming that no major issues have ben reported in
> unstable in the meantime?
correct.
> I wasn't really sure which of the changes made sense to me
On 2021-12-25 12:27:33 [+0100], Michael Below wrote:
> Hi,
Hi,
> I have tested the patch, with help from Salvatore, and the dmesg output
> looks better, but the touchpad still does not work. I am attaching the
> dmesg output.
based on
> [1.575843] idma64 idma64.0: Found Intel integrated DMA
control: tags -1 patch
On 2021-12-23 21:30:28 [+0100], Michael Below wrote:
> [ 20.096966] CPU: 2 PID: 223 Comm: irq/16-i801_smb Not tainted
> 5.15.0-2-rt-amd64 #1 Debian 5.15.5-1
The hunk at the bottom should cure it.
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.
On 2021-12-23 15:38:16 [+], Adam D. Barratt wrote:
> Hi,
Hi Adam,
> fwiw, even with the reduced diffs, neither request made it to debian-
> release.
Oh shoot. You're the best Adam. I meant to ping the list in case it
didn't make through but forgot to check…
> Were you anticipating that 0.103
Package: sup-mail
Version: 1.0-5
Severity: important
Hi,
The package needs a dependency on ruby-xapian:
|$ sup-config
|Traceback (most recent call last):
|8: from /usr/bin/sup-config:6:in `'
|7: from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
|
On 2021-10-16 12:17:40 [+0200], Matthias Klose wrote:
> The change is intended; the configure changes are already in GCC 8, but the
> configure options that we used, are now being deprecated upstream.
>
> Changes: https://gcc.gnu.org/gcc-8/changes.html
I guess you refer to
| The -march and -mcpu
Package: gcc-11
Version: 11.2.0-9
Severity: important
The linux kernel has the following in its ARM Makefile:
$(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
This means the switch "-march=armv7-a" is tested if supported by the
compiler and if so it is used, otherw
On 2021-10-05 20:03:49 [+0200], Michael Biebl wrote:
> Hi Kurt, hi Luca, hi everyone,
Hi Michael,
> That said, I'm not a lawyer and reading license texts hurts my brain.
> So my goal is is mainly to raise awareness of this issue and seek input from
> the community.
GPL code which linked against O
On 2021-09-10 11:49:39 [+0100], Adam D. Barratt wrote:
> It appears that the bullseye upload is stuck on the upload queue,
> because:
Thank you.
> Regards,
>
> Adam
Sebastian
; >>confdefs.h
-VERSION="0.103.2"
+VERSION="0.103.3"
major=`echo $PACKAGE_VERSION |cut -d. -f1 | sed -e "s/^0-9//g"`
minor=`echo $PACKAGE_VERSION |cut -d. -f2 | sed -e "s/^0-9//g"`
@@ -31896,7 +31896,7 @@
# report actual input values of CONFIG_
ERSION="0.103.3"
major=`echo $PACKAGE_VERSION |cut -d. -f1 | sed -e "s/^0-9//g"`
minor=`echo $PACKAGE_VERSION |cut -d. -f2 | sed -e "s/^0-9//g"`
@@ -31896,7 +31896,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options hand
control: tags -1 + patch
control: fixed -1 1:2.3.10.1+dfsg1-1
On 2021-01-19 11:25:06 [+0100], Uwe Jans wrote:
> I think maybe a backport from this Patch may help integrated in buster:
>
> https://github.com/dovecot/pigeonhole/commit/400566cc4a6f938ed1dfe513c38f1bd681717ebe?branch=400566cc4a6f938e
control: found -1 1.1.1g-1
control: tags -1 + pending
On 2021-08-30 19:30:07 [+0200], To Alexey Brodkin wrote:
> On 2021-08-30 16:37:11 [+], Alexey Brodkin wrote:
> > On Thu, 3 Jun 2021 19:14:24 + Vineet Gupta
> > wrote:
> > > This is needed to bootstrap arc port.
> > > Patch attached.
On 2021-08-30 16:37:11 [+], Alexey Brodkin wrote:
> On Thu, 3 Jun 2021 19:14:24 + Vineet Gupta
> wrote:
> > This is needed to bootstrap arc port.
> > Patch attached.
>
> Ping!
Urgh. Sorry, thanks for the ping.
> -Alexey
Sebastian
On 2019-09-19 12:04:41 [+0200], Dominik wrote:
> with the update to 0.101.4+dfsg-0+deb10u1 clamd frequently reports:
> LibClamAV Error: pdf_find_and_extract_objs: Timeout reached in the PDF parser
> while extracting objects.
>
> This has not occured before the update - thus it is surprising.
>
>
On 2021-05-23 08:32:23 [+0800], Paul Wise wrote:
> Whenever freshclam gets restarted, either manually or automatically
> during package upgrades, I get an apparmor denial in the logs. I
> haven't seen any adverse effects from this denial. Reading the
> capabilities(7) manual page where CAP_DAC_READ
On 2020-11-21 18:06:30 [+0100], Stephen Kitt wrote:
> I noticed that clamd now uses large amounts of memory:
>
> clamav1006 1.9 3.6 1405692 1186776 ? Ssl 17:53 0:12
> /usr/sbin/clamd --foreground=true
1.1g RES here.
> I don’t remember it doing so until the last few weeks. Restartin
forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=12607
On 2020-11-02 11:38:10 [+0100], Stephan Jänecke wrote:
> Good question. I filed a report two months ago[1], which hasn't been
> touched to this date. Its visibility is currently limited to the
> security group, so you might have issues
forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=12782
Sebastian
On 2020-05-30 19:53:49 [+], Patrick Schleizer wrote:
> package clamav-daemon ships a file /usr/bin/clamonacc which is a
> background virus scaning guard / real-time protection. It's currently
> non-trivial to use.
>
> sudo clamonacc
>
> ERROR: Clamonacc: at least one of OnAccessExcludeUID,
>
On 2021-03-06 11:44:35 [+0100], Thomas Andrejak wrote:
> Hello Sebastian,
Hi,
> The new libprelude is in debian testing as you can see here :
> https://tracker.debian.org/pkg/libprelude
>
> Is it possible to re-work on this issue ?
So yes I am still alive but somehow didn't deal with this, sorry
On 2019-10-07 08:41:51 [+0200], Hugo Lefeuvre wrote:
> Hi Sebastian,
Hi Hugo,
> I have discovered this during my regression tests for the jessie update. My
> main worry was to have broken something, I'm glad it's not the case.
> Thanks for your time!
What do we do here?
> regards,
> Hugo
Sebast
On 2021-06-23 14:46:37 [+0200], Andreas Beckmann wrote:
> Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
> -
> Warning: No -copy_extensions given; ignoring any extensions in the request
> Cannot write random bytes:
> 8022CB35777F:error:127A:random number g
On 2021-04-23 08:21:44 [+0100], Adam D. Barratt wrote:
> Ah, apologies for not spotting that from your earlier mail. An updated
> draft:
This is perfect Adam, thank you.
>
> Regards,
>
> Adam
>
Sebastian
On 2021-04-22 16:58:46 [+0100], Adam D. Barratt wrote:
> On Wed, 2021-04-21 at 21:35 +0200, Sebastian Andrzej Siewior wrote:
> > On 2021-04-20 20:52:09 [+0100], Adam D. Barratt wrote:
> > > Please feel free to upload. I assume that, given there are security
> > > fixe
On 2021-04-20 20:52:09 [+0100], Adam D. Barratt wrote:
>
> I'm certainly happy to defer to your judgement here, given our previous
> experience with clamav updates in stable. I was simply trying to
> ascertain the scale of the update involved, but fear I may have just
> confused the discussion; pe
On 2021-04-21 08:17:53 [+0100], Athanasius wrote:
> So long as any Debian update of the packages both addresses the
> outstanding CVEs *and* quiets this logging I'll be happy.
Be aware that I am following the process to get an update into Buster.
Sebastian
On 2021-04-19 21:15:06 [+0100], Adam D. Barratt wrote:
> > > I guess the diff against the current buster package is quite large
> > > by
> > > this point?
> >
> > What do you mean by this point? We did full clamav uploads in the
> > past.
> > Please excuse if I miss something obvious.
>
> Sorry,
On 2021-04-19 19:41:58 [+0100], Adam D. Barratt wrote:
> On Fri, 2021-04-16 at 09:27 +0200, Sebastian Andrzej Siewior wrote:
> > This is an update from ClamAV from 0.102.4 to 0.103.2. The 103
> > release was in unstable since the beginning. I skipped it for Buster
> > back
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster
Severity: normal
This is an update from ClamAV from 0.102.4 to 0.103.2. The 103 release
was in unstable since the beginning. I skipped it for Buster back then
because the 102 based release recevied a
On 2021-04-13 16:08:17 [+0530], Utkarsh Gupta wrote:
> Hi Sebastian,
Hi,
> Sebastian Andrzej Siewior wrote:
> > My plan is to get 103.2 into Buster after I spent the day today
> > to look what should be backported and what not.
>
> Do we not generally backport clamav as
On 2021-04-10 15:10:36 [+0200], Matus UHLAR - fantomas wrote:
> Hello,
Hi,
> I just wanted to note that clamav 0.103.2 fixes[1] all issues currently open
> at security tracker[2]
>
> CVE-2021-1252
> CVE-2021-1404
> CVE-2021-1405
Everyone wondering, yes I am aware but not as fast as I would like
G_X509_STRICT)) {
ctx->error = X509_V_ERR_INVALID_EXTENSION;
diff --git a/debian/changelog b/debian/changelog
index 45bfdb99fe8d9..9d1b9d6590ab9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,16 @@
-openssl (1.1.1j-0+deb10u1) buster; urgency=medium
+openssl (1.1.1k-0
On 2020-07-21 16:53:23 [+0200], Santiago Ruano Rincón wrote:
> diff -Nru bzip2-1.0.6/debian/rules bzip2-1.0.6/debian/rules
> --- bzip2-1.0.6/debian/rules 2019-06-24 22:16:40.0 +0200
> +++ bzip2-1.0.6/debian/rules 2020-07-21 10:31:21.0 +0200
> @@ -14,6 +14,9 @@
> DEB_BUILD_MAINT_O
Resending because I managed to accidently clear TO:
On 2021-03-22 19:48:31 [+0100], Cc 959...@bugs.debian.org wrote:
> On 2021-02-24 23:23:07 [+0100], To Kurt Roeckx wrote:
> > On 2021-02-10 21:52:46 [+0100], To Kurt Roeckx wrote:
> > > OpenSSL upstream announced [0] 1.1.1j for next Tuesday with a
On 2021-02-24 23:23:07 [+0100], To Kurt Roeckx wrote:
> On 2021-02-10 21:52:46 [+0100], To Kurt Roeckx wrote:
> > OpenSSL upstream announced [0] 1.1.1j for next Tuesday with a security
> > fix classified as MODERATE [1].
So this happened. OpenSSL upstream announced [0] 1.1.1k for next
Thursday (25
/debian/changelog 2021-03-20 09:37:26.0 +0100
@@ -1,3 +1,15 @@
+clamtk (6.03-3) unstable; urgency=medium
+
+ * Upload to unstable.
+
+ -- Sebastian Andrzej Siewior Sat, 20 Mar 2021 09:37:26 +0100
+
+clamtk (6.03-2) experimental; urgency=medium
+
+ * Remove no-separator from window de
On 2021-03-13 17:31:50 [+], Adam D. Barratt wrote:
> Please go ahead.
Thanks, uploaded.
> Regards,
>
> Adam
Sebastian
On 2021-03-08 18:54:22 [+0100], Paul Gevers wrote:
> Hi,
Hi,
> Please upload to unstable. As said, we'll let it age a bit there.
Thanks, uploaded.
> Paul
Sebastian
On 2021-03-04 16:24:11 [+], Dean P wrote:
> Hello all.
> Would It be possible for someone from the Clam team to address this fixed bug
> with an upload of the latest version.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981384
I will try to look at this around the weekend if nothing e
fix to xzgrep (similar to xzcmp in #844770).
+
+ -- Sebastian Andrzej Siewior Tue, 02 Mar 2021 21:50:25 +0100
+
xz-utils (5.2.5-1.0) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru xz-utils-5.2.5/debian/patches/0001-Scripts-Fix-exit-status-of-xzdiff-xzcmp.patch xz-utils-5.2.5/debia
On 2021-03-02 19:44:58 [+0100], Paul Gevers wrote:
> Hi Sebastian,
Hi Paul,
> Unfortunately we haven't made up our mind yet, but to get some (albeit
> limited) exposure and autopkgtest coverage (via the pseudo-excuses) [2],
> I think your chances for a go are higher if the proposed package is
> av
Andrzej Siewior Tue, 23 Feb 2021
23:41:19 +0100
+
m2crypto (0.31.0-4+deb10u1) buster; urgency=medium
* Non-maintainer upload.
diff -Nru m2crypto-0.31.0/debian/patches/MR262.patch
m2crypto-0.31.0/debian/patches/MR262.patch
--- m2crypto-0.31.0/debian/patches/MR262.patch 1970-01-01 01:00
On 2021-02-21 16:07:37 [+0100], Sebastian Ramacher wrote:
> Control: tags 980592 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for clamav (versioned as 0.103.0+dfsg-3.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
I clearly missed that par
0 +0100
+++ xz-utils-5.2.5/debian/changelog 2021-02-18 23:12:30.0 +0100
@@ -1,3 +1,10 @@
+xz-utils (5.2.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update the patches for #844770 and #975981 to what upstream applied.
+
+ -- Sebastian Andrzej Siewior Thu, 18 Feb 20
23:12:30.0 +0100
@@ -1,3 +1,10 @@
+xz-utils (5.2.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update the patches for #844770 and #975981 to what upstream applied.
+
+ -- Sebastian Andrzej Siewior Thu, 18 Feb 2021 23:12:30 +0100
+
xz-utils (5.2.5-1.0) unstable; urgency=m
On 2021-02-18 08:15:15 [+0100], Paul Gevers wrote:
>
> I copied some of the output at the bottom of this report. I *think*
> this may be related to CVE-2020-25657 "bleichenbacher timing attacks in
> the RSA decryption API" against m2crypto, hence I file this bug against
> m2crypto.
The openssl s
On 2021-02-01 23:50:03 [+0100], To Kurt Roeckx wrote:
> in case someone wants to test.
> I think the ship for this pu is sailing without me but I'm ready for the
> next cruise :)
OpenSSL upstream announced [0] 1.1.1j for next Tuesday with a security
fix classified as MODERATE [1].
[0] https://mta
enssl (1.1.1i-0+deb10u1) buster; urgency=medium
(Closes: #947949).
* Update symbol list.
* Apply two patches from upstream to address x509 related regressions.
+ * Cherry-pick a patch from upstream to address #13931.
- -- Sebastian Andrzej Siewior Sun, 24 Jan 2021 11:22:16 +0100
+ --
Package: sogo
Version: 5.0.1-3
Severity: wishlist
Please link against OpenSSL. OpenSSL is considered as a system library
so there should no license restriction, see #924937.
I rebuild it localy (and src:sope) since I run into connections problems
with imap / web gui. Upstream appears to use OpenS
Package: neomutt
Version: 20201127+dfsg.1-1
Severity: wishlist
Please link against OpenSSL. OpenSSL is considered as a system library
so there should no license restriction, see #924937.
I started to rebuild against OpenSSL almost a year a ago and I didn't
any downside. It connects quicker but I d
control: found -1 0.31.0-1
On 2021-01-24 23:08:27 [+0200], Adrian Bunk wrote:
>
> The release team considers these bugs release critical.
it would be easier to enforce to have all buildds configured equally so
the package does not fail on a random buildd.
> > and let it migrate to
> > testing.
On 2021-01-28 00:28:03 [+0100], Kurt Roeckx wrote:
> On Thu, Jan 14, 2021 at 07:03:37PM +0100, Kurt Roeckx wrote:
> > There are a whole bunch of other issues and pull requests related to
> > this. I hope this is the end of the regressions in the X509 code.
>
> So there is something else now:
> htt
On 2021-01-25 22:59:08 [+0100], Stephen Kitt wrote:
> Control: severity -1 normal
>
> Hi Sebastian,
Hi,
> That was no doubt the intention, however in practice the symbol
> visibility wasn’t as expected: looking at the .so build in version
> 1.3.8, common/pool.c includes common/zstd_internal.h whi
On 2021-01-25 19:57:18 [+0100], Cyril Brulebois wrote:
> Not really *much* easier, to be honest. I can definitely build a package
> locally given a source debdiff, or slightly better, given a source
> package I can run dget against (since we're talking about new upstream
> releases, by the looks of
On 2021-01-25 17:51:28 [+], Adam D. Barratt wrote:
> Please go ahead; thanks.
Uploaded. Thank you.
> Regards,
>
> Adam
Sebastian
On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote:
> Source: m2crypto
> Version: 0.37.1-1
> Severity: serious
> Tags: ftbfs
I suggest to lower the severity to important and let it migrate to
testing. After all this bug did not first appear in 0.37.1-1, it has
been exposed after it hit buildd that
On 2021-01-22 16:38:28 [+], Adam D. Barratt wrote:
> Assuming that a patched m2crypto will also build fine against openssl
> 1.1.1d, then there's no reason that the two shouldn't proceed in
> parallel (i.e. feel free to file the m2crypto request already).
Yes, it does. Bug filled. Thank you.
/changelog 2021-01-24 12:01:15.0 +0100
@@ -1,3 +1,11 @@
+m2crypto (0.31.0-4+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/MR261.patch
+- fix compatibility with openssl/1.1.1i+; Closes: #954402
+
+ -- Sebastian Andrzej Siewior Sun, 24 Jan 2021 12:01:15
4,9 @@ openssl (1.1.1i-0+deb10u1) buster; urgency=medium
- CVE-2019-1551 (Overflow in the x64_64 Montgomery squaring procedure),
(Closes: #947949).
* Update symbol list.
+ * Apply two patches from upstream to address x509 related regressions.
- -- Sebastian Andrzej Siewior Wed, 06 Jan 2
On 2021-01-16 19:14:53 [+0100], Kurt Roeckx wrote:
> So I went over the open issues and pull requests, and currently
> don't see a reason not to upload it to unstable with those 2
> patches. I don't know about any other regressions in 1.1.1.
The openssl package migrated to testing.
I would prepare
On 2021-01-20 11:50:05 [+0100], Julien Cristau wrote:
> > Can this be reassigned to openssl in the meantime? I think it's a goal to
> > have
> > all of Debian built with largefile support, anyways.
>
> Yes.
meh. Is this stable or sid?
> Cheers,
> Julien
Sebastian
On 2021-01-14 19:03:37 [+0100], Kurt Roeckx wrote:
> > Do you have pointers to upstream issues?
>
> There are a whole bunch of other issues and pull requests related to
> this. I hope this is the end of the regressions in the X509 code.
Okay. Please ping once this gets sorted out and I will prepe
Package: src:gnat-gps
Version: 19.2-3
Severity: serious
Tags: sid ftbfs
Hi,
some BD of gnat-gps depend on packages which were built by gnat-9 others
moved to gnat-10. libgnatcoll-db and libgnatcoll-bindings changed their
binary packages and the old ones are by built by gnat-9, the new ones
are bu
On 2020-11-27 18:22:01 [+0100], Vincent Lefevre wrote:
>
> "unxz -k" refuses to decompress a file because it has more than one
> hard link. This is silly!
It may be silly but it is consistent with gzip's & bzip2's behaviour.
`gzip' has this since the 90s. It is now restricted to less than 3
symli
301 - 400 of 1895 matches
Mail list logo
