[continued from previous message]
+and, without any further configuration, you will have its queues listed in +/etc/cups/printers.conf and displayed with 'lpstat -a'.
+
+Now for the bad news! The remote server may not be broadcasting with the +Bonjour protocol but using the CUPS/IPP browsing protocol. cups knows
+nothing whatsoever about this protocol so forget about it being able to
+use or process information from the remote print queues. But, good news; +cups-browsed can come to the rescue. Please read its documentation and
+check the setting for 'BrowseRemoteProtocols' in its configuration file, +/etc/cups/cups-browsed.conf. If it is 'CUPS dnssd' you have nothing to do.
+
+
+Advertising your local queues
+=============================
+
+Your cups install (standard or not) automatically uses only the Bonjour +protocol to advertise any print queues you choose to share. Sharing
+print queues may be done either by
+
+ * setting 'Browsing' to 'On' or 'Off' in /etc/cups/cusd.conf
+or
+ * Using the Administration section of the web interface
+
+Having done this, finer control over individual print queues can be
+achieved in /etc/cups/printers.conf with 'Shared' as 'On' or 'Off' for
+chosen printers. Alternatively, a print queue can be modified from the +Printers section of the web interface.
+
+Ok, you have chosen to share; everything is now alright? Not quite! A
+1.6.x machine listening to your Bonjour broadcasts will be capable of +processing them with the aid of cups-browsed but a 1.5.x (or older)
+machine will not be. This is because it usually does not have
+cups-browsed available to install so can only process CUPS/IPP protocol +broadcasts. But, once again, cups-browsed on your machine can help your
+cups daemon out. Please read its documentation.
+
+Socket-activation under systemd
+========================================
+
+Since 1.7.1-7, when systemd is the active init system, CUPS can be
+configured to be socket-activated; it will then only be launched on accesses to
+its sockets. The socket definition in /lib/systemd/system/cups.socket gets +configured through files in /etc/systemd/system/cups.socket.d/; see +systemd.unit(5) and the examples files in /usr/share/doc/cups-daemon/examples .
+
+CUPS opens its listening ports based on 'Port' and 'Listen' stanzas in +/etc/cups/cupsd.conf. For systemd's socket activation to working, cups.socket +needs to be configured to listen to the correct IPs and aports by dropping +configuration files in the /etc/systemd/system/cups.socket.d/ directory.
+
+When launched by socket-activation, CUPS can additionally exit itself after +being idle for some time (60 seconds by default) by setting 'IdleExitTimeout' +in /etc/cups/cupsd.conf'.
+
+Printing without using a local cups daemon +==========================================
+
+For this to be possible you need to have permission to access a remote
+server and to have at least cups-client installed. The cups and
+cups-daemon packages are not required. The documentation for cups and +client.conf(5) should be sufficient to guide you further.
+
+
+LPD support.
+============
+
+The BSD commands are separated into their own package, cups-bsd, whereas
+the cups-lpd daemon is in the cups package. The hope is to make it
+possible to have cups and some other BSD-style printing system (such as
+lpr) side-by-side for testing purposes. However, it's known that cups +conflicts with LPRng, since LPRng provides some System V printing commands
+as well; this problem will (hopefully) be dealt with in time.
+
+The cups-lpd daemon is disabled by default. To enable it install cups-bsd
+and update-inetd; then run:
+
+ dpkg-reconfigure cups-bsd
+
+and follow the prompts. You will need a compatible inetd daemon installed +(not xinetd).
+
+When using the LPD support provided by cups-bsd you need to ensure
+debconf knows that you want LPD support enabled, otherwise LPD support
+will be disabled when you upgrade cups-bsd. To check, install
+debconf-utils and execute:
+
+ debconf-get-selections | grep setuplpd
+
+The command should return:
+
+ cups-bsd cups-bsd/setuplpd boolean true
+
+
+Reporting bugs
+==============
+
+Please see /usr/share/doc/cups/HOWTO_BUGREPORT.txt.
+
+
+
+
+This document is based on the one originally written by
+
+Jeff Licquia <
licquia@debian.org> and Kenshi Muto <
kmuto@debian.org>
+
+and has been updated by Brian Potkin to reflect changes in the Debian +printing system during the intervening period.
diff -Nru cups-2.4.7/debian/libcups2t64.symbols cups-2.4.7/debian/libcups2t64.symbols
--- cups-2.4.7/debian/libcups2t64.symbols 1970-01-01 00:00:00.000000000 +0000
+++ cups-2.4.7/debian/libcups2t64.symbols 2024-02-28 20:53:15.000000000 +0000
@@ -0,0 +1,458 @@
+libcups.so.2 libcups2t64 #MINVER#
+* Build-Depends-Package: libcups2t64-dev
+# Keep these at the latest upstream release
+ (optional|regex)"^_pwg.*@Base$" 2.3~b6
+ (optional|regex)"^_cups.*@Base$" 2.3~b6
+ (optional|regex)"^_http.*@Base$" 2.3~b6
+ (optional|regex)"^_ipp.*@Base$" 2.3~b6
+ (optional|regex)"^_ppd.*@Base$" 2.3~b6
+#MISSING: 2.4.7-1#(optional=GnuTLS)_httpReadGNUTLS@Base 1.4.4-3~
+#MISSING: 2.4.7-1#(optional=GnuTLS)_httpWriteGNUTLS@Base 1.4.4-3~
+ cupsAddDest@Base 1.4.0
+ cupsAddDestMediaOptions@Base 2.3~b1
+ cupsAddIntegerOption@Base 2.2.4
+ cupsAddOption@Base 1.4.0
+ cupsAdminCreateWindowsPPD@Base 1.4.0
+ cupsAdminExportSamba@Base 1.4.0
+ cupsAdminGetServerSettings@Base 1.4.0
+ cupsAdminSetServerSettings@Base 1.4.0
+ cupsArrayAdd@Base 1.4.0
+ cupsArrayClear@Base 1.4.0
+ cupsArrayCount@Base 1.4.0
+ cup