Bug#1106516: [Pkg-openssl-devel] Bug#1106516: Bug#1106516: libssl3t64: illegal instruction in ppc64el

On May 25, 2025 5:23:58 PM GMT+02:00, Sebastian Andrzej Siewior wrote: >On 2025-05-25 15:17:24 [+0200], Kurt Roeckx wrote: >> I think this has been fixed upstream in >> https://github.com/openssl/openssl/pull/27429 >> >> There has not been an upstream release

Bug#1106516: [Pkg-openssl-devel] Bug#1106516: libssl3t64: illegal instruction in ppc64el

I think this has been fixed upstream in https://github.com/openssl/openssl/pull/27429 There has not been an upstream release since the fix. Kurt

Bug#1104425: softhsm2: tries to load rdrand engine

On May 3, 2025 10:17:32 AM GMT+02:00, Chris >softhsm2, as you point out, trys to load RDRAND. However as you >point out, openssl has disabled the RDRAND engine. > >Given there is no visible problem caused by this, could you please >explain why you consider this to be serious? I've been told

Bug#1104425: softhsm2: tries to load rdrand engine

Source: softhsm2 Version: 2.6.1-2.2 Severity: serious I've been told that it ties to load rdrand: But we don't have the rdrand engine in Debian. Kurt

Bug#1063664: closed by Matthias Klose (no feedback, closing this issue)

On Sun, Apr 27, 2025 at 05:39:10PM +0200, Helmut Grohne wrote: > Hi Kurt, > > This is more subtle in two regards. For one thing, I implied that the > problem would be fully architecture-generic. It is not. For > gnat-13-aarch64-linux-gnu, no problem exists, because there is no > gnat-12-aarch64-li

Bug#1063664: closed by Matthias Klose (no feedback, closing this issue)

On Fri, Apr 11, 2025 at 09:59:01PM +0200, Helmut Grohne wrote: > Control: reopen -1 > > Hi Matthias, > > On Thu, Nov 14, 2024 at 11:21:01AM +, Debian Bug Tracking System wrote: > > no feedback, closing this issue. > > I can still reproduce it in quite some variety. > > gnat-13- as built fro

Bug#994510: libunwind8 abuses setcontext() causing SIGSEGV on i386 with glibc >= 2.32

tags 994510 - sid trixie experimental tags 994510 + bullseye thanks Thinking about this some more, I don't see why the patch would fix anything. But it also shoudln't hurt. Without the patch we just store things that aren't restored by setcontext anymore. I also don't see a CI problem in rspamd i

Bug#1031060: knewstuff: FTBFS: flaky test "knewstuff-installationtest"

On Mon, Mar 31, 2025 at 02:17:53AM +0200, Santiago Vila wrote: > > Cc: to all known uploaders. I think at least Aurélien is around > and maybe he can upload a fix. So it seems a new upstream version was uploaded. Wny wasn't this patch included? Kurt

Bug#1089432: shim: Supporting rootless builds by default

On Sat, Jan 04, 2025 at 05:43:11PM +, Steve McIntyre wrote: > > I'm looking at your MR now, thanks! > > I should warn you: I'm *not* planning on doing a new upload of the > current packages soon, even so. There's a new upstream version due > soon, and I'll fold things in there. Do you have a

Bug#1091668: debian-installer: Explicitly declare requirement for root

Can someone clarify the current state of this?

Bug#1076350: Segfault with shared libuv on x86

Is the problem that it just needs to be rebuild with the proper LFS flags? It's marked as pending, but I don't see anything pending in salsa.

Bug#1084066: amdgcn-tools: Please upgrade build-dep to llvm/clang 18 or 19

On Fri, Jan 10, 2025 at 12:08:39PM +0100, Emilio Pozuelo Monfort wrote: > I don't see in the changelog for llvm 18 or 19 that the targets were > removed, so perhaps the removal was unintentional? Sylvestre, can those be > added back, so that amdgcn-tools can move to a newer llvm? This is one of > t

Bug#994510: libunwind8 abuses setcontext() causing SIGSEGV on i386 with glibc >= 2.32

tags 994510 + patch thanks Hi, I've attached a patch that does the same difference as the glibc change. An alternative is that we also create a setcontext. I can't reproduce the original issue, so I can't check if this fixed anything. Kurt diff --git a/getcontext-linux.S.old b/getcontext-lin

Bug#1092472: Uploaded libmad to Debian Multimedia team (and switching from cdbs to dh)

