Bug#1064889: libproxy: should have transitional packages for the plugins

2024-02-27 Thread Jeremy Bícha
On Tue, Feb 27, 2024 at 12:36 PM Simon McVittie wrote: > > (Sorry, I thought I had sent this earlier.) > > On Tue, 27 Feb 2024 at 08:39:05 -0500, Jeremy Bícha wrote: > > On Tue, Feb 27, 2024 at 5:33 AM Simon McVittie wrote: > > > If that's the case, then we should have transitional packages with

Bug#1064889: libproxy: should have transitional packages for the plugins

2024-02-27 Thread Simon McVittie
(Sorry, I thought I had sent this earlier.) On Tue, 27 Feb 2024 at 08:39:05 -0500, Jeremy Bícha wrote: > On Tue, Feb 27, 2024 at 5:33 AM Simon McVittie wrote: > > If that's the case, then we should have transitional packages with those > > names that just depend on libproxy1v5 (>= 0.5.3). This

Bug#1064889: libproxy: should have transitional packages for the plugins

2024-02-27 Thread Jeremy Bícha
On Tue, Feb 27, 2024 at 5:33 AM Simon McVittie wrote: > 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: What do you think about adding versioned Breaks/Replaces/Provides instead? That seemed to

Bug#1064889: libproxy: should have transitional packages for the plugins

2024-02-27 Thread Simon McVittie
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 -