FS#37591 - [cups] cupsd.conf.pacnew woes.
Attached to Project:
Arch Linux
Opened by René Herman (rene) - Saturday, 02 November 2013, 00:17 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 02 November 2013, 08:43 GMT
Opened by René Herman (rene) - Saturday, 02 November 2013, 00:17 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 02 November 2013, 08:43 GMT
|
Details
Description:
Upstream seems to think it's a good laugh to have arch linux users manually intervene on each and every cups update only to find, again and again, that the new cupsd.conf triggered a .pacnew version only due to: diff -u cupsd.conf.orig cupsd.conf.pacnew --- cupsd.conf.orig 2013-10-11 18:09:02.000000000 +0200 +++ cupsd.conf.pacnew 2013-10-25 21:14:56.000000000 +0200 @@ -1,5 +1,5 @@ # -# "$Id: cupsd.conf.in 11173 2013-07-23 12:31:34Z msweet $" +# "$Id: cupsd.conf.in 11025 2013-06-07 01:00:33Z msweet $" # # Sample configuration file for the CUPS scheduler. See "man cupsd.conf" for a # complete description of this file. @@ -130,5 +130,5 @@ </Policy> # -# End of "$Id: cupsd.conf.in 11173 2013-07-23 12:31:34Z msweet $". +# End of "$Id: cupsd.conf.in 11025 2013-06-07 01:00:33Z msweet $". # I'm getting really sick of this. Would it be possible either for the arch maintainer (as speaking for more than just one enduser) to complain to upstream about this and/or to just strip these ID lines from the config? Steps to reproduce: Update cups. Growl. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 02 November 2013, 08:43 GMT
Reason for closing: Not a bug
Saturday, 02 November 2013, 08:43 GMT
Reason for closing: Not a bug
Comment by Andreas Radke (AndyRTR) -
Saturday, 02 November 2013, 08:42 GMT
Feel free to annoy Micheal Sweet the upstream (Apple) developer. I
won't do this.