5d00
-clamav_0.103.6+dfsg.orig.tar.xz
-6212705bf2cb168a55f76ae4cab31fa40909aed8
-7135300
+f2466c7aaf6e140ea150e0f219c86594f3bc04cb
+f2466c7aaf6e140ea150e0f219c86594f3bc04cb
+d1ea680af611ee417616ec3d8615a0e67a495795
+d1ea680af611ee417616ec3d8615a0e67a495795
+clamav_0.103.7+dfsg.orig.tar.xz
+f0708e3df3a
Source: havp
Version: 0.93-2
Severity: grave
While testing havp before uploading I noticed that starting havp ends
quickly with:
| Starting HAVP Version: 0.93
| Filesystem not supporting mandatory locks!
| On Linux, you need to mount filesystem with "-o mand"
The so called "mandatory locks" have
On 2022-08-02 20:18:32 [+0200], Jérémy Lal wrote:
> Indeed, something has changed somewhere else.
I've been looking at this because I assumed that something may be
different in the init path on mips vs everywhere else leading to a
similar kind of an error like the last time where the error strings
Package: openssl
Version: 3.0.5-1
Severity: serious
Control: forward -1 https://github.com/openssl/openssl/issues/18912
Control: affects -1 libnet-dns-sec-perl
It appears the EC code is broken for ed25519/ed448 on s390x.
Sebastian
On 2022-07-07 19:17:43 [+0300], Martin-Éric Racine wrote:
> Since the above bug report was filed, upstream has moved up to
> 0.105.0, while Debian is still at 0.103.6, so I was wondering what is
> going on?
The testing got a little bit easier since I had the same version
everywhere (old-stable/ st
control: notfound -1 1.1.1f-1ubuntu2.12
control: found -1 3.0.4-2
On 2022-07-21 12:25:51 [+0200], Alexey Brodkin wrote:
> Package: openssl
> Version: 1.1.1f-1ubuntu2.12
Please use Debian's verions, not Ubunut's.
This will only be addressed in unstable as it does not affect
stable/oldstable in any
On 2020-07-03 11:37:39 [+0200], Michael Ott wrote:
> Dear Maintainer,
>
> After update openssl gsconnect does not longer work
>
> I already create a bug report on gsconnect
> https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/886#
>
> ~# cat /var/log/syslog | grep gsconnect
> J
On 2021-10-26 12:21:20 [+0200], Vincent Lefevre wrote:
> On 2021-10-26 12:00:34 +0200, Dylan Aïssi wrote:
> > Wireplumber needs the libspa-0.2-bluetooth package to support
> > bluetooth. I guess it was missing from your system.
> > libspa-0.2-bluetooth is only a plugin, wireplumber can work without
On 2022-05-20 19:16:06 [+0200], Bernhard Schmidt wrote:
> On 19/05/22 01:35 PM, Hopea Jonne wrote:
>
> > Uninstalling libssl-dev helped, for some reason libssl-dev also ships with
> > a
> > libssl.so binary which may or may not be of same version as other ones.
>
> I don't think this is the rea
On 2022-06-24 13:07:59 [+0200], Sébastien Noel wrote:
> Hi,
Hi,
> I had a similar crash with the same error message with openvpn.
> Downgrading libssl3 to version 3.0.3-8 did fix the issue.
>
> It seems to be related to this upstream bug:
> https://github.com/openssl/openssl/issues/18625
My plan
On 2022-06-20 19:10:27 [+0200], To Arthur Marsh wrote:
> I have here
>telnet-ssl 0.17.41+0.2-3.3+b1
>telnetd-ssl 0.17.41+0.2-3.3+b1
>libssl3 3.0.3-8
>openssl 3.0.3-8
adding
ckermit305~alpha07-1+b1
and then:
| ~$ kermit
| C-Kermit 9.0.305 OPEN SOURCE: Alpha.07,
On 2022-06-16 11:33:13 [+0930], Arthur Marsh wrote:
>* What led up to the situation?
>
> I also found that telnet-ssl and ckermit could not connect to telnetd-ssl
> if openssl 3.0.3-8 was installed.
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
>
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
I confirmed on eller that nodejs 16.15.0+dfsg-1 builds with openssl
3.0.3-7. I was about to give-it-back but then
control: forwarded -1 https://github.com/openssl/openssl/issues/18535
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
Okay. So if you do
OPENSSL_init_cry
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
I added RAND_status() as the first instruction in Start() (src/node.cc)
before InitializeOncePerProcess(). With th
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
before I forget:
on amd64 the entry point to init is:
| #0 OPENSSL_init_crypto (opts=opts@entry=64, settings=set
On 2022-06-08 20:07:48 [+0200], Jérémy Lal wrote:
> Hi Sebastian,
Hi Jérémy,
> Any hint or idea about this ? Even wild ideas that I could try,
> before I have to remove the files from mips.
for some reason ossl_err_load_crypto_strings() is not invoked on mipsel
but is invoked on amd64. Therefore
On 2022-06-09 23:18:07 [+0930], Arthur Marsh wrote:
…
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> Upgrading openssl, libssl3 to 3.0.3-7 from 3.0.3-6 on host system prevented
> ckermit 305~alpha07-1+b1 on client syste
On 2022-06-06 21:22:41 [+0200], MERLIN Philippe wrote:
> The non-functioning of SSL in version 3 is still relevant. Another example of
> its failure is given by a screenshot in p.J. this is a KDE bug report
> regarding Kdeconnect it says in French "impossible to contact bug.kde.org SSL
> negotia
On 2022-06-08 22:13:09 [+0200], Sebastian Ramacher wrote:
> That would be much appreciated, thanks!
Did so, sorry for the delay. I aimed for Monday but…
> Cheers
Sebastian
On 2022-06-07 08:23:40 [+0200], Vincent Bernat wrote:
> Willy Tarreau already asked the team for QuicTLS packaging without an
> answer:
>
> https://alioth-lists.debian.net/pipermail/pkg-openssl-devel/2021-October/007668.html
there was an answer:
https://alioth-lists.debian.net/pipermail/pkg-o
On 5 June 2022 19:03:17 UTC, Kurt Roeckx wrote:
>The suggestion was to make an openssl.cnf that's compatible with 1.1.1,
>and so remove or comment out everything related to providers.
>
Ah okay. In that case let me so that tomorrow and close that rc bug with this
change.
>
>Kurt
>
--
Sebasti
On 2022-06-05 19:42:43 [+0200], Sebastian Ramacher wrote:
> Hi Sebastian
Hi Sebastian,
> > Otherwise I'd fear that the only other options are openssl breaking
> > libssl1.1 or renaming /etc/ssl/openssl.cnf to have a version specific
> > name. Given the high number reverse dependencies involved in
On 2022-05-31 23:47:15 [+0200], Jérémy Lal wrote:
> Le jeu. 26 mai 2022 à 09:01, Sebastian Andrzej Siewior <
> sebast...@breakpoint.cc> a écrit :
>
> Shout out... I've tried some things but it still fails.
> I think there's some bug or option activated on mipse
On 2022-05-26 13:49:13 [+0200], Jérémy Lal wrote:
> Thanks for the feedback.
np.
> Indeed, the latest nodejs version (18.x) embeds an updated openssl.cnf,
> which is exactly the one
> of the openssl debian package, without the [ssl_sect] part at the end.
>
> Why this fails only on mipsel is a mys
On 2022-05-26 18:26:57 [+0200], Sebastian Ramacher wrote:
> Hi Sebastian
Hi,
> We're now at the following blockers for openssl's migration:
…
> Bugs for the autopkgtest regressions have been filed and some are
> already fixed in unstable. So I'll add hints to ignore those
> regressions.
good.
>
change [devel] to the real version [0.xy]
dnl also change VERSION below
-AC_INIT([ClamAV], [0.103.5], [https://github.com/Cisco-Talos/clamav/issues],
[clamav], [https://www.clamav.net/])
+AC_INIT([ClamAV], [0.103.6], [https://github.com/Cisco-Talos/clamav/issues],
[clamav], [https://www.clamav.net/
[devel] to the real version [0.xy]
dnl also change VERSION below
-AC_INIT([ClamAV], [0.103.5], [https://github.com/Cisco-Talos/clamav/issues],
[clamav], [https://www.clamav.net/])
+AC_INIT([ClamAV], [0.103.6], [https://github.com/Cisco-Talos/clamav/issues],
[clamav], [https://www.clamav.ne
On 2022-05-20 13:07:55 [+0200], Jérémy Lal wrote:
> nodejs dynamically links to openssl, and since openssl >= 3,
> on mipsel, some of its tests are failing, see
> https://buildd.debian.org/status/package.php?p=nodejs
>
> The failures look like openssl was configured with no-err, e.g:
> Asserti
On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote:
> Last time so many openssl-related test failures happened,
> OPENSSL_CONF env was set to a relative path, and nodejs/openssl3
> expected an absolute path.
I don't understand why mipsel is different here. The init looks okay. I
copied the .cnf from
On 2022-05-16 17:15:29 [+0200], Julien Cristau wrote:
> Hi,
Hi,
> The failures happen in parts of the test that spin up and attempt to
> connect to a TLS1.0 or TLS1.1 server. It used to pass on 1.1.1n and (I
> think) 1.1.1o.
That is something I don't understand.
> Trying to replicate with opens
On 2022-02-27 23:37:35 [+], Luca Boccassi wrote:
> This is known and expected, this package is an engine for OpenSSL 1.x.
> The 3.x version is shipped as a separate and different project, already
> uploaded to experimental:
>
> https://tracker.debian.org/pkg/tpm2-openssl
>
> Once OpenSSL 3.x
control: forward -1 https://github.com/openssl/openssl/issues/18334
On 2022-05-17 16:01:35 [+0200], Wolfgang Walter wrote:
>
> Yes, with libssl3_3.0.3-4.noendbr_i386.deb this is fixed.
perfect, thank you for the confirmation.
I forwarded it upstream and I hope to have something for the next
uplo
On 2022-05-17 12:53:07 [+0200], Wolfgang Walter wrote:
> Systems with VIA Nehemiah cpu break after upgrading unstable. All commands
> using libssl3 fail with
…
> lscpu shows:
>
> Architecture:i686
> CPU op-mode(s): 32-bit
…
> Flags: fp
On 14 May 2022 12:46:07 UTC, John Paul Adrian Glaubitz
wrote:
...
>This is fixed by removing "-fzero-call-used-regs=used-gpr" from "cflags" in
>Configurations/20-debian.conf.
Buh. Is that new? I think that I had this change for a few releases in
experimental an ia64 built.
>After that, the bu
On 2022-05-09 00:11:22 [+0200], Sebastian Ramacher wrote:
> Control: tags -1 = confirmed
>
> Please go ahead
Thank you, done.
> Cheers
Sebastian
On 2022-04-30 15:51:00 [+0300], Vladimir Oltean wrote:
> This is my first Intent To Package. I am the upstream maintainer of the
> project, would like to be the maintainer of the Debian package as well,
> and would need a sponsor and mentor to help with review and walk me
> through the packaging pr
On 2022-05-11 17:58:22 [+0200], Uwe Kleine-König wrote:
> I just confirmed that. I built libp11 in sid + openssl3. With the
> resulting packages installed rauc just builds fine against openssl3.
>
> So I'm unsure what I should do about this bug. Close it? Reassign to
> libp11? Just wait until it r
On 2022-05-07 20:52:41 [+0200], Paul Gevers wrote:
> Hi Sebastian,
Hi Paul,
> On 07-05-2022 18:22, Sebastian Andrzej Siewior wrote:
> > Usertags: flaky
>
> Why do you conclude that? Normally we call something flaky if it has a
> reasonable amount of failures in pure testin
Package: stunnel4
Version: 3:5.63-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
The debci testsuite failed for all architectures after the recent
openssl upload
https://ci.debian.net/data/autopkgtest/testing/amd64/s/stunnel4/21436404/log.gz
Am I right to assume as per
|
On 2022-04-29 15:52:52 [+0200], Matthias Blümel wrote:
> The openssl.cnf contains an entry for openssl_conf since #12333 [1].
>
> The attached patch-file should work but I haven't tested it yet.
Thank you.
Sebastian
control: forwarded -1 https://github.com/openssl/openssl/pull/11545
On 2022-04-20 15:46:41 [-0700], Vagrant Cascadian wrote:
> The compiler flags usually contain the build path on Debian package
> builds, and openssl embeds the compiler flags used in various binaries:
…
> Unfortunately, there are
On 2022-04-27 10:15:58 [-0700], Chris Lamb wrote:
> Hey Sebastian,
Hi Chris,
> > strip-nondeterminism damages .zip files with bzipped members
>
> According to:
>
>
> https://github.com/redhotpenguin/perl-Archive-Zip/issues/26#issuecomment-529170764
>
> ... this has now been fixed. Can you co
On 2022-03-24 12:39:55 [+], Adam D. Barratt wrote:
> I've added that text to the announcement for the buster point release.
Thanks.
> If anyone has any changes, please yell ASAP.
The gnutls and perl changes are not yet built. I guess this is intended
;)
> Regards,
>
> Adam
Sebastian
On 2022-03-23 17:40:59 [+], Adam D. Barratt wrote:
> Right, let's have another go at this then:
>
> "
> OpenSSL signature algorithm check tightening
> =
>
> The OpenSSL update provided in this point release includes a
> change to ensure that the req
On 2022-03-22 21:47:52 [+0100], Kurt Roeckx wrote:
> On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote:
> > OpenSSL signature algorithm check tightening
> > =
> >
> > The OpenSSL update included in this point release includes a change to
>
On 2022-03-21 22:11:17 [+0100], Julien Cristau wrote:
> Hi,
Hi,
> Specifically, we were hoping to better understand the risk of openssl
> changes breaking existing setups. It's possible the issues with gnutls
> and libnet-ssleay-perl tests were narrowly scoped enough that that risk
> is low, but
On 2022-03-21 22:04:08 [+0100], Salvatore Bonaccorso wrote:
> Hi Sebastian,
Hi Salvatore,
> > +gnutls28 (3.6.7-4+deb10u7.1) buster; urgency=medium
>
> As not yet uploaded, can you change this to 3.6.7-4+deb10u8 instead.
Just did so.
> Regards,
> Salvatore
Sebastian
-improve-testing-against-secured-O.patch to
+pass testsuite with openssl 1.1.1e.
+
+ -- Sebastian Andrzej Siewior Mon, 21 Mar 2022 14:52:01 +0100
+
gnutls28 (3.6.7-4+deb10u7) buster; urgency=medium
* 46_handshake-reject-no_renegotiation-alert-if-handshake.patch pulled from
diff -Nru
On 2022-03-21 17:55:00 [+0200], Adrian Bunk wrote:
> > * Backport upstream fix for test failures with OpenSSL 1.1.1n.
> > (Closes: #1008055)
Thank you Adrian.
Sebastian
SECLEVEL=2 and
+requiring minimum TLSv1.2. However, smaller hashes/keys/versions are
+allowed if one enables SECLEVEL=1. Do so when testing pre v1.2 algos,
+and thus enabling testing more compatability combinations.
+
+Signed-off-by: Dimitri John Ledkov
+Signed-off-by: Sebastian Andrzej Siewior
+
On 2022-03-20 23:15:57 [+0100], Kurt Roeckx wrote:
> > https://ci.debian.net/data/autopkgtest/oldstable/amd64/g/gnutls28/20199677/log.gz
> >
> > Checking TLS 1.0 with ECDHE-ECDSA (SECP384R1)...
> > %COMPAT: Checking TLS 1.0 with ECDHE-ECDSA (SECP384R1)...
> > *** Fatal error: A TLS fatal alert has
On 2022-03-19 09:35:48 [+0100], Kooda Loutre wrote:
> Hello,
Hi,
> libssl seems to segfault again since version 1.1.1n-1 (unstable) on arm64
> (MNT Reform/i.MX 8)
>
> CPU features: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
I have here a box with the same feautes and no segfault.
Do you s
On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> Boo. Hope you're doing better.
Thanks, yes.
> > I would also do the upload for Buster, would that work? I remember
> > that
> > the packages, that broken, were already uploaded a few cycles ago.
>
> Also as 1.1.1n?
Yes.
> I assume there
On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> Apologies if the status here got confused - based on the above, I was
> assuming that in the absence of a negative response you would proceed
> with the 1.1.1n-0+deb11u1 plan. For complete clarity, please feel free
> to do so, bearing in mind
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.
There will be the release of 1.1.1n on Tuesday 15th March 2022 including
a security fix. Therefore I will:
- prepare a security release against 1.1.1k-1
On 2022-03-06 11:38:15 [+0100], Ferenc Wágner wrote:
> Sebastian Andrzej Siewior writes:
>
> > Your package is failing to build using OpenSSL 3.0 with the
> > following error:
> >
> > | make[5]: Entering directory '/<>/xmltoolingtest'
>
On 2022-03-05 16:34:29 [-0800], Anders Kaseorg wrote:
> Any progress on this fix, via either my targeted debdiff or a full update to
> ≥ 1.1.1i?
There will be an openssl security release on Tuesday 15th March 2022. I
intend to a fix to this as part of the security update.
> Anders
Sebastian
On 2022-03-05 08:46:56 [-0800], tony mancill wrote:
>
> This should be addressed by the upload of 0.9.1-3 to unstable. The
> package is building fine against experimental for me in a chroot. Once it
> transitions to testing, I'll update the fixed version and close the bug.
Didn't work for me:
control: tags -1 - moreinfo
control: fixed -1 5.17~rc6-1~exp1
On 2022-01-16 17:04:57 [+0100], Salvatore Bonaccorso wrote:
> Hi Michael,
Hi Salvatore,
> Where you by chance already able to test this?
Just some updates:
- The issue is going to be addressed by
https://lore.kernel.org/all/2022021
Control: tags -1 - moreinfo
Removing moreinfo tag since I provide more information in my previous
reply.
On 2022-02-28 00:23:22 [+0100], To 995...@bugs.debian.org wrote:
> On 2022-02-14 15:01:34 [+0100], To Sebastian Ramacher wrote:
> > On 2022-02-01 21:11:11 [+0100], Sebastian Ramacher wrote:
>
On 2022-02-28 17:22:35 [+0100], Bernhard Schmidt wrote:
> If you want to feel free to push this transition ahead, I can either live
> with temporary removal from testing or I will upload a git snapshot.
Thank you for looking into it. And no need to rush. The transistion did
not start yet. Once it
On 2022-02-14 15:01:34 [+0100], To Sebastian Ramacher wrote:
> 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
Source: tboot
Version: 1.10.2+dfsg.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:
| cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-Wformat -We
Source: tcltls
Version: 1.7.22-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:
| Tests began at Tue Feb 15 07:16:51 UTC 2022
| ciphers.test
| tlsIO.test
|
| =
Source: tpm2-pkcs11
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:
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./src/lib -Wdate-time
-D_FOR
Source: tpm2-tss-engine
Version: 1.1.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:
| gcc -DHAVE_CONFIG_H -I. -I./src -Wdate-time -D_FORTIFY_SOURCE=2 -I./
Source: transmission
Version: 3.00-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:
| make[4]: Entering directory '/<>/libtransmission'
| PASS: bitfield-test
|
Source: validns
Version: 0.8+git20160720-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:
| cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=.
Source: xir
Version: 1.4.1-5
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:
| [ 21%] Building CXX object src/xir/CMakeFiles/xir.dir/util/tool_function.cpp.o
| c
Source: xmltooling
Version: 3.2.1-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:
| make[5]: Entering directory '/<>/xmltoolingtest'
| ../build-aux/test-driver
Source: xrdp
Version: 0.9.17-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:
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DXRDP_CFG_PATH=\"/etc/xrdp\"
-
Source: yapet
Version: 2.5-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:
| make[5]: Entering directory '/<>/tests/crypt'
| FAIL: key448
| PASS: key256
| FAIL
Source: swi-prolog
Version: 8.2.4+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:
| /<>/packages/ssl/crypto4pl.c: In function ‘get_padding’:
| /<>/pac
Source: stunnel4
Version: 3:5.60+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:
| gcc -DHAVE_CONFIG_H -I. -I/usr/kerberos/include -I/usr/include
-DLIBD
Source: sscg
Version: 3.0.1-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:
| [4/26] cc -Ilibsscg.a.p -I. -I.. -fdiagnostics-color=always
-D_FILE_OFFSET_BITS=
Source: sbsigntool
Version: 0.9.4-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:
| gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextr
Source: sendmail
Version: 8.16.1-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:
| gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werro
Source: serf
Version: 1.3.9-10
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:
| buckets/ssl_buckets.c: In function 'ssl_need_client_cert':
| buckets/ssl_buckets
Source: rauc
Version: 1.6-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:
|Creating bundle in 'plain' format
|C08ACC46967F:error:12800067:DSO support routi
Source: qpid-proton
Version: 0.22.0-5.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:
| [ 11%] Building C object
proton-c/CMakeFiles/qpid-proton-core.dir/src/
Source: python-asyncssh
Version: 2.5.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:
| Test with stdout redirected to a socketpair ... ok
| test_keys (tests.
Source: python-scrapy
Version: 2.5.1-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:
|dh_auto_test -O--buildsystem=pybuild
| I: pybuild pybuild:298: cd /<>
Source: pgbouncer
Version: 1.16.1-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:
| /usr/bin/make -C ssl check
| make[3]: Entering directory '/<>/test/ssl'
| .
On 2018-08-31 15:03:38 [+0300], Yavor Doganov wrote:
> Package: petri-foo
> Version: 0.1.87-4
> Severity: serious
>
> This package is licensed under GPLv2 only but links with the OpenSSL
> library which makes it impossible for distribution as the licenses are
> incompatible. See
>
> https://www.
Source: pdns-recursor
Version: 4.6.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/usr/include/luajit-2.1 -I./ext/ya
Source: openvpn
Version: 2.5.5-1
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:
| Testing cipher CHACHA20-POLY1305... OK
| Testing cipher
Source: openrct2
Version: 0.3.5.1+ds-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:
| [ 22%] Building CXX object
CMakeFiles/libopenrct2.dir/src/openrct2/core
Source: nordugrid-arc
Version: 6.14.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:
| PASS: UsernameTokenTest
| .There is not wsu:Id attribute in soap body,
Source: openpace
Version: 1.1.0+ds-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:
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DCVCDIR=\"/etc/eac/cvc\"
Source: ocaml-cohttp
Version: 4.0.0-1
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:
| OCAMLPATH=/<>/_tmp/usr/lib/ocaml dune build -p coht
Source: net-snmp
Version: 5.9.1+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:
| transports/snmpTLSBaseDomain.c:59:22: error: static declaration of
‘E
Source: myproxy
Version: 6.2.9-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:
| make check-TESTS
| make[3]: Entering directory '/<>'
| make[4]: Entering dire
Source: moonshot-trust-router
Version: 3.5.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:
| common/tr_dh.c: In function ‘tr_dh_new’:
| common/tr_dh.c:82
Source: m2crypto
Version: 0.38.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:
| tests/test_authcookie.py ... [
Source: mit-scheme
Version: 11.2-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:
| gcc -DHAVE_CONFIG_H -DMIT_SCHEME
-DDEFAULT_LIBRARY_PATH=\"/usr/lib/x86_64-l
Source: libzorpll
Version: 7.0.4.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:
| checking pkg-config is at least version 0.9.0... yes
| checking for openss
Source: libsecp256k1
Version: 0.1~20210825-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:
|dh_auto_test
| make -j1 check VERBOSE=1
| make[1]: Enteri
Source: libmongocrypt
Version: 1.3.0-1
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:
| [ 14%] Building C object CMakeFiles/mongocrypt.dir
Source: libewf
Version: 20140807-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:
| gcc -DHAVE_CONFIG_H -I. -I../common -I../include -I../common -I../libcerror
201 - 300 of 1860 matches
Mail list logo
