Bug#1070367: linux-image-6.7.12-amd64: No WiFi

Package: src:linux X-Debbugs-Cc: yahweh19...@hailmail.net Version: 6.7.12-1 Severity: important Dear Maintainer, * What led up to the situation? Booting with the linux-image-6.7.12-amd64 kernel results in Wi-Fi not working and Wi-Fi isn't even an option under network-manager. This issue also

Bug#1070353: linux-image-6.7.12-amd64: No WiFi

Package: src:linux X-Debbugs-Cc: yahweh19...@hailmail.net Version: 6.7.12-1 Severity: important Dear Maintainer, * What led up to the situation? Booting with the linux-image-6.7.12-amd64 kernel results in Wi-Fi not working and Wi-Fi isn't even an option under network-manager. This issue also

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#1067584: linux-image-6.7.9-amd64: Wi-Fi Doesn't Work

Package: src:linux Version: 6.7.9-1 Severity: important Dear Maintainer, * What led up to the situation? Booting with the linux-image-6.7.9-amd64 kernel results in Wi-Fi not working and Wi-Fi isn't even an option under network-manager. This issue also manifested when I attempted to boot using

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#1063992: gitlab-cli: manual page for python-gitlab has no descriptive content due to an error

, it is picked up when building with `dpkg-buildpackage`. Another tool is needed, e.g. sbuild or git-buildpackage. Cheers, Kurt

Bug#1066974: freecad: package got copletely removed from Debian testing

better suggestions or reservations about this approach. Thanks, 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#1060837: update-auctex-elisp --daemon creates INITFILE in /

Package: auctex Version: 13.2-1 Invoking /usr/sbin/update-auctex-elisp --daemon creates and leaves behind INITFILE in /, from if [ -n "${DAEMON_MODE}" -a "${DAEMON_MODE}" = 'true' ]; then export _UPDATE_AUCTEX_ELISP_DAEMON_MODE=${DAEMON_MODE} cd / && nohup ${0}

Bug#1016430: netgen: New upstream version 6.2.2007 available / why is the version overriden with +really?

that corresponds to x86's _mm_pause() behavior. So, since you've gotten it working, there is indeed no reason to hold off on closing this bug and moving forward. Thanks, 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#1049866: kernelshark: segfaults with certain trace.dat files

=9f2097c9669fb7d5f72351343f34fb86649d1365 Please, consider updating kernelshark to v2.2.1. The diff between v2.2.0..v2.2.1 are only two bugfixes. And one of them fixes the observed segmentation fault. Furthermore, please get the bugfix also into Debian stable. Example: |kurt@kurt tmp % kernelshark |loading plugin "sched_e

Bug#1042889: Debian PR #1042889

Ian/Dirk, Have you seen ? This points to a branch of VM at which apparently at some point in time passed native compilation (I never got a chance to try to far). I can try to follow

Bug#1035296: kicad: Program crashes

Hello After installing "libngspice0 (40+ds-1)" from experimental repository the problem was not recur. Thank you for your interest. Best regards.Serkan

Bug#1030626: Unable to print PDF file with Evince on Gnome on Debian 12.

Dear Maintainer,Unfortunately the problem persists.I reinstalled the system with the iso dated 2023-04-05. All updates have been made as of now. yours sincerely

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#1030060: gforth info manual is not installed

Package: gforth Version: 0.7.3+dfsg-9+b3 The info manual for gforth is not installed. The emacs lisp support is, so the info manual should be also. -- T. Kurt Bond, tkurtb...@gmail.com, https://tkurtbond.github.io

Bug#991788: xfce4-settings: black screen after suspend when laptop lid is closed and re-opened

This bug also causes the desktop to be accessible for a split second before the lock screen kicks in when resuming from suspend, c.f https://askubuntu.com/questions/1383379/xubuntu-desktop-visible-after-suspend-before-lock-screen/ I know disabling upower-glib support was frowned upon in the past

Bug#1021530: wireplumber: No sound after upgrade to 0.4.12-1

This is still an issue with the 0.4.13-1 upgrade. I'm downgrading once again to 0.4.11-5 until the issue gets resolved or a proper workaround is provided, preferrably via apt-listchanges News.

Bug#1026103: aflplusplus: FTBFS on s390x

ll the test seem to pass. Other architectures also have the "not all test cases were executed" message. I've tried to build it again on the buildds, but it failed the same way. Kurt

Bug#1025454: afl: Downloads software during build

ian should be build only from the source and not download more sources from internet. Kurt

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

LTO mode This is because there is a missing Build-Depends on lld-14. The LTO mode is the recommended mode. Kurt

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

d to 0.2.2, which depends on omniauth-oauth2 (~> 1.0) x86_64-linux Could not find gem 'omniauth-oauth2 (~> 1.7.1)', which is required by gem 'omniauth-auth0 (~> 2.0)', in any of the sources. Kurt

Bug#993089: marked as pending in freecad

Sorry for the noise, looks like we have an automation double-fire from when I merged the master branch into a PPA one and pushed it.

