On 10/17/24 21:46, John Scott wrote:
I have a question as a random passerby.
Thorsten Alteholz wrote:
libcupsfilters2-common is part of the new CUPSv3 family of packages, but this
is far from being ready to use.
Nowadays nobody should use libcupsfilters2 at all.
If libcupsfilters2 is not ready for end user systems and is only to play with
right now, wouldn't it be better to keep it in experimental? Having it migrate
to testing and hence be slated for the next stable release sends the message
that applications can use it and it will be supported for the release
lifecycle. It's not very helpful to have this package in the next stable
release if people aren't actually supposed to use it.
A preliminary search suggests that, with the new GTK 4 upload, there probably
won't be any reverse build dependencies on this package besides
cpdb-backend-cups, so maybe the FTP masters would be willing to remove this
package from testing and unstable after an experimental upload is made? If that
isn't possible, a crude hack that gcc-snapshot and like packages use is to keep
a high-severity bug report intentionally open to prevent migration to testing.
The error message says that libcupsfilter2 conflicts with cups-filters < 2.0.
The solution is to update the cups-filters which comes with Debian to the
current 2.x upstream version. then everything will work. cups-filters,
libcupsfilters, libppd, and cups-browsed 2.x, they all work without problems
with CUPS 2.x. They are used in Ubuntu and Fedora already for more than a year.
Till
