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

What do you think about adding versioned Breaks/Replaces/Provides
instead? That seemed to work when Ubuntu dropped
adwaita-icon-theme-full this month.

Thank you,
Jeremy Bícha

Hello,

Bug #1064889 in libproxy reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/libproxy/-/commit/302ee018ae76b179b7a9d3ea7acbb4a682104fbb
------------------------------------------------------------------------
Add back transitional packages for the plugins

These provide smooth upgrades from Debian 12 and Ubuntu 22.04, and
should be removed after Debian 13 and Ubuntu 24.04 are released.

Closes: #1064889
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064889

We believe that the bug you reported is fixed in the latest version of
libproxy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064889@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@debian.org> (supplier of updated libproxy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 27 Feb 2024 12:53:32 +0000
Source: libproxy
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Closes: 1064889
Changes:
 libproxy (0.5.4-2) unstable; urgency=medium
 .
   * Team upload
   * d/control: Add back transitional packages for the plugins.
     These provide smooth upgrades from Debian 12 and Ubuntu 22.04, and
     should be removed after Debian 13 and Ubuntu 24.04 are released.
     (Closes: #1064889)
   * d/tests/libproxy-tools: Don't depend on gsettings-desktop-schemas here.
     The autopkgtest should prove that the minimum dependencies are
     sufficient to run without crashing in a non-GNOME environment,
     which we can ensure by making one test not depend on g-s-d.
   * d/python3-libproxy.install: Remove obsolete packaging file
   * d/p/tests-Copy-pxProxyFactory-correctly.patch,
     d/p/px_proxy_factory_copy-Add-a-new-reference-to-the-manager.patch,
     d/p/tests-Don-t-leak-the-copied-pxProxyFactory.patch:
     Add proposed patches to fix internal PxManager refcounting
   * d/libproxy1v5.lintian-overrides: Silence library-not-linked-against-libc.
     libproxy links to GLib, and to a backend library that does the real
     work, so it genuinely does not have any direct dependency on libc
     and this is non-problematic.
Checksums-Sha1:
 d40072702dd94fae77843ee5dd64a177fc77f28d 3025 libproxy_0.5.4-2.dsc
 26c3ff1b4e00231f1e2d79e67a4baa03bd2420b4 15760 libproxy_0.5.4-2.debian.tar.xz
 046e2a4156f7855d14ae8e1e0ebea87e96d8e236 18720 libproxy_0.5.4-2_source.buildinfo
Checksums-Sha256:
 826dbf4bb2a2cc6e5d460e3b07effc8da6d9cb006651781452bd85500ab5eade 3025 libproxy_0.5.4-2.dsc
 654a3cf773fa353983bd92ca98ba430f2d477ebfc4c986953f807a485654e312 15760 libproxy_0.5.4-2.debian.tar.xz
 5119d03c0ff38cc37cebed1f2a376c1514451aaa86521728b0327f4ac5d82e0f 18720 libproxy_0.5.4-2_source.buildinfo
Files:
 4e65bff8a0d40f01c60f20b60d42097e 3025 libs optional libproxy_0.5.4-2.dsc
 422fc2f535bb4c9a9c7e5ffafbb48902 15760 libs optional libproxy_0.5.4-2.debian.tar.xz
 754e5670de250c225064668791cc651e 18720 libs optional libproxy_0.5.4-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmXd8J4ACgkQ4FrhR4+B
TE+tYg/9GphQTd0FBtVjotv0FRTyLI0hExZbBKIQg8JKYlQDT1DgF7i6uZxNwdvM
x2uPD+4KslMUcZtwvh9y3JSpIUAKeifEoTa6i9XRaJ+SvuOV9haeOCXe2DKQS/tK
h/0ffl9wglb8JyElz6RLQ23IHBbmN51szjZrfQJoRm/wiEHGRC3HONFOMFwuelS7
adGdr2SGPGwc+jzRTSWMiGu5hHO67w0S2a3e6zWzsbD40HUEDbFMCgH3GtVAwu5R
Zi8u1JvetLNudt+s/zeKL9+SI6tqBa0gKE4MsXDmndnBD5aVhV1eTWU/GokgFurv
2XQvkxYKBua2Hkt89SuxV6xXjq4toGTCwcJrXC/q8evsu40e2HwJxyrT1RXJEazS
DTaP7VKSo4JXvl8W0xGv1PqHYpOeLDIhINrZluNL85zrW4zE4FWo54FiYfD+1JNo
gMoVRvmAcRln3HZ/7oYY+Q4qM1ZCWL6umFOjg/Kz3R2jcODtalT45b1btNnG3Th7
mpSuGIjVziZHWyiitjFMWykAlcydJ82+L7TbQcvLcRy+8hDJaqg8ziARwJuLfgEC
TX60Wm5AnBh79gJirCgpTmQsdeOKx/jbLKljRFW/wrmYP6I8nUbnF33CHwrhUTNW
d8azdS8++DeEy1HCCZMjesqtztJwEfmOOn7siRPQot8btCiSauo=
=9dxh
-----END PGP SIGNATURE-----

(Sorry, I thought I had sent this earlier.)
able to find a solution that its heuristics see as acceptable. In my
experience, having real transitional packages has always worked, so it's
a more robust route.

The upgrade to Debian 13 and Ubuntu 24.04 is going to include a lot of
Conflicts/Replaces as a result of the 64-bit time_t transition, so I think
anything we can do to reduce the number of packages being removed in the
upgrade path is likely to be helpful.

    smcv

Yes, your fix is fine for me especially since you've already uploaded.
I wonder if the addition of versioned Provides is making upgrades like
this smoother than they were before.

Thank you,
Jeremy Bícha