Bug#935166: Re-instate Debian-9's remote CUPS queue naming model

[Brian Potkin <claremont102@gmail.com>]

On Tue 20 Aug 2019 at 10:58:46 +0000, Mike Gabriel wrote:

> Package: cups
> 
> on a Debian Edu setup that got upgraded from Debian 8 to Debian 10, I
> noticed today that remote CUPS queue naming is completely unusable on
> networks where different printer queues share the same driver (name).
> 
> I propose the following change to Debian's default cups-browsed.conf:
> 
> ```
> root@disklserver:/# diff -u /etc/cups/cups-browsed.conf.orig
> /etc/cups/cups-browsed.conf
> --- /etc/cups/cups-browsed.conf.orig	2019-08-20 12:53:43.619548720 +0200
> +++ /etc/cups/cups-browsed.conf	2019-08-20 12:53:48.687534966 +0200
> @@ -384,7 +384,7 @@
> 
>  # LocalQueueNamingRemoteCUPS DNS-SD
>  # LocalQueueNamingRemoteCUPS MakeModel
> -# LocalQueueNamingRemoteCUPS RemoteName
> +LocalQueueNamingRemoteCUPS RemoteName
>  # LocalQueueNamingIPPPrinter DNS-SD
>  # LocalQueueNamingIPPPrinter MakeModel
> ```
> 
> With this change (it should hit Debian buster, finally, IMHO), the queue
> naming style of remote CUPS queues gets changed back from
> 
>   DNS-SD style: <driver-name-with-underscores>_<host>
> 
> to
> 
>   RemoteName style: <queue-as-named-on-remote-server>
> 
> Please consider enforcing this configuration default on Debian system's.
> Upstream's default is not really usable on big networks with many printers.

Thanks for your report, Mike. 

Please say what the LibreOffice print dialog shows you with

 * The default Debian installation.
 * The default Debian installation but cups-browsed is stopped.
 * LocalQueueNamingRemoteCUPS RemoteName is uncommented and cups-browsed
   is running.

On unstable would be good.

Cheers,

Brian.