FS#50896 - [cups] client.conf is not deprecated and should not be removed from the package

Attached to Project: Arch Linux
Opened by Baptiste (zorun) - Monday, 26 September 2016, 11:10 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 26 September 2016, 14:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Upgrading to libcups-2.2.0-3 causes /etc/cups/client.conf to be copied as /etc/cups/client.conf.pacsave, because this file was removed from the package.

The package changelog at https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/cups&id=41fefa22ac5189d726e0e35e2f87ad12fa2855f3 mentions: "upstream update 2.2.0; drop deprecated client.conf".

However, I see no indication in the upstream changelog that this file has been deprecated. In fact, it's still very useful when using a remote Cups server, by setting "ServerName printserver.xxx.yy" in /etc/cups/client.conf. Unless there is an alternative method to do exactly the same thing, I believe this file should be included back into the package.

There is one mention of deprecation in the man page client.conf(5), but this only relates to OS X, not Linux: "The client.conf file is deprecated on macOS and will no longer be supported in a future version of CUPS."
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 26 September 2016, 14:37 GMT
Reason for closing:  Won't fix
Comment by Doug Newgard (Scimmia) - Monday, 26 September 2016, 13:47 GMT
It should be removed from the package if it's no longer needed by the package. That doesn't mean you can't keep using it.
Comment by Andreas Radke (AndyRTR) - Monday, 26 September 2016, 14:13 GMT
Read upstream explenation why you should run a local cups server even if you want to connect to a remote cups server sharing the printer:

http://lists.cups.org/pipermail/cups/2015-October/027226.html

I'm going to also remove the client.conf manpage to avoid confusion. Yes it is still working but not intended to be used and not recommended in any way anymore.

Loading...