[Bug 1220520] Configure remote printer: does not disable local cups entirely
https://bugzilla.suse.com/show_bug.cgi?id=1220520 https://bugzilla.suse.com/show_bug.cgi?id=1220520#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Johannes Meixner <jsmeix@suse.com> --- In general regarding the YaST printer module: In practice the YaST printer module is no longer acually further developed since it was "converted from YCP to Ruby by YCP Killer" that happened in July 2013, see the yast2-printer.changes entry ---------------------------------------------------------- Wed Jul 31 08:37:43 UTC 2013 - yast-devel@opensuse.org - converted from YCP to Ruby by YCP Killer (https://github.com/yast/ycp-killer) - version 3.0.0 ---------------------------------------------------------- at https://build.opensuse.org/package/view_file/YaST:Head/yast2-printer/yast2-p... My last change is dated Mon Jan 19 14:51:39 UTC 2015 and my last actual development enhancements are dated before it was "converted from YCP to Ruby by YCP Killer". Since that time the YaST printer module is kept working as is as far as possible with reasonable effort by YaST team members who know about how to deal with their generated Ruby code. Since my YCP code was converted into generated Ruby code it is no longer my code and it is no longer code that I could further develop with reasonable effort. Because the YaST printer module is based on the traditional way how printing had worked with CUPS <= 1.5.4 (in particular for printing in the network) within a traditional system environment at that time (in particular before systemd - i.e. with old SysVinit), the YaST printer module has various shortcomings and bugs with nowadays CUPS within a nowadays system environment. According to https://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html I can only close it as "wontfix" because this issue is a bug but I cannot fix it in practice in foreseeable future. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com