[opensuse-factory] Testers needed for new cups
Hello people, I need testers for cups-2.0 series. Currently it is residing in my home because I want to be sure it won't explode in our faces [1]. Give it a spin, report issues by bugzilla if you are able to set asignee in them to me. Or report them via mail here if you are unsure how to achieve that. Also as this is not "find your bug" approach try to report only issues that you observe after you migrated and didn't have before. What I tested was direct printing over USB, discovery over avahi, printing over network and our crazy SUSE internal network printing. All seem to work okay so I need to broaden the thing before we throw it on everybody in Factory. TIA Tom [1] https://build.opensuse.org/package/show/home:scarabeus_iv:branches:Printing/...
Hello, On Feb 12 10:33 Tomáš Chvátal wrote (excerpt):
I need testers for cups-2.0 series.
Currently it is residing in my home because I want to be sure it won't explode in our faces [1].
Give it a spin, report issues by bugzilla if you are able to set asignee in them to me.
Also issues in bugzilla.opensuse.org with component "Printing" are perfectly o.k. because I get them all. FYI see https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue
[1] https://build.opensuse.org/package/show/home:scarabeus_iv:branches:Printing/...
In contrast to how the major version number change looks CUPS 2.x does not have real major incompatible changes in the actual CUPS software - in contrast to CUPS <= 1.5.4 versus CUPS >= 1.6 where various major incompatible changes happened, for details see https://bugzilla.suse.com/show_bug.cgi?id=735404 This means when you upgrade from CUPS 1.5.4 to CUPS 2.x there will be various major incompatible changes because you upgraded to CUPS >= 1.6. Basically when you upgrade from CUPS 1.5.4 to CUPS >= 1.6 you should also install all cups-filters* RPMs, i.e.: cups-filters-ghostscript cups-filters-foomatic-rip cups-filters cups-filters-cups-browsed None of them are required by the cups* RPMs because CUPS does not strictly require filtering software for example on a client machine in the network (e.g. a workstation) where the print job processing (in particular the filtering) happens on a CUPS server. In particular CUPS Browsing is dropped since CUPS >= 1.6, see "Configuring CUPS <= 1.5 in the Network" in https://en.opensuse.org/SDB:CUPS_in_a_Nutshell To get back some basic CUPS Browsing support, start the cups-browsed ("rccups-browsed start"). In contrast when you upgrade from CUPS >= 1.6 to CUPS 2.x (e.g. from CUPS 1.7.5 form the OBS "Printing" project there it is the source package "cups-SLE12") there should be no major incompatible changes in the actual CUPS software. To keep issues because of the major incompatible changes from CUPS <= 1.5.4 to CUPS >= 1.6 separated from issues because of an upgrade from CUPS >= 1.6 to CUPS 2.x I would recommend to upgrade in two separated steps: First upgrade from CUPS <= 1.5.4 to CUPS 1.7.5 form the OBS "Printing" project plus all cups-filters* RPMs and test to what extent this works for you. If CUPS 1.7.5 plus the cups-filters* RPMs works sufficiently well for you, then you may upgrade from CUPS 1.7.5 to CUPS 2.x in a separated second step. As far as I know the only noteworthy change when you upgrade from CUPS >= 1.6 to CUPS 2.x is its upstream systemd support: CUPS 2.x is the first CUPS version where CUPS upstream provides systemd support. CUPS 2.x provides several systemd unit files in particular one for socket activation. I am interested how CUPS 2.x behaves regarding starting/stopping the cupsd via its various systemd unit files (in particular regarding socket activation). I fear when you have all its systemd service and socket files enabled then https://bugzilla.opensuse.org/show_bug.cgi?id=857372 will re-appear. Up to now we have only one single "cups.service" unit file because this is a precondition that starting/stopping cupsd "just works" with YaST (in particular with the YaST printer module) and also by simple traditional "rccups start/stop", cf. https://bugzilla.opensuse.org/show_bug.cgi?id=857372#c120 I do not know if meanwhile YaST supports that multiple systemd unit files for one same service "just work", cf. https://bugzilla.opensuse.org/show_bug.cgi?id=800492#c6 and https://bugzilla.opensuse.org/show_bug.cgi?id=857372#c115 and https://bugzilla.opensuse.org/show_bug.cgi?id=857372#c124 and follow the comments/links therein. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg)
On 02/12/2015 01:13 PM, Johannes Meixner wrote:
Basically when you upgrade from CUPS 1.5.4 to CUPS >= 1.6 you should also install all cups-filters* RPMs, i.e.: cups-filters-ghostscript cups-filters-foomatic-rip cups-filters cups-filters-cups-browsed
None of them are required by the cups* RPMs because CUPS does not strictly require filtering software for example on a client machine in the network (e.g. a workstation) where the print job processing (in particular the filtering) happens on a CUPS server.
Are we making sure via dependencies that this happens without user intervention? eg. Recommends/Supplements? -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne Čt 12. února 2015 15:09:17, Duncan Mac-Vicar P. napsal(a):
On 02/12/2015 01:13 PM, Johannes Meixner wrote:
Basically when you upgrade from CUPS 1.5.4 to CUPS >= 1.6
you should also install all cups-filters* RPMs, i.e.: cups-filters-ghostscript cups-filters-foomatic-rip cups-filters cups-filters-cups-browsed
None of them are required by the cups* RPMs because CUPS does not strictly require filtering software for example on a client machine in the network (e.g. a workstation) where the print job processing (in particular the filtering) happens on a CUPS server.
Are we making sure via dependencies that this happens without user intervention?
eg. Recommends/Supplements?
Yep these are recommended packages. This is what you get by default: i | cups-filters | OpenPrinting CUPS filters, backends, and cups-browsed | package i | cups-filters-cups-browsed | OpenPrinting cups-browsed for CUPS Browsing | package | package i | cups-filters-foomatic-rip | OpenPrinting CUPS filter foomatic-rip | package i | cups-filters-ghostscript | OpenPrinting CUPS filters for Ghostscript | package Tom
Hello, On Feb 12 15:09 Duncan Mac-Vicar P. wrote (excerpt):
Are we making [... things work ...] without user intervention?
Please actually test it and provide meaningful iusse reports via our Bugzilla component "Printing" when something does not work for you. In the end CUPS and all the other printing stuff are only applications. Your system won't explode because you upgraded CUPS and other printing packages and if the new stuff does not work, just downgrade again. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Duncan Mac-Vicar P. -
Johannes Meixner -
Tomáš Chvátal