I thought I sent an email agreeing to it. In any case, it's fine for me.

Bug#1094576: [Pkg-openssl-devel] Bug#1094576: openssl-provider-fips: package is not FIPS compliant

We are not saying this is a validated version. I'm not sure how useful the current version is to people. I'm not sure we can actually ship a validated version. But having something based on a validated version might make it easy to rebrand the validation. Kurt

Bug#1092307: [Pkg-openssl-devel] Bug#1092307: Bug#1092307: openssl: relocation R_LARCH_PCALA_HI20 against `OPENSSL_loongarch_hwcap_P` can not be used when making a shared object

This was fixed upstream with pr #26336

Bug#1089351: ircd-irc2: Supporting rootless builds by default

On Wed, Jan 01, 2025 at 10:47:56AM +0100, Niels Thykier wrote: > > Hi > > Please see attached as a patch. > > I intend to NMU to make progress on the MBF if I do not hear from you on > this. It would help me if you either uploaded this soon or approved the NMU > (enabling me to skip the delay).

Bug#1091336: ITS: dutch

The upstream sources are available at https://www.opentaal.org/bestanden, but I think I had to combine some into a tar the last time. Kurt On December 30, 2024 11:41:06 PM GMT+01:00, Soren Stoutner wrote: >Kurt, > >On Wednesday, December 25, 2024 5:40:06 AM MST Kurt Roeckx wro

Bug#1091336: ITS: dutch

Hi, I suggest you just do it. I'll probably not have much time to look at it. Kurt

Bug#1083201: ITS: libid3tag

On Thu, Oct 03, 2024 at 06:08:17PM +0200, Andreas Tille wrote: > Hu Kurt, > > Am Thu, Oct 03, 2024 at 10:21:55AM +0200 schrieb Kurt Roeckx: > > I did see your other mail, and intended to reply to it. I might as well say > > it here. > > > > The last upstream

Bug#1083201: ITS: libid3tag

Hi, I did see your other mail, and intended to reply to it. I might as well say it here. The last upstream release was 20 years ago. I'm not sure there is a new upstream. There seem to be some forks. The one pointed to seems the most useful, I was not aware of it until a few weeks ago. They a

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: Bug#1068045: libssl3: breaks YAPET

There might be a related change that doesn't allow restarting the operation with the same context without setting things up again.

Bug#1067087: GCC frame pointers

Source: gcc-14 Severity: wishlist Please consider enabling frame pointers on 64 bit arches. See: https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html Kurt

Bug#1065424: [Pkg-openssl-devel] Bug#1065424: Can't connect to Active Directory with openssl

Hi, It's unclear to me what you're reporting as error. The connection seems to be working. The verification of the certificate seems to fail. It seems you have your own CA, but the CA is not trusted because it's not in the certificate store. Kurt

Bug#1007669: lice: please consider upgrading to 3.0 source format

You seem to have moved the config file for some reason. Are you sure you wanted to do that?

Bug#1034004: afl++: afl-clang(-fast) does not support -m32 due to missing afl-compiler-rt-32.o

This seems to be caused by a missing build-depends. If I build it locally, I do get support for 32 bit builds.

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

Hi, Is the issue that with older glibc versions, it was silently casted to a 32 bit value, but now that glibc supports 64 bit, it knows it can't represent it, and gives an error? Maybe for bookworm, we should just ignore the test error? Kurt

Bug#1026508: ca-certificates: FTBFS: TypeError: argument 'data': 'bytearray' object cannot be converted to 'PyBytes'

Hi, Are you waiting for something before uploading this fix? Kurt

Bug#1023284: libevent: FTBFS with glibc 2.36

Hi, It seems a fix for this is sitting git, but hasn't been uploaded. Is there a reason it's not been uploaded yet? Kurt

Bug#1026103: aflplusplus: FTBFS on s390x

