Source: libproxy Version: 0.5.4-1 Severity: serious Justification: breaks debian-edu-config dependencies
It looks as though the new libproxy1v5 has absorbed all of the functionality of the older libproxy plugins: - libproxy1-plugin-gsettings replaced by config-gnome internal to the library - -kconfig replaced by config-kde - -networkmanager functionally replaced by a GNetworkMonitor - -webkit functionally replaced by pacrunner-duktape If that's the case, then we should have transitional packages with those names that just depend on libproxy1v5 (>= 0.5.3). This serves two purposes: - avoid breaking metapackages that explicitly depend on a plugin: debian-edu-config (now fails its autopkgtest, <https://ci.debian.net/packages/d/debian-edu-config/testing/armel/43359142/>), gnome, gnome-core and phosh-full; - minimize the number of packages that are forced to be removed when upgrading from bookworm to trixie or Ubuntu jammy to noble, to help apt to find a solution The transitional packages can/should be removed after Debian 13 'trixie' and Ubuntu 24.04 'noble' are released. Running a command like this on the developer-accessible archive mirror, coccia.debian.org, is a useful way to assess the impact *before* removing packages: dak rm -R -n -b \ libproxy1-plugin-gsettings \ libproxy1-plugin-kconfig \ libproxy1-plugin-webkit \ libproxy1-plugin-networkmanager Thanks, smcv
