[Privoxy-devel] (fwd) Bug#1075870: privoxy: FTBFS with MbedTLS 3.6

[Roland Rosenfeld]

Hi,

seems that privoxy currently isn't compatible with MbedTLS 3.6, see
the attached bug report.

I tried to replace mbedtls/config.h by mbedtls/build_info.h, but this
doesn't solve the issue but opens several more compile time problems.
Seems that MbedTLS 3.x is quite incompatible to 2.8.
There is a migration guide at
https://github.com/Mbed-TLS/mbedtls/blob/development/docs/3.0-migration-guide.md
but since I'm not familiar with the code, it would be hard for me to
fix the issues, maybe someone else can do this...

Greetings
Roland

----- Weitergeleitete Nachricht von Andrea Pappacoda <andrea at pappacoda.it> -----

From: Andrea Pappacoda <andrea at pappacoda.it>
Subject: Bug#1075870: privoxy: FTBFS with MbedTLS 3.6
To: Debian Bug Tracking System <submit at bugs.debian.org>
Date: Sat, 06 Jul 2024 22:28:19 +0200
Reply-To: Andrea Pappacoda <andrea at pappacoda.it>, 1075870 at bugs.debian.org

Source: privoxy
Version: 3.0.34-5
Severity: important
Tags: ftbfs
Control: block 1074248 by -1

Hi!

Hi! I'm working on transitioning Debian to MbedTLS 3.6 LTS from the old 2.28
LTS branch. Unfortunately, privoxy is failing to build with this new version.

I haven't been able to report the issue upstream, and it seems that nobody has
done so either. Nonetheless, you could try to start working on this by
replacing "#include mbedtls/config.h" with "#include mbedtls/build_info.h", and
see what breaks from there.

If you could manage to fix this and upload a new version to unstable, it'd be
great!

Bye :)


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

----- Ende weitergeleitete Nachricht -----