Bug#1021530: wireplumber: No sound after upgrade to 0.4.12-1

Uninstalling PulseAudio is a workaround, not a bug fix in my opinion. The latest wireplumber and libwireplumber-0.4-0 upgrade still results in no audio. Additionally, I failed to mention in my previous reply that I was also unable to stream video with the upgrades; e.g. YouTube. The Debian

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#1021530: wireplumber: No sound after upgrade to 0.4.12-1

Same issue on my end. Specs for the affected hardware below. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads) Locale:

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

e > > following to properly solve this issue: > > > > 1) properly load certificates from /etc/ssl/certs when > >SSL_CTX_set_default_verify_paths is called > > so I guess this works but it does not provide what it should provide, > right Kurt? > > > 2) c

Bug#1017817: Emacs 28.1+1-2 Upgrade

Using the new upgrade causes high CPU usage on my ASUS Zenbook UX303LA laptop. Downgrading all emacs packages to v28.1+1-1 resolved the issue.

Bug#1017779: emacs-common dies in postinst with "corrupted double-linked list"

I've upgraded emacs-common on both of my computers without issue, so the issue that the OP is experiencing may be unique to the emacs-lucid package, which I do not have installed on either of my computers.

Bug#1017798: emacs-common can't be installed

I've upgraded emacs-common on both of my computers without issue, so the issue that the OP is experiencing may be unique to the elpa-htmlize package, which I do not have installed on either of my computers.

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

appears to be broken on s390x](https://bugs.debian.org/1016290), > but it's not the same bug. It will be totally unrelated. That one is very specific to s390x. Kurt

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

o boot older kernels if needed. Kurt

Bug#995636: transition: openssl

libssl1.1 -> > > > libssl3 upgrade to be more of a lockstep transition than needed. > > > > I see that there was another openssl upload. Any reason a fix for this > > issue wasn't included in the upload of 3.0.3-6? > > I wasn't aware that this is someth

Bug#995636: transition: openssl

tabile with 1.1.1. That would make it a little bit harder to load some providers by default, but maybe that's something you want to do per application anyway. Kurt

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#1010128: Acknowledgement (linux-image-5.17.0-1-amd64: DKMS Module Rebuild for Broadcom Wireless Chip BCM4352 Fails to Build)

Consider closing this bug report. The broadcom-sta-dkms 6.30.223.271-19 upgrade resolved the issue. On Sun, Apr 24, 2022, at 19:03, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1010128: >

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#1010128: linux-image-5.17.0-1-amd64: DKMS Module Rebuild for Broadcom Wireless Chip BCM4352 Fails to Build

Package: src:linux Version: 5.17.3-1 Severity: important Dear Maintainer, I received the following errors when linux-image-5.17.0-1-amd64 was installed. Error also occurred with the linux-headers-5.17.0-1-amd64 package. Result is I have no wireless connectivity when booting with kernel version

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

ll clients and server applications making use of the library are. Some applications might have a way to set the cipher in their own configuration file, others might need to change the defaults in /etc/ssl/openssl.cfg Kurt

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

curity level, or might > specifying -sigalgs work on its own in some scenarios? So to clarify things. The problem is that SHA1 was allowed as signature algorithm while the security level should not have allowed it. If the peer does not support SHA256, the security level needs to be lowered so that SHA1 is allowed again. Kurt

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: Thu

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 > > > >

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

t; > > that > > > the packages, that broken, were already uploaded a few cycles ago. > > > > Also as 1.1.1n? > > Yes. > > > I assume there haven't been any regressions reported with l/m/n in the > > meantime. I'm not aware of any regressions the past year. Kurt

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

it in the ~/.devscripts file, but that doesn't have any effect. strace says it's being read. Putting it in an environment variable does make the warning go away. Kurt

Bug#733094: uvcdynctrl still filling the disk

gt; > > A quarta, 8/12/2021, 04:12, Kurt Meyer escreveu: >> __ >> "Guvcview doesn't depend upon uvcdynctrl it just recommends it." Okay, but >> unless you disable "recommends", uvcdynctrl gets installed. Based on a >> little bit of research

Bug#733094: uvcdynctrl still filling the disk

"Guvcview doesn't depend upon uvcdynctrl it just recommends it." Okay, but unless you disable "recommends", uvcdynctrl gets installed. Based on a little bit of research I performed, it is not recommended to disable "recommends" because recommended packages are usually needed for a more useful

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:

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

. This worked until version 6.4.21-1. Kurt

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

t; > > It triggers this stderr output during openssl rehash (l. 184): > > > > rehash: warning: skipping ca-certificates.crt,it does not contain > > exactly one certificate or CRL > > > Ah, that makes sense. Annoying... > > Kurt/Sebastian, do you think there

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

errors in warnings and should allow building against and using OpenSSL 3.0. The functions are still available but marked for removal in some future version. Kurt

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

returned 1 exit status `x86_64-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1 Kurt

Bug#996423: haproxy: FTBFS with OpenSSL 3.0

:5: error: missing binary operator before token "1" 2178 | #if SSL_OP_NO_TLSv1_3 | ^~~~~ Kurt

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

e 2 make: *** [debian/rules:4: binary] Error 25 For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

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

t.pl line 38. not ok 3 - grid-proxy-info type is RFC 3820 compliant impersonation proxy # Failed test 'grid-proxy-info type is RFC 3820 compliant impersonation proxy' # at ./grid-proxy-utils-test.pl line 41. ok 4 - create_proxy -draft not ok 5 - grid-proxy-info -draft [...] Kurt

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

23. ERROR: GSS Major Status: General failure [...] Kurt

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

some point in the future. So this is something we should be able to ignore until upstream fixes it. I currently don't know when the transition will start. Kurt

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

reference output' # at ./globus-openssl-error-test.pl line 38. # Looks like you failed 1 test of 4. FAIL globus-openssl-error-test.pl (exit status: 1) Kurt

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

in this scope; did you mean EVP_cleanup? 92 | HMAC_cleanup(&(impl->ctx)); | ^~~~ | EVP_cleanup make[1]: *** [: crypto-openssl-10.o] Error 1 Kurt

Bug#996286: freerdp2: FTBFS with OpenSSL 3.0

reference to `FIPS_mode' collect2: error: ld returned 1 exit status For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#996285: freelan: FTBFS with OpenSSL 3.0

ERR_GET_FUNC(err.error_code); | ^~~~ | ERR_GET_LIB For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#996275: coturn: FTBFS with OpenSSL 3.0

at. Kurt

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

/migration_guide.html Kurt

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

uot;}, {pattern,"{ badmatch , { error , _ } }"}, {value,ok}]} output:<<"">> [done in 1.244 s] Kurt