Source: aflplusplus Version: 4.04c-2 Severity: serious Hi, Your package is failing to build on s390x: [*] Compiling afl++ for OS Linux on ARCH s390x ./test/unittests/unit_maybe_alloc [==] Running 6 test(s). [ RUN ] test_pow2 [ OK ] test_pow2 [ RUN ] test_null_allocs [

Bug#1025454: afl: Downloads software during build

Source: aflplusplus Version: 4.04c-1 Severity: serious Hi, On the buildds, we get: # -/usr/bin/make -C utils/plot_ui /usr/bin/make -C frida_mode make[3]: Entering directory '/<>/frida_mode' mkdir -p /<>/frida_mode/build/ mkdir -p /<>/frida_mode/build/frida/ wget -qO /<>/frida_mode/build/frida/fr

Bug#1025443: aflplusplus: Missing lld-14 Build-Depends

Source: aflplusplus Version: 4.04c-1 Hi, The LTO mode is not build at runtime, the log shows: [+] llvm_mode detected llvm 10+, enabling neverZero implementation and c++14 [+] llvm_mode detected llvm 11+, enabling afl-lto LTO implementation GNUmakefile.llvm:229: ld.lld not found, cannot enable LTO

Bug#1024631: gitlab: preinst: invalid number 9.1

On Tue, Nov 22, 2022 at 06:13:30PM +0100, Kurt Roeckx wrote: > In any case, the default cluster points to 14, it's just not on port 5432. That doesn't seem to be true. Commands like createdb, psql default to port 5432 if there is nothing overriding it, like PGPORT env variable. Kurt

Bug#1024631: gitlab: preinst: invalid number 9.1

On Tue, Nov 22, 2022 at 10:20:06PM +0530, Pirate Praveen wrote: > > > On Tue, Nov 22 2022 at 02:27:05 PM +01:00:00 +01:00:00, Kurt Roeckx > wrote: > > Package: gitlab > > Version: 15.4.2+ds1-1~fto11+3 > > > > On install I get: > > /var/lib/dpk

Bug#1024627: Acknowledgement (gitlab: Fails to install)

fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab

Bug#1024631: gitlab: preinst: invalid number 9.1

Package: gitlab Version: 15.4.2+ds1-1~fto11+3 On install I get: /var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1 I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them are used. 9.1 is using port 5432. Kurt

Bug#1024627: gitlab: Fails to install

Package: gitlab Version: 15.4.2+ds1-1~fto11+3 Severity: serious Setting up gitlab (15.4.2+ds1-1~fto11+3) ... Bundler could not find compatible versions for gem "omniauth-oauth2": In Gemfile: omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on omniauth-oauth2 (~> 1.4) x86_64

Bug#1021997: cargo: New upstream version

Source: cargo Version: 0.57.0-7 Severity: wishlist Hi, Would it be possible to upload a newer version of cargo? The current version is preventing me from building things. I think the 0.62 version matches the 1.61 version of rustc that's currently in testing/unstable. Kurt

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

On Sun, Sep 25, 2022 at 02:16:00AM +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote: > >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 > >> -legacy_renegotiation -tls1 &

Bug#965041: [Pkg-openssl-devel] Bug#965041: Bug#965041: libssl3: Please stop building legacy provider

On Sun, Sep 18, 2022 at 07:09:05PM +0200, Sebastian Andrzej Siewior wrote: > On 2020-07-16 08:46:43 [+0200], Kurt Roeckx wrote: > > On Thu, Jul 16, 2020 at 03:57:17AM +0100, Dimitri John Ledkov wrote: > > > > > > openssl package could ship `.include /etc/ss

Bug#805646: [Pkg-openssl-devel] Bug#805646: Bug#805646: Package using openssl functions does not find default certificates

On Tue, Sep 13, 2022 at 06:40:19PM +0200, Sebastian Andrzej Siewior wrote: > On 2022-09-13 18:30:05 [+0200], Kurt Roeckx wrote: > > > > 3) provide a symlink from /usr/lib/ssl/cert.pem to > > > >/etc/ssl/certs/ca-certificates.crt > > > > > > Kurt, I

Bug#805646: [Pkg-openssl-devel] Bug#805646: Package using openssl functions does not find default certificates

On Tue, Sep 13, 2022 at 05:23:43PM +0200, Sebastian Andrzej Siewior wrote: > On 2016-01-04 23:50:10 [+0100], Jan Dittberner wrote: > > I don't know whether this will have negative side effects but from my point > > of view it would be nice if the openssl package would do one of the > > following to

Bug#1016526: [Pkg-openssl-devel] Bug#1016526: openssl: Regression on mips64el throws error:1E08010C:DECODER

On Tue, Aug 02, 2022 at 12:50:05PM +0200, Jérémy Lal wrote: > Package: openssl > Version: 3.0.5-1 > Severity: normal > Control: affects -1 nodejs > > Hi, > > while building nodejs 18.6.0+dfsg-4 on mips64el, some SSL tests did regress, > https://buildd.debian.org/status/logs.php?pkg=nodejs&arch=mi

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

On Tue, Jul 19, 2022 at 06:11:23PM +0200, Diederik de Haas wrote: > According to that bug report it should be fixed with 5.19-rc6 and that > version > is available in experimental. Can you verify whether it also fixes your issue? With that version the error goes away.

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

This is probably https://bugzilla.kernel.org/show_bug.cgi?id=216140 Kurt

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

I tried older kernels, 5.17.3-1 didn't show it.

Bug#1015240: linux: rejecting DMA map of vmalloc memory

Package: linux-image-5.18.0-2-amd64 Version: 5.18.5-1 Hi, I'm currently seeing this during boot: [5.632167] usb 1-14: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02 [5.632171] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.655513] ---

Bug#995636: transition: openssl

On Sun, Jun 05, 2022 at 08:44:22PM +0200, Sebastian Andrzej Siewior wrote: > 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 ha

Bug#995636: transition: openssl

On Thu, May 26, 2022 at 06:26:57PM +0200, Sebastian Ramacher wrote: > > That leaves #1011051. What's your view on that bug? So my understanding is that 1.1.1 doesn't understand the new configuration file and tries to load an engine (instead of a provider). We could ship a file that's comptabile

Bug#1011243: nvidia-cuda-toolkit: Hard dependency on libssl1.1

Source: nvidia-cuda-toolkit Version: 11.4.3-2 Severity: serious Tags: sid bookworm Hi, It seems build-depends on libssl1.1 and not on libssl-dev. It also depends on libssl1.1 and doesn't transition to libssl3 on rebuild. Can you please move to using libssl3? Kurt

Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

Source: thrift Version: 0.16.0-5 Severity: serious Tags: sid bookworm Hi, It seems that thrift does not depend on libssl after being rebuild against OpenSSL 3.0, but did depend on libssl1.1. Kurt

Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

On Wed, May 11, 2022 at 07:25:45PM +0300, Andriy Grytsenko wrote: > >You can test it by installing the version from unstable. > > It is not in unstable yet, see That should have said experimental. Kurt

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

tags 996276 - bookworm-ignore experimental + bookworm sid thanks This is affecting the bookworm release. The release managers approved the upload to unstable and marked it as serious/release critical. You can test it by installing the version from unstable.

Bug#692917: printer-driver-escpr: color error on armel

On Sat, Apr 02, 2022 at 11:19:26AM +0200, Thorsten Alteholz wrote: > Hi Kurt and Patrik, > > thanks a lot for your reports. Can you please check whether the problem > still exists after a few new upstream versions? Both the printer and the armel server have been replaced in the mean time. Kurt

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

On Tue, Mar 22, 2022 at 10:13:25PM +0100, Sebastian Andrzej Siewior wrote: > 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 algorith

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

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 > ensure that the requested signature algorithm is supported by

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > Is the note below accurate? Yes. Kurt

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

On Tue, Mar 22, 2022 at 07:37:00PM +, Adam D. Barratt wrote: > On Mon, 2022-03-21 at 00:12 +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit > >cc7c6eb8135b ("Check that the default signature type is allowed") > > > > Before the commit in question it connects as:

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

On Mon, Mar 21, 2022 at 12:12:11AM +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit >cc7c6eb8135b ("Check that the default signature type is allowed") So that's: commit cc7c6eb8135be665d0acc176a5963e1eaf52e4e2 Author: Kurt Roeckx Date:

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

On Sun, Mar 20, 2022 at 10:00:15PM +0100, Paul Gevers wrote: > Dear Sebastian, Kurt, > > On 19-03-2022 12:33, Adam D Barratt wrote: > > Upload details > > == > > > > Package: openssl > > Version: 1.1.1n-0+deb10u1 > > > > Explanation: new upstream release > > We're seeing a regressio

Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote: > 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 br

Bug#1002576: dch doesn't read email settings from config file

Package: devscripts Version: 2.21.7 Running dch will give me: dch warning: neither DEBEMAIL nor EMAIL environment variable is set dch warning: building email address from username and mailname dch: Did you see those 2 warnings? Press RETURN to continue... The manual says I can put it in the ~/.d

Bug#999606: Acknowledgement (fetchmail: configuration requires TLS for SSH authentication)

It seems that 6.4.23 actually changed the message to: configuration requires TLS, but STARTTLS is not permitted because of authenticated state (PREAUTH). Aborting connection. If your plugin is secure, you can defeat STARTTLS with --sslproto '' (see manual). See: https://gitlab.com/fetchmail/fe

Bug#999606: fetchmail: configuration requires TLS for SSH authentication

Package: fetchmail Version: 6.4.22-1 Severity: serious Hi, With version 6.4.22-1 and 6.4.23-1 I get the following error: configuration requires TLS, but STARTTLS is not permitted because of authenticated state (PREAUTH). Aborting connection. Server permitting, try --ssl instead (see manual).

Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it does not conta

On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote: > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > > Hi, > > > > I think the following change might be the relevant one: > > > > --- a/update-ca-certificates > > +++ b/update-ca-certificates > > @@ -164,8 +

Bug#996692: Cargo: New upstream release

Source: cargo Version: 0.47.0-3 Severity: wishlist Hi, Can you package a newer version of cargo? The current version seems to be too old for some things. Kurt

Bug#996425: hitch: FTBFS with OpenSSL 3.0

Source: hitch Version: 1.7.1-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: hitch.c: In function init_dh: hitch.c:318:2: error: PEM_read_bio_DHparams is d

Bug#996424: haskell-blogliterately: FTBFS with OpenSSL 3.0

Source: haskell-blogliterately Version: 0.8.7-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: [12 of 12] Compiling Text.BlogLiterately ( src/Text/BlogLiter

Bug#996423: haproxy: FTBFS with OpenSSL 3.0

Source: haproxy Version: 2.2.17-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, 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:2178:

Bug#996422: golang-github-mendersoftware-openssl: FTBFS with OpenSSL 3.0

Source: golang-github-mendersoftware-openssl Version: 1.1.0-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: github.com/mendersoftware/openssl # github.com/

Bug#996421: globus-proxy-utils: FTBFS with OpenSSL 3.0

Source: globus-proxy-utils Version: 7.2-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: make[4]: Entering directory '/<>/test' FAIL: grid-proxy-utils-test.

Bug#996420: globus-gssapi-gsi: FTBFS with OpenSSL 3.0

Source: globus-gssapi-gsi Version: 14.17-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: FAIL: gssapi-thread-test-wrapper

Bug#996275: [Pkg-erlang-devel] Bug#996275: coturn: FTBFS with OpenSSL 3.0

On Wed, Oct 13, 2021 at 07:43:26AM +0300, Sergei Golovan wrote: > > This is a known issue, see https://github.com/erlang/otp/issues/4577 > and I'm afraid the fix will come only with the new major Erlang 25. > It's expected to be released in May 2022. As far as I know, there are 2 issues: - The ca

Bug#996288: globus-gsi-openssl-error: FTBFS with OpenSSL 3.0

Source: globus-gsi-openssl-error Version: 4.3-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: not ok 4 - Match reference output # Failed test 'Match refe

Bug#996287: git-crypt: FTBFS with OpenSSL 3.0

Source: git-crypt Version: 0.6.0-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: crypto-openssl-10.cpp: In constructor Aes_ecb_encryptor::Aes_ecb_encrypto

Bug#996286: freerdp2: FTBFS with OpenSSL 3.0

Source: freerdp2 Version: 2.3.0+dfsg1-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: /<>/winpr/libwinpr/utils/ssl.c /<>/winpr/libwinpr/utils/ssl.c: In fun

Bug#996285: freelan: FTBFS with OpenSSL 3.0

Source: freelan Version: 2.2-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: build/release/libs/cryptoplus/include/cryptoplus/bio/../cipher/../error/error.

Bug#996275: coturn: FTBFS with OpenSSL 3.0

Source: erlang Version: 24.0.6+dfsg-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: pkey.c:76:14: error: implicit declaration of function FIPS_mode [-Werr

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

Source: foxeye_0.12.1-3 Version: 0.12.1-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: openssl.c:450:5: warning: implicit declaration of function FIPS_mod

Bug#996274: erlang-p1-tls: FTBFS with OpenSSL 3.0

Source: erlang-p1-tls Version: 1.1.13-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: EUnit module 'fast

Bug#996273: dovecot: FTBFS with OpenSSL 3.0

Source: dovecot Version: 2.3.16+dfsg1-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: test_get_info_pw_encrypted ..

Bug#996272: crda: FTBFS with OpenSSL 3.0

Source: crda Version: 4.14+git20191112.9856751-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: reglib.c: In function reglib_verify_db_signature: reglib.c:1

Bug#995660: clickhouse: FTBFS with OpenSSL 3.0

Source: clickhouse Version: 18.16.1+ds-7.2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: 11: + openssl dhparam -out /tmp/clickhouse.test..wbgfY/etc/dhparam

Bug#995659: coturn: FTBFS with OpenSSL 3.0

Source: coturn Version: 4.5.2-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: src/client/ns_turn_msg.c: In function stun_produce_integrity_key_str: src/cli

Bug#995657: clevis: FTBFS with OpenSSL 3.0

Source: clevis Version: 18-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: In file included from ../src/pins/sss/sss.c:41: ../src/pins/sss/sss.c: In functi

Bug#995644: lebiniou: Fails to upgrade: trying to overwrite '/usr/share/lebiniou/etc/schemes.json'

Package: lbeibiou Version: 3.61.2-1 Severity: serious Hi, During an upgrade, I get the following: dpkg: considering deconfiguration of lebiniou-data, which would be broken by installation of lebiniou ... dpkg: yes, will deconfigure lebiniou-data (broken by lebiniou) Preparing to unpack .../110-l

Bug#995643: cjose: FTBFS with OpenSSL 3.0

Source: cjose Version: 0.6.1+dfsg1-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: jwk.c: In function _cjose_jwk_rsa_get: jwk.c:58:5: error: RSA_get0_key i

Bug#995642: cfengine3: FTBFS with OpenSSL 3.0

Source: cfengine3 Version: 3.15.2-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: In file included from hash.c:33: ./hash.h:64:28: error: unknown type name

Bug#995641: certmonger: FTBFS with OpenSSL 3.0

Source: certmonger Version: 0.79.13-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: ../../src/util-o.c: In function util_EVP_PKEY_id: ../../src/util-o.c:33

Bug#995640: boxbackup: FTBFS with OpenSSL 3.0

Source: boxbackup Version: 0.13~~git20200326.g8e8b63c-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: NOTICE: Running test bbackupd in debug mode... ERROR

Bug#995639: botan: FTBFS with OpenSSL 3.0

Source: botan Version: 2.18.1+dfsg-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: Thread_Pool ran 100 tests all ok tls: 3DES ECDH ran 2 tests 2 FAILED Fai

Bug#995637: boinc: FTBFS with OpenSSL 3.0

Source: boinc Version: 7.16.17+dfsg-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: In file included from /usr/include/openssl/x509.h:29,

Bug#995636: transition: openssl

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, We would like to transition to OpenSSL 3.0.0. It's currently in experimental. It has an soname change, so the binary packages got renamed and binNMUs will be required. We did a rebu

Bug#995635: azure-uamqp-python: FTBFS with OpenSSL 3.0

Source: azure-uamqp-python Version: 1.4.1-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with errors like: /<>/src/vendor/azure-uamqp-c/deps/azure-c-shared-utility/adapters/x509_op

Bug#995634: autobahn-cpp: FTBFS with OpenSSL 3.0: Uses -Werror and deprecated functions

Source: autobahn-cpp Version: 17.5.1+git7cc5d37-2.1 Severity: important User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is building using -Werror and is using functions that have been deprecated in OpenSSL 3.0. The log contains errors like: In file included from /<

Bug#990369: cfengine3: FTBFS with OpenSSL 3.0

Package: cfengine3 Version: 3.15.2-3 Hi, cfengine3 fails to build with OpenSSL 3.0 beta 1 with the following error: In file included from hash.c:33: ./hash.h:64:28: error: unknown type name RSA 64 | Hash *HashNewFromKey(const RSA *rsa, HashMethod method); |^~~

Bug#990364: certmonger: FTBFS with OpenSSL 3.0

Package: certmonger Version: 0.79.13-3 Hi, Your package is failing to build with OpenSSL 3.0 beta 1. The problem is that EVP_PKEY_base_id has been renamed to EVP_PKEY_get_base_id. There is a define to rename it: /usr/include/openssl/evp.h:# define EVP_PKEY_base_id EVP_PKEY_get_base_id But your

Bug#990363: caml-crush: FTBFS with OpenSSL 3.0

Package: caml-crush Version: 1.0.10-4 Hi, Your package is failing to build against OpenSSL 3.0 beta 1. The log file show: configure:6589: checking for SSL_get_peer_certificate in -lssl configure:6614: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format

Bug#990228: [Pkg-openssl-devel] Bug#990228: Bug#990228: Bug#990228: Bug#990228: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a reg

reassign 990228 ssl-cert severity 990228 normal thanks So I think there is no bug in OpenSSL and the additional check being done in 3.0 makes sense. So I'm reassigning this to ssl-cert. Kurt

  1   2   3   4   5   6   7   8   9   10   >