Bug#996273: dovecot: FTBFS with OpenSSL 3.0

d) [0x55cb6b22463d] -> ./test-crypto(test_run+0x5f) [0x55cb6b2246df] -> ./test-crypto(main+0x4c) [0x55cb6b2136dc] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f5058cc9e4a] -> ./test-crypto(_start+0x2a) [0x55cb6b21381a] /bin/bash: line 1: 161575 Aborted ./$bin Kurt

Bug#996272: crda: FTBFS with OpenSSL 3.0

need to get replaced with non-deprecated versions. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995660: clickhouse: FTBFS with OpenSSL 3.0

***Failed0.06 sec The minimum size that it now allows you to generate is 512 bit, which might be good for a test suite, but is too short for real parameters. Kurt

Bug#995659: coturn: FTBFS with OpenSSL 3.0

: undefined reference to `FIPS_mode' collect2: error: ld returned 1 exit status For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995657: clevis: FTBFS with OpenSSL 3.0

s changed to not return a value; previous versions returned an int. Kurt

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

moved from lebiniou-data to lebiniou. Kurt

Bug#995643: cjose: FTBFS with OpenSSL 3.0

| return RSA_set0_key(rsa, rsa_n, rsa_e, rsa_d) == 1; | ^~ [...] The short term solution is to drop the -Werror. Longer term the functions need to get replaced with non-deprecated versions. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995642: cfengine3: FTBFS with OpenSSL 3.0

functions have been deprecated, so you'll need to replace them at some point. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995641: certmonger: FTBFS with OpenSSL 3.0

ors and warings related to OpenSSL 3.0. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995640: boxbackup: FTBFS with OpenSSL 3.0

/migration_guide.html Kurt

Bug#995639: botan: FTBFS with OpenSSL 3.0

ECDHE_PSK ran 1 tests 1 FAILED Failure 1: EVP_EncryptInit_ex failed: error:0308010C:digital envelope routines::unsupported [...] It's unclear why they would be unsupported. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995637: boinc: FTBFS with OpenSSL 3.0

in OpenSSL 3.0, so you need to change "rsa" to "const RSA *". Note that there are also various other warnings about deprecated functions. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

Bug#995636: transition: openssl

a rebuild of packages and currently have 105 packages that FTBFS with OpenSSL 3.0.0 that build with 1.1.1. I've started filing bugs for that: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-openssl-de...@lists.alioth.debian.org=ftbfs-3.0 Kurt

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

] 140 | RSA* privatekey = EVP_PKEY_get1_RSA(evp_key); | ^~~ At least some of those errors are caused by using deprecated function in combination with -Werror. I'm not sure why you get the other errors, since that's not changed between 1.1 and 3.0. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt

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

on is to remove the -Werror, which will turn it into a warning. For a longer term solution, see https://www.openssl.org/docs/man3.0/man7/migration_guide.html#Deprecated-low-level-MAC-functions Kurt

Bug#994081: libdvd-pkg: 1.4.3-1-1 Upgrade Results in 'apt-get check' Failure

Package: libdvd-pkg Version: 1.4.3-1-1 Severity: normal Dear Maintainer, * What led up to the situation? I performed an upgrade (apt upgrade) with the following manually held back packages due to bug reports: libc6, libc6:i386, libc6-dev, libxml2, libxml2:i386, and lintian. Following is a

  1   2   3   4   5   6   7   8   9   10   >